[DRIVERS-1049] Specify socket/connect timeout to use for KMS requests Created: 07/Apr/20  Updated: 29/Nov/23

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

Type: Spec Change Priority: Major - P3
Reporter: Esha Bhargava Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: leads-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to CSHARP-4461 Add default socket timeouts for kms c... Backlog
Downstream Changes Summary:

Summary of necessary driver changes

  •  

Commits for syncing spec/prose tests
(and/or refer to an existing language POC if needed)

  •  

Context for other referenced/linked tickets

  •  

 Description   

Summary

Specify socket/connect timeout to use for KMS requests

Consider adding an option to configure the timeout.

Background & Motivation

When libmongocrypt enters the MONGOCRYPT_CTX_NEED_KMS state, drivers are expected to connect with TLS to a KMS service and do a socket write and read. It is not currently specified what socket/connect timeouts are expected.

Drivers do not appear to apply timeouts consistently (ranging from 10 seconds, to 5 minutes, to "no timeout"). There is a report of KMS timeouts observed under heavy load with the Java driver using the 10 second timeout.


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