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

Justin Bertram resolved ARTEMIS-3344.
-------------------------------------
    Resolution: Abandoned

> Embedding Zookeeper for Pluggable Quorum Vote 
> ----------------------------------------------
>
>                 Key: ARTEMIS-3344
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3344
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>
> One of the nicer things of the Atomix RI, last minute dropped because of lack 
> of OSS community, related to the single pair use case, was the ability to 
> achieve a sufficient number of nodes in order to prevent split-brain just by 
> adding a "witness" node (without being a full-fat broker) to the existing 
> primary/backup ones.
> It was possible because each broker node was already an active member of the 
> quorum and able to participate to quorum votes.
> This was saving users to configure any external service and just care about 
> brokers and their reachability, on topology setup.
> Providing a similar behavior for Apache Curator/Zookeeper quorum vote RI 
> means:
> * exposing some hook/map all the relevant configuration bits of Zookeeper 
> * consider the performance/stability hit and memory requirements changes 
> while embedding a potentially "noisy" neighbor (network I/O, disk I/O, CPU 
> and java heap/memory-wise)
> There are few ways to achieve embedding ZK:
> # as a proper quorum service in the broker
> # by impl some plugin that treat it as an external service to be run along 
> the broker
> The latter approach is way less invasive because users can just implement 
> such plugin deciding what/which bits configure and expose.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to