Make moveCollection thread in resharding_skip_cloning_and_applying.js retry on NetworkInterfaceExceededTimeLimit error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Sep1-15
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This test triggers failovers on all the shards. When it runs in the sharding_auto_bootstrap (i.e. config_shard) suite, one of the shards is the config server. SERVER-108543 made commands against config.shards have maxTimeMS of 5 seconds, so the failover can now lead to a NetworkInterfaceExceededTimeLimit error like in BF-39515. The moveCollection thread here should retry the command on a NetworkInterfaceExceededTimeLimit error as well. 

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: