This has been fixed in later releases of Cloudera Manager and CDH. When you manage the cluster through CM the config, and changes later on, will be automatically deployed to hive server.   Also don't forget to make sure that hive user must have permission to submit to all queues. Simplest way is to add Hive to the root submit queue ACL.   Wilfred ... View more

You can have differences between the options for the NMs that is not the problem. It could be that the difference in HW used in the NMs requires a different JVM option to be set so it is something that we allow and will also work.   However there can not be an empty line in the options. An empty line in the options is passed on to the settings in the script to set the environment etc. That is where it breaks. The empty line breaks the setting into two in the script which should not happen. The empty line(s) should be trimmed before we generate that settings script, which is the jira I filed.   Wilfred ... View more

Good to hear that you have found the discrepancy between the nodes and have been able to fix it. I reproduced your issue internally on Cloudera Manager 5.9 I have logged an internal jira to fix CM and not allow you to properly handle adding the empty line in the options.   Wilfred ... View more

The issue you have is due to the empty line in theYARN_NODEMANAGER_OPTS variable. That empty line should not be there and is causing the split to fail. Can you check what is in the "Java Configuration Options for NodeManager" in Cloudera Manager and make sure that there is no empty line in that config?   Thanks, Wilfred   ... View more

No this is not a known issue as far as I know. If you have a support contract please open a support case and we can look into it further for you.   Wilfred ... View more

Those directories should be cleaned up in current releases via either SPARK-7503 and or SPARK-7705. They are specific for yarn based setups. It should still happen automatically.   Wilfred ... View more

Umesh,   Those settings are for Spark standalone clusters only. I would strongly advise you not to run standalone but use Spark on Yarn. When you use Yarn the problem does not exist as Yarn handles it for you.   Wilfred ... View more

For the application ownload the application logs and check what the error is in the logs:   yarn application -applicationId APPID -appOwner USERID Check the exit codes of the application and you should be able to tell in a bit more detail what is going on.   Wilfred ... View more