Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object timestamp does not match log timestamp #1

Open
songweijia opened this issue Aug 2, 2020 · 0 comments
Open

Object timestamp does not match log timestamp #1

songweijia opened this issue Aug 2, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@songweijia
Copy link
Contributor

In PersistentCascadeStore<>, ObjectType::ver is a tuple with a version number and timestamp. In the current implementation, the timestamp is set in PersistentCascadeStore<>::ordered_put(). However, in derecho::Persistent<>::set(), the timestamp is assigned on message delivery and passed through persistent_manager. That timestamp will becoming the timestamp index in the log entry. Therefore, the timestamp in ObjectType is slighly earlier than the log entry timestamp.

To fix that issue, we should allow Persistent<>::set() to update the timestamp in ObjectType on delivery.

@songweijia songweijia added the enhancement New feature or request label Aug 2, 2020
@songweijia songweijia self-assigned this Aug 2, 2020
songweijia pushed a commit that referenced this issue Dec 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant