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
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.
The text was updated successfully, but these errors were encountered:
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, inderecho::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.
The text was updated successfully, but these errors were encountered: