[jira] [Commented] (IGNITE-8241) Docs: Triggering automatic rebalancing if the whole baseline topology is not recovered

["Denis Magda (JIRA)" <ji...@apache.org>]

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

Denis Magda commented on IGNITE-8241:
-------------------------------------

[~pgarg], please review the following section and close the ticket:
https://apacheignite.readme.io/v2.4/docs/cluster-activation#section-triggering-rebalancing-programmatically

> Docs: Triggering automatic rebalancing if the whole baseline topology is not recovered
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8241
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8241
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.4
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Critical
>             Fix For: 2.5
>
>         Attachments: BaselineWatcher.java
>
>
> The ticket is created as a result of the following discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Triggering-rebalancing-on-timeout-or-manually-if-the-baseline-topology-is-not-reassembled-td29299.html
> The rebalancing doesn't happen if one of the nodes goes down, 
> thus, shrinking the baseline topology. It complies with our assumption that 
> the node should be recovered soon and there is no need to waste 
> CPU/memory/networking resources of the cluster shifting the data around. 
> However, there are always edge cases. I was reasonably asked how to trigger 
> the rebalancing within the baseline topology manually or on timeout if: 
> * It's not expected that the failed node would be resurrected in the 
>    nearest time and 
> * It's not likely that that node will be replaced by the other one. 
> Until we embedd special facilities in the baseline topology that would consider such situations we can document the following workaround. A user application/tool/script has to subscribe to node_left events and remove the failed node from the baseline topology in some time. Once the node is removed, the baseline topology will be changed, and the rebalancing will be kicked off.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)