[SERVER-15034] Invariant failure when reindexing namespace with embedded control character Created: 26/Aug/14  Updated: 06/Dec/22  Resolved: 22/May/18

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 2.6.4, 2.7.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Backlog - Storage Execution Team
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

It's possible to create a collection with an etx control character (\u0003) in its name. Attempting to reindex that collection triggers an invariant failure in 2.6.4 and 2.7.x (but not 2.4.11).

2014-08-25T20:09:59.157-0400 I          [conn1] Invariant failure collection src/mongo/db/index_builder.cpp 142
 
 mongod(_ZN5mongo15printStackTraceERSo+0x3A) [0x10080a51a]
 mongod(_ZN5mongo10logContextEPKc+0xDB) [0x1007b250b]
 mongod(_ZN5mongo15invariantFailedEPKcS1_j+0x1A2) [0x1007a03a2]
 mongod(_ZN5mongo12IndexBuilder23killMatchingIndexBuildsEPNS_10CollectionERKNS_12IndexCatalog17IndexKillCriteriaE+0x45) [0x1002e1265]
 mongod(_ZN5mongo10CmdReIndex15stopIndexBuildsEPNS_16OperationContextEPNS_8DatabaseERKNS_7BSONObjE+0x136) [0x100168916]
 mongod(_ZN5mongo10CmdReIndex3runEPNS_16OperationContextERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x2B2) [0x100167222]
 mongod(_ZN5mongo12_execCommandEPNS_16OperationContextEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3A) [0x1001fd35a]
 mongod(_ZN5mongo7Command11execCommandEPNS_16OperationContextEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0x992) [0x1001fe262]
 mongod(_ZN5mongo12_runCommandsEPNS_16OperationContextEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x4E3) [0x1001ff5c3]
 mongod(_ZN5mongo11newRunQueryEPNS_16OperationContextERNS_7MessageERNS_12QueryMessageERNS_5CurOpES3_+0x306) [0x100432f26]
 mongod(_ZN5mongo16assembleResponseEPNS_16OperationContextERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x883) [0x1002e7ee3]
 mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0xC9) [0x10000a999]
 mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x380) [0x1007c3a00]
 mongod(_ZN5boost12_GLOBAL__N_112thread_proxyEPv+0x8B) [0x100847f7b]
 libsystem_pthread.dylib(_pthread_body+0x8A) [0x7fff8f582899]
 libsystem_pthread.dylib(_pthread_struct_init+0x0) [0x7fff8f58272a]
 libsystem_pthread.dylib(thread_start+0xD) [0x7fff8f586fc9]



 Comments   
Comment by Eric Milkie [ 22/May/18 ]

The original problem described in the ticket has been fixed; collection name restrictions are covered by other tickets in Query.

Comment by Mark Benvenuto [ 05/Jan/15 ]

Most of the work for this has been done as part of the fixes for: SERVER-16072. The more comprehensive work can be considered for a future release.

Generated at Thu Feb 08 03:36:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.