Fix Full reindex error DocValuesField "ISSUEPROP_request*" on Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In this article, we will explore a scenario where Full Re-index is failing at 97%. The error messages point to DocValuesField "ISSUEPROP_request*"
Environment
Jira Data Center 10.x
Diagnosis
When analysing the atlassian-jira.log files, the following three error messages can be found
#Error 1
2025-05-26 12:19:31,513+0000 IssueIndexer:thread-9 WARN [c.a.jira.index.AccumulatingResultBuilder] DocValuesField "ISSUEPROP_request.channel.type$value" appears more than once in this document (only one value is allowed per field)
java.lang.IllegalArgumentException: DocValuesField "ISSUEPROP_request.channel.type$value" appears more than once in this document (onl
y one value is allowed per field)
at org.apache.lucene.index.SortedDocValuesWriter.addValue(SortedDocValuesWriter.java:67)
at org.apache.lucene.index.DefaultIndexingChain.indexDocValue(DefaultIndexingChain.java:550)
#Error 2:
2025-05-26 12:19:31,536+0000 IssueIndexer:thread-5 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Issue - '18527'
2025-05-26 12:19:31,536+0000 IssueIndexer:thread-5 WARN [c.a.jira.index.AccumulatingResultBuilder] DocValuesField "ISSUEPROP_request.public-activity.lastupdated$" appears more than once in this document (only one value is allowed per field)
java.lang.IllegalArgumentException: DocValuesField "ISSUEPROP_request.public-activity.lastupdated$" appears more than once in this document (only one value is allowed per field)
at org.apache.lucene.index.NumericDocValuesWriter.addValue(NumericDocValuesWriter.java:55)
at org.apache.lucene.index.DefaultIndexingChain.indexDocValue(DefaultIndexingChain.java:536)
at org.apache.lucene.index.DefaultIndexingChain.processField(DefaultIndexingChain.java:466)
#Error 3:
2025-05-27 09:53:59,604+0000 IssueIndexer:thread-19 WARN [c.a.jira.index.AccumulatingResultBuilder] Indexing failed for Issue - '10807'
2025-05-27 09:53:59,604+0000 IssueIndexer:thread-19 WARN [c.a.jira.index.AccumulatingResultBuilder] DocValuesField "ISSUEPROP_service-request-feedback-comment$comment" appears more than once in this document (only one value is allowed per field)
java.lang.IllegalArgumentException: DocValuesField "ISSUEPROP_service-request-feedback-comment$comment" appears more than once in this document (only one value is allowed per field)
at org.apache.lucene.index.SortedDocValuesWriter.addValue(SortedDocValuesWriter.java:67)Based on these errors, use the following database queries for analysis:
#1
SELECT * FROM entity_property_index_document WHERE module_key like '%request.channel.type%';
#2
SELECT * FROM entity_property_index_document WHERE module_key = 'request.public-activity.lastupdated.index';
#3
SELECT * FROM entity_property_index_document WHERE module_key = 'service-request-feedback-comment.index';For each of these queries, two records can be found in the output with two different plugin_keys:
One record with plugin_key com.atlassian.jsd
Second record with plugin_key com.atlassian.servicedesk
Cause
There should be only one record with the plugin_key value com.atlassian.servicedesk. It is likely that the value com.atlassian.jsd originates from previous Jira versions, and these entries are no longer compatible.
Solution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Use the following steps to remove all entries with the plugin_key = 'com.atlassian.jsd' from the table entity_property_index_document to fix the reindex failure:
Run the following query to get all records with plugin_key = 'com.atlassian.jsd':
SELECT * FROM entity_property_index_document WHERE plugin_key = 'com.atlassian.jsd';Use the IDs returned by the above query to remove the incompatible entries. For example, if the returned IDs are 10103 and 10102, then run:
delete from public.entity_property_index_document where id = 10103; delete from public.entity_property_index_document where id = 10102;Restart Jira for the changes to take effect.
Was this helpful?