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/04/14 08:03:00 UTC

[jira] [Updated] (IGNITE-16472) Incorporate the CMG manager into the node lifecycle

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

Aleksandr Polovtcev updated IGNITE-16472:
-----------------------------------------
    Description: 
After the CMG manager is introduced, the code around it should also be updated:
 # Logical topology should be used instead of physical topology, where needed.
 # Node startup order should be altered in order for the CMG manager to work correctly.
 # All components after the CMG Manager should be started after the join procedure has finished successfully.

  was:
After the CMG manager is introduced, the code around it should also be updated:
 # Logical topology should be used instead of physical topology, where needed.
 # Node startup order should be altered in order for the CMG manager to work correctly.


> Incorporate the CMG manager into the node lifecycle
> ---------------------------------------------------
>
>                 Key: IGNITE-16472
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16472
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> After the CMG manager is introduced, the code around it should also be updated:
>  # Logical topology should be used instead of physical topology, where needed.
>  # Node startup order should be altered in order for the CMG manager to work correctly.
>  # All components after the CMG Manager should be started after the join procedure has finished successfully.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)