Stop and Restart the Hub Service
This page provides instructions for stopping and restarting a Hub installation. To prevent unexpected loss of data, you need to stop your Hub server before performing any of the following updates:
Changing the location of the Hub database or other application files.
Modifying Hub properties or JVM options for your Hub server.
Switching traffic from HTTP to HTTPS and vice versa.
Upgrading your Hub installation.
To stop the Hub service gracefully, run the command:
docker exec <containerId> stop
For a graceful shutdown, you can also use the standard docker kill
command:
docker kill --signal=SIGTERM <containerId>
We do not recommend using the standard command docker stop
. By default, this command sends the SIGTERM
signal to the Hub process inside the Docker container, then waits for 10 seconds. If Hub does not shut down completely within that time period, the SIGKILL
is sent to the kernel, immediately terminating the Hub process. This may lead to data corruption. To avoid this outcome, specify an appropriate timeout value when using this command. For example, the following command leaves enough time for the Hub service to shut down:
docker stop -t 60 <containerId>
Thanks for your feedback!