[SERVER-27015] db.shutdownServer doesn't find electable secondaries Created: 14/Nov/16 Updated: 21/Nov/16 Resolved: 21/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yoni Douek | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Ever since we've upgraded to 3.2.10 - when running db.shutdownServer() - we constantly get:
|
| Comments |
| Comment by Yoni Douek [ 19/Nov/16 ] | |||
|
Sounds great. Thanks! | |||
| Comment by Spencer Brody (Inactive) [ 18/Nov/16 ] | |||
|
Hi Yoni, -Spencer | |||
| Comment by Yoni Douek [ 14/Nov/16 ] | |||
|
As mentioned - they are syncd:
logs on either primary or secondary don't mention anything related to this. This reproduces every time, on all of our shard replicas. | |||
| Comment by Ramon Fernandez Marina [ 14/Nov/16 ] | |||
|
yonido, when this happens, can you please provide the output of rs.printSlaveReplicationInfo()? Can you also upload the logs for this node at the time you run db.shutdownServer()? In the mean time I'll try to reproduce on our end. Thanks, |