You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/10/25 02:09:44 UTC

[jira] Assigned: (HBASE-675) Report correct server hosting a table split for assignment to for MR Jobs

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

stack reassigned HBASE-675:
---------------------------

    Assignee: stack

Let me take this one.  I chatted with Arthur and he says his multilocation doohickey works.  I'll refactor his patch -- he gave permission -- and try it out on cluster.

> Report correct server hosting a table split for assignment to for MR Jobs
> -------------------------------------------------------------------------
>
>                 Key: HBASE-675
>                 URL: https://issues.apache.org/jira/browse/HBASE-675
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.2.0
>            Reporter: Billy Pearson
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.20.0
>
>         Attachments: arthur.patch, hbase-675-v1.patch
>
>
> Currently we return a null String array to the MR framework to use a random node for MR job assignment.
> class: org.apache.hadoop.hbase.mapred.tableSplit
> function getLocations()
> We should be able to query the meta now for the current host name of the server hosting the region in question.
> This will help with scaling as there will be less cross server communication removing bandwidth as a bottleneck.
> The side effect of fixing this will help from overloading region servers with lots of MR clients all pulling from the same region server while theres work local for them to do.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.