-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[Remote Store] Add upload timestamp to metada file to be used in conflict resolution #5475
Copy link
Copy link
Closed
Labels
Storage:DurabilityIssues and PRs related to the durability frameworkIssues and PRs related to the durability frameworkenhancementEnhancement or improvement to existing feature or requestEnhancement or improvement to existing feature or requestv2.8.0'Issues and PRs related to version v2.8.0''Issues and PRs related to version v2.8.0'
Description
Is your feature request related to a problem? Please describe.
- Currently, we store metadata file in the remote store with:
metadata__<Primary Term>__<Generation>__<UUID>. - Primary term and generation are used to compare 2 metadata files and to get the latest one.
- But in some cases like primary - primary recovery, primary term and generation will be same.
- For this, we use UUID based comparison to have random but consistent way of resolving conflicts.
- As we are adding support for refresh level durability, it is important to get the latest uploaded metadata file.
- We can't just add timestamp in the filename as it will result in too many metadata files.
- The initial approach we are thinking of is to add timestamp info in the contents of metadata file.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Storage:DurabilityIssues and PRs related to the durability frameworkIssues and PRs related to the durability frameworkenhancementEnhancement or improvement to existing feature or requestEnhancement or improvement to existing feature or requestv2.8.0'Issues and PRs related to version v2.8.0''Issues and PRs related to version v2.8.0'