Method handleError

src/sdam/server.ts:390–444

* Handle SDAM error * @internal

(error: AnyError, connection?: Connection)

   * @internal
   */
  handleError(error: AnyError, connection?: Connection) {
    if (!(error instanceof MongoError)) {
      return;
    }

    if (isStaleError(this, error)) {
      return;
    }

    const isNetworkNonTimeoutError =
      error instanceof MongoNetworkError && !(error instanceof MongoNetworkTimeoutError);
    const isNetworkTimeoutBeforeHandshakeError =
      error instanceof MongoNetworkError && error.beforeHandshake;
    const isAuthOrEstablishmentHandshakeError = error.hasErrorLabel(MongoErrorLabel.HandshakeError);
    const isSystemOverloadError = error.hasErrorLabel(MongoErrorLabel.SystemOverloadedError);

    // Perhaps questionable and divergent from the spec, but considering MongoParseErrors like state change errors was legacy behavior.
    if (isStateChangeError(error) || error instanceof MongoParseError) {
      const shouldClearPool = isNodeShuttingDownError(error);

      // from the SDAM spec: The driver MUST synchronize clearing the pool with updating the topology.
      // In load balanced mode: there is no monitoring, so there is no topology to update.  We simply clear the pool.
      // For other topologies: the `ResetPool` label instructs the topology to clear the server's pool in `updateServer()`.
      if (!this.loadBalanced) {
        if (shouldClearPool) {
          error.addErrorLabel(MongoErrorLabel.ResetPool);
        }
        markServerUnknown(this, error);
        queueMicrotask(() => this.requestCheck());
        return;
      }

      if (connection && shouldClearPool) {
        this.pool.clear({ serviceId: connection.serviceId });
      }
    } else if (
      isNetworkNonTimeoutError ||
      isNetworkTimeoutBeforeHandshakeError ||
      isAuthOrEstablishmentHandshakeError
    ) {
      // Do NOT clear the pool if we encounter a system overloaded error.
      if (isSystemOverloadError) {
        return;
      }
      // from the SDAM spec: The driver MUST synchronize clearing the pool with updating the topology.
      // In load balanced mode: there is no monitoring, so there is no topology to update.  We simply clear the pool.
      // For other topologies: the `ResetPool` label instructs the topology to clear the server's pool in `updateServer()`.
      if (!this.loadBalanced) {
        error.addErrorLabel(MongoErrorLabel.ResetPool);
        markServerUnknown(this, error);
      } else if (connection) {
        this.pool.clear({ serviceId: connection.serviceId });
      }
    }
  }

  /**
   * Ensure that error is properly decorated and internal state is updated before throwing