In addition to these config properties, the BITBUCKET_SHUTDOWN_TIMEOUT environment variable controls when Bitbucket terminates altogether.
To shut down immediately without waiting for any tasks to complete, set this to immediate. Sets whether Bitbucket should initiate a graceful shutdown first upon termination. The following configuration properties control how graceful shutdown works: The job scheduler will not start any new jobs, but will not immediately cancel any running jobs.The SSH server stop accepting new SSH connections without interrupting active connections.Tomcat stops accepting new HTTP connections without interrupting active connections.You can send a SIGTERM signal to Bitbucket to trigger a graceful shutdown. This will give Bitbucket some time to complete any running tasks, in-flight GIT requests, and in-flight user requests before terminating. The bin/stop-bitbucket.sh script, service atlbitbucket stop command, and systemctl bitbucket stop command all use the SIGTERM signal to terminate Bitbucket. Performing a graceful shutdown (Linux only) Learn more about deploying Bitbucket through Docker For Windows start-bitbucket.bat /no-searchįor Docker installations, use the -e ELASTICSEARCH_ENABLED=false parameter.
