[SERVER-11908] Failure to rollback usePowerOf2Sizes should not cause fatal error Created: 30/Nov/13 Updated: 11/Jul/16 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.6, 2.4.8 |
| Fix Version/s: | 2.4.9, 2.5.5 |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Cailin Nelson | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Issue Status as of December 30th, 2013 ISSUE SUMMARY USER IMPACT
It will not be possible to restart the member successfully until this situation is cleared, the member will be left in the FATAL state. This issue is present in all versions of MongoDB prior to and including v2.4.8. SOLUTION WORKAROUNDS PATCHES Original DescriptionIf a replica set member attempts a rollback of a period which contained
this causes a fatal error. The replica set member is thereafter left in the FATAL state. While it seems reasonable that usePowerOf2Sizes cannot be rolled back, this is probably not the best user experience. I would prefer that my replica set member continue to function, even if the disk space allocation algorithm is different than what I asked for. Instead, this op could be skipped (with a loud warning)? Full log snippet demonstrating the problem:
|
| Comments |
| Comment by Githook User [ 20/Dec/13 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Githook User [ 04/Dec/13 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |