You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/06/27 17:02:00 UTC
[jira] [Commented] (GEODE-6925) Added DUnit test to verify behavior
of repeated rebalance operations
[ https://issues.apache.org/jira/browse/GEODE-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874346#comment-16874346 ]
ASF subversion and git services commented on GEODE-6925:
--------------------------------------------------------
Commit 0736e1509601488d2fa042ad3e4bb91c572004cc in geode's branch refs/heads/develop from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0736e15 ]
Added DUnit test to verify behavior of repeated rebalance operations (#3737)
GEODE-6925: Added DUnit test to verify behavior of repeated rebalance operations
Co-authored-by: Benjamin Ross <br...@pivotal.io>
Co-authored-by: Donal Evans <do...@pivotal.io>
> Added DUnit test to verify behavior of repeated rebalance operations
> --------------------------------------------------------------------
>
> Key: GEODE-6925
> URL: https://issues.apache.org/jira/browse/GEODE-6925
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: xiaojian zhou
> Priority: Major
>
> There have been reports that rebalance is often run multiple times in rapid succession to assure the desired result is achieved, but an immediate second rebalance shouldn't produce a different result on a region if rerun before additional region operations are performed. Since we don't have any artifacts on a reproduction of this issue, we were unable to reproduce it ourselves but this test contributes to the coverage of rebalance and may help us diagnose this issue in the future if it appears.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)