Does tombstone blocks shadowed data SSTables from being purged in TWCS

ScyllaDB
, , , ,
1

Installation details
ScyllaDB version: 6.2.1

From the documentation: Avoid overwriting data and deleting data explicitly at all costs, as this can potentially block an expired SSTable from being purged, due to the checks that are performed to avoid data resurrection.

Question:
I have tombstone in one windowed SSTable A, but actual shadowed data in SSTable B (or others as well). Will tombstone in SSTable A block purging of SSTable B (where is shadowed data is stored) and why if it so? Or documentation means that it will block purging of SSTable A (where is tombstone is stored) because we need to wait tombstone expiration (gc_grace_seconds/repair/etc)?

2

It is the other way around. SSTable B (the one with the shadowed data) will block the purge of SSTable A, in particular it will block the purge of the tombstone in SSTable A and said sstable can no longer be expired as a whole.