Free Space Health check fails due to an IllegalArgumentException

Description

Summary

The Free Space Health check uses common-io library to calculate the size of the index directory, to verify there is enough free space for indexing. Due to a bug in the library, IO-389, this can cause the check to fail if a file is deleted whilst the check is running. We use commons-io 1.4 in the plugin.

Steps to Reproduce

  1. Have a large index dir setup

  2. Run the health check

  3. Delete a lucene segment file during the check

Expected Results

The check can continue without problems

Actual Results

An exception is thrown as below:

Workaround

  1. Browse to Manage add-ons

  2. Expand the Atlassian JIRA - Plugins - Instance Health Plugin / Atlassian Troubleshooting & Support Tools Plugin (this depends on the version of Jira you're using)

  3. Click + next to "n of n modules enabled"

  4. Search for "storageIndexSnapshotHealthCheck"

  5. Mouse-over it and click Disable.

Environment

None

Activity

Show:
April
August 17, 2018, 6:40 PM

Hello there,

In Jira 7.9.2, I find 'storageIndexSnapshotHealthCheck' under 'Atlassian Troubleshooting and Support Tools' and cannot find an "Atlassian JIRA - Plugins - Instance Health Plugin plugin."

Presumably the plugin name changed, and I do have the correct module, but could you please confirm that?

Thanks

Dave C
August 19, 2018, 11:08 PM

Hey , thanks for pointing this out - we changed the Jira Instance Health plugin to be the Atlassian Troubleshooting & Support Tools plugin as of Jira 7.4.3 onwards. I've updated the issue accordingly.

Tom Davies
March 14, 2019, 5:12 AM

This will be fixed when JIRA 8.1 is released, as it will provide a version of commons-io which doesn't have this problem.

Tom Davies
November 25, 2019, 11:50 PM

This will be fixed when the products upgrade to versions with fixed commons-io libraries, i.e. commons-io 2.5.

Won't Fix

Assignee

Unassigned

Reporter

Dave C

Components

None

Labels

Add-on Type

None

Team

None

CC

None

Risk factor

None

Affected Product/s

Jira

Priority

Major
Configure