Hello @Aco    Thanks for using Cloudera Community. The Post shows the MetaRegionServer ZNode is missing.    Would request you to review the ATS HBase Master & ATS Region Server Logs. The Link [1] is a good link to start with. In few instances, I have observed unchecking "is_hbase_system_service_launch" or Permission issues causing such issues. The ATS HBase Logs would be right place to review here.    - Smarak   [1] https://my.cloudera.com/knowledge/Troubleshooting-YARN-ATS-v2-Issues-ATS-HBase-Modes?id=310144 ... View more

Hello @Shivam171    Thanks for using Cloudera Community. Based on the Post, Your team is receiving no rows while joining 2 Hive Tables. To put things in perspective, You have Table_1 (Hive Managed Table) & Table_2 (Hive External Table referencing HBase Table via HBaseStorageHandler. Both Tables have rows. While fetching rows from Table_2 with a filter condition, we receive Output. While joining the Table_1 with Table_2 with the same filter condition, we receive no Output.    The 2nd SQL referred by you doesn't seems to use any Join Operation. Please share the SQL for reference. Additionally, Verify if the Joining Column has the required match on both Tables both on any Table-Level filter conditions via WHERE Clause. If there are no match in an Inner Join, the Output would be Zero.   - Smarak  ... View more

Hello @Satya_Singh    Thanks for using Cloudera Community. Based on the Post, Your team is deleted data from a HBase MoB Table & experiencing no HDFS Size reduction post Compaction as well.    Wish to confirm whether your Team is checking the Size of the Table within the Table Level Directory (/hbase/data/<NameSpace>/<Table>) after the MajorCompaction. Additionally, Check the HBase Data Directory recursively for the concerned Table Name (hdfs dfs -ls -R /hbase | grep <TableName>) to confirm if the concerned Table data is being persisted within the Archive Directory. If the Table Data is being moved to Archive Directory, Check the HBase Master Logs for Cleanup details post TTL. Else, enable HBase Master Trace Logging to fetch granular details on the Cleanup activities pertaining to the Archive Directory.    - Smarak ... View more

Hello @CaptainJa    Thanks for using Cloudera Community. Based on the post, the Ranger UI is showing audits slowly sometime, while being fast during other period.    The Ranger Audit is powered by Solr (Infra-Solr in HDP) & likely, the delay in Ranger Audit UI Slowness is being caused by the Slowed Indexing of Audit Documents by Solr. Worth reviewing Link [1], especially "Tuning Environment Specific Parameters" Section, which deals with RangerAudit Collection Shard Count based on the Document being indexed per day. Additionally, Review the Infra-Solr Logs for any warning around data ingestion.    - Smarak   [1] https://docs.cloudera.com/HDPDocuments/Ambari-2.7.5.0/using-ambari-core-services/content/amb_tuning_performance_for_ambari_infra.html ... View more

Hello @rajatsachan    Thanks for sharing the details into the Steps used by you to resolve the issue. This would definitely assist fellow Community Members facing similar issues. If you have no further concerns, Kindly mark the Post as Solved as well.    Thanks, Smarak ... View more

Hello @rajatsachan    Thanks for the Update concerning the post. Based on your Update, Your team used the HBCK2 Jar to move the RegionState to CLOSED. Post the concerned change, Were you able to successfully bring the Regions Online as well ? If Yes, Kindly confirm & share the steps to ensure fellow Community Users like @sainivedant41 can use the same as well.    - Smarak ... View more

Hello @rajatsachan    Based on the Master Trace shared by you, Check the RS "2385" Logs for the concerned RegionID. The RS Logs should provide additional details around the same.   - Smarak ... View more

Hello @rajatsachan    Thanks for the Update. The Screen-Shot showing Error can be ignored as they pertain to the Solr. The Regions are in CLOSING State i.e. the Regions are yet to Closed before they can be opened on a different RegionServer. The PID UI shows the Source RegionServer is "*2383*allstate*. We need to check the Master Logs & the "2383" RegionServer Logs for the Region ID & they should definitely show the reasoning for the CLOSING State.    - Smarak ... View more

Hello @rajatsachan    Thanks for the details. For the Region which you are trying to assign via HBase Shell, We need to check the Logs (Same RS A & RS B depending on the Region State in Master UI). The Logs would confirm if the Assignment is failing owing to Region failing to Close successfully on RS A or Open successfully on RS B. Depending on the Region State, Check the RS Logs & Master Logs.    Additionally, You mentioned the assignment is taking time or getting hung up. Each Command would have PID (Visible via "list_procedures" in HBase Shell or "Locks & Procedures" in HMaster UI). We can check if the PID is in RUNNABLE/WAITING/FAILED State.    Note that you have ~2K Regions per RegionServer & RegionAssignment being Slow isn't unexpected.    - Smarak ... View more

Hello @sam8686    Thanks for using Cloudera Community. Based on the Post, Your team deleted data from 100+ Tables yet there is no change in Disk Usage. It's likely Compaction must run first before any Space Usage reduction is reflected. There isn't any way to manually run Compaction in Kudu.   Review Link [1] Section "4.10 RowSet Compaction" reporting "We take this opportunity to remove deleted rows".    - Smarak   [1] https://kudu.apache.org/kudu.pdf ... View more