[
https://issues.apache.org/jira/browse/IGNITE-18953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-18953:
---------------------------------
Description:
{*}Motivation{*}:
We need to have an ability to set key-value attributes to nodes, so they could
be filtered further, when data nodes for the zones will be recalculated.
*Definition of done:*
* It is possible to set key-value attributes to nodes
* This attributes are available clusterwide
*Implementation details:*
Node attributes must be as part of local configuration, and they must be stored
in the CMG group, so the could be accessible through the cluster. We can extend
{{org.apache.ignite.internal.cluster.management.raft.commands.ClusterNodeMessage}}
so they can have nodes' attributes
As for configuration representation, we can create top level schema
{{NodesAtttributesConfigurationSchema}}, and in this schema we can have
{{@NamedConfigValue}} field with {{NodeAtttributesConfigurationSchema}}, where
we can have a filed with the name (consistentId) of the node, and filed with a
list of String attributes.
was:
{*}Motivation{*}:
We need to have an ability to set key-value attributes to nodes, so they could
be filtered further, when data nodes for the zones will be recalculated.
*Definition of done:*
* It is possible to set key-value attributes to nodes
* This attributes are available clusterwide
*Implementation details:*
Node attributes nust be as part of local configuration, and they must be stored
in the CMG group, so the could be accessible through the cluster.
As for configuration representation, we can create top level schema
{{NodesAtttributesConfigurationSchema}}, and in this schema we can have
{{@NamedConfigValue}} field with {{NodeAtttributesConfigurationSchema}}, where
we can have a filed with the name (consistentId) of the node, and filed with a
list of String attributes.
> Add the ability to set attributes for a node to use them for filtering
> specific nodes
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-18953
> URL: https://issues.apache.org/jira/browse/IGNITE-18953
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> {*}Motivation{*}:
> We need to have an ability to set key-value attributes to nodes, so they
> could be filtered further, when data nodes for the zones will be recalculated.
> *Definition of done:*
> * It is possible to set key-value attributes to nodes
> * This attributes are available clusterwide
> *Implementation details:*
> Node attributes must be as part of local configuration, and they must be
> stored in the CMG group, so the could be accessible through the cluster. We
> can extend
> {{org.apache.ignite.internal.cluster.management.raft.commands.ClusterNodeMessage}}
> so they can have nodes' attributes
> As for configuration representation, we can create top level schema
> {{NodesAtttributesConfigurationSchema}}, and in this schema we can have
> {{@NamedConfigValue}} field with {{NodeAtttributesConfigurationSchema}},
> where we can have a filed with the name (consistentId) of the node, and filed
> with a list of String attributes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
