hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars George <lars.geo...@gmail.com>
Subject HBase 0.89.0-20100924 region assignment woes
Date Thu, 25 Nov 2010 10:49:34 GMT

Talking to Lars we found a weird series of events that led to dying
task attempts during the bulk job they are running. See the attached
log. Region in question is:


After a split the region is assigned to a new server (c1n6) but then
immediately ripped out underneath it because the server is deemed to
be too loaded. Then it releases that region (after a few minutes) and
a few others and then that new daughter region, which did not have
time yet to serve anything really, is reassigned to.... you guessed it
probably, the same server as that is now deemed (?) to be the least
loaded one. So that new daughter is not available for minutes causing
the task attempt to die.

I see that in trunk this is all replaced. No RegionManager but an
AssignmentManager who does random node selection. Is that all obsolete
now and this should be improved on trunk?


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message