Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.0, 1.6.0
    • Component/s: None
    • Labels:
      None

      Description

      I don't have a reproducible test case yet, but it looks like some usage pattern (for example creating, deleting, moving many nodes in one transaction) can cause the counter index to get out of sync with the real data. Worst case, the counter index thinks that the repository is empty (the root node has no descendent nodes).

      I want to write test cases to find the problem, or to prove that it doesn't get out of sync.

        Attachments

        1. OAK-4065.patch
          12 kB
          Thomas Mueller
        2. OAK-4065-b.patch
          15 kB
          Thomas Mueller
        3. probability_1m_10times-add1remove1m.png
          69 kB
          Thomas Mueller

          Issue Links

            Activity

              People

              • Assignee:
                tmueller Thomas Mueller
                Reporter:
                tmueller Thomas Mueller
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: