hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15136) Explore different queuing behaviors while busy
Date Wed, 15 Jun 2016 05:35:09 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331179#comment-15331179

Mikhail Antonov commented on HBASE-15136:

[~stack] setting it as a default is flipping one flag, almost oneliner patch, and this is
where I definitely want to get (yeah, new issue would be good, I actually thought I might
have created one before, need to check).

The reasons I didn't set it to default yet are that 1) though I'd been running it on some
decent size test clusters with realistic workloads, it's not as battle-tested yet and the
defaults need to be tweaked and 2) workloads I was running are different from, say read-only
workloads with ~100% cache hit rate (like this latest one which revealed regression in the
scheduler), so my focus was a bit different.

Since it's mostly FIFO and since fastpath hand-off and codel are kind of non-intersecting
optimizations as I see it (if you need to combat long queues it means there's definitely no
option for direct hand-off), applying fastfast scheduling to codel should be pretty straightforward.
Then yes, we can make this a default?

> Explore different queuing behaviors while busy
> ----------------------------------------------
>                 Key: HBASE-15136
>                 URL: https://issues.apache.org/jira/browse/HBASE-15136
>             Project: HBase
>          Issue Type: New Feature
>          Components: IPC/RPC
>            Reporter: Elliott Clark
>            Assignee: Mikhail Antonov
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0
>         Attachments: HBASE-15136-1.2.v1.patch, HBASE-15136-v2.patch, deadline_scheduler_v_0_2.patch
> http://queue.acm.org/detail.cfm?id=2839461

This message was sent by Atlassian JIRA

View raw message