[jira] [Resolved] (AMQ-6441) Incorrect File System Size Reported with Amazon Elastic File System (EFS)

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully resolved AMQ-6441.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 5.15.0

I added a PercentUsage section at the end of[1] that covers the percentLimit and total attributes that are common to the Store and Temp Usage. With a note on the caveat.

[1] https://cwiki.apache.org/confluence/display/ACTIVEMQ/Producer+Flow+Control

> Incorrect File System Size Reported with Amazon Elastic File System (EFS)
> -------------------------------------------------------------------------
>
>                 Key: AMQ-6441
>                 URL: https://issues.apache.org/jira/browse/AMQ-6441
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.11.1
>            Reporter: Ismail Bhana
>            Assignee: Gary Tully
>             Fix For: 5.15.0
>
>
> I've set up Active MQ in production with a shared file system master/slave configuration (KahaDB). I've set everything up and mounted the EFS on both EC2 instances. 
> When I check the disk free stats I get 8 exabytes for the shared file system: 
> {code}
> $ df -h 
> eu-west-1a.***.efs.eu-west-1.amazonaws.com:/  8.0E     0  8.0E   0% /mnt/efs 
> {code}
> Unfortunately, ActiveMQ cannot interpret this number (8 exabytes). This may be due to integer truncation.
> Here is a snippet of the log:
> {code}
> Store limit is 102400 mb (current store usage is 0 mb). The data directory: /mnt/efs/kahadb only has -8796093022208 mb of usable space - resetting to maximum available disk space: -8796093022207 mb 
> Store limit is -8796093022207 mb, whilst the max journal file size for the store is: 32 mb, the store will not accept any data when used. 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)