[
https://issues.apache.org/jira/browse/ARTEMIS-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613485#comment-16613485
]
ASF GitHub Bot commented on ARTEMIS-2075:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2293
@andytaylor Cherry-pick on this doesn't work. Quite a few conflicts.
You have two options:
I - you do the cherry-pick yourself:
```
git checkout 2.6.x
git cherry-pick -x 3b34127bb3ce6720ff794551a2877ba9794f0960
```
resolve the conflits yourself:
```
git push apache 2.6.x
```
or II:
Do the cherry-pick like I, and send a pull request into 2.6.x. at that
point it would be a simple merge.
I would prefer I, as Pull Requests don't automatically close unless it's a
simple merge (no rebase involved).
> Extra backups only try to replicate once
> ----------------------------------------
>
> Key: ARTEMIS-2075
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2075
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.6.3
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Priority: Major
> Fix For: 2.7.0, 2.6.4
>
>
> If a backup starts and it turns out there are no live brokers to replicate
> from it will wait until one comes online. However if a current live stops
> being replicated it is not retried. th passive backup should retry after a
> specific wait time and try all the servers available again.
>
> this is to cover the following scenario
>
> # live comes up
> # 2. backup comes up and replicates
> # another backup comes up and fails to replicate as there are no lives
> # 1st backup stops
> At this point the backup needs to retry to find a live, this is the code ive
> added
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
