Attempt to reindex the node as per Search Indexing and monitor the logs for any errors.

• A slow disk speed can contribute to indexing problems and can be tested as per our Testing Disk Access Speed KB.

• There may be other services updating the JIRA Database, or issue without re-indexing. Run the following SQL to locate the last updated issue, and review the update history to narrow down the problem. The sample SQL below should work for Postgres:

  SELECT p.pkey 
             ||'-' 
             ||j.issuenum AS jiraissue, 
         j.updated 
  FROM   project p, 
         jiraissue j 
  WHERE  p.id=j.project 
  AND    j.updated = 
         ( 
                SELECT Max(updated) 
                FROM   jiraissue);

  
  

  
  

Check status at each node to see if there is an actual problem. Monitor instance status over period of time to see if difference will grow. Attempt to copy index from healthy node if required. If no other nodes available, attempt to reindex the node as per Search Indexing and monitor the logs for any errors.

Improvement ticket:

JRA-61501 - 課題詳細を取得中... ステータス