[
https://issues.apache.org/jira/browse/ARTEMIS-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815436#comment-15815436
]
Erich Duda commented on ARTEMIS-914:
------------------------------------
Sorry I forgot to mention that. I think the value is hard-coded in \[1\] and
\[2\].
\[1\]
https://github.com/apache/activemq-artemis/blob/1.5.1/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/ha/ReplicatedPolicy.java#L51
\[2\]
https://github.com/apache/activemq-artemis/blob/1.5.1/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/ha/ReplicatedPolicy.java#L125
> 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
>
> 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)
