[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=615106&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-615106
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jun/21 17:06
Start Date: 25/Jun/21 17:06
Worklog Time Spent: 10m
Work Description: michaelandrepearce edited a comment on pull request
#3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-868704324
Well why shouldn't it try for ever to connect. In both situations. All you
are doing by it not is making it manual intervention which you operationally
want to not do. And what is an operator to do. Restart it.... so your not
getting any win.
A system should ideally always just self heal and until it does continue
trying. Imo
Obviously people have different opinions here, so make it configurable this
way if someone doesnt wish it to keep trying they can set that and vice versa.
Just as with client failover completely optional if it fails first go, 15th go
or never stops trying its users choice.
--
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: 615106)
Time Spent: 17h 20m (was: 17h 10m)
> 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: 17h 20m
> 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)
