You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timo Kanera (JIRA)" <ji...@apache.org> on 2016/12/06 11:11:36 UTC

[jira] [Commented] (AMQ-5619) logSize does not work with Replicated LevelDB store

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

Timo Kanera commented on AMQ-5619:
----------------------------------

Did anyone have a chance to look into this one yet? I just tried the logSize parameter on a replicated levelDB store on 5.14.1 and it still doesn't seem to have any effect.

> logSize does not work with Replicated LevelDB store
> ---------------------------------------------------
>
>                 Key: AMQ-5619
>                 URL: https://issues.apache.org/jira/browse/AMQ-5619
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.11.0, 5.11.1
>         Environment: Linux
>            Reporter: Artem Karpenko
>
> Setting logSize to anything lower than 100MB does not change actual size of log file that is created by LevelDB. Removing the whole data directory and starting from scratch does not help.
> {code}
>  <replicatedLevelDB directory="${activemq.data}/replicatedLevelDB"
>                                 replicas="3"
>                                 bind="tcp://0.0.0.0:61619"
>                                 zkAddress="instance-6:2181"
>                                 zkPath="/activemq/leveldb-stores"
>                                 hostname="instance-7" />
> {code}
> The attribute does work with {{levelDB}} persistence adapter though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)