[ 
https://issues.apache.org/jira/browse/ACTIVEMQ6-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

clebert suconic updated ACTIVEMQ6-30:
-------------------------------------
    Description: 
On this you could have a number of backup Nodes (M) serving a number of live 
Nodes (N)

On that scenario you would always have N+M nodes. you would only support M 
lives failing on this scenario.

Right now a backup can only support one live. With this we would allow it to 
serve multiple lives.

I'm not sure yet if this applies to replication as well. It's easy to be 
implemented with shared storage. We will need to investigate if this makes 
sense with replication or not. (To be discussed during design discussions 
before the implementation)


  was:
We called this as N+M Backup with shared storage, but the same policy could be 
applied with replication.

You have a few nodes elected to be backups. Say you have for example 3 nodes as 
dedicated backups (M) for 10 live nodes (N), resulting in N+M nodes.

We could implement the same using replication? That point is optional though.. 
depending on the design we could ellect to implement this only for shared 
storage options.


> allow backup servers to service multiple live servers
> -----------------------------------------------------
>
>                 Key: ACTIVEMQ6-30
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-30
>             Project: Apache ActiveMQ 6
>          Issue Type: New Feature
>            Reporter: clebert suconic
>
> On this you could have a number of backup Nodes (M) serving a number of live 
> Nodes (N)
> On that scenario you would always have N+M nodes. you would only support M 
> lives failing on this scenario.
> Right now a backup can only support one live. With this we would allow it to 
> serve multiple lives.
> I'm not sure yet if this applies to replication as well. It's easy to be 
> implemented with shared storage. We will need to investigate if this makes 
> sense with replication or not. (To be discussed during design discussions 
> before the implementation)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to