Do not set inherited maxTimeMSOpOnly deadline on hello command in v4.4

XMLWordPrintableJSON

    • Fully Compatible
    • v5.0
    • Service Arch 2021-07-12, Service Arch 2021-08-09
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In v5.0 we began setting the maxTimeMSOpOnly field on internal commands, but ignore it and do not set a deadline on the opCtx for the hello command to avoid interfering with the RSM. In a mixed version cluster, nodes that are on v4.4 do not ignore this field and do set a deadline on the opCtx, causing nodes on v5.0 to see a lot of RSM failures due to MaxTimeMsExpired. We should also ignore this field for the hello command in v4.4.

              Assignee:
              George Wangensteen (Inactive)
              Reporter:
              Janna Golden
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: