You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/11/28 00:18:38 UTC
[jira] [Updated] (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
[ https://issues.apache.org/jira/browse/HBASE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-8836:
----------------------------------
Fix Version/s: (was: 0.98.0)
Moving out of 0.98
> 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
> Attachments: HBase-8836-QosAnotation.patch, Hbase-8836-perfNumber.pdf, hbase-8836.patch, threadPool-write-NoWAL.png, threadPool-write-WithWAL.png
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)