Hi All,
As per the discussion on https://review.gluster.org/23645, recently we
changed the status of gNFS (gluster's native NFSv3 support) feature to
'Depricated / Orphan' state. (ref:
https://github.com/gluster/glusterfs/blob/master/MAINTAINERS#L185..L189).
With this email, I am proposing to chan
On Thu, Nov 21, 2019 at 12:31 PM Amar Tumballi wrote:
> Hi All,
>
> As per the discussion on https://review.gluster.org/23645, recently we
> changed the status of gNFS (gluster's native NFSv3 support) feature to
> 'Depricated / Orphan' state. (ref:
> https://github.com/gluster/glusterfs/blob/mast
Hi Markus,
Looks like your email got bounced as you were not member of the list. I got
the email as I had you in Cc earlier (through the github communications).
Forwarding it to the list so everyone gets your email.
Also, Yaniv, about the 'name' *Odd Fixes, *I am not a big fan either, but
out o
Hello Gluster community,
My name is Barak and I’ve joined RH gluster development in August.
Shortly after my arrival, I’ve identified a potential problem with
gluster’s logging mechanism and I’d like to bring the matter up for
discussion.
The general concept of the current mechanism is that every
I personally wouldn't call three years ago — when we started to deprecate
it, in glusterfs-3.9 — a recent change.
As a community the decision was made to move to NFS-Ganesha as the
preferred NFS solution, but it was agreed to keep the old code in the tree
for those who wanted it. There have been p
Independent of anything else—
Maintain it. Send patches to gerrit. Get the requisite +2 reviews on the
patches. Amar still has commit privs AFAIK; he can merge anything that gets
two votes.
It's open source meritocracy.
If there's real support for it then it makes a stronger case for adding it
b
在 2019/11/22 5:14, Kaleb Keithley 写道:
I personally wouldn't call three years ago — when we started to
deprecate it, in glusterfs-3.9 — a recent change.
As a community the decision was made to move to NFS-Ganesha as the
preferred NFS solution, but it was agreed to keep the old code in the
tre
This is definitely a good start. In fact the experiment you have done which
indicates a 20% improvement of run time perf with out logger does put this
work for a ‘worth a try’ category for sure. The only thing we need to be
mindful here is the ordering of the logs to be provided, either through a
t
On Fri, Nov 22, 2019 at 8:33 AM Xie Changlong wrote:
>
> 在 2019/11/22 5:14, Kaleb Keithley 写道:
>
> I personally wouldn't call three years ago — when we started to deprecate
> it, in glusterfs-3.9 — a recent change.
>
> As a community the decision was made to move to NFS-Ganesha as the
> preferred
在 2019/11/21 21:04, Barak Sason Rofman 写道:
I see two design / implementation problems with that mechanism:
1.
The mutex that guards the log file is likely under constant
contention.
2.
The fact that each worker thread perform the IO by himself, thus
slowing his "real" work.
On Fri, 22 Nov 2019, 5:03 Xie Changlong wrote:
>
> 在 2019/11/22 5:14, Kaleb Keithley 写道:
>
> I personally wouldn't call three years ago — when we started to deprecate
> it, in glusterfs-3.9 — a recent change.
>
> As a community the decision was made to move to NFS-Ganesha as the
> preferred NFS s
11 matches
Mail list logo
