Skip to content

[FEATURE REQ] [Thin Client][Gateway V2] Connect timeout bifurcation — 1s for thin client proxy (port 10250) vs 45s for gateway (port 443) #48092

@jeet1995

Description

@jeet1995

Summary

Thin client proxy (Gateway V2, port 10250) is co-located and should respond to TCP SYN-ACK in <10ms. The default 45s connect timeout masks proxy outages. Bifurcate to 1s for GW V2, keep 45s for GW V1.

Implementation Status

  • Branch: AzCosmos_H2ConnectAcquireTimeout
  • Per-request CONNECT_TIMEOUT_MILLIS via reactor-netty immutable .option()
  • 3/3 iptables DROP SYN tests passed — 3 gateway stats entries in 3s budget proves 1s timeout
  • PR not yet created

Acceptance Criteria

  • PR created and merged
  • GW V2 (port 10250): 1s connect timeout
  • GW V1 (port 443): 45s connect timeout (unchanged)
  • Metadata requests to port 443 unaffected
  • Configurable via system property as fallback

GA Blocker: Yes

Metadata

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Cosmosneeds-team-attentionWorkflow: This issue needs attention from Azure service team or SDK team

Type

No type

Projects

Status

Untriaged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions