----- Original Message ----- > From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx> > To: "Emmanuel Dreyfus" <manu@xxxxxxxxxx>, gluster-devel@xxxxxxxxxxx > Sent: Wednesday, September 2, 2015 2:04:32 PM > Subject: Re: FOP ratelimit? > > > > 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. Data is not moved across bricks during rename. So, may be something else is causing the issue. Were you running rebalance while these renames were being done? > > > > 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. Thanks Pranith. @Manu and others, Its helpful if you can give some pointers on what parameters (like latency, throughput etc) you want us to consider for QoS. Also, any ideas (like interface for QoS) in this area is welcome. With my very basic search, seems like there are not many filesystems with QoS functionality. regards, Raghavendra. > > Pranith > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
