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

The exhaustiveFindOnConfig() method should retry on NetworkInterfaceExceededTimeLimit errors

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

      In HELP-48617 the ShardRegistry::_lookup() failed with a NetworkInterfaceExceededTimeLimit error. The underlying Shard::exhaustiveFindOnConfig() method retries thrice in case of a Retriable error, but did not in this case because the NetworkInterfaceExceededTimeLimit error does not belong to the Retriable Error category, (it only belongs to the ExceededTimeLimitError,NetworkTimeoutError categories). Since this is an idempotent operation, it should be retried on NetworkInterfaceExceededTimeLimit errors as well.

      Note: NetworkInterfaceExceededTimeLimit errors will be made retrievable in the future by SERVER-72055.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: