Member since
04-02-2019
12
Posts
0
Kudos Received
0
Solutions
04-24-2023
09:02 PM
I think in case of other built-in services like HDFS and Yarn, there are some kind of health tests that trigger alerts when any one role goes down. What I want to know is how to implement this feature with a custom service created using CSD framework. I couldn't find anything relevant in the CSD doc: https://github.com/cloudera/cm_ext/wiki
... View more
05-07-2021
11:36 AM
Is there any way out for this? In Ambari, there is a role_command_order.json for custom service's component start/stop ordering. Anything similar in Cloudera Manager?
... View more
02-23-2021
10:00 PM
Hi @FRG96 as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post.
... View more
01-14-2021
09:33 PM
@nij23 I have the correct account and resource role in my environment. I restarted the cluster created from the custom cluster definition and when I opened the CM-UI I got this message: Above Text for reference: HTTP ERROR 500 javax.servlet.ServletException: javax.servlet.ServletException: java.lang.NullPointerException: Custom client SSL context, if set, must not be null. URI: /test5/cdp-proxy/cmf/home/ STATUS: 500 MESSAGE: javax.servlet.ServletException: javax.servlet.ServletException: java.lang.NullPointerException: Custom client SSL context, if set, must not be null. SERVLET: cdp-proxy-knox-gateway-servlet CAUSED BY: javax.servlet.ServletException: javax.servlet.ServletException: java.lang.NullPointerException: Custom client SSL context, if set, must not be null. CAUSED BY: javax.servlet.ServletException: java.lang.NullPointerException: Custom client SSL context, if set, must not be null. CAUSED BY: java.lang.NullPointerException: Custom client SSL context, if set, must not be null. When I try to open the CM-UI the second time and in any subsequent tries, I get the 403 Forbidden message. I see the 500 Servlet Exception only the first time when I try to access CM-UI. Could it be because the "enableAutoTls" property was automatically set to false when I registered the custom cluster definition even though I had explicitly set it to true in my cluster definition JSON?
... View more