Hi Greg,
Was wondering which version of Ambari you were using?
When maintenance mode is enabled on service, bulk host operations are
ignored.
When maintenance mode is enabled on hosts, service level operations are
ignored on host.
So was wondering if you enabled maintenance mode in one level, and
Anyone know if this is intentional or not? It seems to ignore setting the
HostRole/state if the host_component is in maintenance mode. I was able
to work around it by immediately setting maintenance mode after changing
the state. But that leads to a race condition as to whether nagios notices
the
Ambari's git commit log would be the easiest way to browse changes for a
release.
https://github.com/apache/ambari/commits/branch-1.6.1
On Mon, Jul 21, 2014 at 10:29 AM, Anoop Rajendra wrote:
> Hey all,
>
> Is there a changelog available for Ambari 1.6.1?
>
> -a
>
--
CONFIDENTIALITY NOTICE
Hey all,
Is there a changelog available for Ambari 1.6.1?
-a
Hi Suraj,
You can edit the /usr/sbin/ambari-server.py file on the VM running Ambari
server and search for START_CMD.
The debug instruction is just below it in the python script. Rename the
DEBUG_CMD to the start and the start to something else and restart the
ambari server.
You can then connect
I did some debugging and it turns out that the problem is that I set
maintenance mode prior to stopping the components. Unfortunately, this
makes it so nagios starts alerting me. My script is attempting to remove
a slave node from a cluster by doing the following:
1. Set maintenance mode on all
Can anyone help me on running Ambari from Eclipse or Locally in a Linux
development machine ? So testing changes will be easier.
I checked in
https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Code+Layout .
No documentation is under Ambari-Server.
--
Suraj Nayak
On Friday 11 July 201
