Hi,
I cannot advice on other settings, but -nobrl is CIFS based flag. Assuming that
you are using NFS and not SMB for your volume this flag will be of no use.
--
Vilius
-----Original Message-----
From: Lino Pereira <lino.pere...@redpointglobal.com.INVALID>
Sent: Friday, October 4, 2024 11:54 PM
To: users@activemq.apache.org
Subject: Recommendation on Azure Storage Class settings for the
activemq-shared-store-pvc volume shared by both Artemis-HA instances
Hi,
We are using Artemis-HA, with the live and backup instances, in our K8S
deployment in Azure. In our config, we have a “activemq-shared-store-pvc”
volume backed by an Azure File Share that is shared by both the live and
backup Artemis instances to keep live/backup state.
Generally, do you have specific recommendations for the Azure Storage Class
settings that should be used for such a volume.
More specifically, when creating a StorageClass in Azure Kubernetes for such a
volume, I encountered an advisory in Azure documentation that recommends
including the -nobrl flag in the mount Options. The documentation states that
this flag is crucial for avoiding issues related to byte range locks in certain
applications, i.e.:
# Disables sending byte range lock requests to the server and for applications
which have challenges with POSIX locks.
What is your recommendation regarding including the -nobrl flag for the
“activemq-shared-store-pvc” volume that is shared by Artemis-HA instances to
keep live/backup state?
Thanks,
Lino
[rg] <https://www.redpointglobal.com/>
Lino Pereira
C++ Developer, Redpoint Global Inc.
34 Washington Street, Suite 205 Wellesley Hills, MA 02481
lino.pere...@redpointglobal.com<mailto:lino.pere...@redpointglobal.com>
PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is
confidential and is intended solely for the use of the individual(s) to whom it
is addressed. If you believe you received this e-mail in error, please notify
the sender immediately, delete the e-mail from your computer and do not copy,
print or disclose it to anyone else. If you properly received this e-mail as a
customer, partner or vendor of Redpoint, you should maintain its contents in
confidence subject to the terms and conditions of your agreement(s) with
Redpoint.
