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

    Variable QWP_RECONNECT_EVENT_KINDConst

    QWP_RECONNECT_EVENT_KIND: {
        ALL_ENDPOINTS_UNREACHABLE: "all-endpoints-unreachable";
        AUTH_FAILED: "auth-failed";
        CONNECTED: "connected";
        DISCONNECTED: "disconnected";
        DURABLE_ACK_PERSISTENT_FAILURE: "durable-ack-persistent-failure";
        DURABLE_ACK_UNAVAILABLE: "durable-ack-unavailable";
        ENDPOINT_ATTEMPT_FAILED: "endpoint-attempt-failed";
        FAILED_OVER: "failed-over";
        PRIMARY_UNAVAILABLE: "primary-unavailable";
        RECONNECTED: "reconnected";
    } = ...

    The kinds of reconnect.onEvent notification. The first seven are the connection events the Java, Rust, Go and Python clients share (Java's SenderConnectionEvent.Kind), so a listener ported from one of them keeps its meaning. The last three report store-and-forward conditions that only this client puts on the same stream.

    Type declaration

    • ReadonlyALL_ENDPOINTS_UNREACHABLE: "all-endpoints-unreachable"

      A sweep tried every endpoint and none accepted the connection. Fired once per failed sweep, after that sweep's endpoint-attempt-failed events, with endpoint set to the last endpoint tried.

    • ReadonlyAUTH_FAILED: "auth-failed"

      The server rejected the credentials with HTTP 401 or 403. A credential applies to the whole cluster, so the sweep stops at that endpoint and no all-endpoints-unreachable follows. Browsers report it only when the sessionBootstrap request is rejected, because their WebSocket API hides the upgrade status.

    • ReadonlyCONNECTED: "connected"

      The session's first successful connection.

    • ReadonlyDISCONNECTED: "disconnected"

      The active connection was lost. Fired once per outage, before the first reconnect attempt.

    • ReadonlyDURABLE_ACK_PERSISTENT_FAILURE: "durable-ack-persistent-failure"

      An orphan exhausted its consecutive durable-ACK mismatch budget.

    • ReadonlyDURABLE_ACK_UNAVAILABLE: "durable-ack-unavailable"

      An unbounded SF loop is waiting for durable-ACK-capable endpoints.

    • ReadonlyENDPOINT_ATTEMPT_FAILED: "endpoint-attempt-failed"

      One endpoint failed: it could not be opened, or it opened and then failed before the session could use it, as when it refuses the replayed frames. Fired as each endpoint fails, before the sweep moves on. A browser auth provider that cannot produce a credential fails the attempt this way too, and like auth-failed it ends the sweep, so no all-endpoints-unreachable follows.

    • ReadonlyFAILED_OVER: "failed-over"

      A reconnect succeeded against a different endpoint than before.

    • ReadonlyPRIMARY_UNAVAILABLE: "primary-unavailable"

      Every reachable ingress endpoint is temporarily unable to be primary.

    • ReadonlyRECONNECTED: "reconnected"

      A reconnect succeeded against the endpoint that was active before.

    Settings

    Member Visibility