[ 
https://issues.apache.org/jira/browse/AMQ-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Nagy updated AMQ-4851:
-----------------------------

    Description: 
It's possible to specify absolute values to storeUsage and tempUsage in bytes 
and usage percent to storeUsageHighWaterMark in per destination policies.
I would like to set them the other way: set storeUsage to a relative (percent) 
value and limit a queue to given bytes.
The rationale behind this: I use a compressed file system, which compresses 
messages more or less, depending on their actual contents.
The ability to set storeUsage to a percent value (similar to its counterpart 
percentOfJvmHeap) would help to match the reality closer.
Also, I would like to limit queues to an absolute value, like -eg- 1 GiB, not 3 
percent of 70% of a compressible file system, which can mean anything.

AMQ currently doesn't allow raising the limit above the file system capacity:
2013-11-06 12:39:39,247 | WARN  | Store limit is 51200 mb, whilst the data 
directory: /data/activemq/leveldb only has 50092 mb of usable space - resetting 
to maximum available disk space: 50092 mb | 
org.apache.activemq.broker.BrokerService | main
however, with my average messages, the file system compression ratio is above 
4x, meaning that AMQ could write nearly 200 GiB to it.

  was:
It's possible to specify absolute values to storeUsage and tempUsage in bytes 
and usage percent to storeUsageHighWaterMark in per destination policies.
I would like to set them the other way: set storeUsage to a relative (percent) 
value and limit a queue to given bytes.
The rationale behind this: I use a compressed file system, which compresses 
messages more or less, depending on their actual contents.
The ability to set storeUsage to a percent value (similar to its counterpart 
percentOfJvmHeap) would help to match the reality closer.
Also, I would like to limit queues to an absolute value, like -eg- 1 GiB, not 3 
percent of 70% of a compressible file system, which can mean anything.


> Ability to set percent and exact values to storeUsage, tempUsage and per 
> destination policies
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4851
>                 URL: https://issues.apache.org/jira/browse/AMQ-4851
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, Message Store
>    Affects Versions: 5.9.0
>            Reporter: Attila Nagy
>            Priority: Minor
>
> It's possible to specify absolute values to storeUsage and tempUsage in bytes 
> and usage percent to storeUsageHighWaterMark in per destination policies.
> I would like to set them the other way: set storeUsage to a relative 
> (percent) value and limit a queue to given bytes.
> The rationale behind this: I use a compressed file system, which compresses 
> messages more or less, depending on their actual contents.
> The ability to set storeUsage to a percent value (similar to its counterpart 
> percentOfJvmHeap) would help to match the reality closer.
> Also, I would like to limit queues to an absolute value, like -eg- 1 GiB, not 
> 3 percent of 70% of a compressible file system, which can mean anything.
> AMQ currently doesn't allow raising the limit above the file system capacity:
> 2013-11-06 12:39:39,247 | WARN  | Store limit is 51200 mb, whilst the data 
> directory: /data/activemq/leveldb only has 50092 mb of usable space - 
> resetting to maximum available disk space: 50092 mb | 
> org.apache.activemq.broker.BrokerService | main
> however, with my average messages, the file system compression ratio is above 
> 4x, meaning that AMQ could write nearly 200 GiB to it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to