#tcp-retry

Whisper timestamp overwrite versus client-side retry tokens for duplicate-free metric ingestion in Carbon

Uncertainty in Carbon Retry Handling When a client retries a metric write to carbon-cache over TCP after a transport-level failure, it is unclear whether the point has already been durably stored in the Whisper file or merely queued pending acknowledgment. Whisper's design stores a single value per (metric, timestamp) pair and overwrites on replay, which nat