[
https://issues.apache.org/jira/browse/ARTEMIS-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363325#comment-15363325
]
ASF subversion and git services commented on ARTEMIS-612:
---------------------------------------------------------
Commit 8154120027ba2b758ae3632204831247288bcc99 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=8154120 ]
ARTEMIS-612 Improving Failback's max replication
The server will always restart now, with older files being removed.
The system will now move current data into ./oldreplica.#, and remove old ones.
All the logic for moving these files is encapsulated at FileMoveManager.
> Replication should remove old files when MAX-replication is set
> ---------------------------------------------------------------
>
> Key: ARTEMIS-612
> URL: https://issues.apache.org/jira/browse/ARTEMIS-612
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 1.3.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 1.4.0
>
>
> Currently if there's a max set on the replication failback, the server will
> not be activated.
> Instead the system should remove older folders and keep running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
