@Michael Bronson we do not need to worry about this "stack-recommendations" directory it should be created as soon as we make any configuration changes to ambari UI and when ambari has some recommendations for us. But if you want to test before hand then you might want to refer to the following HCC thread which suggexst how you can run some stack advisory scripts on your own. (i have not tested them manually on my own) https://community.hortonworks.com/questions/141855/stack-advisor-how-to-use-it.html ... View more

@Bill Brooks If you are worrying about the following error message then it is not to be worried much as sometimes due to slow startup ambari might take more than the default 50 seconds time to be completely Up and running. So you can ignore the error if you are able to access the ambari. Try accessing ambari server URL. http://localhost:8080. with the new credentials that you have set ERROR: Exiting with exit code 1. REASON: Server not yet listening on http port 8080 after 50 seconds. . Some explanation about this error you can find tin the following thread: \https://community.hortonworks.com/questions/149848/change-the-port-for-ambari-server.html So edit the "/etc/ambari-server/conf/ambari.properties" and increase the following property value to 120 or 150 seconds. server.startup.web.timeout=120 and then hopefully you should not see that error again. ... View more

@Michael Bronson The latest error indicates that AMS collector is still going down. But after running for some time. Means it requires further tuning. 2018-03-12 08:54:19,037 WARN org.apache.zookeeper.ClientCnxn: Session 0x1621966a8020001 for server null, unexpected error, closing socket connection and attempting reconnect java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) . So can you please restart the AMS collector and then check the heap usage after some time to see if it is reaching the maximum limit? # $JAVA_HOME/bin/jmap --heap $PID_AMS ... View more

@Michael Bronson Please try making any small config change from ambari UI and then see that the dir "stack-recommendations" created or not? If there is nothing to recommend then you won't see the dir created. ... View more

@Michael Bronson Yes, correct, this one should be good. . So please check if the AMS collector host has enough free memory or not? # free -m . ... View more

@Michael Bronson The Cluster Size means the total number of hosts present in the cluster. So if the number of cluster host increases then the ambari metrics data will grow accordingly and hence we will need more data aggregation and data so in that case we will need to have the heap size set accordingly. A rough calculation of heap settings is mentioned in the above tuning doc. - In this case as the AMS is going down very frequently then we should check the following things: 1. Usually it happens when the Heap is not set properly. Increasing the memory works in many cases. So please try to Increased heap memory for AMS collector and hbase. 2. We need to know how many nodes are there in the cluster to see if the current tuning is OK or not? 3. We can check the current AMS tunning by looking at the following logs: (So if you can attach them then it will be good to review them) # tar czhfv ./amsc_etc_$(hostname)_$(date +"%Y%m%d%H%M%S").tar.gz /etc/ambari-metrics-collector/ # tar czhfv ./amsh_etc_$(hostname)_$(date +"%Y%m%d%H%M%S").tar.gz /etc/ams-hbase/ 4. The complete collector logs along with the following from location "/var/log/ambari-metrics-collector" on AMS host. ambari-metrics-collector.log (latest one) hbase-ams-master-*.log (latest one) collector-gc.log (latest) gc.log (latest) . ... View more

@Michael Bronson Through API call it will be bit complex because ambari client needs to send a very huge Payload to make that change. However the easiest option will be to use the following approach from ambari server host: To Enable Auto start Services # /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=set --host=localhost --cluster=TestCluster --config-type=cluster-env -k "recovery_enabled" -v "true" . To Disable Auto start Services # /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=set --host=localhost --cluster=TestCluster --config-type=cluster-env -k "recovery_enabled" -v "false" . Please change the Cluster name "TestCluster" and ambari credentials in the above script . Above script needs to be executed from ambari server host as it has the "config.py" file. ... View more

@Jane Becker @Constantin Stanca If it is happening with few specific users then it will be good to check if by any chance their users name contains any UpperCase/MixedCase letters? Also we can enable the DEBUG on fileview to collect more detailed information (by default the logging level will be INFO) # grep 'INFO' /var/lib/ambari-server/resources/views/work/FILES\{1.0.0\}/view.log4j.properties log4j.logger.org.apache.ambari.view.filebrowser=INFO,filesView . After the change we will need to restart the ambari server and then we can see some additional logging inside /var/log/ambari-server/files-view/files-view.log . ... View more