Done: https://issues.apache.org/jira/browse/AMQ-6441
If anyone wants to update the ticket, feel free.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-Elastic-File-System-tp4715818p4716851.html
Sent from the ActiveMQ - User
No not yet, but I will do so now.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-Elastic-File-System-tp4715818p4716848.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The issue is perhaps that EFS supports NFS4 but with the following
limitations:
http://docs.aws.amazon.com/efs/latest/ug/nfs4-unsupported-features.html
In particular: "All locks in Amazon EFS are advisory, which means that READ
and WRITE operations do not check for conflicting locks before the
Tim,
I contacted AWS tech support and their response was this:
"I've checked with our EFS team to see if there is any EFS-related
workaround they can offer. Unfortunately, they have confirmed that this is
EFS intended behavior and there is no way of mounting a filesystem with
"predetermined
Thanks Tim. I'll get this up on JIRA soon.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-Elastic-File-System-tp4715818p4715867.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
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
