Re: FOP ratelimit?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 09/02/2015 01:59 PM, Emmanuel Dreyfus wrote:
Hi

Yesterday I experienced the problem of a single user bringing down
a glusterfs cluster to its knees because of a high amount of rename
operations.

I understand rename on DHT can be very costly because data really have
to be moved from a brick to another one just for a file name change.
Is there a workaround for this behavior?
This is not true.

And more generally, do we have a way to ratelimit FOPs per client, so
that one client cannot make the cluster unusable for the others?
Do you have profile data?

Raghavendra G is working on some QOS related enahancements in gluster. Please let us know if you have any inputs here.

Pranith


_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux