-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v5.0
-
Service Arch 2021-07-12, Service Arch 2021-08-09
-
3
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.