Hi, we recently faced the issue that our Oak based enterprise content management system run into failures due to too much open files. Monitoring the lsof output we found out that most of the opened files of the process are the files within the configured localIndexDir of the LuceneIndexProviderService. We have copyonread and copyonwrite enabled.
Are there any know limitations with handling open files related to those 2 options? If so, I naively would expect the implementation to manage file handles following kind of a LRU pattern and to allow configuring a maximum amount of file handles to use. Talking in numbers we have, after a fresh restart of the process about 20k open files, 13k are index files, 2.5k segmentstore and most of the others jar files. The ulimit is already set to more then 65k but the instance crashed with more then 75k open file handles. Many thanks in advance, /Dirk
