[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=616039&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-616039
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jun/21 08:05
Start Date: 29/Jun/21 08:05
Worklog Time Spent: 10m
Work Description: franz1981 edited a comment on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-870285487
@michaelandrepearce @gtully
I have both added the ZK default locks path (but I'm playing with ZK to see
if it satisfies me) and the warning for users mentioning the upstream JIRA that
explain the data misalignment issue.
I'm going to add a doc JIRA to produce some meaningful mitigation actions
for replication in general, given that `classic` replication is affected by
this, but is very unlikely that's gonna be fixed.
I used this `manager` configuration:
```java
<manager>
<properties>
<property key="connect-string"
value="localhost:2181" />
<property key="namespace"
value="artemis_test" />
</properties>
</manager>
```
And using the ZK Cli cmd:
```
[zk: localhost:2181(CONNECTED) 16] ls
/artemis_test/locks/f2ed3b55-d8ac-11eb-9420-8cc68169c75b/leases
[_c_d3b7e156-7599-4125-b891-0ebca91d3e63-lease-0000000000]
```
Where `f2ed3b55-d8ac-11eb-9420-8cc68169c75b` is a broker NodeID: it seems ok
to me.
If in the follow-up PRs we're gonna expose counters/mutable longs holding
the journal/data versioning/timestamp with the same NodeID it would look like
```
/artemis_test/mutable_longs/f2ed3b55-d8ac-11eb-9420-8cc68169c75b
```
That looks ok to me (name `mutable_longs` is temporary).
--
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: 616039)
Time Spent: 23h 40m (was: 23.5h)
> 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 40m
> 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)
