You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Zhanwei Wang (JIRA)" <ji...@apache.org> on 2017/11/14 12:23:00 UTC

[jira] [Commented] (AMBARI-22423) Ambari Metrics does not work after restart service

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

Zhanwei Wang commented on AMBARI-22423:
---------------------------------------

Does anyone has any idea to fix this issue?

> Ambari Metrics does not work after restart service
> --------------------------------------------------
>
>                 Key: AMBARI-22423
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22423
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.6.0
>         Environment: centos7
>            Reporter: Zhanwei Wang
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node centos7 cluster for test.
> With all default configurations I manager to make Ambari Metrics work normally. But after restart Ambari Metrics service, HBase died with following exception.
> {noformat}
> 2017-11-11 16:03:36,800 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181] server.NIOServerCnxn: Closed socket connection for client /192.168.110.7:41352 which had sessionid 0x15faa1aa2a90005
> 2017-11-11 16:03:48,253 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181] server.NIOServerCnxnFactory: Accepted socket connection from /192.168.110.7:41390
> 2017-11-11 16:03:48,258 INFO  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181] server.ZooKeeperServer: Client attempting to establish new session at /192.168.110.7:41390
> 2017-11-11 16:03:48,262 INFO  [SyncThread:0] server.ZooKeeperServer: Established session 0x15faa1aa2a90006 with negotiated timeout 120000 for client /192.168.110.7:41390
> 2017-11-11 16:03:51,437 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Master not active after 30 seconds
> 	at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194)
> 	at org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> 	at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227)
> 	at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> 	at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> 	at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2452)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)