[SERVER-10219] Assertion failure when creating text index (saveerrmsg) Created: 16/Jul/13 Updated: 10/Dec/14 Resolved: 10/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.4.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tom Robinson | Assignee: | J Rassi |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 8 Pro 64-bit |
||
| Issue Links: |
|
||||||||||||||||
| Operating System: | Windows | ||||||||||||||||
| Steps To Reproduce: | Using the following collection: { , ...and after creating a text index on one of the fields. The output from mongod is: Mon Jul 15 18:31:44.000 [conn21] Index: (1/3) External Sort Progress: 13554300/14065458 96% |
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When creating a text index on a fairly large collection, mongod crashes with an assertion and the index isn't created. |
| Comments |
| Comment by J Rassi [ 10/Sep/13 ] |
|
Resolving as "cannot reproduce". Please re-open if you encounter this again. |
| Comment by Tom Robinson [ 17/Jul/13 ] |
|
I had to abort the second attempt for now as it had been running for about 18 hours and was still only at 12% of stage 2. The good news is that it got further than before and so I think it was down to running out of disk space. I cleared more space the second time around. I'll try again but probably over the weekend. |
| Comment by J Rassi [ 16/Jul/13 ] |
|
Alright. Please reply with whether your second attempt was successful (and include updated disk stats), when it finishes. Could you also post the output of db.<collection>.stats() for the collection with the index in question, in addition to the db.stats() output you provided above? |
| Comment by Tom Robinson [ 16/Jul/13 ] |
|
Unfortunately I hadn't been running mongod with logging to a file enabled so can't supply the log file at the moment. But I'm re-running the ensureIndex command as I write this, to see if I can reproduce it. I'm currently running ensureIndex again so this is going to mess up the results somewhat, but my _tmp directory is currently 17.8GB and there's 38.1GB free on the drive. |
| Comment by J Rassi [ 16/Jul/13 ] |
|
Could you upload the full mongod log as an attachment to this ticket? In addition, could you answer the following disk usage questions:
|
| Comment by Tom Robinson [ 16/Jul/13 ] |
|
The command run to create the index was: > db.articles.ensureIndex( { "article.description.content.#cdata-section": "text" }) |