Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Date: Sun, 16 Oct 2016 12:27:14 -0700 (PDT)
From: Shobhana <shobhana@quickride.in>
To: users@activemq.apache.org
Message-ID: <1476646034325-4717977.post@n4.nabble.com>
In-Reply-To: <CAPVVMa8vQ3Ao799bRxDfEx-AQovG9XMYtN87do4vMrYeQa09mg@mail.gmail.com>
References: <D406E440.B2A2E%shill@armada.net> <d7ed3913-38be-fda4-b8ad-34fd1f919e76@futurelogix.co.uk> <bd9a9689-eed7-d0e9-116f-f1fa9f02ce93@futurelogix.co.uk> <CAPVVMa8pL=Yk0XeBvdsW5=JLmffdDxqjV71WfJrT5qbYS_Fo4g@mail.gmail.com> <CAPVVMa_hGrcPT+Kf1rGP-sqJ8mKCPUZn4hwG5xcS3bA5nHJ8_Q@mail.gmail.com> <f39622b9-e5d8-5d5e-4912-a06022151c0b@futurelogix.co.uk> <ADA41E52-AF7B-4FB2-9C52-3C8748870081@su.se> <CAPVVMa_6_e3ReL337WFm33a_VP-CHgpC0d59Qn9za2t_sVfrjQ@mail.gmail.com> <FAAD71A0-FD09-485D-8309-575385017370@su.se> <CAPVVMa8vQ3Ao799bRxDfEx-AQovG9XMYtN87do4vMrYeQa09mg@mail.gmail.com>
Subject: Re: KAHADB clean up old log files
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Sun, 16 Oct 2016 19:34:55 -0000

Sorry about adding to somebody else's thread.... I am adding here since I see
same issue in our production server.

We use 5.14.0 version and I have already enabled DLQ to discard all expired
messages and also set expiry of 1 day to all messages (MQTT) and offline
durable consumers using the following configurations :

a) I enabled following plug-in to set expiry of 1 day for every message (we
use only MQTT messages) : 
<plugins>
  <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true"
dropTemporaryQueues="true" />
        <timeStampingBrokerPlugin ttlCeiling="86400000"
zeroExpirationOverride="86400000"/>
</plugins>

b) I enabled DLQ to drop all expired messages for all topics and queues : 
    <deadLetterStrategy>
          <sharedDeadLetterStrategy processExpired="false" />
    </deadLetterStrategy>

<discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true"
dropTemporaryQueues="true" />

c) I enabled offline durable subscribers to timeout after 1 day : 
offlineDurableSubscriberTimeout="86400000"
offlineDurableSubscriberTaskSchedule="3600000" 

After these changes, I could see a few log files got deleted, but majority
of the log files remain in the Kahadb folder which consume lot of disk
space. 

I observed this in our production server where I cannot enable trace or JMX.
Is there any other way to identify what is causing this issue?

TIA,
Shobhana


--
View this message in context: http://activemq.2283324.n4.nabble.com/KAHADB-clean-up-old-log-files-tp4716661p4717977.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.