[
http://jira.jboss.com/jira/browse/JBMESSAGING-1230?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1230:
--------------------------------------
This is a tricky one.
The problem is that some customers want
1) Clean shutdown to *not* cause failover - since they don't want all their messages
bunching up on one node
But other customers:
2) Clean shutdown to cause failover as expressed in this task.
So if we always have one kind of behaviour (whatever it is) we alienate some users.
Solution seems to me to add an attribute on the post office
"enableFailoverOnShutdown" which defaults to false (current behaviour) but if
set to true will cause failover to occur when a node is shutdown.
Client failover support if one node of a cluster is cleanly shut
down.
----------------------------------------------------------------------
Key: JBMESSAGING-1230
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1230
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
If one node of a cluster fails in someway, the client will attempt to failover
transparently. However, if one node is shutdown cleanly, the client will not
automatically failover to another node in the cluster. This functionality would be very
useful for "rolling upgrades" where a portion of the cluster is left up while
the other nodes are being updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira