[SERVER-5783] met a 'No master error' when replica set contains 1 fatal node Created: 08/May/12 Updated: 15/Aug/12 Resolved: 09/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Xiong | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux |
||
| Participants: |
| Description |
|
Steps when met the Error: 1) set up a replica set: 1 primary and 2 secondary. 2) one secondary status was changed to fatal because of some network 3) then shut down primary. 4) start node in step3, |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 09/May/12 ] |
|
If you see this again please include the information in a new issue. |
| Comment by Xiong [ 09/May/12 ] |
|
it happened two or three month ago, no log can be found now. I checked rs.conf() and rs.status() at that time. rs.conf()looks good. rs.status()shows 1 fatal and 2 secondary. |
| Comment by Scott Hernandez (Inactive) [ 08/May/12 ] |
|
Please attach the logs from the servers and rs.conf()/rs.status(). |