[JBoss JIRA] Updated: (JBCLUSTER-68) enhance farm deployment to handle cluster partitioning and merging
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-68?page=all ]
Brian Stansberry updated JBCLUSTER-68:
--------------------------------------
Fix Version/s: Q1Y7
(was: Q3Y6)
Move to Q1 '07 as we may get a chance to make farming improvements in 4.0.x next year.
> enhance farm deployment to handle cluster partitioning and merging
> ------------------------------------------------------------------
>
> Key: JBCLUSTER-68
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-68
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Scott Marlow
> Assigned To: Scott Marlow
> Priority: Optional
> Fix For: Q1Y7
>
>
> Handle partitions and merges. Here's a use case:
> * Group is {A,B,C,D,E}
> * Partition occurs
> * Groups are now {A,B,C} and {D,E}
> * User drops WAR into E
> * D and E will have WAR
> * Partition heals, merge occurs
> o Group is now {A,B,C,D,E}
> * A,B,C don't have the WAR, D and E have it
> We could possibly use the same algorithm we use to reconcile this when D
> and E were offline and a user dropped the WAR into E's ./farm dir.
--
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
18 years, 1 month
[JBoss JIRA] Updated: (JBCLUSTER-25) HA JMS
by Brian Stansberry (JIRA)
[ http://jira.jboss.com/jira/browse/JBCLUSTER-25?page=all ]
Brian Stansberry updated JBCLUSTER-25:
--------------------------------------
Fix Version/s: Q4Y6
(was: Q3Y6)
> HA JMS
> ------
>
> Key: JBCLUSTER-25
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-25
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Brian Stansberry
> Fix For: Q4Y6
>
>
> Currently JBossMQ is using HA-Singleton for limited high availbility. There is no fail over for state, per se.
> We don't have plan to enhance any HA in JBossMQ (4.0x release).
> Ovidiu's new messaging system has a built-in high-availbility capability in there through the servless nature of the system. So when his new system is ready for JMS, this piece should be built in.
> Remaining issues are to integrate with the current clustering framework.
--
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
18 years, 1 month