ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Lukyanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8210) Rebalancing sometimes is not triggered when a node is added to the baseline topology
Date Tue, 10 Apr 2018 17:59:00 GMT

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

Stanislav Lukyanov commented on IGNITE-8210:
--------------------------------------------

Simple example (see RebalanceAfterNodeAddedToBaseline.java attached) doesn't reproduce the
issue - data is properly rebalanced right after the node is added to the baseline.
A proper reproducer to follow.

> Rebalancing sometimes is not triggered when a node is added to the baseline topology
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8210
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8210
>             Project: Ignite
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Stanislav Lukyanov
>            Priority: Major
>         Attachments: RebalanceAfterNodeAddedToBaseline.java
>
>
> When a cluster already has baseline topology set and activated adding a new node to the
baseline should lead to rebalancing. However, in some cases the new node will not receive
any data when joined and added to the baseline; if a cluster is later deactivated and activated
again, the rebalancing happens properly and partitions are assigned and transferred to the
new node.



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

Mime
View raw message