Member since
01-16-2014
336
Posts
43
Kudos Received
31
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3354 | 12-20-2017 08:26 PM | |
3348 | 03-09-2017 03:47 PM | |
2815 | 11-18-2016 09:00 AM | |
4929 | 05-18-2016 08:29 PM | |
3785 | 02-29-2016 01:14 AM |
12-08-2017
03:35 AM
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
03-09-2017
03:47 PM
2 Kudos
The code is there and you can use it if you want it but we do not expose it in the Cloudera Manager UI. You will need to use a configuration snippet in the HDFS service for core-site.xml (cluster wide) and add the relevant keys: hadoop.security.group.mapping -> org.apache.hadoop.security.CompositeGroupsMapping
hadoop.security.group.mapping.providers -> ProviderName1,ProviderName2
hadoop.security.group.mapping.providers.combined -> true
hadoop.security.group.mapping.providers.<ProviderName1> That should work. Wilfred
... View more
01-08-2017
04:03 PM
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
01-04-2017
07:07 PM
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
12-22-2016
04:56 PM
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
12-01-2016
06:24 AM
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
12-01-2016
05:56 AM
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
11-30-2016
09:56 PM
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
11-18-2016
09:00 AM
1 Kudo
In CM you can retrieve the file that is pushed out from the RM instance information page. Go to the Yarn service -> Instances (in the bar on top) -> Select a RM instance from the list on the right -> Process (in the top bar again). There should be a list of all the configuration and environment files there that you can download. If they do not show up click the Show link under Configuration Files/Environment. Hope that helps, Wilfred
... View more
06-13-2016
04:42 AM
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