-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.0
-
Component/s: Admin
-
Fully Compatible
-
v4.4, v4.2
-
Sharding 2020-05-04, Sharding 2020-05-18
-
(copied to CRM)
ISSUE SUMMARY
When constructing a command response, mongos may need to refresh its set of signing keys if the key for the cluster time isn’t currently known. If the client disconnects before this refresh, the resulting error is not properly handled and causes mongos to crash.
USER IMPACT
mongos will crash with a message saying “operation was interrupted because a client disconnected. terminate() called.”
AFFECTED VERSIONS
This affects 4.2.6 and earlier versions of 4.2.
FIXED VERSIONS
The fix will be included in 4.4.0 and 4.2.7.
Original Summary
Unexpected Shutdown mongos version v4.2.0
Original Description
Hello,
I'm facing a problem in a PROD server. 3 Mongos nodes was unexpectedly shutdown.
This is a message in the log file when the node down.
"[conn132492] operation was interrupted because a client disconnected [conn132492] terminate() called. No exception is active 0x5620c0615da1 0x5620c0615b58 0x5620c0720386 0x5620c07203c1 0x5620bf8a29ad 0x5620bfb1c5f9 0x5620bfb1cb72 0x5620bfa41f28 0x5620bfa6540c 0x5620bfa5f80f 0x5620bfa62a8c 0x5620bfdca2f2 0x5620bfa5d22d 0x5620bfa604c3 0x5620bfa5e8f7 0x5620bfa5f76b 0x5620bfa62a8c 0x5620bfdca75b 0x5620c04bcc64 0x7f4a7735cdd5 0x7f4a77085ead"
How do I know the root cause of this issue?
Could anyone help and suggest?
- is caused by
-
SERVER-39150 markKillOnClientDisconnect
- Closed
- is duplicated by
-
SERVER-52918 Mongos router repeatedly crashes
- Closed
- is related to
-
SERVER-47037 4.2. mongos crash
- Closed
- related to
-
SERVER-82027 Repeated Restarting of Mongos Processes in Sharded Cluster
- Closed