[
https://issues.apache.org/jira/browse/IGNITE-28441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-28441:
-----------------------------------------
Description:
Current way of getting local node information (like name and ID) is using
{{TopologyService#localMember}}. This not optimal for several reasons:
1. It involves reading of the volatile state of ScaleCube's {{Cluster}},
including conversion between different types;
2. It is only available after the corresponding component has been started
(i.e. it's not accessible in constructors), which results in ugly code
involving {{Lazy}} and lambdas.
Since this information is actually always available, it's proposed to add a
method to the {{ClusterService}} that will return the local node without
metadata (the only reason we need ScaleCube's volatile state).
> Add method for getting constant local node
> ------------------------------------------
>
> Key: IGNITE-28441
> URL: https://issues.apache.org/jira/browse/IGNITE-28441
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> Current way of getting local node information (like name and ID) is using
> {{TopologyService#localMember}}. This not optimal for several reasons:
> 1. It involves reading of the volatile state of ScaleCube's {{Cluster}},
> including conversion between different types;
> 2. It is only available after the corresponding component has been started
> (i.e. it's not accessible in constructors), which results in ugly code
> involving {{Lazy}} and lambdas.
> Since this information is actually always available, it's proposed to add a
> method to the {{ClusterService}} that will return the local node without
> metadata (the only reason we need ScaleCube's volatile state).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
