Start, stop, and restart

Keep this terminal open or run the command through your deployment’s process manager. Record the configuration path and executable version with the service definition. Check the startup log for address conflicts, filesystem permissions, and recovery errors.

From another terminal:

A live process may still be initializing or recovering data. Route traffic only after readiness succeeds. Configuration And Health explains the health endpoints.

Stop a foreground process with Ctrl+C. For a managed service, use its normal stop action and wait for the process to exit before starting another process against the same directory. For the container in the installation chapter, use docker stop shrikedb and docker start shrikedb.

Restart with the same executable, configuration, and volume. After readiness succeeds, repeat a saved query whose identifiers and expected values are known. The installation verification procedure provides a small persistence check.

A deployed web console has its own URL and connection settings; obtain these from your administrator. Select the logical database before running a query. You can also connect directly with the command-line client or gRPC and HTTP.

Before changing the storage path, binary version, or cluster configuration, stop writes and take a backup. Keep the old volume available until the new deployment has passed readiness, query, and restart checks.