You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2013/06/19 17:47:20 UTC
[jira] [Updated] (QPID-4937) [Java Broker] Separate virtual host
implementations into different types
[ https://issues.apache.org/jira/browse/QPID-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-4937:
------------------------------
Issue Type: Improvement (was: Bug)
> [Java Broker] Separate virtual host implementations into different types
> ------------------------------------------------------------------------
>
> Key: QPID-4937
> URL: https://issues.apache.org/jira/browse/QPID-4937
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 0.23
>
>
> Replicating virtual hosts have different lifecycle properties to non-replicating virtual hosts. moreover different replication, storage and group leader election strategies may be employed by different implementations. Currently HA functionality - and in particular master election - is only able to be provided by the store (in line with how the BDB HA solution works). Instead we should make replication and failover a property of the virtual host and allow alternative implementations with alternative strategies
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org