Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: 9.4.7.Final, 10.0.0.Final
Affects Version/s: 6.0.1.Final
Component/s: Core
Labels:
None

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
Git Pull Request:
https://github.com/infinispan/infinispan/pull/6525, https://github.com/infinispan/infinispan/pull/6572, https://github.com/infinispan/infinispan/pull/6629, https://github.com/infinispan/infinispan/pull/6630

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.

causes

ISPN-9871 Error executing command PutKeyValueCommand when using protobuf

Closed

is cloned by

JDG-2025 State transfer should preserve the creation timestamp of entries

Closed

is duplicated by

ISPN-9367 State transfer should preserve the creation timestamp of entries

Closed

is related to

ISPN-11554 Off-heap state transfer does not preserve the timestamp of entries

Closed

relates to

ISPN-10031 Remove doc regarding expiration not working with state transfer

Closed

Assignee:: Dan Berindei (Inactive)

Reporter:: Dan Berindei (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2014/03/05 9:25 AM

Updated:: 2024/01/16 3:13 PM

Resolved:: 2019/01/29 11:10 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates