[
https://issues.apache.org/jira/browse/AMQ-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532849#comment-15532849
]
Christopher L. Shannon commented on AMQ-6441:
---------------------------------------------
I would probably do a combination of the two things.
First, as Tim said, I would implement a flag (defaulting to false) that can be
turned on that would disable the usage check altogether. Also note that there
is a task that gets scheduled to periodically check the usage and this flag
should also make sure this task is not scheduled.
Second, as a sanity check, I see no harm in also adding a check for a negative
value of totalSpace. If the value is negative then I would think the safest
thing to do is to throw an exception with a good error message that explains
why the error most likely happened (probably an overflow) and how to fix it
(enable the new flag to true to disable the check). You could also just allow
the broker to start up with the negative value and skip the check but I would
think it's better to error to make sure the user is aware of the issue and can
explicitly decide if they want to disable the check or use a smaller partition.
> 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)
