apache / apache/iotdb-client-rust
connect_timeout is applied per resolved address, not per endpoint
- Vorherrschende Sprache
- Rust
- Sterne
- 1
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
`connect_stream` applies `connect_timeout` **per resolved address**, not per endpoint, contradicting the doc comment ("TCP connect timeout per endpoint attempt"). A hostname resolving to two addresses multiplies every bound: measured 2.0011s for two blackhole addresses at a 1s timeout.
Fix: give `connect_stream` a single total deadline across all resolved addresses, so the timeout bounds the endpoint attempt as documented.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start by reading connect_stream and its connect_timeout doc comment, then reproduce the two-address case described in the issue to confirm the current per-address timing. Done means one total deadline is shared across all resolved addresses so the endpoint attempt stays within the documented timeout.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- rust
- Bereich
- databases
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 68/100