3 ms·
From the clustering page of the Wiki: "The pymq cluster is not designed to survive a master crash. If the master is to crash, all bets are off. However, client
by hawthornenigel 16y ago
From the clustering page of the Wiki:
"The pymq cluster is not designed to survive a master crash. If the master is to crash, all bets are off. However, clients that are already connected to the individual nodes can continue to operate normally. It's just that automatic failover and queue discovery won't work (which is basically what the master does)."
This is not fail-safe, unlike most enterprise messaging systems. Though you could stick the master on a VMware cluster with FT enabled and survive hardware failures, there is nothing preventing data loss from software or networking failures.
- dhruvbird 16y agoThe assumption is that the master isn't flaky. You can achieve this in multiple ways. One of them you mention. If the software is bad, you can't help it. As far as network failures are concerned, I think those are handled. If your network fails, you basically won't be able to send a message or won't get confirmation of it being sent. Either ways, if the queuing system works in at least once mode, you are guaranteed message delivery. If there is an error, the library reports an error and the application must re-try.