Member since
04-22-2014
1218
Posts
341
Kudos Received
157
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 26238 | 03-03-2020 08:12 AM | |
| 16375 | 02-28-2020 10:43 AM | |
| 4706 | 12-16-2019 12:59 PM | |
| 4470 | 11-12-2019 03:28 PM | |
| 6652 | 11-01-2019 09:01 AM |
11-19-2016
08:08 AM
There are some vendors who distribute CDH as part of an appliance. I do not know of a closed list of these approved vendors, but an example of an appliance is Oracle's BDA: https://www.oracle.com/engineered-systems/big-data-appliance/index.html
... View more
11-18-2016
04:16 PM
1 Kudo
Hello, There is no lockout feature in Cloudera Manager. If you are using SAML or LDAP, you can leverage their lockout features. There is an internal Cloudera Jira requesting the feature. I'll update it with your interest. Thanks, Ben
... View more
11-17-2016
08:35 AM
Hello David, Sorry we didn't answer your question right away. It seems that something undesirable happened to our documentation in 5.9.0, so the statement we had is no longer available. The stance is the same as in 5.8.0, though: Multihoming CDH or Cloudera Manager is not supported outside specifically certified Cloudera partner appliances. Cloudera finds that current Hadoop architectures combined with modern network infrastructures and security practices remove the need for multihoming. Multihoming, however, is beneficial internally in appliance form factors to take advantage of high-bandwidth InfiniBand interconnects. Although some subareas of the product may work with unsupported custom multihoming configurations, there are known issues with multihoming. In addition, unknown issues may arise because multihoming is not covered by our test matrix outside the Cloudera-certified partner appliances. We will work to correct the documentation so this information is published. Thank you very much for bringing this to our attention. Ben
... View more
11-15-2016
09:41 AM
I do not believe there is any purging of the Cloudera Manager audits. I checked and did not see any code that performed a purge or deletion. Let us know if you see anything that suggests otherwise. Thanks, Ben
... View more
11-14-2016
02:43 PM
Hi... this is old, but just came across it. hiveserver2_enable_impersonation is set at the HiveServer2 role level, so you would need to use the full path to your HiveServer2 role. for instance: curl -X PUT -H "Content-Type:application/json" -u admin:admin -k "https://localhost:7183/api/v12/clusters/cluster/services/hive/roles/hive-HIVESERVER2-609b6bea2fc852513192152e64d3ec19/config" -d '{ "items" : [ { "name" : "hiveserver2_enable_impersonation", "value" : "false" } ] }' Since the attribute does not exist at the service level (where you attempted to set it), the attribute is not found. I hope that might help you or others. Cheers, Ben
... View more
11-08-2016
12:09 PM
Yes, check the Manage krb5.conf through Cloudera Manager box and Save. You can then follow the steps that Katelynn explained. Cloudera Manager will then overwrite your current /etc/krb5.conf when you Click "Deploy Kerberos Client Configuration" from the cluster menu on the front page of Cloudera Manager
... View more
11-08-2016
09:57 AM
SORRY! My copy/paste got messed up... here is the response I intended: It depends... If you use Cloudera Manager to manage your krb5.conf (Manage krb5.conf through Cloudera Manager is checked in Administration --> Settings --> Kerberos) then make the additions as Katelynn recommended. If you are not using Cloudera Manager to mange krb5.conf (Manage krb5.conf through Cloudera Manager is not checked) then you need to edit the /etc/krb5.conf files manually outside of Cloudera Manager. I just wanted to clarify since you could be using Cloudera Manager but not have Cloudera Manager manage krb5.conf.
... View more
11-08-2016
09:55 AM
It depends... If you use Cloudera Manager to manage your krb5.conf (Manage krb5.conf through Cloudera Manager is checked in Administration --> Settings --> Kerberos) If you are not using Cloudera Manager to mange krb5.conf (Manage krb5.conf through Cloudera Manager is not checked) then you need to edit the /etc/krb5.conf files manually outside of Cloudera Manager. I just wanted to clarify since you could be using Cloudera Manager but not have Cloudera Manager manage krb5.conf.
... View more
11-03-2016
08:56 AM
Hello, This type of error can have various causes, but there are a few things to do before troubleshooting this much further: (1) Restart Hue and Hive services to make sure that HiveServer2 is talking to the Metastore properly and that any Hive sessions are cleared out. If the problem still occcurs continue on... (2) Test with beeline. Hue talks to HiveServer2 and the exception you showed is returned by HiveServer2. If you use the deprecated "hive" CLI, that communicates with the Metastore directly and impala-shell communicates with the daemon. Testing with beeline will be a more accurate indicator of the HiveServer2 health. Testing with Impala and hive CLI shows that the metastore is functioning, but now we need to determine if HiveServer2 seems to be ok. Let us know the command you ran and the results
... View more
10-31-2016
12:55 PM
I think you can use the wait() method too as demonstrated here: https://cloudera.github.io/cm_api/docs/python-client/#service-lifecycle-and-commands
... View more