[
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981590#comment-15981590
]
ASF GitHub Bot commented on GEODE-2816:
---------------------------------------
GitHub user nabarunnag opened a pull request:
https://github.com/apache/geode/pull/476
GEODE-2816: Redundancy recovery inititiated even if redundancy set to 0
Potential reviewers
@upthewaterspout @jhuynh1 @gesterzhou @boglesby @ladyVader
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nabarunnag/incubator-geode feature/GEODE-2816
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/476.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #476
----
commit 074349cd03c3e19ea16ee80a6c257a6d7a7322b3
Author: nabarun <n...@pivotal.io>
Date: 2017-04-24T17:50:06Z
GEODE-2816: Redundancy recovery inititated even if redundancy set to 0
----
> Redundancy recovery must also kick in when redundancy recovery is set to 0
> ---------------------------------------------------------------------------
>
> Key: GEODE-2816
> URL: https://issues.apache.org/jira/browse/GEODE-2816
> Project: Geode
> Issue Type: Bug
> Components: regions
> Reporter: nabarun
> Assignee: nabarun
>
> Issue:
> In methods {noformat}scheduleRedundancyRecovery{noformat} and
> {noformat}initPRInternals{noformat} redundancy recovery is initiated only
> when redundancy is set to a value greater than zero.
> This leads to issues where a bucket is hosted in multiple datastores when the
> redundancy is set to 0 as redundancy recovery never removes the extra buckets.
> Solution:
> remove the checks where the redundancy recovery is initiated only when the
> redundancy is set to a value greater than 0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
