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

[5.0] fsync_deadlock.js is not resilient to StaleConfig errors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • 147

      Force the recipient shard to refresh its routing table for the collection to ensure the transaction is not implicitly aborted when running fsync_deadlock.js in mixed version test suites (v6.0 & v5.0).

      Improvements were made to chunk migration such that refreshing the routing cache forcefully was not needed in 6.0+.

            Assignee:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Reporter:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: