It may be https://issues.apache.org/jira/browse/AMBARI-15235 ... View more

As of now, there is no option to do that. You can create few folders as symlinks such as /usr/hdp and /usr/lib/ambari-server, /var/log etc and then install Ambari and the services. ... View more

@vpoornalingam can you check if on the host where it is failing you have a "ambari_commons" folder in the /var/lib/ambari-agent/tmp folder? ... View more

Thanks for reporting this. This looks like a bug and the work-around you have provided is the valid one till the bug is fixed. ... View more

Sadly, no. In general, the smaller the blueprint the lesser the chances of breaking compatibility. Let me explain a bit as its not an intention to break backward compatibility. At a very high level, blueprint contains a) components and their layout, b) config settings that are Ambari influenced, c) config settings that are stack influenced, and d) templates for *-env/sh files etc. In general, * (a) remains backward compatible even through major releases. * (b) and (c) should remain backward compatible unless some config cleanup is performed e.g. created new configs for env/log4j files, cleaned up how heap sizes are specified - rare * (d) includes scripts - these can go through bug fixes for any release So if you have a blueprint with primarily (a) and only the configs for which you want to over-write the default it should remain backward compatible. The biggest hurdle you can run into is that when you export a blueprint it does not export a minimal blueprint - rather a blueprint with all sections including (d). ... View more

The decommission request from does not wait for decommission to complete - it issues the decommission command to hdfs and then hdfs asynchronously continues the decommissioning operation. At this point the jmx data from NN has to be monitored from the outside to know when hdfs completes decommissioning. ... View more

The desired_stack_id for hostcomponentdesiredstate and servicecomponentdesiredstate and current_stack_id for hostcomponentstate should point to HDP-2.3. That could be the reason for the error you see. Also check the version field for hostcomponentstate and see if that is reporting the 2.3 version. ... View more