[ https://issues.apache.org/jira/browse/FLINK-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nico Kruber closed FLINK-13018. ------------------------------- Resolution: Works for Me Looks like this was solved by rebooting and thus resetting any rogue inotify instances. I also verified that starting the build and stopping it (with the current code) does not leak inotify instances by looking at {code} find /proc/*/fd/* -type l -lname 'anon_inode:inotify' 2>/dev/null | wc -l {code} > Serving docs locally with jekyll fails with inotify limit > --------------------------------------------------------- > > Key: FLINK-13018 > URL: https://issues.apache.org/jira/browse/FLINK-13018 > Project: Flink > Issue Type: Bug > Components: Documentation > Affects Versions: 1.9.0 > Reporter: Nico Kruber > Assignee: Nico Kruber > Priority: Major > > Both {{build-docs.sh -i}} and {{build-docs.sh -p}} currently fail (also in > the dockerized builds in {{docs/docker}}): > {code} > $ ./build_docs.sh -p > Fetching gem metadata from https://rubygems.org/.......... > ... > Bundle complete! 8 Gemfile dependencies, 36 gems now installed. > Bundled gems are installed into `./.rubydeps` > Configuration file: /home/nico/Projects/flink/docs/_config.yml > Source: /home/nico/Projects/flink/docs > Destination: /home/nico/Projects/flink/docs/content > Incremental build: disabled. Enable with --incremental > Generating... > done in 167.943 seconds. > jekyll 3.7.2 | Error: Too many open files - Failed to initialize inotify: > the user limit on the total number of inotify instances has been reached. > {code} > I wouldn't suggest working around by setting a higher inotify limit but > upgrading jekyll did not solve it and so far there are two options: > # disable watching files via {{--no-watch}} > # use polling instead of `inotify` via `--force_polling` > # try to reduce the set of files by adding excludes for (expected) static > files -- This message was sent by Atlassian JIRA (v7.6.3#76005)