QuestDB JavaScript Client - v5.0.0
    Preparing search index...

    Interface QwpReconnectOptions

    Reconnect tuning shared by ingress and egress. The two sides ship different defaults, so every field below documents both; an unset field keeps its own side's default rather than the other's.

    The ingress defaults favour survival -- a producer holding buffered or journalled rows must outlast an outage rather than give up on it -- while egress bounds a query connection so a caller is not left waiting.

    interface QwpReconnectOptions {
        initialBackoffMs?: number;
        maxAttempts?: number;
        maxBackoffMs?: number;
        maxDurationMs?: number;
        maxFrameRejections?: number;
        onEvent?: (event: QwpReconnectEvent) => void;
        poisonMinEscalationWindowMs?: number;
    }
    Index

    Properties

    initialBackoffMs?: number

    Full-jitter ceiling before the first failed sweep is retried. Must not exceed 2_147_483_647ms. Ingress defaults to 100ms, egress to 50ms.

    maxAttempts?: number

    Maximum connection sweeps per outage; zero is unlimited. Ingress defaults to zero, egress to 8.

    maxBackoffMs?: number

    Full-jitter exponential-backoff ceiling. Must not exceed 2_147_483_647ms. Ingress defaults to 5s, egress to 1s.

    maxDurationMs?: number

    Total reconnect deadline; zero disables the deadline. Ingress defaults to 5 minutes, egress to 30s.

    maxFrameRejections?: number

    Consecutive retriable rejections of one ingress frame before it is treated as poison and retained for inspection. Defaults to 4. Ingress only.

    onEvent?: (event: QwpReconnectEvent) => void
    poisonMinEscalationWindowMs?: number

    Minimum time the same ingress frame must remain suspect before repeated rejections or non-orderly closes become terminal. Defaults to 5 minutes; zero escalates as soon as maxFrameRejections is reached. Ingress only.