-
1. Re: HA without SAN?
ataylor Jul 20, 2011 8:51 AM (in response to billy.sjoberg)1 of 1 people found this helpfulReplication is currently disabled in the current version, we are in the process of reenabling it and it will be in the next release
-
2. Re: HA without SAN?
billy.sjoberg Jul 20, 2011 9:15 AM (in response to ataylor)That was a very quick answer Andy, thanks for the info!
Ok, it starts to make sense to me now as I've seen discussions regarding the replication feature but it's not reflected in the latest manual.
Reading an old manual (eg. http://hornetq.sourceforge.net/docs/hornetq-2.0.0.CR1/user-manual/en/html/ha.html) this makes sense.
But this snippet is worrying me though:
"One a live server has failed over onto a backup server, the old live server becomes invalid and cannot just be restarted. To resynchonize the pair as a working live backup pair again, both servers need to be stopped, the data copied from the live node to the backup node and restarted again.
The next release of HornetQ will provide functionality for automatically synchronizing a new backup node to a live node without having to temporarily bring down the live node."
Is the reason why you chose to remove it in order to rework it completely?
If so, would the new functionality synchronize delivered messages while the primary was out as well in order to not duplicate messages?
Say i.e. that
- A had 50 undelivered persistent msgs in different queues during server crash
- B becomes active and respective consumers picks up all messages
- Failback occurs as A is fixed/restarted
- A synchronizes deliveries performed by B, meaning that the messages won't be duplicated and redelivered?
-
3. Re: HA without SAN?
ataylor Jul 20, 2011 9:18 AM (in response to billy.sjoberg)Is the reason why you chose to remove it in order to rework it completely?
Yes amongst others, including dealing with split brain etc
If so, would the new functionality synchronize delivered messages while the primary was out as well in order to not duplicate messages?
Say i.e. that
- A had 50 undelivered persistent msgs in different queues during server crash
- B becomes active and respective consumers picks up all messages
- Failback occurs as A is fixed/restarted
- A synchronizes deliveries performed by B, meaning that the messages won't be duplicated and redelivered?
what would happen is that on restart server A wouls start receiving replication packets from node B until it was synched, once this had happened failback would occur.