[
https://issues.apache.org/jira/browse/IGNITE-28990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105132#comment-18105132
]
Ignite TC Bot commented on IGNITE-28990:
----------------------------------------
{panel:title=Branch: [pull/13488/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13488/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9287100&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9287100
rerunBuildIds=9287102,9287104{color}
> 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
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 0.5h
> 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)
