-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Networking
-
None
-
Fully Compatible
-
ALL
-
Platforms 2016-08-26, Platforms 2016-09-19
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It's easy to get log messages like this on Windows, particularly when shutting down members of a replica set:
[ReplicationExecutor] unexpected error when checking if a stream was open: An existing connection was forcibly closed by the remote host., the only error we expected was EOF
"Socket disconnect by peer" should not be reported as an unexpected error.
Many replica set tests on Windows report this in their logs.