[
https://issues.apache.org/jira/browse/QPID-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112406#comment-15112406
]
Keith Wall commented on QPID-7016:
----------------------------------
This has highlighted a case where
{{EnvironmentConfig.CLEANER_ADJUST_UTILIZATION=true}} (the default for 5.0.104)
has had a negative consequence. The automated adjustment process put the
cleaner into a state where no further cleaning was done. JE's javadocs for
{{EnvironmentConfig.CLEANER_ADJUST_UTILIZATION}} state that there are some
cases where this setting should be turned off.
I read that in JE 6.0 onwards
(http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/EnvironmentConfig.html#CLEANER_ADJUST_UTILIZATION)
bq. in JE 6.3. Adjustments are no longer needed because LN log sizes have been
stored in the Btree since JE 6.0.
> BDB JE cleaner can make no progress allowing for unbounded store growth
> -----------------------------------------------------------------------
>
> Key: QPID-7016
> URL: https://issues.apache.org/jira/browse/QPID-7016
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Priority: Critical
>
> A user on a 0.32 derivative (including QPID-6734 and using BDB JE 5.0.104)
> encountered a problem where the store continued to grow (3GB per hour) even
> though messages were not accumulating within the Broker.
> Analysis with the showed the the BDB JE cleaner was making no progress and in
> particular, JE's getEnvironmentStats() revealed that lnSizeCorrectionFactor
> had fallen to 0.079. On restarting the Broker, the store size shrunk back to
> a normal size. (Java Broker's Recovery evicted no messages).
> More details here:
> https://community.oracle.com/message/13647939#13647939
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
