You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2013/08/02 07:41:54 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 ]
Lars Hofhansl updated HBASE-8836:
---------------------------------
Fix Version/s: (was: 0.94.11)
0.94.12
Moving on to 0.94.12. We need to maintain the batch nature *especially* for update (so that they go in batch through doMiniBatchMutation).
> 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.12
>
> 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