[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=615604&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-615604
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jun/21 13:39
Start Date: 28/Jun/21 13:39
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-869693805
@michaelandrepearce I hear you. there is more work to do for sure, but it
won't be in any way easier to shoot ones self in the foot with these changes.
It is all about collaboration, it is difficult to get folks to commit to
code on a PR or even a feature branch.
The reality is that If it is not on main, it does not exist.
This feature is ripe for collaboration because it pulls in a distributed
lock service, getting more users of that would be great to shape the API. The
journal exclusive lock is just one use case (all be it an important one).
--
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.
To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 615604)
Time Spent: 21.5h (was: 21h 20m)
> Implements pluggable Quorum Vote
> --------------------------------
>
> Key: ARTEMIS-2716
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2716
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Attachments: backup.png, primary.png
>
> Time Spent: 21.5h
> Remaining Estimate: 0h
>
> This task aim to ideliver a new Quorum Vote mechanism for artemis with the
> objectives:
> # to make it pluggable
> # to cleanly separate the election phase and the cluster member states
> # to simplify most common setups in both amount of configuration and
> requirements (eg "witness" nodes could be implemented to support single
> master-slave pairs)
> Post-actions to help people adopt it, but need to be thought upfront:
> # a clean upgrade path for current HA replication users
> # deprecate or integrate the current HA replication into the new version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
