influxdata/influxdb · error · Error

Current node mode does not use the processing engine

Error message

Current node mode does not use the processing engine

What it means

Error variant `NoProcessingEngine` in influxdb3_server/src/http.rs (ErrorWrite enum). It means the HTTP request required the Processing Engine (e.g. a trigger or plugin-bearing write path), but the node was started in a mode where the Processing Engine is not enabled, so the server cannot fulfill it.

Solutions

1. Start the server in a node mode that enables the Processing Engine (e.g. pass the appropriate --node-mode / processing-engine flags at startup)
2. Route the request to a node that runs the Processing Engine instead of this one
3. Remove or disable the plugin/trigger-dependent calls from the client if the engine is intentionally disabled

Example fix

// before: server started without processing engine
influxdb3 serve --node-id=host1
// after: enable processing engine mode
influxdb3 serve --node-id=host1 --node-mode=all

// Check node capabilities before sending engine-dependent requests
const supportsPE = await fetch(`${host}/health`).then(r => r.json()).then(h => !!h.processing_engine_enabled);

try {
  await writeWithTriggers(payload);
} catch (e) {
  if (String(e.message).includes('does not use the processing engine')) {
    routeToProcessingEngineNode(payload);
  } else { throw e; }
}

When it happens

Trigger: Sending an HTTP request whose handling requires the Processing Engine (e.g. writes or triggers meant to invoke plugins/WAL processing) to an InfluxDB 3 node launched without Processing Engine support in its node mode.

Common situations: Running a plain Core/Enterprise node (no processing-engine feature) and pointing an application or plugin pipeline at it; deploying a cluster where only some node types run the Processing Engine but clients route engine-dependent requests to all nodes.

Related errors

• failed to build an http client
• No plugin directory configured
• Node doesn't have proper mode, expect
• {0}
• An unexpected error occurred in the client library

AI-assisted analysis of influxdata/influxdb@06200ef96b (2026-09-19). Data as JSON: /api/errors/dcf8d5ecfbacf5ff. Report an issue: GitHub.

Appendix: source

Thrown at influxdb3_server/src/http.rs:388

    #[error("Authentication error: {0}")]
    Authentication(#[from] AuthenticatorError),

    #[error("The following Database does not exist: {0}")]
    MissingDb(String),

    #[error("The following Database Table does not exist: {0}")]
    MissingTable(String),

    #[error("Cannot parse the given human time: {0}")]
    ParsingHumanTime(#[source] humantime::DurationError),

    #[error("Cannot parse the timestamp: {0}")]
    ParsingTimestamp(#[from] chrono::ParseError),

    #[error("Timestamp is out of range")]
    TimestampOutOfRange,

    #[error("Current node mode does not use the processing engine")]
    NoProcessingEngine,

    #[error("invalid request: {0}")]
    InvalidRequest(String),

    #[error(transparent)]
    LegacyWriteParse(#[from] WriteParseError),
}

#[derive(Debug, Error)]
pub(crate) enum AuthenticationError {
    #[error("the request was not authenticated")]
    Unauthenticated,
    #[error(
        "Authorization header was malformed, the request was not in the form of 'Authorization: <auth-scheme> <token>', supported auth-schemes are Bearer, Token and Basic"
    )]
    MalformedRequest,
    #[error("requestor is forbidden from requested resource")]

View on GitHub (pinned to 06200ef96b)