You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgenii Zhuravlev (JIRA)" <ji...@apache.org> on 2017/06/20 09:19:00 UTC
[jira] [Commented] (IGNITE-5399) Manual cache rebalancing feature
is broken
[ https://issues.apache.org/jira/browse/IGNITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055426#comment-16055426 ]
Evgenii Zhuravlev commented on IGNITE-5399:
-------------------------------------------
Tc: http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&branch_Ignite20Tests=pull%2F2158%2Fhead
PR: https://github.com/apache/ignite/pull/2158
> Manual cache rebalancing feature is broken
> ------------------------------------------
>
> Key: IGNITE-5399
> URL: https://issues.apache.org/jira/browse/IGNITE-5399
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.8, 1.9, 2.0
> Reporter: Andrew Mashenkov
> Assignee: Evgenii Zhuravlev
> Priority: Critical
> Fix For: 2.2
>
> Attachments: ManualRebalanceBug.java
>
>
> Cache.rebalance() javadoc says "Future that will be completed when rebalancing is finished". But it is not true.
> 1. The method return value is Object, however actually it is Boolean and it is not obvious.
> 2. Future.get() return true if rebalance is finished, but can return false and reschedule rebalancing. So, control can return to thread before rebalancing even started.
> 3. Spinning on rebalance().get() until it true will not help. Seems like rebalance either restarted (1.9) or hanged (2.0).
> PFA repro attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)