I'd guess that the way ActiveMQ is "working" is that your persistent messages, which should have been stored in the persistence store, are instead being stored in the memory store. This means they will not survive a broker restart/failover even though they should, and you'll be subject to the memory store's limit rather than the persistence store's. So yes, messages are getting delivered, but that doesn't mean ActiveMQ is working.
Could you submit a bug in JIRA to capture the fact that we're not handling a disk size that large? I suspect the problem is that we're using an int where we should be using a long. Till the bug is fixed, I'd suggest allocating an EBS volume just for the persistence store that's sized to match whatever limit you're going to put on the KahaDB store. Tim On Aug 25, 2016 2:18 AM, "ishmeister" <ibh...@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. >
