[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% |
| 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() |
| Comment by devhd [ 04/Jul/11 ] |
|
> 2151000000 is approximately 2^32. I mean a 32 bit signed integer maximal value |