Hi all,
There are 2 unit test failures in ambari-server that I see locally as well as
Apache builds. If this is caused by your changes, please can you take a look at
it and address it ASAP.
Thanks
Jayush
https://builds.apache.org/job/Ambari-trunk-Commit/4493/testReport/
All Failed Tests
Test Nam
Fine with flag, but prefer to use rco as default though. Since the default
behavior is only recently changed in the last 6 months. It would be better
to restore to the v1 behavior.
regards,
Eric
On Mon, Mar 14, 2016 at 5:55 PM, Bhuvnesh Chaudhary
wrote:
> I have created a placeholder JIRA doc
I have created a placeholder JIRA documenting the feature and if we all
agree let's do it.
https://issues.apache.org/jira/browse/AMBARI-15417
Thanks,
Bhuvnesh Chaudhary
Email: bchau dh...@pivotal.io
Desk: +1-650-846-1696 | Mobile: +1-973-906-6976
On Mon, Mar 14, 2016 at 11:17 AM, Alejandro Fernan
Hi,
I ambari-server and ambari-agent (version 2.1.2-377), oozie_tmp_dir path is
hard-coded to /var/tmp/oozie. This is problematic on CentOs/RHEL where /var/tmp
is trashed periodically. Because of which, Oozie service stop/start through
Ambari UI thrown an error about given path does not exist
I agree configuring this with a flag is ideal.
Thanks,
Alejandro
From: Bhuvnesh Chaudhary mailto:bchaudh...@pivotal.io>>
Date: Monday, March 14, 2016 at 11:06 AM
To: Ambari mailto:dev@ambari.apache.org>>
Cc: Sumit Mohanty mailto:smoha...@hortonworks.com>>,
Alejandro Fernandez
mailto:afernan...@
Thank you very much Robert for the detailed explanation. It helps
to understand the background.
Regarding HAWQ to capitalize on retry: We can potentially do some
tweaks to verify if HAWQ has been initialized or not according to the
current behavior, and change the way of doing init so that it can
We have a use case where a service depends on Sqoop, Hive Metastore, HBase
Client, Hadoop Client on a worker node. We found that Hadoop Client is
sometimes not yet installed when our service installation has already
started. This looks like a big problem for our use case. Is there a way
to keep
Hi Bhuvnesh,
You are correct. The Blueprints deployment mechanism in Ambari no longer
relies on Role-command ordering to install or start components across the
cluster.
This change to Blueprints was actually implemented in Ambari 2.1.0, so it has
been around for several releases now. The new
