XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      2014-07-24 12:18:37,088 IssueIndexer:thread-7 WARN xxxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10540] and issue [70955]
      2014-07-24 12:18:37,088 IssueIndexer:thread-7 WARN xxxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankCFType] gh.lexorank.service.error.retrytimeout
      2014-07-24 12:18:37,088 IssueIndexer:thread-7 WARN xxxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankIndexer] Could not retrieve LexoRank value for issue[id=70955]. Indexing max LexoRank value instead.
      2014-07-24 12:21:18,521 IssueIndexer:thread-7 WARN xxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10540] and issue [69656]
      2014-07-24 12:21:18,522 IssueIndexer:thread-7 WARN xxxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankCFType] gh.lexorank.service.error.retrytimeout
      2014-07-24 12:21:18,522 IssueIndexer:thread-7 WARN xxx 638x8069x1 1rcz7cs 172.26.6.181,172.30.2.137 /secure/admin/jira/IndexReIndex.jspa [greenhopper.customfield.lexorank.LexoRankIndexer] Could not retrieve LexoRank value for issue[id=69656]. Indexing max LexoRank value instead.

      The above WARN appear in all Lexo Rank problem starting from version 6.4. Most of the time, this WARN didn't bring much value to investigation and spamming jira and agile application log as it thrown for every issues.

      Suggestion:

      1. set the JIRA Agile default IssueIndexer log to ERROR.
      2. increase the information as to why it can't retrieve the LexoRank value for specific issue.
      3. reduce the quantity of the WARN message.

      Attachments

        Activity

          People

            Unassigned Unassigned
            vkharisma vkharisma (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: