You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2022/11/25 12:15:00 UTC

[jira] [Commented] (IGNITE-18241) Introduce support code for LogicalTopologyService

    [ https://issues.apache.org/jira/browse/IGNITE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638643#comment-17638643 ] 

Aleksandr Polovtcev commented on IGNITE-18241:
----------------------------------------------

Looks awesome, thanks

> Introduce support code for LogicalTopologyService
> -------------------------------------------------
>
>                 Key: IGNITE-18241
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18241
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> In IGNITE-18085, we will need to have {{LogicalTopologyService}} that will be used to get current topology (with version) and also subscribe to the topology changes.
> Currently, {{CmgRaftGroupListener}} uses its package local  {{RaftStorageManager}} to work with CMG-related storage, including operations with logical topology. The {{RaftStorageManager}} is the code that will trigger topology modification events, so it needs to either implement the public interface, or be made available to the public interface implementation.
> The idea is to create a new component (a suggested name is {{{}InternalLogicalTopologyService{}}}) instantiated by {{IgniteImpl}} and then injected to both {{ClusterManagementGroupManager}} and an implementation of {{{}LogicalTopologyService{}}}.



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