You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "liang xie (JIRA)" <ji...@apache.org> on 2012/10/22 04:10:12 UTC
[jira] [Commented] (HBASE-6998) Uncaught exception in main() makes
the HMaster/HRegionServer process suspend
[ https://issues.apache.org/jira/browse/HBASE-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481125#comment-13481125 ]
liang xie commented on HBASE-6998:
----------------------------------
Could anyone have a review on this issue? Thanks:)
> Uncaught exception in main() makes the HMaster/HRegionServer process suspend
> ----------------------------------------------------------------------------
>
> Key: HBASE-6998
> URL: https://issues.apache.org/jira/browse/HBASE-6998
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 0.94.2, 0.96.0
> Environment: CentOS6.2 + CDH4.1 HDFS + hbase0.94.2
> Reporter: liang xie
> Assignee: liang xie
> Attachments: HBASE-6998.patch
>
>
> I am trying HDFS QJM feature in our test env. after a misconfig, i found the HMaster/HRegionServer process still up if the main thread is dead. Here is the stack trace:
> xception in thread "main" java.net.UnknownHostException: unknown host: cluster1
> at org.apache.hadoop.ipc.Client$Connection.<init>(Client.java:214)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1196)
> at org.apache.hadoop.ipc.Client.call(Client.java:1050)
> at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:225)
> at $Proxy8.getProtocolVersion(Unknown Source)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:396)
> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:379)
> at org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:119)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:238)
> at org.apache.hadoop.hdfs.DFSClient.<init>(DFSClient.java:203)
> at org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:89)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1386)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:66)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1404)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:254)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:123)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.startRegionServer(HRegionServer.java:3647)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.startRegionServer(HRegionServer.java:3631)
> at org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.start(HRegionServerCommandLine.java:61)
> at org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.run(HRegionServerCommandLine.java:75)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
> at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.main(HRegionServer.java:3691)
> Then i need to kill the process manually to cleanup each time, so annoyed.
> After applied the attached patch, the process will exist as expected, then i am happy again :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira