Member since
01-16-2018
602
Posts
46
Kudos Received
100
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
38 | 04-15-2024 12:28 AM | |
51 | 04-15-2024 12:17 AM | |
93 | 04-15-2024 12:04 AM | |
60 | 04-14-2024 11:54 PM | |
73 | 04-14-2024 11:45 PM |
11-15-2022
09:11 PM
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
11-09-2022
10:53 PM
Hello @hanumanth Thanks for using Cloudera Community. Based on the Post & Screenshot shared, the CPU Usage for the concerned Timeframe of (2022-10-27 11:30 PM - 2022-10-28 05:30 AM) was 2.2% as a Mean i.e. Average, considering the samples collected during the concerned period. Regards, Smarak
... View more
11-09-2022
10:41 PM
Hello @TheFixer We hope your queries around the RegionServer log traces has been answered by us. As such, We shall mark the Post as Solved. If you have any further ask, Feel free to update the Post & we shall get back to you accordingly. Regards, Smarak
... View more
11-09-2022
10:39 PM
Hello @Venkatd Since this is an Old Post & we have shared a few Action Plan with missing "atlas.application.properties" from Atlas Configuration Directory in HBase Configuration Directory "/etc/hbase/conf" being the Most-Likely reason for the concerned failure along with Steps to mitigate the HMaster/RegionServer failure (By setting "hbase.coprocessor.abortonerror" as "false") to avoid any Co-Processor failure cause Master/RegionServer startup failure, We shall mark the Post as Solved now. Thank You for using Cloudera Community. Regards, Smarak
... View more
11-09-2022
08:51 AM
1 Kudo
Hello @TouguiOmar Update acknowledged. You may wish to use Step (VI) from above Action Plan & share the Outcome. Regards, Smarak
... View more
11-08-2022
11:22 PM
Hello @Venkatd Thanks for using Cloudera Community. This is an Older Post, yet I am sharing a review for fellow Community Users. Based on the Post, the Service is affected owing to "org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor" issues. A Quick Solution is to use "hbase.coprocessor.abortonerror" as "false" to avoid any Co-Processor failure cause Master/RegionServer startup failure. Typically, Such issues are caused by few factors as shared below: 1. Missing "atlas.application.properties" from Atlas Configuration Directory in HBase Configuration Directory "/etc/hbase/conf". 2. The HBase-Atlas Hook being disabled. 3. Ensure "org.apache.atlas.hbase.hook.HBaseAtlasCoprocessor" is present in the Co-Processor Classes ("hbase.coprocessor.<master|region>.classes"). The Missing "atlas.application.properties" file is the Most-Likely Cause. Regards, Smarak
... View more
11-08-2022
11:12 PM
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
11-08-2022
11:05 PM
Hello @balance002 The Error "IllegalStateException: Invalid currTagsLen" likely indicates Hfile Corruption & a possible factor is too many cell-level ACL tags being applied to a specific table. Unfortunately, such Corruption requires additional review into the Hfile Metadata & is extremely rarely observed. As such, It's best to open a Support Case with Cloudera, if you are experiencing the concerned issue to avoid sharing any Hfile Metadata (Which includes Customer's Data) over Community. As a last resort, We need to use the HFile tool with the -p or -k flags, and determine which HFile the command fails on. The -p flag will print all of the data scanned, while -k will only check the integrity of the row, but both will fail on the affected HFile, indicating which has the affected cell: (1) Find the bad HFile with: hfile -k <HFile location> (2) Disable the table: disable '<table name>' (2) Move the HFile to a different location in HDFS: hdfs dfs -mv <Hfile location> <tmp location> (3) Reload all of the data from that HFile, applying the tags to those rows so that they are not too large Regards, Smarak
... View more
11-08-2022
10:55 PM
Hello @Kings We hope our Post dated 2022-10-10 has answered your Q & shall mark the Post as Solved. If you have any further ask, Feel free to Update the Post & we shall get back to you accodingly. Thank You for using Cloudera Community. Regards, Smarak
... View more
11-08-2022
10:47 PM
Hello @mohamed_t We hope your Q concerning SDX has been answered. We are marking the Post as Solved. Assuming you have any further ask, Feel free to Update the Post & we shall get back to you accordingly. Regards, Smarak
... View more