Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-5587

Node counter index estimates must not be used before first async index cycle

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.6.1, 1.8.0
    • None
    • None

    Description

      Oak traversing index returns a very low estimate when first async index cycle hasn't completed yet, so that the wrong index can be used on first startup.

      NodeCounter#getCombinedCost() should treat non-existing /oak:index/counter/:index same as /oak:index/counter not existing.

      Attachments

        Activity

          People

            thomasm Thomas Mueller
            thomasm Thomas Mueller
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: