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

Posted to issues@geode.apache.org by "Anilkumar Gingade (Jira)" <ji...@apache.org> on 2022/06/08 16:32:00 UTC

[jira] [Resolved] (GEODE-10350) volunteerForPrimary should proceed when being elector or knowing elector

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

Anilkumar Gingade resolved GEODE-10350.
---------------------------------------
    Resolution: Abandoned

The issue was created based on the assumption that the elector was not properly set/used. The planned change (PR in this ticket) is causing issue with Fixed partitioning. We need to understand more about the primary logic. Closing this issue for now.

> volunteerForPrimary should proceed when being elector or knowing elector
> ------------------------------------------------------------------------
>
>                 Key: GEODE-10350
>                 URL: https://issues.apache.org/jira/browse/GEODE-10350
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Xiaojian Zhou
>            Assignee: Joris Melchior
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>
> Inside BucketAdvisor.volunteerForPrimary(), when current member is elector or has profile for elector, then current member should proceed to volunteer for primary bucket. 
> Current logic happened to be opposite. It might be due to careless code. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)