IndexConsistency constructor should use ValidateState's index list rather than simply durable indexes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2019-10-07
    • 6
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ValidateState does extra filtering regarding what indexes to validate, making sure indexes are ready and in the checkpoint, whereas IndexConsistency does not. Additionally, IndexConsistency currently opens its own cursor and so could be looking at indexes in a different checkpoint than the one used by ValidateState, creating an inconsistent view.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: