Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 27 Sep 2016 19:28:20 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13007166.1474640776000.677752.1475004500491@Atlassian.JIRA>
In-Reply-To: <JIRA.13007166.1474640776000@Atlassian.JIRA>
References: <JIRA.13007166.1474640776000@Atlassian.JIRA> <JIRA.13007166.1474640776761@arcas>
Subject: [jira] [Comment Edited] (AMQ-6441) Incorrect File System Size
 Reported with Amazon Elastic File System (EFS)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 27 Sep 2016 19:28:22 -0000


    [ https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527178#comment-15527178 ] 

Christopher L. Shannon edited comment on AMQ-6441 at 9/27/16 7:27 PM:
----------------------------------------------------------------------

This should be tested in a unit test regardless so my recommendation is to not worry about that and see if you could use something like mockito to mock/spy on the File api interface and then you can configure it to return whatever value you want (ie 8 EB) to test.  Off the top of my head maybe something like mocking out what the getPersistenceAdapter() method returns in BrokerService could work so that when the usage checks get the directory to check the size it will return your Directory/File mock etc.


was (Author: christopher.l.shannon):
This should be tested in a unit test regardless so my recommendation is to not worry about that and see if you could use something like mockito to mock/spy on the File api interface and then you can configure it to return whatever value you want (ie 8 EB) to test.  Off the top of my head maybe something like mocking out out the getPersistenceAdapter() method in BrokerService so that when it returns a directory for the usage checks it will return your Directory/File mock etc.

> 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
>
> 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)