[
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987257#comment-15987257
]
ASF subversion and git services commented on GEODE-2816:
--------------------------------------------------------
Commit 70340783a4617f141b937ee960a0a373ebe0f46e in geode's branch
refs/heads/feature/GEM-1299 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=7034078 ]
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)