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? 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? -- Emmanuel Dreyfus manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
