Rollback to stable aborts the unstable updates in the datastore and replaces them with a stable update from the history store. As part of this process, RTS takes the decision of the history store update visibility based on the timestamps stored in the HS key/value.

Reading these values to decide visibility can go wrong when the history store update is removed with a globally visible tombstone either due to no timestamp update rewriting the history store or an earlier rollback to stable remove operation.

Reading these keys whenever a globally visible tombstone is present as part of the RTS causes problems in restoring a wrong update/tombstone that leads to the entire key removal.