[DRIVERS-934] Drivers should ensure mongocryptd stdout/err is redirected to /dev/null Created: 04/Mar/20  Updated: 07/Jan/22  Resolved: 07/Jan/22

Status: Closed
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Spec Change Priority: Minor - P4
Reporter: Jeffrey Yemin Assignee: Rachelle Palmer
Resolution: Done Votes: 0
Labels: matt+
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-3636 Improve reliability of mongocryptd de... Closed
is related to DRIVERS-933 Set default socket timeout for connec... Backlog
Driver Changes: Not Needed
Quarter: FY22Q3

 Description   

Add a new requirement to the Managing mongocryptd section of the client-side encryption specification for drivers to ensure that stdout/stderr of mongocryptd auto-started processes are redirected to /dev/null (or on Windows, NUL)

The lack of this can cause a deadlock, because mongocryptd flushes its log synchronously with handling of socket responses. If the owner of the stdout/err streams (in this case the driver) is not pulling data off of these streams, mongocryptd will block trying to flush the streams.



 Comments   
Comment by Jeffrey Yemin [ 18/May/20 ]

AFAIK just Java, which has already been fixed.

Comment by Matt Broadstone [ 15/May/20 ]

jeff.yemin do you remember which drivers don't? Maybe we can just close this

Comment by Jeffrey Yemin [ 04/Mar/20 ]

Note: an informal poll in #drivers-fle suggests that most drivers already do this.

Generated at Thu Feb 08 08:22:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.