activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Korny Sietsma <ko...@sietsma.com>
Subject Re: Active MQ Shared File System Master Slave with Elastic File System
Date Fri, 02 Sep 2016 11:16:16 GMT
Interesting - we set up ActiveMQ 5.9 successfully on EFS, I'm guessing
these error messages relate to checks made in later versions of the product.

Note that we gave up on this approach - we found that shared filesystem
master/slave had several problems for us when we tested it with network lag
and splits between the master and the EFS file system.

We have since moved to testing LevelDB + Zookeeper, which has been rather
more reliable in failure scenarios.

- Korny

On 25 August 2016 at 09:16, ishmeister <ibhana@visibilityltd.com> wrote:

> I'm setting 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:
>
> $ df -h
> eu-west-1a.***.efs.eu-west-1.amazonaws.com:/  8.0E     0  8.0E   0%
> /mnt/efs
> Unfortunately, ActiveMQ cannot interpret this number:
>
> 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.
>
> However, this has not prevented ActiveMQ from working as far as I can tell.
> Is it a problem that "the store will not accept any data when used"?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-
> Elastic-File-System-tp4715818.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
Kornelis Sietsma  korny at my surname dot com http://korny.info
.fnord { display: none !important; }

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message