[
https://issues.apache.org/jira/browse/ARTEMIS-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818953#comment-15818953
]
ASF GitHub Bot commented on ARTEMIS-914:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/957
ARTEMIS-914 use defaults for ReplicaPolicy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis master_work
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/957.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #957
----
commit 5da9a71c611ebe62a131188a3f1838b0ac10ff19
Author: Justin Bertram <[email protected]>
Date: 2017-01-11T17:40:13Z
ARTEMIS-914 use defaults for ReplicaPolicy
----
> Max saved replicated journal size on Live node should not be -1
> ---------------------------------------------------------------
>
> Key: ARTEMIS-914
> URL: https://issues.apache.org/jira/browse/ARTEMIS-914
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.1
> Reporter: Erich Duda
> Assignee: Justin Bertram
>
> The max-saved-replicated-journal-size on Live node is {{-1}} what can lead to
> fill the disk by old replicas. The value is hard coded in Artemis code and
> cannot be changed. I think the default value should be some small number,
> e.g. 2.
> I hit this issue with Wildfly. There are plans to update Artemis in Wildfly
> to 1.5.2 version. It would be great if the fix was included in 1.5.2 release.
> Thanks :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
