[SERVER-21534] race between setting socket non_blocking and remote host closing connection can cause invariant failure Created: 18/Nov/15  Updated: 25/Nov/15  Resolved: 19/Nov/15

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.2.0-rc4

Type: Bug Priority: Major - P3
Reporter: Adam Midvidy Assignee: Adam Midvidy
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: Platform D (12/11/15)
Participants:

 Description   

Discovered by spencer.jackson in a patch build. Currently we assume that setting the socket non_blocking always succeeds, when it can in fact fail in the aforementioned scenario.

See failure in tags.js

https://evergreen.mongodb.com/task/mongodb_mongo_master_solaris_64_bit_replicasets_WT_9f055d483c3238a785c0f508f4011dc49a770504_15_11_18_14_17_08



 Comments   
Comment by Githook User [ 19/Nov/15 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-21534 do not assume that setStreamNonBlocking will always succeed
Branch: master
https://github.com/mongodb/mongo/commit/b42f5356a233404a5d77229892ebbd37c24001a6

Generated at Thu Feb 08 03:57:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.