hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tianying Chang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8836) Separate reader and writer thread pool in RegionServer, so that write throughput will not be impacted when the read load is very high
Date Thu, 11 Jul 2013 18:47:49 GMT

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

Tianying Chang commented on HBASE-8836:
---------------------------------------

ideally in 94 since our cluster is running on 94. But if the risk is too high, we can discuss
more. 
                
> Separate reader and writer thread pool in RegionServer, so that write throughput will
not be impacted when the read load is very high
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8836
>                 URL: https://issues.apache.org/jira/browse/HBASE-8836
>             Project: HBase
>          Issue Type: New Feature
>          Components: Performance, regionserver
>    Affects Versions: 0.94.8
>            Reporter: Tianying Chang
>            Assignee: Tianying Chang
>             Fix For: 0.98.0, 0.95.2, 0.94.10
>
>         Attachments: hbase-8836.patch, Hbase-8836-perfNumber.pdf
>
>
> We found that when the read load on a specific RS is high, the write throughput also
get impacted dramatically, and even cause write data loss sometimes. We want to prioritize
the write by putting them in a separate queue from the read request, so that slower read will
not make fast write wait nu-necessarily long.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message