Hello @GregDol    Thanks for using Cloudera Community. This is an Old Post, yet I am sharing a review for other Community Users, in case they encounter the concerned issue.    Reviewing the Post indicates the Issue is likely caused by missing "rt.jar" in the JDK used by the Solr Service. In other words, the concerned Class "java.time.zone.ZoneRulesProvider" is present in "/usr/java/jdk1.8.0_232-cloudera/jre/lib/rt.jar" for CDP Cluster (Path & Version may be different for Customer). The concerned JDK is used by the various Services running including Solr.   In your scenario, the concerned Class appears to be missing. Assuming your team wish to confirm whether a JAR consists of the Class, you may use Command [ /usr/java/jdk1.8.0_232-cloudera/bin/jar -tvf /usr/java/jdk1.8.0_232-cloudera/jre/lib/rt.jar] to list the Classes, which should include "java.time.zone.ZoneRulesProvider" as well. If your Team is using any different JDK, Review the same & ensure the "rt.jar" is present for Class "java.time.zone.ZoneRulesProvider" to be loaded successfully.    Regards, Smarak ... View more

Hello @QiDam    As stated by JD above, the CDE Service relies on Ozone Service on Base Cluster. If Ozone Service wasn't in Healthy State, the CDE Service enabling would fail with similar tracing as shared by you. We would recommend the following checks: Ensure Ozone Service is Up & Running on Base Cluster.  Create a new Environment & check CDE Service enabling on the new Environment.  If the above CDE Service enabling on new Environment is Successful, Reattempt the CDE Service enabling on the existing Environment. If the above Suggestion doesn't help, We would suggest engaging Support as any further troubleshooting would require sharing the Logs over the Public Community forum, which may have Customer's details.    We shall mark the Post as Resolved now. If you have any concerns, Feel free to Update the Post likewise.    Regards, Smarak ... View more

Hello @sfdragonstorm & @pacman    In the Region Name "img,0006943d-20150504220458043384375D00000002-00093,1527295748538.7b45a9f6f5584fc50b3152d41a5323a2.", the Table Name is "img", StartKey is "0006943d-20150504220458043384375D00000002-00093", Timestamp is "1527295748538" & "7b45a9f6f5584fc50b3152d41a5323a2" is the Region ID.    Under HBase Data Directory, each Table Directory would have Region-Level Directories as identified by Region ID ("7b45a9f6f5584fc50b3152d41a5323a2" in Example). The Region ID is an MD5 encoded string for the Region Name & generated by HBase itself. Refer [1], if your Team wish to review the same.    Regards, Smarak   [1] https://hbase.apache.org/apidocs/src-html/org/apache/hadoop/hbase/client/RegionInfo.html#line.164   ... View more

Hello @hanumanth    Hope you are doing well. Kindly confirm if your ask has been addressed by our Post dated 2022-11-09. If Yes, Please mark the Post as Solved. If No, Feel free to share any further queries/concerns & we shall respond accordingly.   Regards, Smarak ... View more

Hello @sekhar1    Thanks for using Cloudera Community. The Error received by you is caused by a missing entitlement. For Customer without the concerned entitlement, the Error is received. We are improving the Product Experience to ensure the Error isn't displayed for Customer missing the entitlement.    In your Case Or any one receiving the error, Kindly engage Cloudera Support to enable an entitlement to avoid getting the concerned error. Since Entitlement enabling requires few Customer's specific details, the Support engagement path is recommended.    Regards, Smarak ... View more