Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 511AED273 for ; Tue, 25 Jun 2013 13:28:26 +0000 (UTC) Received: (qmail 45936 invoked by uid 500); 25 Jun 2013 13:28:25 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 45133 invoked by uid 500); 25 Jun 2013 13:28:23 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 44978 invoked by uid 99); 25 Jun 2013 13:28:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 13:28:21 +0000 Date: Tue, 25 Jun 2013 13:28:21 +0000 (UTC) From: "Jean-Marc Spaggiari (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8804) Received exception while doing rolling-restart MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jean-Marc Spaggiari created HBASE-8804: ------------------------------------------ Summary: Received exception while doing rolling-restart Key: HBASE-8804 URL: https://issues.apache.org/jira/browse/HBASE-8804 Project: HBase Issue Type: Bug Reporter: Jean-Marc Spaggiari I got this exception while doing a rolling restart on my cluster: {code} 13/06/25 09:19:13 INFO region_mover: Wrote list of moved regions to /tmp/no= de6 Unloaded node6 region(s) node6: stopping regionserver.. node6: starting regionserver, logging to /home/hbase/hbase-0.94.3/bin/../lo= gs/hbase-hbase-regionserver-node6.out Reloading node6 region(s) 13/06/25 09:19:20 INFO region_mover: hostname=3Dnode6 is not up yet, waitin= g 13/06/25 09:19:20 INFO region_mover: hostname=3Dnode6 is not up yet, waitin= g 13/06/25 09:19:21 INFO region_mover: hostname=3Dnode6 is not up yet, waitin= g 13/06/25 09:19:21 INFO region_mover: hostname=3Dnode6 is not up yet, waitin= g 13/06/25 09:19:23 ERROR io.HbaseObjectWritable: Error in readFields java.lang.IllegalArgumentException: Not a host:port pair: de7,60020,1370440= 536028=02=02 X=EF=BF=BD=01=EF=BF=BD=02UIntegrationTestBigLinkedList=06m=EF=BF=BDN=EF=BF= =BD|=EF=BF=BD,1366851785897.6fb3d84e41ffed2f =09at org.apache.hadoop.hbase.util.Addressing.parseHostname(Addressing.java= :60) =09at org.apache.hadoop.hbase.ServerName.(ServerName.java:101) =09at org.apache.hadoop.hbase.ServerName.parseVersionedServerName(ServerNam= e.java:283) =09at org.apache.hadoop.hbase.ClusterStatus.readFields(ClusterStatus.java:3= 14) =09at org.apache.hadoop.hbase.io.HbaseObjectWritable.readObject(HbaseObject= Writable.java:690) =09at org.apache.hadoop.hbase.io.HbaseObjectWritable.readFields(HbaseObject= Writable.java:331) =09at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HB= aseClient.java:668) =09at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.ja= va:580) NativeException: java.lang.reflect.UndeclaredThrowableException: Call to no= de3/192.168.23.7:60000 failed on local exception: java.io.IOException: Erro= r in readFields getServers at /home/hbase/hbase-0.94.3/bin/region_mover.rb:193 loadRegions at /home/hbase/hbase-0.94.3/bin/region_mover.rb:367 (root) at /home/hbase/hbase-0.94.3/bin/region_mover.rb:469 Reloaded node6 region(s) Restoring balancer state to true Disabling balancer! (if required) {code} Ran successfuly on the 6 previous nodes, but failed on this one. This table= has 14 regions spreaded over all the RS. The region which failed is "Integ= rationTestBigLinkedList,\x08\x06m\xDENxFD|\xD2,1366851785897.6fb3d84e41ffed= 2f33931e3dac8b114f." and is online on Node2. I'm not really sure what the r= olling restart failed. Bad since I will have to re-try it and it takes 2h := ( -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira