[jira] [Commented] (HBASE-10169) Batch coprocessor

["Andrew Purtell (JIRA)" <ji...@apache.org>]

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

Andrew Purtell commented on HBASE-10169:
----------------------------------------

As we are just adding API not changing/removing anything, I am +1 for trunk and 0.98 on HBASE-10169-alternate-4.patch . Let's get it into a release so it might pick up users and we can get feedback on it ahead of 1.0. I can guarantee one user for this feature in 0.98 anyway.

[~jingcheng.du@intel.com] or [~ghelmling], nice work both, please open a follow on issue for parallel execution concerns not covered in HBASE-10169-alternate-4.patch, and we can proceed there.

> 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-3.patch, HBASE-10169-alternate-4.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.2#6252)