Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 6 Dec 2016 14:21:03 +0000 (UTC)
From: "clebert suconic (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12754629.1415750005000.450410.1481034063517@Atlassian.JIRA>
In-Reply-To: <JIRA.12754629.1415750005000@Atlassian.JIRA>
References: <JIRA.12754629.1415750005000@Atlassian.JIRA> <JIRA.12754629.1415750005897@arcas>
Subject: [jira] [Updated] (ARTEMIS-30) allow backup servers to service
 multiple live servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 14:21:12 -0000


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

clebert suconic updated ARTEMIS-30:
-----------------------------------
    Fix Version/s:     (was: 1.5.1)
                   1.6.0

> allow backup servers to service multiple live servers
> -----------------------------------------------------
>
>                 Key: ARTEMIS-30
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-30
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: clebert suconic
>             Fix For: 1.6.0
>
>
> 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)