Custom field indexes dropped with errors in Jira server
Problem
When indexing operations within JIRA, exceptions are thrown with errors such as 'Error indexing issue GOPLANET-1234: Dropping 'customfield_11279'
The following appears in the atlassian-jira.log:
2015-03-28 04:27:01,424 IssueIndexer:thread-4 WARN [jira.issue.index.DefaultIssueDocumentFactory] Error indexing issue GOPLANET-1234: Dropping 'customfield_11279'
java.lang.NullPointerException
at com.intenso.jira.plugins.tms.customfield.AbstractProgressCF.getValueFromIssue(AbstractProgressCF.java:101)
at com.intenso.jira.plugins.tms.customfield.AbstractProgressCF.getValueFromIssue(AbstractProgressCF.java:31)
at com.atlassian.jira.issue.fields.CustomFieldImpl.getValue(CustomFieldImpl.java:437)
at com.atlassian.jira.issue.index.indexers.impl.NumberCustomFieldIndexer.addDocumentFields(NumberCustomFieldIndexer.java:41)
at com.atlassian.jira.issue.index.indexers.impl.NumberCustomFieldIndexer.addDocumentFieldsSearchable(NumberCustomFieldIndexer.java:31)
at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(AbstractCustomFieldIndexer.java:46)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.add(DefaultIssueDocumentFactory.java:102)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.addAll(DefaultIssueDocumentFactory.java:91)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:60)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:37)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$DefaultDocumentCreationStrategy.get(DefaultIssueIndexer.java:664)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$IndexIssuesOperation.perform(DefaultIssueIndexer.java:502)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:337)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:333)
at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:9)
at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:5)
at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:38)
at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:35)
at com.atlassian.jira.util.concurrent.BoundedExecutor$2.call(BoundedExecutor.java:77)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Cause 1
There is an exception thrown during the indexing operation, which means a problem was encountered when JIRA was trying to create an index for that custom field. Rather than failing the entire index operation for that issue, JIRA will drop the Custom Field from that index.
Cause 2
The 'Dropping 'customfield_XXXXX' exception might be false positive and occurring due to the actual server running out of space.
For that, the following log entries will be evident prior to the dropping customfield exception:
Caused by: java.nio.file.FileSystemException: /opt/jirasoftware-home/caches/indexesV1/issues/_f1xf.fdx: No space left on device
at sun.nio.fs.UnixException.translateToIOException(Unknown Source)
at sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source)Workaround
If there's no 'no space left on device' error, please review the actual 'dropping customfield_exception' thrown in the logs after the error message. In this example KB it appears to be a problem with the Abstract Progress Custom Field in a third-party plugin. Disabling the plugin will alleviate the problem, and raising the issue with the plugin developers will assist in overall resolution for the issue. Their details can be found on the Atlassian Marketplace.
If shortage of space is evident in the logs, please follow this article to resolve the issue.