activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharatkumar Khokhani (JIRA)" <>
Subject [jira] [Commented] (AMQ-6441) Incorrect File System Size Reported with Amazon Elastic File System (EFS)
Date Wed, 28 Sep 2016 19:06:20 GMT


Bharatkumar Khokhani commented on AMQ-6441:

I think it should be whenever JDK call returns negative value for max file system size then
BrokerService method set it to Long.MAX_VALUE will avoid any other side effects. 

If file system is small then it should do normal operation of resetting max size to actual
file size.

> Incorrect File System Size Reported with Amazon Elastic File System (EFS)
> -------------------------------------------------------------------------
>                 Key: AMQ-6441
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.11.1
>            Reporter: Ismail Bhana
> 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.***  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
> 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

View raw message