[SERVER-48508] test our EINTR resilience Created: 29/May/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Billy Donahue Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Participants:

 Description   

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)

 



 Comments   
Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ]

We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:17:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.