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

Resharding occasionally restarts/retries after critical section timeout in jstest

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • Hide

      Run sharding/resharding_stepdown_during_critical_section.js repeatedly, especially in sharding and sharding_max_mirroring_opportunistic_secondary_targeting suites.

      Show
      Run sharding/resharding_stepdown_during_critical_section.js repeatedly, especially in sharding and sharding_max_mirroring_opportunistic_secondary_targeting suites.

      This is a continuation of SERVER-84709.

      In sharding/resharding_stepdown_during_critical_section.js an intentional critical section timeout triggered by the test is overriden by a resharding retry which subsequently succeeds, causing the test to fail since it expects the critical-section-timeout error.

      The cause for the spurious retry needs to be found and eliminated or debugged.

            Assignee:
            israel.hsu@mongodb.com Israel Hsu
            Reporter:
            israel.hsu@mongodb.com Israel Hsu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: