JIRA process reaching linux open files limit, because UseTFS plugin failed to release file handles

[Marc-Philip Blath]

Hi,

this issue caused a standstill of our JIRA. Max. open files limit was set to 10240 and the process never reached more than 2000 open files at once.

Catalina.out showed this error after every Index run of UseTFS during the day.

ERROR - com.pigsty.jira.plugins.usetfs.revision.RevisionIndexer - Exception while indexing
com.atlassian.jira.issue.index.IndexException: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/usr/local/jira_home/caches/indexes/plugins/usetfs-changesets/write.lock
at com.pigsty.jira.plugins.usetfs.revision.DefaultLuceneIndexAccessor.getIndexWriter(DefaultLuceneIndexAccessor.java:41)
at com.pigsty.jira.plugins.usetfs.revision.RevisionIndexer.addRevisionsToRepository(RevisionIndexer.java:674)
at com.pigsty.jira.plugins.usetfs.revision.RevisionIndexer.updateIndex(RevisionIndexer.java:436)
at com.pigsty.jira.plugins.usetfs.revision.RevisionIndexService$1.run(RevisionIndexService.java:117)
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/usr/local/jira_home/caches/indexes/plugins/usetfs-changesets/write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:84)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1115)
at com.pigsty.jira.plugins.usetfs.revision.DefaultLuceneIndexAccessor.getIndexWriter(DefaultLuceneIndexAccessor.java:37)
... 3 more

This caused the process to reach the limit of 10240 open files at the end of the day.

we are using UseTFS version 2.10.3.

Is this a known issue?

[andrzej_p]

Sorry to hear that. Somehow we've lost notifications from Atlassian Answers so we were not aware of any issues registered here. 

[Marc-Philip Blath]

A bit late, we have no more logs of this day. We disabled the sync from work items back to TFS, because this never worked really well. Since than this error didn't appear again.

[andrzej_p]

I don't think we've encountered such issue before. Could you provide log file for analysis to pigsty@pigsty.com.pl