diff options
| author |   Sai Sindhur Malleni <smalleni@redhat.com> | 2017-09-19 15:12:35 -0400 |
|---|---|---|
| committer | Sai Sindhur Malleni <smalleni@redhat.com> | 2017-10-04 13:05:20 +0000 |
| commit | 6a7428898f7fa7a0d46e1de60ca57e7ec6ce14c9 (patch) | |
| tree | a74e8202297378db931aaceb31e8e18ea8b466d8 /docker/services/rabbitmq.yaml | |
| parent | f2d8fa73f6cec2e3d754dbd9a9973918cc9832d0 (diff) | |
Bump fs.inotify.max_user_instances for scale
Since each dnsmasq process consumes one inotify socket, the default
value of fs.inotify.max_user_instances which is 128 lets us scale to
only around a 116 neutron subnets (a few other sockets are used by other
processes on the system). Since, we need to provide better defaults,
this patch proposes to bump this value to 1024 by default, while giving
the user a way to cahnge it. Based on
https://unix.stackexchange.com/a/13757 each inotify watch takes 1KB of
memory and we have fs.inotify.max_user_watches set to 8192 by default.
This means that even in the worst case we won't be using more than 8MB
of memory. Bumping the fs.inotify.max_user_instances value to 1024 is
safe because there is fs.inotify.max_user_watches which caps the total
number of files that can be watched by all the inotify instances a user
has.
Related Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1474515
https://bugzilla.redhat.com/show_bug.cgi?id=1491505
Change-Id: I39664312bf6cf06f1e1ca2e86ffd86fb9a4582ad
Closes-Bug: 1718266
(cherry picked from commit d2d0c3ff00de9b62382193d942239d543aa9499f)
Diffstat (limited to 'docker/services/rabbitmq.yaml')
0 files changed, 0 insertions, 0 deletions