- Original Message -
> From: "Tahereh Fattahi"
> To: "Raghavendra Gowdappa"
> Cc: "Gluster Devel"
> Sent: Sunday, April 30, 2017 10:04:25 AM
> Subject: Re: [Gluster-devel] About spread count, lookup and layout
>
> Thanks a lot
> I read in document that when we want to create a file, f
Thanks a lot
I read in document that when we want to create a file, first we should be
sure that this file does not exist in the directory. So first look at the
hashed subvolume and if it does not exist then broad cast this lookup to
other subvolume (when lookup optimize is off) to ensure that this
All,
Its a common perception that the resolution of a file having linkto file on the
hashed-subvol requires two hops:
1. client to hashed-subvol.
2. client to the subvol where file actually resides.
While it is true that a fresh lookup behaves this way, the other fact that
get's ignored is tha
- Original Message -
> From: "Tahereh Fattahi"
> To: "Gluster Devel"
> Sent: Sunday, April 30, 2017 8:03:15 AM
> Subject: [Gluster-devel] About spread count, lookup and layout
>
> Hi
> I have some question about spread count:
>
> 1. When I set spread count less than subvolume count, I
Hi
I have some question about spread count:
1. When I set spread count less than subvolume count, I see the hash is
assigned to one directory layout for some subvolumes are zero (that is ok)
, but I expect these subvolumes should not bee looked up in case
lookup_everywhere for creating a file. Unf
Hi Poornima and others,
Could someone please review the patch that adds reference counting to
the timer-wheel structure that is used by glusterfs_ctx_t?
https://review.gluster.org/17068
> core: make the per glusterfs_ctx_t timer-wheel refcounted
>
> xlators can use a 'global' timer-wheel for sc
