`CheckOrphansAreDeletedHelpers` may consider some owned documents as orphans

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • ALL
    • Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The hook checking that no orphaned documents are present on disk at the end of a test works as follows:

      It has been observed a failure on step (3) because the hook wrongly believed that some documents actually owned by a shard were orphaned.

      The reason of the failure was the following: shard1 was migrating data to shard0 and the hook started analyzing shard0:

      • Step 1 passed because the migration coordinator is only present on the donor side
      • Step 2 passed because the "pending" range deleter task document was removed right after the migration committed
      • Step 3 failed because the read from config.chunks did not account for the migration just committed, probably because reading from a secondary node of the config server

              Assignee:
              Marcos José Grillo Ramirez
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: