[SERVER-25603] clarify asio error handling Created: 15/Aug/16 Updated: 19/Nov/16 Resolved: 06/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.14 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Eric Milkie | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 2016-08-26, Platforms 2016-09-19 |
| Participants: |
| Description |
|
It's easy to get log messages like this on Windows, particularly when shutting down members of a replica set:
"Socket disconnect by peer" should not be reported as an unexpected error. |
| Comments |
| Comment by Githook User [ 06/Sep/16 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: Our logic to check if a connection is healthy involves a 1 byte peek read on a socket. Don't log |