[jira] [Commented] (HBASE-6465) Load balancer repeatedly close and open region in the same regionserver.

2012-07-26 Thread shen guanpu (JIRA) 

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

shen guanpu commented on HBASE-6465:


ok thanks
i am not quit catch the rule，sorry！

> Load balancer repeatedly close and open region in the same regionserver.
> 
>
> Key: HBASE-6465
> URL: https://issues.apache.org/jira/browse/HBASE-6465
> Project: HBase
>  Issue Type: Bug
>  Components: master, regionserver
>Affects Versions: 0.94.0
>Reporter: shen guanpu
>
> Through the master and regionserver log,I find load balancer repeatedly
> close and open region in the same regionserver(period in
> hbase.balancer.period ).
> Does this is a bug in load balancer and how can I dig into or avoid this?
> the hbase and hadoop version is
> HBase Version0.94.0, r1332822Hadoop Version0.20.2-cdh3u1,
> rbdafb1dbffd0d5f2fbc6ee022e1c8df6500fd638
> the following is a detail log about the same region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956,
> and it repeats again and again.:
> 2012-07-16 00:12:49,843 INFO org.apache.hadoop.hbase.master.HMaster: balance
> hri=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.,
> src=192.168.1.2,60020,1342017399608, dest=192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:49,843 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Starting unassignment of
> region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> (offlining)
> 2012-07-16 00:12:49,843 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:6-0x4384d0a47f40068 Creating unassigned node for
> 93caf5147d40f5dd4625e160e1b7e956 in a CLOSING state
> 2012-07-16 00:12:49,845 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Sent CLOSE to
> 192.168.1.2,60020,1342017399608 for region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_CLOSED, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler: Handling CLOSED
> event for 93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Forcing OFFLINE;
> was=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> state=CLOSED, ts=1342368770556, server=192.168.1.2,60020,1342017399608
> 2012-07-16 00:12:50,555 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:6-0x4384d0a47f40068 Creating (or updating) unassigned node for
> 93caf5147d40f5dd4625e160e1b7e956 with OFFLINE state
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=M_ZK_REGION_OFFLINE, server=10.75.18.34,6,1342017369575,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Found an existing plan
> for
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> destination server is 192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan
> for region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.;
> plan=hri=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.,
> src=192.168.1.2,60020,1342017399608, dest=192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Assigning region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> to 192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,574 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENING, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,635 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENING, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,639 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENED, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,639 DEBUG
> org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED
> event for
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> from 192.168.1.2,60020,1342017399608; deleting unassigned node
> 2012-07-16 00:12:50,640 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:6-0x

[jira] [Commented] (HBASE-6465) Load balancer repeatedly close and open region in the same regionserver.

2012-07-26 Thread Zhihong Ted Yu (JIRA) 

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

Zhihong Ted Yu commented on HBASE-6465:
---

This particular issue appeared on user mailing list.
svarma...@gmail.com made the last post.

Please continue discussion using that thread.

Normally JIRA is logged when the issue has been confirmed as an HBase bug (with 
sub-component identified).

> Load balancer repeatedly close and open region in the same regionserver.
> 
>
> Key: HBASE-6465
> URL: https://issues.apache.org/jira/browse/HBASE-6465
> Project: HBase
>  Issue Type: Bug
>  Components: master, regionserver
>Affects Versions: 0.94.0
>Reporter: shen guanpu
>
> Through the master and regionserver log,I find load balancer repeatedly
> close and open region in the same regionserver(period in
> hbase.balancer.period ).
> Does this is a bug in load balancer and how can I dig into or avoid this?
> the hbase and hadoop version is
> HBase Version0.94.0, r1332822Hadoop Version0.20.2-cdh3u1,
> rbdafb1dbffd0d5f2fbc6ee022e1c8df6500fd638
> the following is a detail log about the same region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956,
> and it repeats again and again.:
> 2012-07-16 00:12:49,843 INFO org.apache.hadoop.hbase.master.HMaster: balance
> hri=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.,
> src=192.168.1.2,60020,1342017399608, dest=192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:49,843 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Starting unassignment of
> region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> (offlining)
> 2012-07-16 00:12:49,843 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:6-0x4384d0a47f40068 Creating unassigned node for
> 93caf5147d40f5dd4625e160e1b7e956 in a CLOSING state
> 2012-07-16 00:12:49,845 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Sent CLOSE to
> 192.168.1.2,60020,1342017399608 for region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_CLOSED, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler: Handling CLOSED
> event for 93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,555 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Forcing OFFLINE;
> was=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> state=CLOSED, ts=1342368770556, server=192.168.1.2,60020,1342017399608
> 2012-07-16 00:12:50,555 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:6-0x4384d0a47f40068 Creating (or updating) unassigned node for
> 93caf5147d40f5dd4625e160e1b7e956 with OFFLINE state
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=M_ZK_REGION_OFFLINE, server=10.75.18.34,6,1342017369575,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Found an existing plan
> for
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> destination server is 192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan
> for region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.;
> plan=hri=trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.,
> src=192.168.1.2,60020,1342017399608, dest=192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,558 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Assigning region
> trackurl_status_list,zO6u4o8,1342291884831.93caf5147d40f5dd4625e160e1b7e956.
> to 192.168.1.2,60020,1342002082592
> 2012-07-16 00:12:50,574 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENING, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,635 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENING, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,639 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_OPENED, server=192.168.1.2,60020,1342017399608,
> region=93caf5147d40f5dd4625e160e1b7e956
> 2012-07-16 00:12:50,639 DEBUG
> org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED
> event for
> trackurl_status_list,zO6u4