risingwavelabs/risingwave · error · SinkError

Mongodb error

Error message

Mongodb error: {0}

What it means

Sentinel variant of SinkError wrapping anyhow errors from the MongoDB sink connector. Applied to all MongoDB-specific failures (client connect, command execution, BSON issues not otherwise specialized); the inner error carries the underlying cause.

Solutions

1. Inspect the wrapped anyhow error for the underlying MongoDB driver failure (connection, write errors, authentication).
2. Verify connection URI, credentials, and write concern settings.
3. Retry transient network errors; fix permanent write/auth errors in configuration.

When it happens

Trigger: Thrown at src/connector/src/sink/mod.rs:1232 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of risingwavelabs/risingwave@6469eb736d (2026-09-11). Data as JSON: /api/errors/d3aea0a19c0ef4c3. Report an issue: GitHub.

Appendix: source

Thrown at src/connector/src/sink/mod.rs:1232

    #[error("Postgres error: {0}")]
    Postgres(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error(transparent)]
    Connector(
        #[from]
        #[backtrace]
        ConnectorError,
    ),
    #[error("Secret error: {0}")]
    Secret(
        #[from]
        #[backtrace]
        SecretError,
    ),
    #[error("Mongodb error: {0}")]
    Mongodb(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("Redshift error: {0}")]
    Redshift(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
}

#[allow(clippy::disallowed_types)]
impl From<::iceberg::Error> for SinkError {
    fn from(err: ::iceberg::Error) -> Self {
        SinkError::Iceberg(anyhow!(err))
    }

View on GitHub (pinned to 6469eb736d)