You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
As part of shallow snapshot optimisations, we are introducing timestamp based implicit locking support. This feature will be called Timestamp Pinning in remote backed storage. When a timestamp is pinned, remote store garbage collectors will skip deleting data corresponding to the timestamp. We need to make changes to restore flow as well to restore data against the given pinned timestamp.
Describe the solution you'd like
Currently, remote store restore only supports restoring to last successful write operation for a given shard.
With pinned timestamp support, we will make changes to restore flow which will download segment and translog data for the given timestamp.
Related component
Storage:Remote
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
As part of shallow snapshot optimisations, we are introducing timestamp based implicit locking support. This feature will be called Timestamp Pinning in remote backed storage. When a timestamp is pinned, remote store garbage collectors will skip deleting data corresponding to the timestamp. We need to make changes to restore flow as well to restore data against the given pinned timestamp.
Describe the solution you'd like
Related component
Storage:Remote
The text was updated successfully, but these errors were encountered: