[SERVER-22709] Log that connection was accepted before configuring socket options Created: 17/Feb/16 Updated: 22/Nov/16 Resolved: 17/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.2 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 10 (02/19/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The MongoDB listener code first accepts an incoming connection, then configures the socket options and only then logs that the connection was accepted. Configuring the socket options involves calls to setsockopt/getsockopt, which theoretically may block and this is the suspected cause of a JS test failure. In order to help diagnose test failures better, log that a connection was accepted before making any blocking calls. |
| Comments |
| Comment by Githook User [ 17/Feb/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |