[
https://issues.apache.org/jira/browse/IGNITE-28990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-28990:
------------------------------------
Fix Version/s: 2.19
> Embed Ignite features to IgniteClusterNode API
> ----------------------------------------------
>
> Key: IGNITE-28990
> URL: https://issues.apache.org/jira/browse/IGNITE-28990
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Priority: Major
> Fix For: 2.19
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, Ignite node features are stored in node attributes as marshalled
> bytes and must be deserialized before they can be accessed.
> This causes two issues:
> 1. We need to rely on some form of caching if node features are accessed
> frequently. Otherwise, repeated deserialization may negatively impact
> performance.
> 2. Sending features between nodes as marshalled bytes makes it difficult to
> evolve the feature set classes in an RU-compatible manner.
> It is proposed to introduce a dedicated field in the node message to hold the
> node features. The features will be serialized using the message
> serialization mechanism before being transmitted between nodes.
> It must be taken into account that ClusterNode instances can be stored in the
> PDS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
