ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15328) Exception on manual start of AMS is misleading
Date Tue, 08 Mar 2016 01:06:40 GMT

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

Aravindan Vijayan commented on AMBARI-15328:
--------------------------------------------

Manually tested.

{code}
[root@c6401 tmp]# su - ams -c '/usr/sbin/ambari-metrics-collector --config /etc/ambari-metrics-collector/conf/
start'
Tue Mar  8 00:59:07 UTC 2016 Starting HBase.
starting master, logging to /var/log/ambari-metrics-collector/hbase-ams-master-c6401.ambari.apache.org.out
Verifying ambari-metrics-collector process status...
Tue Mar  8 00:59:10 UTC 2016 Collector successfully started.
Tue Mar  8 00:59:10 UTC 2016 Initializing Ambari Metrics data model
Tue Mar  8 00:59:33 UTC 2016 Ambari Metrics data model initialization check 1
Tue Mar  8 01:01:09 UTC 2016 Ambari Metrics data model initialization check 2
Tue Mar  8 01:02:06 UTC 2016 Ambari Metrics data model initialization check 3
Tue Mar  8 01:02:20 UTC 2016 Ambari Metrics data model initialization completed.
{code}


> Exception on manual start of AMS is misleading
> ----------------------------------------------
>
>                 Key: AMBARI-15328
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15328
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.2.0
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15328.patch
>
>
> On manual start of AMS in embedded mode, following stderr messages are logged to console
which is misleading since the start succeeds when the server is up.
> {code}
> 2016-01-27 19:15:21,487 ERROR [main] zookeeper.ZooKeeperWatcher: hconnection-0x799ed4e80x0,
quorum=localhost:61181, baseZNode=/ams-hbase-unsecure Received unexpected KeeperException,
re-throwing exception
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
for /ams-hbase-unsecure
> 	at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> 	at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> 	at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> 	at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:221)
> 	at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:417)
> 	at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.checkIfBaseNodeAvailable(ConnectionManager.java:902)
> 	at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.access$400(ConnectionManager.java:552)
> 	at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation$StubMaker.makeStubNoRetries(ConnectionManager.java:1490)
> 	at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation$StubMaker.makeStub(ConnectionManager.java:1531)
> {code}
> We already log this to a file so not need to print stderr to console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message