[Gluster-users] gluster volume traffic shaping / throttling

[Mateusz Zajakala]

Vijay,

no, as you said, R/W priority solves my case which is keeping volume
available for multiple clients heavy R traffic while allowing background W
processes to continue.

However I see potential uses for QoS traffic shaping (based on many rules -
client identity, client requested priority, accessed file on the volume,
size of the accessed file etc). That would be a very interesting feature to
have in next releases.

Best,
Mat

On Tue, Dec 22, 2015 at 5:18 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On 12/21/2015 08:25 AM, Pranith Kumar Karampuri wrote:
>
>>
>>
>> On 12/21/2015 02:26 PM, Mateusz Zajakala wrote:
>>
>>> Pranith,
>>>
>>> that sounds good, Option to configure relative priorities of READ and
>>> WRITE operations would be probably sufficient in my case (as long as
>>> it really affects the operations throughput).
>>>
>>> But what if you wanted to differentiate write/read priorities from
>>> different clients? maybe it's worth thinking about some way to enable
>>> this?
>>>
>>
>> Oh, these options will be on server side. So all clients will see same
>> priorities. That is probably the reason why the Original developer
>> didn't allow these priorities to be changed. I am not sure how we can
>> configure in a generic way. Any thoughts?
>>
>>
> All clients observing the same set of priorities does address the initial
> problem discussed here.
>
> Addressing the second one - configurable priorities based on client's
> identity is something that we intend addressing as part of quality of
> service in Gluster.next releases.
>
> Mateusz - are there other use cases related to traffic shaping/throttling
> that would interest you?
>
> Thanks,
> Vijay
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151222/594e2def/attachment.html>