Member since
03-11-2020
186
Posts
28
Kudos Received
40
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
449 | 11-07-2024 08:47 AM | |
309 | 11-07-2024 08:36 AM | |
424 | 06-18-2024 01:34 AM | |
230 | 06-18-2024 01:25 AM | |
498 | 06-18-2024 01:16 AM |
03-30-2023
04:11 AM
@jjjjanine Thanks for providing your valuable inputs.
... View more
01-25-2023
09:26 PM
If the same Node is getting down every time, it's worth checking the Memory utilization at the OS end. You can check the /var/log/messages of the NN host when the NN went down and check if the process is getting killed by an oom.
... View more
01-16-2023
11:44 PM
@techfriend this can be resolved after modifiying the principle. WARNING: no policy specified for mapred/ip-172-31-46-169.us-west-2.compute.internal@HADM.RU; defaulting to no policy
add_principal: Principal or policy already exists while creating "mapred/ip-172-31-46-169.us-west-2.compute.internal@HADM.RU".
+ '[' 604800 -gt 0 ']'
++ kadmin -k -t /var/run/cloudera-scm-server/cmf5922922234613877041.keytab -p cloudera-scm/admin@HADM.RU -r HADM.RU -q 'getprinc -terse mapred/ip-172-31-46-169.us-west-2.compute.internal@HADM.RU'
++ tail -1
++ cut -f 12
+ RENEW_LIFETIME=0
+ '[' 0 -eq 0 ']'
+ echo 'Unable to set maxrenewlife'
+ exit 1 modprinc -maxrenewlife 90day +allow_renewable mapred/ip-172-31-46-169.us-west-2.compute.internal@HADM.RU
... View more
01-10-2023
05:47 AM
To resolve this issue, open /opt/cloudera/cm/bin/gen_credentials.sh for editing and add the following to the very end of the script: exit ${PIPESTATUS[0]} And then try generating Kerberos credentials once more.
... View more
12-27-2022
07:51 AM
2 Kudos
@asish Thanks!!! that worked.
... View more
12-25-2022
11:33 AM
I solved problem, reason was not in filter
... View more
12-23-2022
09:19 PM
@quangbilly79 It should be /opt/cloudera/parcels/SPARK2/lib/
... View more
12-21-2022
09:41 PM
@kvbigdata What happens if you set Cloudera Manager > Hive > Configuration > Service Monitor Client Config Overrides > Add
Name: hive.metastore.client.socket.timeout
Value: 600 We have provided the below information regarding the current situation of the canary jira . https://my.cloudera.com/knowledge/quotError--The-Hive-Metastore-canary-failed-to-create-a?id=337839 You have only one workaround ,that is to disable the canary test as you already did currently and that will not harm anything on your cluster . Currently the workaround is to disable the Canary tests on the HMS. # Access HIve Service
# Configuration Tab >> Look for Hive Metastore Canary Health Test
# Uncheck the box
# Restart the service.
... View more
12-18-2022
07:25 PM
1 Kudo
@Tomas79 To get the truststore password and location use below CM API curl -s -k -u admin:admin 'https://CM HOSTNAME(FQDN):7183/api/v45/certs/truststorePassword' If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.
... View more
12-18-2022
07:15 PM
@myzard Increase the timeout below. You can also check after changing the below property from Ambari UI > Advance Hive-interactive-env:
Number of retries while checking LLAP app status = 40
(It will show a warning, please ignore that and save)
This should increase the timeout from 400 to 800s. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.
... View more