Skip to content

K
k3s
Commit 4e87973a authored by Yu-Ju Hong's avatar Yu-Ju Hong
Browse files
Options

Bump container-linux and gci timeout for docker health check

The command `docker ps` can take longer time to respond under heavy load or when encountering some known issues. In these cases, the containers are running fine, so aggressive health check could cause serious disruption. Bump the timeout to 60s to be consistent with the debian-based containerVM.
parent 3683e0a6
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
cluster/gce/container-linux/health-monitor.sh
View file @ 4e87973a
...@@ -26,7 +26,7 @@ set -o pipefail ...@@ -26,7 +26,7 @@ set -o pipefail
# automatically restart the process. # automatically restart the process.
function docker_monitoring { function docker_monitoring {
while [ 1 ]; do while [ 1 ]; do
if ! timeout 10 docker ps > /dev/null; then if ! timeout 60 docker ps > /dev/null; then
echo "Docker daemon failed!" echo "Docker daemon failed!"
pkill docker pkill docker
# Wait for a while, as we don't want to kill it again before it is really up. # Wait for a while, as we don't want to kill it again before it is really up.
......
cluster/gce/gci/health-monitor.sh
View file @ 4e87973a
...@@ -26,7 +26,7 @@ set -o pipefail ...@@ -26,7 +26,7 @@ set -o pipefail
# automatically restart the process. # automatically restart the process.
function docker_monitoring { function docker_monitoring {
while [ 1 ]; do while [ 1 ]; do
if ! timeout 10 docker ps > /dev/null; then if ! timeout 60 docker ps > /dev/null; then
echo "Docker daemon failed!" echo "Docker daemon failed!"
pkill docker pkill docker
# Wait for a while, as we don't want to kill it again before it is really up. # Wait for a while, as we don't want to kill it again before it is really up.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment