I am using activmq 5.9.0.
Is there a way to get the storage limit check to take into consideration the
~60G already used for AMQ storage? so that it doesn't block every producer?
My experience with the issue:
I have a storage limit set using the following parameters:
<systemUsage>
<systemUsage>
<storeUsage>
<storeUsage limit="100 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="100 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
On my file system I have the following usage:
Filesystem
Size Used Avail Use% Mounted on
amq
100G 60G 41G 60% /amqdata
On start up I have the following message:
2013-11-21 12:23:21,752 | WARN | Store limit is 102400 mb, whilst the data
directory: /amqdata/shared-data only has 41492 mb of usable space -
resetting to maximum available disk space: 41492 mb |
org.apache.activemq.broker.BrokerService | WrapperSimpleAppMain
At this point every message
2013-11-21 14:36:02,562 | INFO |
Usage(default:store:queue://InteractionActivity.queue:store)
percentUsage=105%, usage=45972489618, limit=43539333120,
percentUsageMinDelta=1%;Parent:Usage(default:store) percentUsage=105%,
usage=45972489618, limit=43539333120, percentUsageMinDelta=1%: Persistent
store is Full, 100% of 43539333120. Stopping producer
(ID:server-46888-1384963965247-7:1:110387:1) to prevent flooding
queue://InteractionActivity.queue. See
http://activemq.apache.org/producer-flow-control.html for more info
(blocking for: 6522s) | org.apache.activemq.broker.region.Queue | ActiveMQ
NIO Worker 5
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Storage-Limit-doesn-t-take-into-consideration-existing-AMQ-Storage-tp4674732.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
