[
https://issues.redhat.com/browse/ISPN-4075?page=com.atlassian.jira.plugin...
]
Pedro Zapata Fernandez updated ISPN-4075:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid
Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint
#36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint
10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid
Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint
#37, DataGrid Sprint #38)
State transfer should preserve the creation timestamp of entries
----------------------------------------------------------------
Key: ISPN-4075
URL:
https://issues.redhat.com/browse/ISPN-4075
Project: Infinispan
Issue Type: Feature Request
Components: Core
Affects Versions: 6.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Major
Fix For: 9.4.7.Final, 10.0.0.Beta1, 10.0.0.Final
State transfer inserts values with the current time as the creation time. Since the
entries store the expected lifespan and not the expected expiration time, entries on the
receiving node could expire much later than intended.
The argument probably doesn't apply to the timestamp of the last usage. Since state
transfer process could be interpreted as a reader, it should be fine to extend the update
the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)