Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1747
I so first this doesnât mean that the replication needs to occur after
sync to disk. They can continue in parallel.
You simply want the slave to fsync before replying success of replication.
Also note this should be togglable with the current behaviour being default to
not effect existing users, who simply need to have protection from a single
failure in HA mode. eg you have to toggle this on if you want this.
Lastly Iâm not sure what this brings you still, as soon as slave
activates on master failure it fsyncs itâs journal to disk as part of
becoming active. you should note that if youâre actual requirement is you
want to protect from data loss in case of two node failure you can simply add
more slave nodes. So in case Master died, and then the first slave failed you
would still have the second slave with the data (and now active) and on
activation would fsync to disk.
---
