[
https://issues.apache.org/jira/browse/HBASE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695924#comment-13695924
]
Otis Gospodnetic commented on HBASE-8836:
-----------------------------------------
Have you run any test and have any numbers to show how much impact this has?
I'm wondering how well this works if the underlying server/IO is actually maxed
out. In such situation, can separating writes from reads help?
> 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.94.8
>
>
> 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
