-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Labels:None
-
Service Arch
We probably have some code that's vulnerable to EINTR, or performs poorly if it's encountered. In SERVER-48396 it would cause dropped connections.
EINTR is part of life in Unix and we have to be resilient. We had this idea to run a gremlin thread in torture tests that sends spurious signals to other threads just to make their syscalls deal with the EINTR result.
(out of discussion on SERVER-48396)