[SERVER-15076] remove RS_FATAL state and usage Created: 28/Aug/14 Updated: 27/Oct/15 Resolved: 12/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Switch such conditions to simply fassertNoTraceback the server. |
| Comments |
| Comment by Eric Milkie [ 12/Sep/14 ] |
|
https://github.com/mongodb/mongo/commit/f7a403b6ef67f6870adde252cf2dd794e8c1604b |
| Comment by Eric Milkie [ 29/Aug/14 ] |
|
It's a state that was used to stop replication but keep sending heartbeats to avoid a loss of quorum. Some rollback failures resulted in this state. The server will now simply shut down in those cases. |
| Comment by A. Jesse Jiryu Davis [ 29/Aug/14 ] |
|
What is the RS_FATAL state, and how is it triggered? What behavior change will we observe once this ticket is resolved? |