You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2023/10/13 07:50:00 UTC

[jira] [Assigned] (IGNITE-20359) Expose node storage as a node attribute

     [ https://issues.apache.org/jira/browse/IGNITE-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mirza Aliev reassigned IGNITE-20359:
------------------------------------

    Assignee: Mirza Aliev

> Expose node storage as a node attribute
> ---------------------------------------
>
>                 Key: IGNITE-20359
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20359
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Assignee: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> To introduce the nodes' filtering by storage type and profile we need to expose the appropriate node storage configurations as node attributes (kind of inner attributes, not suitable for general filters).
> *Definition of done*
> - Node storage and storage profile exposed as node attributes for further filtering during the zone dataNodes setup.
> *Implementation notes*
> - These attributes must be the sepparate list of inner attributes, which are not exposed for the usual zone filtering. So, ClusterNodeMessage must be extended with the appropriate field.
> - The attrbiutes should looks like a map of (String engineType-> String profileName)
> - While the IGNITE-20564 is not done yet, the part about attributes receiving from the node configurations can be implemented around the engine and dataRegions, instead of profiles.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)