ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit Mohanty <smoha...@hortonworks.com>
Subject Re: Old Cluster name appering in logs even after Ambari-Server Reset Query!
Date Fri, 03 Feb 2017 04:44:35 GMT
Once you deploy the new cluster they will go away. Agent may respond as there could be inflight
commands and alert definitions.

-Sumit
________________________________________
From: Sandy <sandy.wadhwa@gmail.com>
Sent: Thursday, February 02, 2017 8:42 PM
To: dev@ambari.apache.org
Subject: Old Cluster name appering in logs even after Ambari-Server Reset Query!

I created an AMBARI cluster using Vagrant VMs.  After cluster creation, I
stopped all the services and did ambari-server reset.

I assumed that It'll be clearing all the information about cluster from DB
and none of the AGENTS maintain the state about cluster.  They just send
heartbeat messages to the server and in return look for commands that may
have to execute.

But after restarting the server, I observed the log messages, that
mentioned my cluster name (before reset).  Just wondering, How is this name
persisted??

Do AGENTS remember state regarding clusters and services??  If yes, how do
I clear that off (Like ambari-server reset, is there something like
ambari-agent reset too)??

// A SNIP FROM LOG MESSAGES

03 Feb 2017 15:19:12,911 DEBUG [alert-event-bus-1]
AlertReceivedListener:477 - Unable to process alert
hbase_regionserver_process for an invalid cluster named *hdpCluster*
org.apache.ambari.server.ClusterNotFoundException: Cluster not found,
clusterName=*hdpCluster*
    at
org.apache.ambari.server.state.cluster.ClustersImpl.getCluster(ClustersImpl.java:293)
    at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener.isValid(AlertReceivedListener.java:468)
    at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener.onAlertEvent(AlertReceivedListener.java:150)
    at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$ea7961df.CGLIB$onAlertEvent$0(<generated>)
    at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$ea7961df$$FastClassByGuice$$a5084ed4.invoke(<generated>)
    at
com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
    at
com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
    at
org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:43)
    at
com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
    at
com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
    at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$ea7961df.onAlertEvent(<generated>)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at
com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
    at
com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
    at
com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

--

*Sandeep Kumar,*
 Mobile +91-9866507368

*“Happiness is not a destination, It is the journey”*

Mime
View raw message