Layered tombstone decode guard triggered while persisting the recovery doc of an inflight chunk operation

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Layered Tables
    • Storage Engines - Foundations
    • 173.857
    • None
    • 3

      WT-17905 introduced a new guard to ensure that no user data containing a "tombstone encoding" gets persisted to disk.

      WiredTiger is supposed to prevent such a state by applying proper escaping to potential conflicting values; nevertheless, regressions (e.g.) started appearing while the Server CAR team was testing changes to the chunk migration infrastructure (which now includes the persistence of a recovery document to record its progress).

      It is believed that the exact content of the document (and the way this gets updated) may be instrumental to reproduce the scenario.

        1. test_layered_tombstone_modify.py
          7 kB

            Assignee:
            Salman Javed
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: