Hello @krishpuvi    Thanks for using Cloudera Community. Based on the Post, You wish to run HBase Major Compaction on a particular queue to ensure the Compaction activity doesn't impact other resources in the Cluster.    Please note that HBase Major Compaction isn't using any YARN managed resources & as such, We can't map Major Compaction to be run on any YARN Queue. You can restict MajorCompaction to use lesser bandwidth via [1] & [2], which explains the "PressureAwareCompactionThroughputController" with Min & Max Speed along with the Parameter to disable any Speed Limit via "NoLimitThroughputController". Additionally, You can disable Compaction & run Compaction manually during Off-Business-Hours at Table/ColumnFamiliy Level as well.    - Smarak   [1] https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/configuring-hbase/topics/hbase-limit-the-speed-of-compactions.html [2] https://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/regionserver/throttle/PressureAwareCompactionThroughputController.html   ... View more

Hello @proble    As we haven't received any response from your side, We shall be marking the Post as Resolved. Having said that, Please do share your experience with handling the concerned issue & whether the details shared by us assisted you.    In short, the HBase Table Creation is failing as Master hasn't completed Initialisation. You have to use HBCK2 Tool to assign the HBase:Meta & HBase:Namespace (Whichever isn't assigned as per Master Logs). Link [1] covers our response to the Post on 2021/05/31 with the Log trace to be verified in Master Logs & the Steps to be followed. We hope the Post was helpful to you & assisted in resolving the issue.    - Smarak   [1] https://community.cloudera.com/t5/Support-Questions/Error-while-creating-table-in-hbase/m-p/317429/highlight/true#M227161   ... View more

Hello @Aman_Patel_CV    Thanks for using Cloudera Community. Based on the Post, You would like to take HBase Table Backup in incremental fashion to S3.    Kindly use [1] for using Incremental Backup to S3, which list the Usage with S3 as Backup Path as well. Additionally, Customer may use Snapshot yet the Snapshot needs to be exported to S3 as covered via [2]. Link [3] also offers more details into S3 Backup Scenario available with S3 & HBase.    Let us know if the shared references assist you. Please report if you have any issues as well & we shall get back to you with the required details.   - Smarak   [1] https://hbase.apache.org/book.html#br.terminology [2] https://hbase.apache.org/book.html#snapshots_s3 [3] https://hbase.apache.org/book.html#br.s3.backup.scenario ... View more

Hello @Priyanka26    As we haven't heard from your side, We shall summarise the Discussion in the Post to ensure the same benefits Users with similar experiences:   PROBLEM: In HDP v3.1.0, HBase NameSpace Region isn't assigned, thereby causing the following Message: 2021-03-17 20:29:54,614 WARN [Thread-18] master.HMaster: hbase:namespace,,1575575842296.0c72d4be7e562a2ec8a86c3ec830bdc5. is NOT online; state={0c72d4be7e562a2ec8a86c3ec830bdc5 state=OPEN, ts=1616010947554, server=itk-phx-prod-compute-6.datalake.phx,16020,1615483461273}; ServerCrashProcedures=false. Master startup cannot progress, in holding-pattern until region onlined.  Your Team tried to use HBCK2 Assign yet the same fails with the following Error: Caused by: org.apache.hbase.thirdparty.com.google.protobuf.ServiceException: java.io.IOException: Call to itk-phx-prod-master-2.datalake.phx/192.168.15.180:16000 failed on local exception: java.io.IOException: Failed to specify server's Kerberos principal name   DISCUSSION SUMMARY: (I) In Customer's HDP v3.1.0, We have a Bug wherein the HBCK2 JAR can't used with the available Hbase-Client & Hbase-Server JAR in a Secure Cluster. There is no issue with the way your team is using the HBCK2. Owing to the Bug being mentioned above, the HBCK2 Jar is throwing the concerned exception. Without the modified Hbase-Client & Hbase-Server JAR, We can try to re-initialize the HBase Cluster yet only if the same isn't a Production Cluster.  (II) The referred JAR aren't available for download publicly. Unfortunately, I am not familiar with any other means other than manual intervention (Start HBase on a new DataDir & Bulkload from previous DataDir being one of them). Such issues aren't present in HDP v3.1.5 onwards.  (III) Your Team decided to use the Bulk-Load approach to ensure HBase is Initialised afresh. [1] shares the Steps used by your Team.    In short, Do Upgrade to HDP v3.1.5 (The same would be a Maintenance Upgrade from v3.1.0 to v3.1.5) as soon as possible. Until then, Such issues require Bulk-Loading. The Bug causing the HBCK2 issue in a Kerberized Environment impacts HDP v3.0.0 through (And inclusive) HDP v3.1.4 & Fixed in HDP v3.1.5.    Thanks again for using Cloudera Community.   - Smarak   [1] https://community.cloudera.com/t5/Support-Questions/Hbase-namespace-table-in-not-online/m-p/313460/highlight/true#M225541  ... View more