Rollback to stable doesn't remove history store updates when their stop timestamp is less than the stable timestamp as it treats that this update already available in the update chain. This assumption is wrong when this update is appended to the update chain to replace the on-disk value. This led to a state where the same update is present in both the data store and history store. Usually, this problem occurs when the history store updates are having both start and stop timestamp are same.