[
https://issues.apache.org/jira/browse/ARTEMIS-2717?focusedWorklogId=425250&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425250
]
ASF GitHub Bot logged work on ARTEMIS-2717:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Apr/20 09:00
Start Date: 20/Apr/20 09:00
Worklog Time Spent: 10m
Work Description: franz1981 edited a comment on issue #3094:
URL: https://github.com/apache/activemq-artemis/pull/3094#issuecomment-616395639
@michaelandrepearce @brusdev
In the current state (after the refactoring) the only services exposed by
`QuorumManager` are:
- `registerQuorum`/`unRegisterQuorum`: to register/unregister a listener for
`nodeDown`/`nodeUP` events issued by `ClusterController::defaultLocator`. The
high-level function, looking at `SharedNothingBackupQuorumm`, is to detect a
change in the live role (ie live is going down)
- `isStillLive`: used by the live with `vote-on-replication-failure` to
validate that is still the live
- `hasLive`: used by the backup (on `SharedNothingBackupQuorumm`) to check,
after received a disconnection failure or a `nodeDown` event (see
`registerQuorum`/`unRegisterQuorum`), if there is any live in charge.
- `handleQuorumVote`: to manage `QuorumVoteMessage` packets, perform a vote
and send back a response. It's tied to `ClusterController` (again)
----------------------------------------------------------------
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: 425250)
Time Spent: 1h (was: 50m)
> Isolate the current Quorum Vote implementation
> ----------------------------------------------
>
> Key: ARTEMIS-2717
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2717
> Project: ActiveMQ Artemis
> Issue Type: Sub-task
> Components: Broker
> Reporter: Francesco Nigro
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> As a first step to design and implement the new Quorum Vote API is necessary
> to isolate the functionalities of the current one, to better understand what
> we're going to replace/change.
> From an high level perspective it means understanding the exact
> functionalities it's providing to support shared nothing HA, while from an
> implementation perspective it means to pack the current usage of the classes
> implementing it (eg QuorumManager) into higher abstraction level domain
> methods.
> This effort won't change the way the current Quorum Vote algorithm works
> hence it would be nice to make it part of the Artemis code before delivering
> the new pluggable implementation too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
