[
https://issues.apache.org/jira/browse/HBASE-10169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Helmling updated HBASE-10169:
----------------------------------
Attachment: HBASE-10169-alternate-2.patch
Attaching a new patch:
* Slight cleanup of args and docs for new HTableInterface methods
* Fix use of HashMap in TestBatchCoprocessorEndpoint
* Fix up HadoopQA issues from last patch
> Batch coprocessor
> -----------------
>
> Key: HBASE-10169
> URL: https://issues.apache.org/jira/browse/HBASE-10169
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Affects Versions: 0.99.0
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Attachments: Batch Coprocessor Design Document.docx,
> HBASE-10169-V2.patch, HBASE-10169-V3.patch, HBASE-10169-V3.patch,
> HBASE-10169-V4.patch, HBASE-10169-V5.patch, HBASE-10169-alternate-2.patch,
> HBASE-10169-alternate.patch, HBASE-10169.patch
>
>
> This is designed to improve the coprocessor invocation in the client side.
> Currently the coprocessor invocation is to send a call to each region. If
> there’s one region server, and 100 regions are located in this server, each
> coprocessor invocation will send 100 calls, each call uses a single thread in
> the client side. The threads will run out soon when the coprocessor
> invocations are heavy.
> In this design, all the calls to the same region server will be grouped into
> one in a single coprocessor invocation. This call will be spread into each
> region in the server side.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
