How do I fix corrupted Jira issues?

[Jon Myers]

I came across some issues where I couldn't change their (workflow) state anymore.

Checking the logs gives me

2021-10-07 06:10:01,232+0000 Caesium-1-2 WARN system [c.a.j.issue.index.DefaultIssueIndexer] Issue with id '123' is corrupted. Skipping indexing of that issue

How do I fix these issues? I tried

• a full re-index (no effect)
• checking the integrity (everything is green)
• progressing the state programmatically (ValidationResult simply says nope and trying to execute anyways fails)
• cloning the issue and working on the new one (cloned issue behaves the same)
• moving the issue to a different workflow/issue type and back(no effect)

Does anyone know how to fix this?

[Dirk Ronsmans]

hey @Jon Myers and welcome to the community!

I found the following article 

https://confluence.atlassian.com/jirakb/troubleshoot-lucene-index-corruption-in-jira-server-931237172.html

which handles about fixing the index. The manual index fix part.

Question for me is if the index is corrupt on those issues or the issue itself. (I would guess the index entry).

I assume you've also restarted your instance?

Otherwise you can always reach out to Atlassian engineers through https://support.atlassian.com/contact

[Jon Myers]

Thanks for the suggestion - once our server admin did that I will report back.

[Jon Myers]

Alright, seems this feature doesn't work with the latest Jira versions (8.13.x here) anymore. Let's see if support has any ideas.

[Mir O_]

What about moving the issue and then returning it back? The key won't be the same, but it can help.

[Jon Myers]

That failed due to an internal error (due to corruption) while trying to move it.

[Guilhem Dupuy]

Hello @Jon Myers ,

There's nothing else I can think of;

I know it's not the answer you expect but have you tried raising an issue to the Atlassian support Team ? https://support.atlassian.com/contact/#/

They usually are really helpful and answer quite quickly !

[Jon Myers]

Thanks for the suggestion!

[Daniel Garcia]

how did you go?

[Jon Myers]

For whatever reason our admin never contacted support. I wound up having to delete the corrupted issues via SQL - which is usually the one thing you don't want to do (and of course on that particular system we had no backups in place) but that was all what was left to do. Sorry, no good news here.

However, I could at least identify the root cause. When adding a comment to an issue via the CommentManager and having the event bubble flag set to true these corruptions could be reproduced. Setting the flag to false prevented this from happening.

[Daniel Garcia]

The challenge is figuring out exactly what type of corruption. The error is so vague "something went wrong"