You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2026/07/25 08:05:00 UTC

[jira] [Created] (IGNITE-28920) Reduce MarshallableMessage scope: GridCacheEntryInfo uses marshal hooks only to rebase expireTime

Anton Vinogradov created IGNITE-28920:
-----------------------------------------

             Summary: Reduce MarshallableMessage scope: GridCacheEntryInfo uses marshal hooks only to rebase expireTime
                 Key: IGNITE-28920
                 URL: https://issues.apache.org/jira/browse/IGNITE-28920
             Project: Ignite
          Issue Type: Task
            Reporter: Anton Vinogradov


GridCacheEntryInfo implements MarshallableMessage, but its marshal()/unmarshal() hooks never use the Marshaller: marshal() converts the absolute expireTime into a remaining TTL before send, and unmarshal() restores the absolute value on the receiver, compensating clock differences between nodes. MarshallableMessage should stay reserved for messages that actually carry marshalled payload. Proposal: move the expireTime rebase out of the marshalling hooks and drop the MarshallableMessage interface from GridCacheEntryInfo. Same cleanup direction as IGNITE-28914 (GridDhtPartitionsFullMessage).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)