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

Add additional logging to debug csrs_upgrade test failures

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication, Sharding
    • None
    • Sharding 13 (04/22/16), Sharding 14 (05/13/16), Sharding 15 (06/03/16)
    • 0

    Description

      The csrs upgrade tests sometimes fails with an ExceededTimeLimit error because an operation on the config server timed out. This seems to happen when one of the secondaries doesn't fine a sync source for a long time (about a minute in the tests I've looked at closely), which then causes majority reads and writes to time out. This ticket is to add logging to figure out why the secondary goes so long without a sync source.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: