You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Key Hutu (JIRA)" <ji...@apache.org> on 2018/05/03 10:06:00 UTC

[jira] [Updated] (HBASE-20526) multithreads bulkload performance

     [ https://issues.apache.org/jira/browse/HBASE-20526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Key Hutu updated HBASE-20526:
-----------------------------
    Affects Version/s:     (was: 2.0.0)
                       1.2.0
          Environment: 
hbase-server-1.2.0-cdh5.12.1 

spark version 1.6
          Component/s: Zookeeper

> multithreads bulkload performance
> ---------------------------------
>
>                 Key: HBASE-20526
>                 URL: https://issues.apache.org/jira/browse/HBASE-20526
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce, Zookeeper
>    Affects Versions: 1.2.0
>         Environment: hbase-server-1.2.0-cdh5.12.1 
> spark version 1.6
>            Reporter: Key Hutu
>            Assignee: Key Hutu
>            Priority: Minor
>              Labels: performance
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> When doing bulkload , some interactive with zookeeper to getting region key range may be cost more time.
> In multithreads enviorment, the duration maybe cost 5 minute or more.
> From the executor log, like 'Reading reply sessionid:0x262fb37f4a07080 , packet:: clientPath:null server ...' contents appear many times.
>  
> It likely to provide new method for bulkload, caching the key range outside
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)