hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2240) Balancer should not reassign (because of overloading) a region that was just opened
Date Wed, 01 Sep 2010 18:15:53 GMT

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

stack commented on HBASE-2240:
------------------------------

bq. A region that had just recently moved probably has clients that still are stale when it
moves the second time. So you'd potentially have less NSREs in total. Right?

No.  What I saw was retries trying to find location 1 chained to retries looking for location
2.  The sum of the two retries cased ERROR NSRE and failed MR task.

> Balancer should not reassign (because of overloading) a region that was just opened
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-2240
>                 URL: https://issues.apache.org/jira/browse/HBASE-2240
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: stack
>            Priority: Minor
>
> I'm running a mapreduce job.  I see a region split and its daughters come on line and
then 8 seconds later, master judges the regionserver overloaded and so closes the just-opened
region.  This messes up clients.   They may have just picked up the new location for their
row query and now its moved again and client has to go hunting anew. 
> We need to assign the vintage regions first.
> I'm going to change balancer slop.  Its not sloppy enough and balancing cuts in too early.

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


Mime
View raw message