From a264b0015ec4d319f603b113c7aec3c05349a968 Mon Sep 17 00:00:00 2001 From: Benjamin Elder Date: Fri, 21 Mar 2025 12:54:45 -0700 Subject: [PATCH] kube-up.sh: set inotify limits also debug inotify limits before/after setting --- cluster/gce/gci/configure-helper.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/cluster/gce/gci/configure-helper.sh b/cluster/gce/gci/configure-helper.sh index 9b1afa05693..29f21424adf 100755 --- a/cluster/gce/gci/configure-helper.sh +++ b/cluster/gce/gci/configure-helper.sh @@ -66,6 +66,24 @@ function setup-os-params { # /sbin/crash_reporter which is more restrictive in saving crash dumps. So for # now, set a generic core_pattern that users can work with. echo "/core.%e.%p.%t" > /proc/sys/kernel/core_pattern + echo "Default max_user_watches / max_user_instances:" + # ensure we have enough inotify watches for many pods, versus the OS defaults + # debug before & after / defaults for comparison + sysctl fs.inotify.max_user_watches + sysctl fs.inotify.max_user_instances + cat < /etc/sysctl.d/inotify.conf +fs.inotify.max_user_watches=65536 +fs.inotify.max_user_instances=8192 +EOF + # Ubuntu vs COS, load sysctl settings now + if [[ -e "/usr/lib/systemd/systemd-sysctl" ]]; then + /usr/lib/systemd/systemd-sysctl + else + /lib/systemd/systemd-sysctl + fi + echo "Updated max_user_watches / max_user_instances:" + sysctl fs.inotify.max_user_watches + sysctl fs.inotify.max_user_instances } # secure_random generates a secure random string of bytes. This function accepts