Here's my proposal:
Title: GFProxy: Scaling the GlusterFS FUSE Client
Theme: Experience / (Process & Infrastructure)
I plan to cover the following topics:
- Discuss the benefits of the FUSE client vs. NFS & how we use it @ Facebook
today
- Discuss scalability challenges with the FUSE client,
Hey guys,
Any news on the timeline for this years Gluster Summit? Just trying to plan
ahead ... :)
Shreyas
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
So the way our throttling works is (intentionally) very simplistic.
(1) When someone mounts an NFS share, we tag the frame with a 32 bit hash of
the export name they were authorized to mount.
(2) io-stats keeps track of the "current rate" of fops we're seeing for that
particular mount, using a
Just out of curiosity, what benefits do we think this throttling xlator would
provide over the "enable-least-priority" option (where we put all the fops from
SHD, etc into a least pri queue)?
> On Jan 25, 2016, at 12:29 AM, Venky Shankar wrote:
>
> On Mon, Jan 25, 2016