From 921912810580411060adcd74f824c8030f0a20cc Mon Sep 17 00:00:00 2001 From: Kris Zyp Date: Mon, 6 Jul 2026 14:05:30 -0600 Subject: [PATCH] docs(configuration): document replication.blobSendDrainTimeout New replication config option (HarperFast/harper#1621, HarperFast/harper-pro#529): bounds how long a worker drains in-flight blob sends before shutting down during a restart, so a rolling restart doesn't interrupt a transfer in progress. Co-Authored-By: Claude Opus 4.8 (1M context) --- reference/configuration/options.md | 1 + 1 file changed, 1 insertion(+) diff --git a/reference/configuration/options.md b/reference/configuration/options.md index 99d318e5..6f3e599a 100644 --- a/reference/configuration/options.md +++ b/reference/configuration/options.md @@ -204,6 +204,7 @@ replication: - `securePort` — Secure replication port; _Default_: `9933` (changed from `9925` in v4.5.0) - `enableRootCAs` — Verify against Node.js Mozilla CA store; _Default_: `true` - `blobTimeout` — Blob transfer timeout (ms); _Default_: `120000` +- `blobSendDrainTimeout` — Maximum time (ms) a worker waits for in-flight replication blob **sends** to finish before shutting down during a restart, so a rolling restart (e.g., a component deploy reload) doesn't interrupt a transfer in progress. Only sends that are still making progress are waited on; `0` disables draining; _Default_: `600000` - `failOver` — Failover to alternate node if peer unreachable; _Default_: `true` - `shard` — Shard ID for traffic routing; see [Sharding](../replication/sharding.md) - `mtls.certificateVerification` — Certificate revocation checking (CRL/OCSP) for replication connections; see [Certificate Verification](../security/certificate-verification.md)