[SERVER-4662] Building large index causes primary to stepdown Created: 11/Jan/12 Updated: 30/Mar/12 Resolved: 14/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ben Wyrosdick | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Duplicate | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | Linux | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
We have had several instances where building large indexes causes the primary to become inaccessible and step-down to secondary. This has happened during a copyDatabase command and when it stepped down the copy halted and the primary went into rollback then secondary. This happened several times during the copyDatabase and also just during an ensureIndex. I backed one environment we were getting this error on back to 2.0.1 and it completed normally. That part is anecdotal but it did work in that one case. Also, I don't recall seeing this before our upgrade to 2.0.2. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 14/Jan/12 ] |
|
|
| Comment by Ben Wyrosdick [ 14/Jan/12 ] |
|
any update on this issue? |
| Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ] |
|
No - we know what the issue is and have a fix in the works. |
| Comment by Ben Wyrosdick [ 12/Jan/12 ] |
|
Could this be the issue? https://github.com/mongodb/mongo/blob/master/src/mongo/db/repl/manager.cpp#L166 It looks like it was added between 2.0.1 and 2.0.2 |
| Comment by Ben Wyrosdick [ 12/Jan/12 ] |
|
yes, it is running with auth |
| Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ] |
|
Is this with auth on? |
| Comment by Eliot Horowitz (Inactive) [ 12/Jan/12 ] |
|
Is this with auth on? |
| Comment by Bernie Hackett [ 11/Jan/12 ] |
|
|