Member since
08-07-2018
114
Posts
0
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
972 | 01-09-2024 02:40 AM | |
970 | 10-04-2023 01:48 AM |
01-09-2024
02:40 AM
This may be caused by holes in the region chain, that can be caused by regions not being assigned to any region server or they stuck in transition. Do you see any inconsistencies from hbck report for table USAGE:DATA_TRANSPARENCY?
... View more
11-24-2023
06:21 AM
This can be caused by https://issues.apache.org/jira/browse/HBASE-22739. It doesn't seems HBase 2.0.2 contains this fix. The only workaround is to perform a failover of the HBase Master.
... View more
10-04-2023
01:48 AM
This metric is specific to the region server level and cannot be sorted or filtered based on the table name. However, You can leverage the timerange option with scan to check if there are any rows inserted between two timestamps. By default, the timestamp represents the time on the RegionServer when the data was written, so unless you specify a different timestamp value when you put data into the cell, you can leverage with the cell timestamps to check the insertion time. for example, scan 'NS:TableName', { TIMERANGE => [1589621394000, 1589637999999] } You can get epoch time from HBase shell as well using this option. SimpleDateFormat.new("yy/MM/dd HH:mm:ss").parse("08/08/16 20:56:29", ParsePosition.new(0)).getTime() => 1218920189000
... View more