Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-15931

Repeated "[ReplicationExecutor] could not find member to sync from" in healthy replica set

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.8.0-rc1
    • Affects Version/s: 2.8.0-rc0
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Show
      See SERVER-14809
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      While working on SERVER-14809 I saw repeated messages like this in the logs:

      2014-11-03T16:18:24.424-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:25.424-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:26.425-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:27.425-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:28.425-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:29.425-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      2014-11-03T16:18:30.425-0500 I REPLSETS [ReplicationExecutor] could not find member to sync from
      

      These messages just add noise, but would be nice to fix them at some point.

            Assignee:
            matt.dannenberg Matt Dannenberg (Inactive)
            Reporter:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: