About banshidhar_saho

banshidhar_saho · ‎05-30-2023

Hi @steven-matison The issue got fixed after making below 2 changes in /etc/krb5.conf file 1. Issue was a include line in my /etc/krb5.conf file which was not valid. Removed below from /etc/krb5.conf "includedir /etc/krb5.conf.d/" 2. On macOS the default client does not fall back to TCP. In krb5.conf prefix kdc value with tcp/ to force the client to use TCP if your corporate network blocks UDP. kdc = tcp/kdc.example.com:88 Regards, Banshi.

banshidhar_saho · ‎05-30-2023

Hi @steven-matison You are right. I have replaced actual REALM with EXAMPLE.COM while posting. I have checked connectivity using "nc -zv" and "ping" command. Connectivity is fine. ==== nc -zv <kdc_server_VIP> <KDC_Port> Connection to xxxxxxxx port xxxxxx [tcp/sqlexec] succeeded! ==== --- <kdc_server_VIP> ping statistics --- 13 packets transmitted, 12 packets received, 7.7% packet loss ==== "kinit: krb5_get_init_creds: unable to reach any KDC in realm EXAMPLE.COM, tried 0 KDCs" By seeing the above error, I feel it's not able to locate the krb5.conf file. When we run kinit command, is it referring to /etc directory for krb5.conf file or some other location in Mac machine? Regards, Banshi.

banshidhar_saho · ‎05-30-2023

Hi Team, I want to setup kerberos client in my Mac Laptop having MacOS Monterey (version 12.6.5). I have put the krb5.conf file at below paths. /etc/krb5.conf /Library/Preferences/edu.mit.kerberos But when I try to run kinit, i get gelow error. -- kinit -kt /Users/banshidhar_sahoo/Desktop/POC_KEYTAB/test.headless.keytab test@EXAMPLE.COM kinit: krb5_get_init_creds: unable to reach any KDC in realm EXAMPLE.COM, tried 0 KDCs -- I have also set the ENV Variable as below: KRB5_CONFIG=/etc/krb5.conf But getting same error while doing kinit. Can you please suggest how to point to krb5.conf so that it can reach out to the correct kdc server. Regards, Banshi.

banshidhar_saho · ‎02-16-2022

Hi All, I want to append cluster name in the 'Cloudera Alert mail subject'. I am not getting any configuration for same. Please suggest how to do that. Current Subject: [Cloudera Alert] 4 Alerts since 2:31:41 AM Want to change as below (assuming cluster name as ABC): [Cloudera Alert - ABC ] 4 Alerts since 2:31:41 AM Regards, Banshi.

banshidhar_saho · ‎11-05-2020

Hi Team, Thank you very much for promptly responding and providing useful solution/direction. While testing, app team reported that child dir/files are having r-x (for dir) and r--(files) for Others. Looks like ACL are not getting inherited to child dir and files. Can you confirm if ACL should inherit to child dir and files or not? Is there any other configuration that I need to check and modify? Regards, Banshi.

banshidhar_saho · ‎11-04-2020

Hi @Shelton, Thank you very much for sharing the exact commands. Only thing that needs to change in the shared commands is - others should be other Here is the command that worked for me. $ hdfs dfs -setfacl -m other::--- /path/to/dir Regards, Banshi.

banshidhar_saho · ‎11-04-2020

Hi @tusharkathpal , Thank you very much. I tested it. It worked for ownership. I want 750 permission on the directory recursively. However it's not reflecting in case of new file. Is there a way to do that? Idea is to restrict 'others' from accessing the file/dir. Regards, Banshi.

banshidhar_saho · ‎11-04-2020

Hi All, In our CDP 7.1.2 cluster, default ownership of any file or directory is <user>and supergroup. One application team wants their data owner group to be their own group in stead of supergroup. for example: Let the app team user is 'abc' and group is 'abc'. Currently owner and group for any file/dir in HDFS is abc:supergroup. They want it to be abc:abc. Please suggest how to achieve this so that any new file created by abc user will have ownership as abc:abc. Regards, Banshi.

banshidhar_saho · ‎09-07-2020

Hi @GangWar, As per CDH package information, Impala 3.2 comes with CDH 6.3.x. Not with CDH 5. Refer below details. ====== CDH 5.x comes with Impala 2.x. https://docs.cloudera.com/documentation/enterprise/release-notes/topics/cdh_vd_cdh_package_tarball_515.html#cm_vd_cdh_package_tarball_515 CDH 6.3.x comes with Impala 3.2. https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_cdh_63_packaging.html#concept_rtm_b5p_m3b ====== Can you elaborate how to upgrade impala from 2.11 to 3.2 in CDH 5.14. Regards, Banshi.

banshidhar_saho · ‎09-07-2020

Hi All, Good Afternoon. We have CDH 5.14 and Impala 2.11 in one of our Cloudera cluster. We have a requirement to upgrade Impala to 3.2 in the same cluster. Please suggest us the best way to achieve this. Can we just upgrade Impala without upgrading CDH. Regards, Banshi.

Online	Offline
Last Visited	‎10-29-2024 11:31 AM

Member Since	‎08-03-2018 05:42 AM
Last Visited	‎10-29-2024 11:31 AM
Posts	26
Kudos received	2

Cloudera Community

Re: Kerberos authentication from MacOS Monterey to...

Re: Mapreduce job failure due to hadoop-unjarxxxxx...

Re: Kerberos authentication from MacOS Monterey to...

Re: Kerberos authentication from MacOS Monterey to...

Kerberos authentication from MacOS Monterey to acc...

How can I change Cloudera Alert mail subject

Re: HDFS file/dir ownership to be <user>:<correspo...

Re: HDFS file/dir ownership to be <user>:<correspo...

Re: HDFS file/dir ownership to be <user>:<correspo...

HDFS file/dir ownership to be <user>:<correspondin...

Re: Upgrade Impala to 3.2 in CDH 5.14

Upgrade Impala to 3.2 in CDH 5.14