cb-analytics-admin

You check Couchbase Analytics health by reviewing service state, replica lag, ingestion progress, and active requests to identify stalls or long-running queries before taking any disruptive action.

Couchbase Analytics ingestion may lag due to stuck ingestion links or long-running queries. Inspect the service snapshot and request history to identify failure patterns and determine if a specific request is blocking ingestion.

To cancel a runaway Couchbase Analytics query, inspect active requests to identify the problematic query, then perform a confirmed destructive operation to cancel that specific request instead of restarting the full service.

Yes, you can restart a single Couchbase Analytics node. The service supports controlled restarts of individual nodes or the full Analytics service, requiring confirmation for these destructive operations in production clusters.

The best way to diagnose slow Couchbase Analytics queries is to inspect active and completed request history to identify long-running queries and failure patterns before deciding on cancellations or service restarts.

Restart the full Couchbase Analytics service only when necessary after checking service status and ingestion health. Cancel individual requests when a specific runaway query is identified, avoiding broader disruption to production clusters.