slight followup to my own question here,
assuming we had a pure master/slave setup and the master dies, we then:
1) stop slave
2) copy files from slave to master
3) delete files from slave?
4) start master
5) (since clients were sitting the retrying, they'll connect and start
sending before slav
true, but I was shooting for zero message loss and reasonably high
performance with no single points of failure
shared db will put us right back at single point of failure(db) that we're
looking to avoid with MasterSlave
On 5/4/07, Hiram Chirino <[EMAIL PROTECTED]> wrote:
If you use a shared D
If you use a shared DB or file system you should be able to failover
and fail back without a problem.
On 5/4/07, David Budworth <[EMAIL PROTECTED]> wrote:
I mistakenly hijacked another thread yesterday when asking this, so I'll
repost it as it's own thread.
If I understand the wiki and comments
I mistakenly hijacked another thread yesterday when asking this, so I'll
repost it as it's own thread.
If I understand the wiki and comments I've read on this list recently, AMQ
has no state synchronizer.
Meaning that if I have Master / Slave and the Master dies, i can't restart
it without stopp
