Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.0.7, 5.1, 5.1.2
-
None
-
WAR-Installations of 5.0.7 and 5.1.2 running on a linux server.
-
5
-
Description
When reindexing Jira does not close the handles on the old index-files properly.
Using lsof +L1 we could identify 6.89GiB of old indexes still open by jira but allready unlinked on the hard-drive.
We run reindexing every night at 3am triggered by a service-task. Right now this means we should better restart Jira every week or two so we don't need a bigger data partition and improve Jira performance.
How to reproduce?
I just now hit "Reindex" inside Jira and after it finished there were 17 new lines in the output of lsof +L1.
Workaround
- Disable the index optimization job as per our How to Disable the Index Optimization Job in JIRA KB article.
This job is not necessary from JIRA 5.0 onwards and was deprecated as of JIRA 5.1.6 (JRA-29487). - Whenever a full reindex is performed on JIRA, restart it afterwards.
Attachments
Issue Links
- has a regression in
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
JRASERVER-38039
JIRA IndexReader is leaking file descriptors
-
- Closed
-
-
JRASERVER-32080 Update Supported Platforms Docs to have info about NFS
- Closed
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed