You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by "nabarun (JIRA)" <ji...@apache.org> on 2017/05/02 18:02:04 UTC

[jira] [Resolved] (GEODE-2816) Redundancy recovery must also kick in when redundancy recovery is set to 0

     [ https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nabarun resolved GEODE-2816.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.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
>             Fix For: 1.2.0
>
>
> 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)