DEV: Wait up to 10 minutes for safe PG stop (#709)
Over the years we had LOTS of cases of PostgreSQL instances that weren't stopped properly. This gives PG more time to handle it's shutdown cleanly on the worst case, but will still shutdown fast in normal cases.
This commit is contained in:
parent
82bec846a1
commit
d54cc57f5f
6
launcher
6
launcher
|
@ -521,7 +521,7 @@ run_stop() {
|
|||
then
|
||||
(
|
||||
set -x
|
||||
$docker_path stop -t 30 $config
|
||||
$docker_path stop -t 600 $config
|
||||
)
|
||||
else
|
||||
echo "$config was not started !"
|
||||
|
@ -817,7 +817,7 @@ case "$command" in
|
|||
echo "Stopping old container"
|
||||
(
|
||||
set -x
|
||||
$docker_path stop -t 60 $config
|
||||
$docker_path stop -t 600 $config
|
||||
)
|
||||
fi
|
||||
|
||||
|
@ -838,7 +838,7 @@ case "$command" in
|
|||
|
||||
|
||||
destroy)
|
||||
(set -x; $docker_path stop -t 10 $config && $docker_path rm $config) || (echo "$config was not found" && exit 0)
|
||||
(set -x; $docker_path stop -t 600 $config && $docker_path rm $config) || (echo "$config was not found" && exit 0)
|
||||
exit 0
|
||||
;;
|
||||
esac
|
||||
|
|
Loading…
Reference in New Issue