[jira] [Created] (HBASE-28623) Scan with MultiRowRangeFilter very slow
chaijunjie created HBASE-28623:
--
Summary: Scan with MultiRowRangeFilter very slow
Key: HBASE-28623
URL: https://issues.apache.org/jira/browse/HBASE-28623
Project: HBase
Issue Type: Bug
Components: Client
Affects Versions: 2.4.14
Reporter: chaijunjie
when we *scan* a big table({*}more than 500 regions{*}) with
{*}MultiRowRangeFilter{*}, it is very slow...
it seems to {*}scan all regions{*}...
for example:
we scan 3 ranges..
startRow: 097_28220_ stopRow: 097_28220_~
startRow: 098_28221_ stopRow: 098_28221_~
startRow: 099_28222_ stopRow: 099_28222_~
and enable TRACE log in hbase client
we find the too many scans
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28541) RegionServer abort when max sequence id wrong
chaijunjie created HBASE-28541: -- Summary: RegionServer abort when max sequence id wrong Key: HBASE-28541 URL: https://issues.apache.org/jira/browse/HBASE-28541 Project: HBase Issue Type: Bug Affects Versions: 2.2.3 Reporter: chaijunjie When we disable a table, some region close failed because max sequence id is less than the old max sequence id, then RS abort...Then the region close success on another RS.. we just use bulkload...is it releated? 2024-04-20 23:44:20,611 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Bulk-load file hdfs://hacluster/hbase/staging/cdr__boss20240420__t20amapi48eb4ce0k0t80jatvnnhpm5rohaj26a5rdsp0s7kifokcdd32ko89u7n/info/4f43f6cf569643da8ecc140668fa726e is on different filesystem than the destination store. Copying file over to destination filesystem. | org.apache.hadoop.hbase.regionserver.HRegionFileSystem.bulkLoadStoreFile(HRegionFileSystem.java:540) 2024-04-20 23:44:20,645 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Copied hdfs://hacluster/hbase/staging/cdr__boss20240420__t20amapi48eb4ce0k0t80jatvnnhpm5rohaj26a5rdsp0s7kifokcdd32ko89u7n/info/4f43f6cf569643da8ecc140668fa726e to temporary path on destination filesystem: viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/.tmp/6f7e97f2e3994881a6e04b36759f495e | org.apache.hadoop.hbase.regionserver.HRegionFileSystem.bulkLoadStoreFile(HRegionFileSystem.java:544) 2024-04-20 23:44:20,648 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Loaded HFile viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/.tmp/6f7e97f2e3994881a6e04b36759f495e into dc30be37cbd0ddee2f49712c55fd36cd/info as viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/info/3946dc15ea1c49b582a2ed175fe12ec3_SeqId_26_ - updating store file list. | org.apache.hadoop.hbase.regionserver.HStore.bulkLoadHFile(HStore.java:908) 2024-04-20 23:44:20,664 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Loaded HFile viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/info/3946dc15ea1c49b582a2ed175fe12ec3_SeqId_26_ into dc30be37cbd0ddee2f49712c55fd36cd/info | org.apache.hadoop.hbase.regionserver.HStore.bulkLoadHFile(HStore.java:942) 2024-04-20 23:44:20,664 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Successfully loaded viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/.tmp/6f7e97f2e3994881a6e04b36759f495e into dc30be37cbd0ddee2f49712c55fd36cd/info (new location: viewfs://ClusterX/hbase/data/default/boss20240420/dc30be37cbd0ddee2f49712c55fd36cd/info/3946dc15ea1c49b582a2ed175fe12ec3_SeqId_26_) | org.apache.hadoop.hbase.regionserver.HStore.bulkLoadHFile(HStore.java:914) 2024-04-20 23:44:23,592 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Validating hfile at viewfs://ClusterX/tenant/hw_cdr/dsttab/load_20240420232000/boss20240420/info/a97bb2bfcb5244279bcedbe20ec8322b for inclusion in b3d102e51ca3b78a1078580ed8a002de/info | org.apache.hadoop.hbase.regionserver.HStore.assertBulkLoadHFileOk(HStore.java:817) 2024-04-20 23:44:23,669 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Bulk-load file hdfs://hacluster/hbase/staging/cdr__boss20240420__t20amapi48eb4ce0k0t80jatvnnhpm5rohaj26a5rdsp0s7kifokcdd32ko89u7n/info/a97bb2bfcb5244279bcedbe20ec8322b is on different filesystem than the destination store. Copying file over to destination filesystem. | org.apache.hadoop.hbase.regionserver.HRegionFileSystem.bulkLoadStoreFile(HRegionFileSystem.java:540) 2024-04-20 23:44:23,743 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Copied hdfs://hacluster/hbase/staging/cdr__boss20240420__t20amapi48eb4ce0k0t80jatvnnhpm5rohaj26a5rdsp0s7kifokcdd32ko89u7n/info/a97bb2bfcb5244279bcedbe20ec8322b to temporary path on destination filesystem: viewfs://ClusterX/hbase/data/default/boss20240420/b3d102e51ca3b78a1078580ed8a002de/.tmp/f40ec16d10ab4474ace7af41d9126aa0 | org.apache.hadoop.hbase.regionserver.HRegionFileSystem.bulkLoadStoreFile(HRegionFileSystem.java:544) 2024-04-20 23:44:23,747 | INFO | RpcServer.default.FPBQ.Fifo.handler=483,queue=33,port=21302 | Loaded HFile viewfs://ClusterX/hbase/data/default/boss20240420/b3d102e51ca3b78a1078580ed8a002de/.tmp/f40ec16d10ab4474ace7af41d9126aa0 into b3d102e51ca3b78a1078580ed8a002de/info as viewfs://ClusterX/hbase/data/default/boss20240420/b3d102e51ca3b78a1078580ed8a002de/info/7cfcf858a6b34bd1b9d47ccce5dde9e4_SeqId_41_ - updating store file list. | org.apache.hadoop.hbase.regionserver.HStore.bulkLoadHFile(HStore.java:908) 2024-04-20 23:44:23,760 | INFO |
[jira] [Created] (HBASE-28185) Alter table to set TTL using hbase shell failed when ttl string is not match format
chaijunjie created HBASE-28185:
--
Summary: Alter table to set TTL using hbase shell failed when ttl
string is not match format
Key: HBASE-28185
URL: https://issues.apache.org/jira/browse/HBASE-28185
Project: HBase
Issue Type: Bug
Affects Versions: 2.4.14
Reporter: chaijunjie
Assignee: chaijunjie
create 'test','f1'
alter 'test',\{NAME=>'f1',TTL=>'111x'}
{code:java}
hbase:001:0> alter 'test',{NAME=>'f1',TTL=>'111x'}
ERROR: org.apache.hadoop.hbase.DoNotRetryIOException: TTL for column family f1
must be positive. Set hbase.table.sanity.checks to false at conf or table
descriptor if you want to bypass sanity checks at
org.apache.hadoop.hbase.util.TableDescriptorChecker.warnOrThrowExceptionForFailure(TableDescriptorChecker.java:321)
at
org.apache.hadoop.hbase.util.TableDescriptorChecker.sanityCheck(TableDescriptorChecker.java:165)
at org.apache.hadoop.hbase.master.HMaster$14.run(HMaster.java:2666) at
org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:132)
at org.apache.hadoop.hbase.master.HMaster.modifyTable(HMaster.java:2660)
at org.apache.hadoop.hbase.master.HMaster.modifyTable(HMaster.java:2698)
at
org.apache.hadoop.hbase.master.MasterRpcServices.modifyTable(MasterRpcServices.java:1554)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:477) at
org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123) at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
For usage try 'help "alter"' {code}
it is so confuse..
we need tell user wether theire command is wrong..
some times we copy some string which may have some invisible characters， we
need let user to check it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28150) Too many master region WAL cause HDFS disk space full
[
https://issues.apache.org/jira/browse/HBASE-28150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaijunjie resolved HBASE-28150.
Fix Version/s: 2.6.0
Resolution: Cannot Reproduce
After https://issues.apache.org/jira/browse/HBASE-26454
HMaster will not create tmp table dir, so it will not reproduce，so it just
influence HBase 2.5 and 2.4
close it, use HBase 2.6 is ok
> Too many master region WAL cause HDFS disk space full
> -
>
> Key: HBASE-28150
> URL: https://issues.apache.org/jira/browse/HBASE-28150
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.4.14
>Reporter: chaijunjie
>Assignee: chaijunjie
>Priority: Critical
> Fix For: 2.6.0
>
>
> create a table, but it failed when execute CREATE_TABLE_WRITE_FS_LAYOUT, then
> will try again and again, will write too many proc record to master:store, we
> find num of the master WAL in oldWALs more than 13000..
>
> Q: should add a suspend time logic for create table proc retry? i see
> TransitRegionStateProcedure has the logic..
>
> ---
> sorry, i upload screenshot failed, just copy to here
> {code:java}
> // 2023-10-12 12:34:35,360 | INFO | RegionOpenAndInit-themis:a-pool-0 |
> Closing region themis:a,,1697025107991.513d3d5b4d3ad5c8f13bacea4a888d69. |
> org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1688)
> 2023-10-12 12:34:35,360 | INFO | RegionOpenAndInit-themis:a-pool-0 | Closed
> themis:a,,1697025107991.513d3d5b4d3ad5c8f13bacea4a888d69. |
> org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1900)
> 2023-10-12 12:34:35,360 | INFO | PEWorker-1 | Region directories are created
> at hdfs://hacluster/hbase/.tmp for table themis:a |
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.createFsLayout(CreateTableProcedure.java:346)
> 2023-10-12 12:34:35,362 | WARN | PEWorker-1 | Retriable error trying to
> create table=themis:a state=CREATE_TABLE_WRITE_FS_LAYOUT |
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:159)
> java.io.IOException: Unable to move table from
> temp=hdfs://hacluster/hbase/.tmp/data/themis/a to hbase
> root=hdfs://hacluster/hbase/data/themis/a
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.moveTempDirectoryToHBaseRoot(CreateTableProcedure.java:391)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.createFsLayout(CreateTableProcedure.java:350)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.createFsLayout(CreateTableProcedure.java:318)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:121)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:75)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:188)
> at
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:922)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1650)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1396)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1000(ProcedureExecutor.java:75)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.runProcedure(ProcedureExecutor.java:1962)
> at org.apache.hadoop.hbase.trace.TraceUtil.trace(TraceUtil.java:221)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1988)
> 2023-10-12 12:34:35,387 | INFO | PEWorker-1 | pid=917,
> state=RUNNABLE:CREATE_TABLE_WRITE_FS_LAYOUT, locked=true;
> CreateTableProcedure table=themis:a execute
> state=CREATE_TABLE_WRITE_FS_LAYOUT |
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:102)
> 2023-10-12 12:34:35,414 | INFO | RegionOpenAndInit-themis:a-pool-0 |
> creating {ENCODED => 513d3d5b4d3ad5c8f13bacea4a888d69, NAME =>
> 'themis:a,,1697025107991.513d3d5b4d3ad5c8f13bacea4a888d69.', STARTKEY => '',
> ENDKEY => ''}, tableDescriptor='themis:a', {NAME => 'f1', BLOOMFILTER =>
> 'ROW', IN_MEMORY => 'false', VERSIONS => '1', KEEP_DELETED_CELLS => 'FALSE',
> DATA_BLOCK_ENCODING => 'NONE', COMPRESSION => 'NONE', TTL => 'FOREVER',
> MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => '65536',
> REPLICATION_SCOPE => '0'}, regionDir=hdfs://hacluster/hbase/.tmp |
> org.apache.hadoop.hbase.regionserver.HRegion.createHRegion(HRegion.java:7906)
> 2023-10-12 12:34:35,432 | INFO |
[jira] [Created] (HBASE-28150) Too many master region WAL cause HDFS disk space full
chaijunjie created HBASE-28150: -- Summary: Too many master region WAL cause HDFS disk space full Key: HBASE-28150 URL: https://issues.apache.org/jira/browse/HBASE-28150 Project: HBase Issue Type: Improvement Affects Versions: 2.4.14 Reporter: chaijunjie -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28117) [HBCK2] extraRegionsInMeta need supoort delete extra regions when table not exist
chaijunjie created HBASE-28117: -- Summary: [HBCK2] extraRegionsInMeta need supoort delete extra regions when table not exist Key: HBASE-28117 URL: https://issues.apache.org/jira/browse/HBASE-28117 Project: HBase Issue Type: Improvement Components: hbck2 Affects Versions: 2.4.14 Reporter: chaijunjie Some times, we delete one table dir on hdfs, we need use hbck2 to fix region info in hbase:meta... but some times, we use hbase shell delete the table state uncarefully，just like execute: deleteall 'hbase:meta','t1,xxx' (it not prevented...) then the table state lose when we want to use extraRegionsInMeta to remove these unuseful regions in meta...but it failed,beacuse the table is not exist.. I think we should support do extraRegionsInMeta when table not exists...or there are other method to fix it? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27972) Scan result wrong when using filterlist and specifing scan colums
chaijunjie created HBASE-27972:
--
Summary: Scan result wrong when using filterlist and specifing
scan colums
Key: HBASE-27972
URL: https://issues.apache.org/jira/browse/HBASE-27972
Project: HBase
Issue Type: Bug
Components: Filters
Affects Versions: 2.4.17
Reporter: chaijunjie
When I run these tests...
The results is different from expectations
{code:java}
// Test
create 't1',{NAME=>'cf1'}
put 't1','r1','cf1:cq1','1'
put 't1','r1','cf1:cq2','2'
put 't1','r2','cf1:cq1','2'
put 't1','r2','cf1:cq2','3'
put 't1','r3','cf1:cq1','3'
put 't1','r3','cf1:cq2','4'
put 't1','r4','cf1:cq1','4'
put 't1','r4','cf1:cq2','5'
java_import org.apache.hadoop.hbase.filter.SingleColumnValueFilter
java_import org.apache.hadoop.hbase.util.Bytes
java_import org.apache.hadoop.hbase.filter.CompareFilter
java_import
org.apache.hadoop.hbase.filter.FilterListfilter1=SingleColumnValueFilter.new(Bytes::toBytes('cf1'),Bytes::toBytes('cq1'),CompareFilter::CompareOp::LESS_OR_EQUAL,Bytes::toBytes('2'))
filter2=SingleColumnValueFilter.new(Bytes::toBytes('cf1'),Bytes::toBytes('cq2'),CompareFilter::CompareOp::GREATER_OR_EQUAL,Bytes::toBytes('5'))
filterList1=FilterList.new(FilterList::Operator::MUST_PASS_ONE,filter1,filter2)
filterList2=FilterList.new(FilterList::Operator::MUST_PASS_ALL,filter1,filter2)scan
't1',{COLUMNS=>['cf1:cq1'],FILTER =>filter1}
scan 't1',{COLUMNS=>['cf1:cq2'],FILTER =>filter2}scan
't1',{COLUMNS=>['cf1:cq1'],FILTER =>filterList1}
scan 't1',{COLUMNS=>['cf1:cq1'],FILTER =>filterList2} {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-27552) HMaster can not finish Initialization when hbase:namespace is in ABNORMALLY_CLOSED state and the proc corrupt
[ https://issues.apache.org/jira/browse/HBASE-27552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaijunjie resolved HBASE-27552. Resolution: Not A Problem cannot be reproduced again...close it > HMaster can not finish Initialization when hbase:namespace is in > ABNORMALLY_CLOSED state and the proc corrupt > - > > Key: HBASE-27552 > URL: https://issues.apache.org/jira/browse/HBASE-27552 > Project: HBase > Issue Type: Bug > Components: proc-v2 >Affects Versions: 2.4.14 >Reporter: chaijunjie >Priority: Major > Labels: core > > 2023-01-05 19:56:41,385 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=102, ppid=97, > state=SUCCESS; OpenRegionProcedure 1903713b7f970a75db1e7a0e72da21d7, > server=node-master2mesq,21302,1672817611868 | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,385 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=103, ppid=96, > state=SUCCESS; OpenRegionProcedure 6695b9c5ad80249bc43830ddc5259487, > server=node-master2mesq,21302,1672817611868 | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,402 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=106, ppid=82, > state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; > TransitRegionStateProcedure table=ImportTable1, > region=050bcf6e15ddd079d750992bbfb53163, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,403 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=107, ppid=82, > state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; > TransitRegionStateProcedure table=hbase:hindex, > region=6789443c0a98d2b34f891ae60878aac3, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,404 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=108, ppid=82, > state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; > TransitRegionStateProcedure table=hbase:acl, > region=96a2ec5ea797e6847188c965f8c78ce1, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,404 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=109, ppid=82, > state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; > TransitRegionStateProcedure table=ImportTable1, > region=24e0cb0a958d242976a790ff435d24b5, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,405 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=110, ppid=82, > state=RUNNABLE:REGION_STATE_TRANSITION_OPEN; TransitRegionStateProcedure > table=ImportTable1, region=a2e7b85420a3cf98fc731ad93f7129a2, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > *2023-01-05 19:56:41,405 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=111, ppid=82, > state=RUNNABLE:REGION_STATE_TRANSITION_OPEN; TransitRegionStateProcedure > table=hbase:namespace, region=9be1542260fa8af4a712ddda322b7b6f, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343)* > 2023-01-05 19:56:41,406 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=112, ppid=82, > state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; > TransitRegionStateProcedure table=hbase:rsgroup, > region=eaf1531c6cc0738027def0b4d4615b5f, ASSIGN | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,406 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=125, ppid=95, > state=SUCCESS; OpenRegionProcedure 85301e5c14a8c3e5ba31822d7db0a6fc, > server=node-master3mpye,21302,1672817640502 | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,407 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=126, ppid=96, > state=SUCCESS; OpenRegionProcedure 6695b9c5ad80249bc43830ddc5259487, > server=node-master3mpye,21302,1672817640502 | > org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) > 2023-01-05 19:56:41,408 | ERROR | > master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=127, ppid=94, > state=SUCCESS; OpenRegionProcedure 448b88d503d4e31c47b80ac10d8ef6a4, >
[jira] [Created] (HBASE-27888) Record readBlock message in log when it takes too long time
chaijunjie created HBASE-27888: -- Summary: Record readBlock message in log when it takes too long time Key: HBASE-27888 URL: https://issues.apache.org/jira/browse/HBASE-27888 Project: HBase Issue Type: Improvement Components: HFile Affects Versions: 2.4.17, 2.5.3, 2.4.15 Reporter: chaijunjie -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27764) scan table is slow when enter hbase shell first time
chaijunjie created HBASE-27764:
--
Summary: scan table is slow when enter hbase shell first time
Key: HBASE-27764
URL: https://issues.apache.org/jira/browse/HBASE-27764
Project: HBase
Issue Type: Bug
Components: Client, shell
Affects Versions: 2.4.14
Reporter: chaijunjie
When we test HBase 2.4.14 on our cluster...
I find we scan a table is slow when enter hbase shell first time.
step like this:
hbase shell
scan 't1',\{LIMIT=>1}
the cost time is more than HBase 1.3
Any one can help compare the two versions(HBase 2.x vs HBase 1.x) in first scan
process?
thanks~
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27718) The regionStateNode only need remove one time in regionOffline
chaijunjie created HBASE-27718: -- Summary: The regionStateNode only need remove one time in regionOffline Key: HBASE-27718 URL: https://issues.apache.org/jira/browse/HBASE-27718 Project: HBase Issue Type: Bug Components: amv2 Affects Versions: 2.4.14 Reporter: chaijunjie The regionStateNode only need remove one time in regionOffline when delete a table. In org.apache.hadoop.hbase.master.assignment.AssignmentManager#deleteTable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27552) HMaster can not in finish Initialization when hbase:namespace is in ABNORMALLY_CLOSED state and the proc corrupt
chaijunjie created HBASE-27552: -- Summary: HMaster can not in finish Initialization when hbase:namespace is in ABNORMALLY_CLOSED state and the proc corrupt Key: HBASE-27552 URL: https://issues.apache.org/jira/browse/HBASE-27552 Project: HBase Issue Type: Bug Components: proc-v2 Affects Versions: 2.4.14 Environment: 2023-01-05 19:56:41,385 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=102, ppid=97, state=SUCCESS; OpenRegionProcedure 1903713b7f970a75db1e7a0e72da21d7, server=node-master2mesq,21302,1672817611868 | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,385 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=103, ppid=96, state=SUCCESS; OpenRegionProcedure 6695b9c5ad80249bc43830ddc5259487, server=node-master2mesq,21302,1672817611868 | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,402 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=106, ppid=82, state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; TransitRegionStateProcedure table=ImportTable1, region=050bcf6e15ddd079d750992bbfb53163, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,403 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=107, ppid=82, state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; TransitRegionStateProcedure table=hbase:hindex, region=6789443c0a98d2b34f891ae60878aac3, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,404 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=108, ppid=82, state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; TransitRegionStateProcedure table=hbase:acl, region=96a2ec5ea797e6847188c965f8c78ce1, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,404 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=109, ppid=82, state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; TransitRegionStateProcedure table=ImportTable1, region=24e0cb0a958d242976a790ff435d24b5, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,405 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=110, ppid=82, state=RUNNABLE:REGION_STATE_TRANSITION_OPEN; TransitRegionStateProcedure table=ImportTable1, region=a2e7b85420a3cf98fc731ad93f7129a2, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,405 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=111, ppid=82, state=RUNNABLE:REGION_STATE_TRANSITION_OPEN; TransitRegionStateProcedure table=hbase:namespace, region=9be1542260fa8af4a712ddda322b7b6f, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,406 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=112, ppid=82, state=WAITING:REGION_STATE_TRANSITION_CONFIRM_OPENED; TransitRegionStateProcedure table=hbase:rsgroup, region=eaf1531c6cc0738027def0b4d4615b5f, ASSIGN | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,406 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=125, ppid=95, state=SUCCESS; OpenRegionProcedure 85301e5c14a8c3e5ba31822d7db0a6fc, server=node-master3mpye,21302,1672817640502 | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,407 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=126, ppid=96, state=SUCCESS; OpenRegionProcedure 6695b9c5ad80249bc43830ddc5259487, server=node-master3mpye,21302,1672817640502 | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) 2023-01-05 19:56:41,408 | ERROR | master/node-master3MPYe:21300:becomeActiveMaster | Corrupt pid=127, ppid=94, state=SUCCESS; OpenRegionProcedure 448b88d503d4e31c47b80ac10d8ef6a4, server=node-master3mpye,21302,1672817640502 | org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.handleCorrupted(ProcedureExecutor.java:343) Reporter: chaijunjie -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27330) Improvements of HMaster web ui
chaijunjie created HBASE-27330: -- Summary: Improvements of HMaster web ui Key: HBASE-27330 URL: https://issues.apache.org/jira/browse/HBASE-27330 Project: HBase Issue Type: Improvement Components: UI Affects Versions: 2.4.13 Reporter: chaijunjie The HMaster web ui open very slowly when there are many regions in the cluster, it may takes above 3min to load region and table messages， The RIT and table on home page is very slow, because we load all info on one time... we need improve page loading speed of HMaster home page... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27282) CME in AuthManager
chaijunjie created HBASE-27282: -- Summary: CME in AuthManager Key: HBASE-27282 URL: https://issues.apache.org/jira/browse/HBASE-27282 Project: HBase Issue Type: Bug Components: acl Reporter: chaijunjie -- This message was sent by Atlassian Jira (v8.20.10#820010)
