hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaPing Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16224) Reduce the number of RPCs for the large PUTs
Date Fri, 15 Jul 2016 08:16:20 GMT

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

ChiaPing Tsai edited comment on HBASE-16224 at 7/15/16 8:15 AM:
----------------------------------------------------------------

waiting for [HBASE-16235|https://issues.apache.org/jira/browse/HBASE-16235]


was (Author: chia7712):
waiting for [HBASE-16235|https://issues.apache.org/jira/browse/HBASE-16235}

> 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
>
>
> 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)

Mime
View raw message