Hi Justin,
Yes.I agree that if we have shared store, we don't need to replication. But
it would good option to have jdbc (shared store) for lock only to avid the
split-brain issue as configuring 3 pair is not suitable for small
environment and 3 pairs add lot of complexity.
Thanks for the detail
> ...many people use the replication to avoid a spof with shared store and
also perf with NVMe...
Fair enough.
> I dont see why we would discourage anyone in implementing that.
For what it's worth, I didn't mean to discourage anybody from implementing
anything. I was mainly trying to answer his
Justin i disagree many people use the replication to avoid a spof with shared
store and also perf with NVMe , simply having a shared store just for the
filelock sounds entirely sensible to me. I dont see why we would discourage
anyone in implementing that.
Get Outlook for Android
On Mon, Oct
I'm not aware of any plans to implement what you suggest here. It seems to
me that if you want to mitigate the risk of split brain and you have access
to shared storage then you should just use a shared store configuration
instead of replication. The main benefit of replication that you don't need
Hi,
For small environment to use High availability, it is often difficult to
setup 3-pair cluster to avoid split-brain.
It would be great if artemis master and slave use data replication and use
shared store only for lock and providing HA . So anytime, master/slave
verifies and gets lock before t
