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

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

                Author: ASF GitHub Bot
            Created on: 28/Jun/21 18:45
            Start Date: 28/Jun/21 18:45
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-869929829


   Yep, that's already implemented using the "namespace" parameter of the 
manager, but I would like to already separate locks from "others" (journal 
timestamps or any other primitives we will need in the future)


-- 
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: 615745)
    Time Spent: 23h 10m  (was: 23h)

> 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: 23h 10m
>  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)

Reply via email to