apurtell edited a comment on pull request #3234:
URL: https://github.com/apache/hbase/pull/3234#issuecomment-832857609
Although the unit test will fail, when I tried this change out on a cluster
in a very write heavy ingestion test, the end result was good. The ingestion
test completes successfully and without weird artifacts in the logging. All
split regions are GCed by procedures. In memory state aligns with filesystem
state.
/hbase/logs/hbase-apurtell-master-ip-172-31-58-47.us-west-2.compute.internal.log:130972:2021-05-05
15:47:39,190 INFO [master/ip-172-31-58-47:8100.Chore.1]
master.HbckChore: Loaded 230 regions (0 disabled, 0 split parents) from
in-memory state
/hbase/logs/hbase-apurtell-master-ip-172-31-58-47.us-west-2.compute.internal.log:130973:2021-05-05
15:47:39,190 DEBUG [master/ip-172-31-58-47:8100.Chore.1]
master.HbckChore: Regions by state: OPEN=230
/hbase/logs/hbase-apurtell-master-ip-172-31-58-47.us-west-2.compute.internal.log:130974:2021-05-05
15:47:39,190 INFO [master/ip-172-31-58-47:8100.Chore.1]
master.HbckChore: Loaded 230 regions from 5 regionservers' reports and
found 0 orphan regions
/hbase/logs/hbase-apurtell-master-ip-172-31-58-47.us-west-2.compute.internal.log:130986:2021-05-05
15:47:39,200 INFO [master/ip-172-31-58-47:8100.Chore.1]
master.HbckChore: Loaded 3 tables 230 regions from filesyetem and found
0 orphan regions
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
