Yes if you have a ton of data on a durable subscription and delete the durable it tends to write a large temp file because of the kahadb index. Even though the temp file should be deleted automatically after deletion this is certainly not ideal.
Right now there isn't really a good way to discard all of the messages other than the current deletion. I've been working on a prototype for purging a durable subscription that works similar to how purge works for a Queue in that it iterates over the messages and acks them one by one so it doesn't blow memory trying to delete them all at once. I haven't added it to the broker yet but it seems to work ok in my local testing and is something I can probably add to the 5.15.0 release. Also in regards to the inactive durable sub using up all of the memory, that's something else I want to improve in 5.15.0. If you look at the discussion from https://issues.apache.org/jira/browse/AMQ-4467 from the last couple of days this issue came up. One solution discussed is purging an inactive destination from the in memory cache (but not from the store) to save memory for other destinations. On Wed, Jan 11, 2017 at 8:19 AM, xabhi <xabh...@gmail.com> wrote: > Hi, > > Yes these log messages appeared at the startup only. I had faced an issue > where activemq dumped 7gb file - tx-14693130-1483907222896.tmp in one of > the mkahadb directories when i tried to destroy a durable topic consumer > which was inactive for quite some time and had hit the memory threshold of > 70% (this was causing activemq to be unresponsive). I removed this file > manually and when failover switch happened I saw above log messages in log > file. > > Is there a clean way to discard all the messages in durable topic > subscription without dumping a 7gb file? > > Thanks, > Abhishek > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Ignoring-sub-command-log-messages-tp4720928p4720974.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
