openstack/openstack-ansible
Code Issues Proposed changes

Add a known issue release note regarding inotify watch limits

Browse Source 
Change-Id: I3b5cadb510fd0804365c63cdc4d026d4a92d7508
This commit is contained in:
Jonathan Rosser 2019-02-18 09:22:45 +00:00
parent 442d53a4d5
commit 3c7005360b
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
releasenotes/notes/inotify-exhaustion-77f7ecab13358c4c.yaml Normal file
View File

@ -0,0 +1,16 @@
---
issues:
- |
The number of inotify watch instances available is limited system wide
via a sysctl setting. It is possible for certain processes, such as
pypi-server, or elasticsearch from the ops repo to consume a large number
of inotify watches. If the system wide maximum is reached then any process
on the host or in any container on the host will be unable to create a new
inotify watch. Systemd uses inotify watches, and if there are none available
it is unable to restart services. The processes which synchronise the repo
server contents between infra nodes also relies on inotify watches. If the
repo servers fail to synchronise, or services fail to restart when expected
check the the inotify watch limit which is defined in the sysctl value
fs.inotify.max_user_watches. Patches have merged to increase these limits,
but for existing environments or those which have not upgraded to a recent
enough point release may have to apply an increased limit manually.