Why is the re-index and JiraIssueService referencing a deleted issue?

Matt Parks May 17, 2018

My QA environment is running very slowly when attempting to run a re-index or edit/update issues.

Looking at the logs, I see the following errors over and over

2018-05-17 09:37:50,905 http-nio-8080-exec-22 WARN Jira-AutoTask 577x198686x1 1i6oqi4 10.10.33.32 /rest/agile/latest/issue/CAC-49 [c.a.r.j.env.issues.JiraIssueService] could not load issue with id 10466.

and 

2018-05-17 09:37:56,331 JiraTaskExectionThread-1 WARN redactedUsername 513x177942x1 1bamfm3 10.10.165.4 /secure/admin/IndexReIndex.jspa [c.a.r.j.env.issues.JiraIssueService] could not load issue with id 10466.

 

When I look at the database, I don't see any entry in the jiraissue table with an id of 10466, so it looks like it's been deleted. If that's the case, why are these other services referencing the deleted issue and how can I get them to stop?

1 answer

0 votes
Matt Parks May 17, 2018

Please delete this question. I didn't mean to ask it in Marketplace-Apps. I've asked it in the appropriate forum (https://community.atlassian.com/t5/Jira-questions/Why-the-re-index-and-JiraIssueService-services-referencing-a/qaq-p/798898#M257652)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events