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

syncSourceFeedback can spin, with network traffic, during reconfig

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 2.8.0-rc3
    • Replication
    • None
    • ALL

    Description

      During a replica set reconfig, each node independently increments and installs the new config. While this is happening, it is possible for a node to attempt to run an updatePosition command on a sync source node with a different config version than its own. Currently, the code tries again immediately until the config versions between the two nodes becomes the same and the updatePosition command finally succeeds; this can result in heavy network traffic.
      One stopgap solution to this problem is to put in a sleep between retries.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-16272 SyncSourceFeedback spams log on errors

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26494 remove unreachable else-branch in sync_source_feedback.cpp logic

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27397 Disable OplogFetcher sync source re-evaluation during initial sync

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              milkie@mongodb.com Eric Milkie
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: