Github user bgutjahr commented on the issue:
https://github.com/apache/activemq-artemis/pull/1204
So what's your suggestion? Is it OK to change the semantics and should I
adapt the failing test cases?
Or is this rather a new feature? I could either add new option to
SharedStoreMasterPolicyConfiguration and related config files (but I don't have
a good name for that option), or a new SharedStorePolicyConfiguration class
with the new semantics of: become master if no master is running, otherwise
become backup. No failback, always failover on server shutdown (since all
servers are treated equal, none of them is a dedicated master).
Thinking about this, my personal favorite would be the new policy class and
leaving the existing semantics unchanged. I could go for that, if you agree.
What we actually want it this: run the artemis bus on two servers with a
started store. Whichever is started first shall become master, the other
backup. But we need to have the start method return in any case, to know that
startup is completed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
