[SERVER-3365] Assertion failure: ensureIndex on a 2 billions collection (2^32 limit ?) Created: 04/Jul/11  Updated: 19/Mar/13  Resolved: 11/Mar/13

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 1.8.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: devhd Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, indexing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 6.0, 64 bit, Core i7, 24 GB RAM, Software RAID 1


Operating System: Linux
Participants:

 Description   

We have created a new database, a singe collection with similar but simple random documents with 10 keys and some subkeys.

2151000000 is approximately 2^32. Is it a index limit bug?

Command:

db.testcoll.ensureIndex(

{"key5.subkey2": 1}

)

Log after 4 hours:

Mon Jul 4 16:19:34 [snapshotthread] cpu: elapsed:4000 writelock: 0%
2151000000/2177356393 98%
Mon Jul 4 16:19:38 [snapshotthread] cpu: elapsed:4000 writelock: 0%
Mon Jul 4 16:19:38 [FileAllocator] allocating new datafile /root/mongodb-linux-x86_64-1.8.2/data/test_db/test_db.469, filling with zeroes...
Mon Jul 4 16:19:42 [snapshotthread] cpu: elapsed:4000 writelock: 0%
Mon Jul 4 16:19:48 [FileAllocator] done allocating datafile /root/mongodb-linux-x86_64-1.8.2/data/test_db/test_db.469, size: 2047MB, took 9.85 secs
Mon Jul 4 16:19:48 [conn1] test_db.system.indexes Assertion failure isOk() db/pdfile.h 259
0x54f0ee 0x56073d 0x789a9a 0x787bf8 0x7764e4 0x77874d 0x77a0ae 0x77b4cf 0x7595bd 0x75b23f 0x8a8fce 0x8bb630 0x7fc7adc938ba 0x7fc7ad24f02d
bin/mongod(_ZN5mongo12sayDbContextEPKc+0xae) [0x54f0ee]
bin/mongod(_ZN5mongo8assertedEPKcS1_j+0xfd) [0x56073d]
bin/mongod(_ZNK5mongo7Forward4nextERKNS_7DiskLocE+0x1ea) [0x789a9a]
bin/mongod(_ZN5mongo11BasicCursor7advanceEv+0xd8) [0x787bf8]
bin/mongod(_ZN5mongo14fastBuildIndexEPKcPNS_16NamespaceDetailsERNS_12IndexDetailsEi+0x614) [0x7764e4]
bin/mongod() [0x77874d]
bin/mongod(_ZN5mongo11DataFileMgr6insertEPKcPKvibRKNS_11BSONElementEb+0xf4e) [0x77a0ae]
bin/mongod(_ZN5mongo11DataFileMgr16insertWithObjModEPKcRNS_7BSONObjEb+0x5f) [0x77b4cf]
bin/mongod(_ZN5mongo14receivedInsertERNS_7MessageERNS_5CurOpE+0x37d) [0x7595bd]
bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE+0x192f) [0x75b23f]
bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x21e) [0x8a8fce]
bin/mongod(thread_proxy+0x80) [0x8bb630]
/lib/libpthread.so.0(+0x68ba) [0x7fc7adc938ba]
/lib/libc.so.6(clone+0x6d) [0x7fc7ad24f02d]
Mon Jul 4 16:19:49 [snapshotthread] cpu: elapsed:7273 writelock: 0%



 Comments   
Comment by Ian Whalen (Inactive) [ 11/Mar/13 ]

devhd, because of the amount of time transpired since you filed this ticket I'm resolving it as incomplete. My apologies for us not responding sooner. Please do add a comment if you're still able to recreate (especially on a 2.2.x or 2.4 release candidate) and I'll reopen this.

Comment by devhd [ 04/Jul/11 ]

After that:

> db.testcoll.totalIndexSize()
isOk()

Comment by devhd [ 04/Jul/11 ]

> 2151000000 is approximately 2^32.

I mean a 32 bit signed integer maximal value

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