-
Type: Improvement
-
Resolution: Cannot Reproduce
-
Priority: Minor - P4
-
None
-
Affects Version/s: 3.2.0-rc3
-
Component/s: Diagnostics, Replication
-
None
Spin-off from SERVER-21560
- Start with a 3-member replica set, with all members reflecting the same point in time.
- Restart one of the secondaries.
- The mongoD log will contain the following in regards to sync-source choice:
2015-11-19T11:25:06.306-0500 I REPL [ReplicationExecutor] could not find member to sync from
- No further sync source messages will be written until a write is handled by the primary.
The current message "could not find member to sync from" could be confused to be an error condition. We should instead write something like "X potential sync sources found, waiting for write activity to choose a source"
- is related to
-
SERVER-21560 On restart, sync source not set until first write
- Closed
-
SERVER-26528 Add additional logging when sync source is changed or cleared
- Closed