-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Wire Protocol
-
None
“The responseTo (1113396) in the response does not match the requestId (1113399) in the request”
Occasionally seeing this returned from the java mongo client ‘org.mongodb:mongodb-driver-async:3.12.3’ – mainly during read requests.
We have a sharded cluster with 20+ shards and 2 router nodes running mongodb community edition 4.4 on ARM64 machines in AWS.
Anyone know more about this error, why it happens, how to resolve it – is this a bug?