[
https://issues.apache.org/jira/browse/HBASE-16224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406996#comment-15406996
]
Heng Chen commented on HBASE-16224:
-----------------------------------
{quote}
t is necessary to reset the inner state of TaskCheckerHost if we do the
TaskCheckerHost out of while scope. The reasons are shown below:
1) TaskCheckerHost keeps the "END" state returned from any checker.
2) Size-checker keeps the overflow infos
It seems to me that the TaskCheckerHost should be in the while loop if there
are more Stateful checkers in the future.
{quote}
So we should add one method "reset()" in TaskChecker, it should be better, wdyt?
> Reduce the number of RPCs for the large PUTs
> --------------------------------------------
>
> Key: HBASE-16224
> URL: https://issues.apache.org/jira/browse/HBASE-16224
> Project: HBase
> Issue Type: Improvement
> Reporter: ChiaPing Tsai
> Assignee: ChiaPing Tsai
> Priority: Minor
> Attachments: HBASE-16224-v1.patch, HBASE-16224-v2.patch,
> HBASE-16224-v3.patch, HBASE-16224-v4.patch, HBASE-16224-v5.patch,
> HBASE-16224-v6.patch, HBASE-16224-v7.patch, HBASE-16224-v8.patch,
> experiment.xlsx
>
>
> This patch is proposed to reduce the number of RPC for the large PUTs
> The number and data size of write thread(SingleServerRequestRunnable) is a
> result of three main factors：
> 1) The flush size taken by BufferedMutatorImpl#backgroundFlushCommits
> 2) The limit of task number
> 3) ClientBackoffPolicy
> A lot of threads created with less MUTATIONs is a result of two reason: 1)
> many regions of target table are in different server. 2) flush size in step
> one is summed by “all” server rather than “individual” server
> This patch removes the limit of flush size in step one and add maximum size
> to submit for each server in the AsyncProcess
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
