[SERVER-21656] Improve sync source logging when waiting for write activity Created: 24/Nov/15  Updated: 12/Dec/16  Resolved: 12/Dec/16

Status: Closed
Project: Core Server
Component/s: Diagnostics, Replication
Affects Version/s: 3.2.0-rc3
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: James Wahlin Assignee: Judah Schvimer
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-21560 On restart, sync source not set until... Closed
is related to SERVER-26528 Add additional logging when sync sour... Closed
Participants:

 Description   

Spin-off from SERVER-21560

  1. Start with a 3-member replica set, with all members reflecting the same point in time.
  2. Restart one of the secondaries.
  3. 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
    

  4. 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"



 Comments   
Comment by Judah Schvimer [ 12/Dec/16 ]

Closing as "Cannot Reproduce". SERVER-26528 will improve sync source selection logging.

Comment by James Wahlin [ 12/Dec/16 ]

I tried to reproduce this on 3.2.0-rc3 as well and no longer see the error message.

Comment by Judah Schvimer [ 12/Dec/16 ]

I'm not able to reproduce this as described due to the work done in SERVER-15931. When I restart a secondary, the "could not find member to sync from" log message is not printed.

Generated at Thu Feb 08 03:58:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.