[
https://issues.apache.org/jira/browse/IGNITE-28908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097680#comment-18097680
]
Mikhail Petrov commented on IGNITE-28908:
-----------------------------------------
Basic TC Suite Run -
https://ci2.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Basic1&branch_IgniteTests24Java8=pull%2F13385%2Fhead&tab=buildTypeStatusDiv
> Fix features activation completion on client nodes with missing component
> -------------------------------------------------------------------------
>
> Key: IGNITE-28908
> URL: https://issues.apache.org/jira/browse/IGNITE-28908
> Project: Ignite
> Issue Type: Bug
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Labels: IEP-132, ise,
> Fix For: 2.19
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, client nodes may have fewer components than the cluster's server
> nodes. In this case, however, the client node will never complete local
> feature activation because of the following logic:
> {code:java}
> /** */
> public void onGridDataReceived(IgniteNodeFeatureSet activeClusterFeatures) {
> if (locVerFeatures.equals(activeClusterFeatures))
> activateLocalVersionFeatures();
> else
> this.activeFeatures = activeClusterFeatures;
> }
> {code}
> Since `locVerFeatures` includes only the components available on the local
> node, it can never be equal to `activeClusterFeatures`on client node if the
> cluster contains additional components. As a result,
> `activateLocalVersionFeatures()` is never invoked, and local feature
> activation never completes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)