Member since
05-21-2020
109
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
15302 | 03-29-2023 04:12 AM |
05-08-2023
05:12 AM
Hi @Ammar00, If possible, please share /etc/ambari-server/conf/ambari.properties and ambari-server logs.
... View more
04-20-2023
05:09 AM
Hello @xedonedron, I believe that something is wrong with the configured repository on the hosts. The 403-Forbidden states that either you do not have access to the repository or it is not available. As far as I know the public repositories for HDP have been disabled.
... View more
04-17-2023
05:06 AM
Hello @xedonedron, What is the error you are receiving? You can safely click on "Proceed Anyway" and install the service on Ambari.
... View more
03-29-2023
04:23 AM
Hi @aleezeh, please make sure that "Audit Logging" setting is enabled for the masking policies.
... View more
03-29-2023
04:12 AM
1 Kudo
Hi @BrianChan, This is a known CM issue, which incurs a bad spark-defaults.conf generated by the CM Agent after some users (or applications) logged the hosts as root and kinited as some user (for example, hdfs), and left that ticket cache around. To avoid the issue, do the following: Navigate to Cloudera Manager > Spark > Configuration. Add the following in the Spark Client Advanced Configuration Snippet (Safety Valve) for spark-conf/spark-defaults.conf. Ensure a correct value is set: spark.eventLog.dir=hdfs://nameserviceXYZ/user/spark/applicationHistory Deploy the client configuration If this helps to resolve the issue, please accept this as a solution. Thanks.
... View more
05-24-2022
11:01 AM
Hi @AlohaDecember, Could you please share your spark interpreter settings?
... View more
10-21-2021
01:47 PM
@ajaytrivedi can you help here?
... View more
10-21-2021
01:40 PM
Hi @PrernaU , It seems like the logged in user does not have permission to access the interpreter page. The authorization is dependent on how you have configured your shiro authentication. If you have integrated your AD with zeppelin the make sure the role mapping has done correctly and you have the correct user/group defined in the shiro roles section.
... View more