Re: Old Cluster name appering in logs even after Ambari-Server Reset Query!

[Sumit Mohanty]

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 
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()
at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$ea7961df$$FastClassByGuice$$a5084ed4.invoke()
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()
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”*

Old Cluster name appering in logs even after Ambari-Server Reset Query!

[Sandy]

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()
at
org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$ea7961df$$FastClassByGuice$$a5084ed4.invoke()
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()
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”*

Re: Query regarding Python Client and Ambari Shell in Ambari

[Sandy]

Reposting as there was no answer earlier.

On 20-Jan-2017 12:54 PM, "Sandy"  wrote:

Hi folks,

I needed to get automation of ambari tasks done through scripts (python)
and created few scripts for Cluster Creation, Service Checks, Rolling
Upgrade by writing wrapper functions on top of REST APIs.

Noticed that there was some progress made to provide Python Client/Ambari
Shell but then development was stopped an year back.  I am willing to
contribute to these projects but curious to know the reason why they aren't
in active development - Is it due to bandwidth issue?  Some blocker?  There
are better alternatives?

Requesting your response.

Warm Regards,
Sandeep.

Re: How to tell when Ambari server DB was upgraded

[Jonathan Hurley]

There was an initiative to capture this information: AMBARI-16030 ... but this 
seems to have stalled.

If you still have the logs from Ambari Server, you can see when upgrades run by 
looking for text similar to:
Upgrading schema to target version = 2.4.2.0


On Feb 2, 2017, at 10:56 AM, Di Li 
> wrote:

Hello folks,

Are there any indications in Ambari server DB on when it has been upgraded
by the ambari-server upgrade command ?

For example, if I upgrade Ambari from version 2.2.0 to 2.4.2 at "Thu Feb  2
07:54:49 PST 2017" , will this timestamp/date-time info store in the
database ?

I would like to know this information in order to check if certain
operations had run (similar to the service check validation done by the
express upgrade prechecker)

Di

How to tell when Ambari server DB was upgraded

[Di Li]

Hello folks,

Are there any indications in Ambari server DB on when it has been upgraded
by the ambari-server upgrade command ?

For example, if I upgrade Ambari from version 2.2.0 to 2.4.2 at "Thu Feb  2
07:54:49 PST 2017" , will this timestamp/date-time info store in the
database ?

I would like to know this information in order to check if certain
operations had run (similar to the service check validation done by the
express upgrade prechecker)

Di

[GitHub] ambari pull request #50: AMBARI-19850. Default value for storm.messaging.net...

[tibkiss]

GitHub user tibkiss opened a pull request:

https://github.com/apache/ambari/pull/50

AMBARI-19850. Default value for storm.messaging.netty.max_retries is 
incorrect



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tibkiss/ambari 
fix/storm.messaging.netty.max_retries

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ambari/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit 4386d85d4edfa7cce4b73ed97c74c20ffdb884e8
Author: Tibor Kiss 
Date:   2017-02-02T14:12:40Z

AMBARI-19850. Default value for storm.messaging.netty.max_retries is 
incorrect




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---