[SERVER-6919] forceing a server to be primary prevents secondary from taking over if the forced primary fails. Created: 03/Sep/12 Updated: 28/Sep/16 Resolved: 10/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sean Mathews | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mixed UBUNTU 12.04 SLES 11 64 bit |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Participants: | |||||||||
| Description |
|
forcing a server to be primary as described in ) and then stopping the daemon on the new master seems to prevent an election It may be advisable to update the dos on the above page to warn admins that if they preformed this process the system may not recover from a failure. |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 10/Sep/12 ] |
|
I updated the docs to explain what happens when you run replSetStepDown:1000000 and how to undo it. |
| Comment by Sean Mathews [ 08/Sep/12 ] |
|
mongodb-linux-x86_64-v2.2-2012-09-01 |
| Comment by Ian Whalen (Inactive) [ 04/Sep/12 ] |
|
Sean, 2.2.1 (which you listed in the Affects Version) isn't out yet. Can you confirm which version you're on? |