Member since
09-25-2018
99
Posts
6
Kudos Received
5
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2885 | 11-03-2021 02:55 AM | |
| 2072 | 09-21-2020 10:04 PM | |
| 3601 | 08-14-2020 03:20 AM | |
| 4826 | 08-20-2019 11:07 PM | |
| 10974 | 01-06-2019 07:32 PM |
03-30-2021
08:43 AM
@abagal / @PabitraDas Appreciate all your assistance / inputs on this. Thanks Wert
... View more
09-11-2020
04:22 PM
@wert_1311 Domain name changes will affect the KDC database. Kerberos is super sensitive to domain changes according to experience you will have to recreate the KDC database and regenerate the keytabs/principals to enable you applications to reconnect. Cluster hostname If the hosts in the cluster were re-named ie host1.old.com to host1.new.com then ensure those changes are also reflected or resolved by the DNS. This is going a tricky one but fortunately, CM or Ambari will make your work easy now that your domain has changed the earlier generated keytabs have the old domain name . A keytab contains a pair of principals and an encrypted copy of that principal's key it's unique to each host since the principal names include the hostname and may be concatenated with the domain name Delete the old KDC database Usually, as the root user call the Kerberos database utility kdb5_util destroy assuming the old domain was OLD.COM this should delete the keytabs and principals linked to the old REALM, # kdb5_util -r OLD.COM destroy You will need to manually delete the keytabs liked to the old REALM on the file system /etc/security/keytabs/ [HDP] or /etc/hadoop/conf/[CDH]. You will be prompted to confirm before destroying the database, usually, this is a better option if you have second thought rather than using the kdb5_util destroy -f will naturally not prompt you for a confirmation Recreate the New KDC database Use the Kerberos database utility kdb5_util create [-s] assuming the new domain was NEW.COM # kdb5_util NEW.COM create
# kdb5_util -r NEW.COM create -s With the -s option, kdb5_util will stash a copy of the master key in a stash file this allows a KDC to authenticate itself to the database utilities, such as kadmin, kadmind, krb5kdc, and kdb5_util best option. Update Kerberos files. Make sure you update the below files to reflect the new REALM assuming your MIT KDC server's domain isn't changed. krb5.conf
kdc.conf
kadm5.acl
Auth-to-local Rules
jaas.conf files [if being used by applications] Enable Kerberos Using CM or Ambari the process is straight forward. Please let me know if you need more help
... View more
09-07-2020
05:00 AM
@wert_1311 Report Manager is Cloudera Enterprise feature only. So in express it's expected behaviour. You have to purchase a license to use the Report manager and some other Enterprise feature. More details here: https://www.cloudera.com/content/dam/www/marketing/resources/datasheets/cloudera-enterprise-datasheet.pdf.landing.html Also for subscription related queries please Contact Sales.
... View more
08-14-2020
03:20 AM
@GangWar Thanks for your reply. Would like to know, if reducing this to 4000000 help in reducing disk space which event server is consuming, else it would a fruitless exercise. Appericate any help Regards Wert
... View more
02-27-2020
06:38 PM
Thanks @venkatsambath & @EricL this would certainly help in my hadoop journey. Regards
... View more
11-05-2019
08:21 PM
Hi @wret_1311, Thanks for your response and I appreciate for confirming the solution. I'm glad, it helped you 🙂
... View more
10-11-2019
03:59 AM
Hi, Did you tried taking backup of the folder /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state. and deleting all the contents under /var/lib/hadoop-yarn/yarn-nm-recovery/yarn-nm-state and restarting affected node manager? Please share the updates Thanks AKR
... View more
- « Previous
- Next »