activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-914) Max saved replicated journal size on Live node should not be -1
Date Tue, 10 Jan 2017 16:24:58 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815410#comment-15815410
] 

Justin Bertram commented on ARTEMIS-914:
----------------------------------------

Can you elaborate on this a bit more?  {{org.apache.activemq.artemis.core.deployers.impl.FileConfigurationParser#createReplicaHaPolicy}}
reads {{max-saved-replicated-journals-size}} from the XML and the default is 2 (see {{org.apache.activemq.artemis.api.config.ActiveMQDefaultConfiguration#DEFAULT_MAX_SAVED_REPLICATED_JOURNALS_SIZE}}).
 Where do you see this value hard-coded to -1?

> 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)

Mime
View raw message