Update reaper when instantiating collection/index on expired ident

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19, Execution Team 2022-10-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A Collection or Index instance can be re-created because the previous one is expired, waiting for cleanup by the reaper. When this occurs we need to update the token held by the reaper to prevent data from being cleaned up under the newly created collection or index instance used for a PIT read before the drop.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: