Thanks Ravi, so if I understand correctly latency to all the nodes remains
an issue on all file reads.
On Tue, 10 Aug 2021 at 16:49, Ravishankar N wrote:
>
>
> On Tue, Aug 10, 2021 at 8:07 AM David Cunningham <
> dcunning...@voisonics.com> wrote:
>
>> Hi Gionatan,
>>
>> Thanks for that reply.
On Tue, Aug 10, 2021 at 3:23 PM David Cunningham
wrote:
> Thanks Ravi, so if I understand correctly latency to all the nodes remains
> an issue on all file reads.
>
>
Hi David, yes, but only for the lookup and opening of the fd. Once the fd
is open, all readv calls will go only to the chosen
Thanks Ravi. That was my understanding - that the opening of the file is
checked for health with all nodes, and then the file is actually read from
one node. I think it's clear that checking with all nodes when opening the
file for a read can't be avoided at the moment.
On Tue, 10 Aug 2021 at
Hi Strahil and Gilberto,
Thanks very much for your replies. SELinux is disabled on the NFS server
(and the client too), and both have the same UID and GID for the user who
owns the files.
On the NFS mount we had options "rw,noatime,hard,bg,intr,vers=4". I added
"async" which did not solve the
Hi All,
This email is to keep everyone posted regarding the new release cycle
changes for Gluster major and Minor releases.
We had discussed future Gluster release cycle timelines in yesterday's
Community meeting. The details are as below.
1. From Gluster 10 major release, the release cycle for
HOw about the NFS options?
(rw,async,no_root_squash,no_subtree_check)
---
Gilberto Nunes Ferreira
(47) 99676-7530 - Whatsapp / Telegram
Em ter., 10 de ago. de 2021 às 12:46, Strahil Nikolov
escreveu:
> Hey David,
>
> can you give the volume info ?
>
> Also, I assume SELINUX is in
