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

2017-04-24 Thread ASF GitHub Bot (JIRA) 

[ 
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 
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)

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

2017-04-26 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985550#comment-15985550
 ] 

ASF subversion and git services commented on GEODE-2816:


Commit 70340783a4617f141b937ee960a0a373ebe0f46e in geode's branch 
refs/heads/develop 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)

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

2017-04-26 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985559#comment-15985559
 ] 

ASF GitHub Bot commented on GEODE-2816:
---

Github user nabarunnag closed the pull request at:

https://github.com/apache/geode/pull/476


> 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)

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

2017-04-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987089#comment-15987089
 ] 

ASF subversion and git services commented on GEODE-2816:


Commit c1a69140792b1d23ab9c467bb54c746550368b60 in geode's branch 
refs/heads/feature/GEM-1299 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c1a6914 ]

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)

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

2017-04-27 Thread ASF subversion and git services (JIRA) 

[ 
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)

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

2017-04-28 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989610#comment-15989610
 ] 

ASF subversion and git services commented on GEODE-2816:


Commit 84e36d558e92b3d722a7e4c6df2439a72ea8f218 in geode's branch 
refs/heads/feature/GEODE-2852 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=84e36d5 ]

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)