About dice

dice · ‎02-18-2015

You may be hitting YARN-2964 which is current limitation of getting delegation toke over llama. To prevent the error, you should implement the following configurations. Configuring YARN for Long-running Applications http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_sg_yarn_long_jobs.html

dice · ‎02-17-2015

Thanks for the information! Hmm, I have never met such kinds of problem, but I don't think the change you did will break the other finctionalities. Daisuke

dice · ‎02-17-2015

Hi zero, It appears that there's a mismatch of encryption types between clients and the KDC server. Please follow the below steps and see if it helps. 1. Stop the ZooKeeper service through CM (Note that you need to stop entire cluster). 2. Go to CM --> Administration --> Kerberos --> 'Kerberos Encryption Types', then add the following encryption types: aes256-cts aes128-cts des3-hmac-sha1 arcfour-hmac des-hmac-sha1 des-cbc-md5 des-cbc-crc 3. Do deploy krb5.conf through CM, and try to start the ZooKeeper Service.

dice · ‎02-17-2015

http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_mc_hive_udf.html will help.

dice · ‎02-16-2015

Before you do try mine, please uninstall krb5-server and krb5-workstation packages.

dice · ‎02-16-2015

The original script Eric Sammer wrote up used to be working when CM didn't have the wizard which enables Kerberos. I made some changes with his. Please use mine instead and specify the password as cloudera in the wizard. See also the step 7 in my github page. https://github.com/daisukebe/krb-bootstrap daisukebe has changed the behavior for configuring Kerberos with Cloudera Manager 5.1 (and above). Then this script just generates a principal as cloudera-scm/admin for CM with a password as 'cloudera'.

dice · ‎02-16-2015

You're welcome!

dice · ‎02-16-2015

Kerberos (KDC) is not included with the VM, but you can easily configure KDC server by yourself in the VM. I usually run krb-bootstrap for this kinds of test purpose: https://github.com/daisukebe/krb-bootstrap.

dice · ‎02-16-2015

Sentry is a service for strong authorization over Hadoop cluster, so that the cluster needs to be strongly authenticated using Kerberos or LDAP before you integrate Sentry.

dice · ‎02-15-2015

Hi Jason, This might be due to the mismatch of encryption types between clients and the KDC server. Please follow the below steps and see if it helps. 1. Stop the cluster through CM 2. Go to CM --> Administration --> Kerberos --> 'Kerberos Encryption Types', then add the following encryption types: des3-hmac-sha1 arcfour-hmac des-hmac-sha1 des-cbc-md5 des-cbc-crc 3. Do redeploy krb5.conf through CM, and restart the cluster. Daisuke

Online	Offline
Last Visited	‎12-22-2021 11:56 PM

Member Since	‎08-01-2013 05:35 PM
Last Visited	‎12-22-2021 11:56 PM
Posts	187
Kudos received	11

Cloudera Community

Re: Adding a host-- HBase not copying over all Jar...

Re: Can't find the latest SOLR package in CM

Re: Kafka not in list of services to be added

Re: Failed to execute command Initialize Solr on s...

Re: CDH 5.3 Impala Llama Kerberos: yarn is not all...

Re: CDH 5.3 Impala Llama Kerberos: yarn is not all...

Re: Can CDH5.3 Sentry work without Kerberos?

Re: kerberos Could not configure server because SA...

Re: Hive Context in CDH 5.3.x

Re: Can CDH5.3 Sentry work without Kerberos?

Re: Can CDH5.3 Sentry work without Kerberos?

Re: Can CDH5.3 Sentry work without Kerberos?

Re: Can CDH5.3 Sentry work without Kerberos?

Re: Can CDH5.3 Sentry work without Kerberos?

Re: kerberos authentication failure: GSSAPI Failur...