You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Commented) (JIRA)" <ji...@apache.org> on 2012/02/01 03:08:57 UTC
[jira] [Commented] (HBASE-5307) Unable to gracefully decommission a
node because of script error
[ https://issues.apache.org/jira/browse/HBASE-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197510#comment-13197510 ]
Hudson commented on HBASE-5307:
-------------------------------
Integrated in HBase-TRUNK #2649 (See [https://builds.apache.org/job/HBase-TRUNK/2649/])
HBASE-5307 Unable to gracefully decommission a node because of script error
stack :
Files :
* /hbase/trunk/bin/region_mover.rb
> Unable to gracefully decommission a node because of script error
> ----------------------------------------------------------------
>
> Key: HBASE-5307
> URL: https://issues.apache.org/jira/browse/HBASE-5307
> Project: HBase
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.92.0
> Reporter: YiFeng Jiang
> Fix For: 0.92.1
>
> Attachments: region_mover_HBASE-5307-0.92.patch
>
>
> Unable to gracefully decommission a node because NameError occurred in region_mover.rb
> {code}
> $ bin/graceful_stop.sh ip-10-160-226-84.us-west-1.compute.internal
> ...
> NameError: no constructorfor arguments (org.jruby.RubyString) on Java::OrgApacheHadoopHbase::HServerAddress
> available overloads:
> (org.apache.hadoop.hbase.HServerAddress)
> (java.net.InetSocketAddress)
> getRegions at /usr/local/hbase/current/bin/region_mover.rb:254
> unloadRegions at /usr/local/hbase/current/bin/region_mover.rb:314
> (root) at /usr/local/hbase/current/bin/region_mover.rb:430
> Unloaded ip-10-160-226-84.us-west-1.compute.internal region(s)
> ip-10-160-226-84.us-west-1.compute.internal: stopping regionserver..
> {code}
> The reason is the region_mover.rb calls wrong HBase APIs to try to establish a connection to the region server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira