[ 
https://issues.apache.org/jira/browse/ARTEMIS-2702?focusedWorklogId=416809&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-416809
 ]

ASF GitHub Bot logged work on ARTEMIS-2702:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Apr/20 18:07
            Start Date: 06/Apr/20 18:07
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on issue #3068: ARTEMIS-2702 
QuorumVoteServerConnect with requestToStayLive is voting order sensitive
URL: https://github.com/apache/activemq-artemis/pull/3068#issuecomment-609951227
 
 
   I've sent a second commit that (assuming that I've correctly understood the 
original logic) simplify the current logic. @clebertsuconic @jbertram 
@andytaylor please take a look at the 2 commits separately, if I've 
misunderstood how `QuorumVoteServerConnect` is supposed to work...
   
   In addition: I see that we should check for `targetNodeId` vs 
`ServerConnectVote::getNodeId` on `QuorumVoteServerConnect::vote` too 
(probably).
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 416809)
    Time Spent: 0.5h  (was: 20m)

> QuorumVoteServerConnect with requestToStayLive is voting order sensitive
> ------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2702
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2702
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Francesco Nigro
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> QuorumVoteServerConnect with requestoToStayLive should perform the same 
> correct decision regardless the order of a negative votes: this could affect 
> the vote-on-replication-failure functionality if an unlucky timing of vote 
> would happen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to