[jira] [Created] (HBASE-27255) Backport HBASE-22120 (Replace HTrace with OpenTelemetry) to branch-2.4
Kiran Kumar Maturi created HBASE-27255: -- Summary: Backport HBASE-22120 (Replace HTrace with OpenTelemetry) to branch-2.4 Key: HBASE-27255 URL: https://issues.apache.org/jira/browse/HBASE-27255 Project: HBase Issue Type: Task Components: tracing Reporter: Kiran Kumar Maturi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27247) TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of ReplicationPeerConfigUtil.parseTableCFsFromConfig
[
https://issues.apache.org/jira/browse/HBASE-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-27247.
-
Resolution: Fixed
> TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of
> ReplicationPeerConfigUtil.parseTableCFsFromConfig
> -
>
> Key: HBASE-27247
> URL: https://issues.apache.org/jira/browse/HBASE-27247
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Affects Versions: 3.0.0-alpha-4
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> HBASE-27203 has modified
> {{ReplicationPeerConfigUtil.parseTableCFsFromConfig}} which causes
> {{TestPerTableCFReplication.testParseTableCFsFromConfig}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-27247) TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of ReplicationPeerConfigUtil.parseTableCFsFromConfig
[
https://issues.apache.org/jira/browse/HBASE-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell reopened HBASE-27247:
-
> TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of
> ReplicationPeerConfigUtil.parseTableCFsFromConfig
> -
>
> Key: HBASE-27247
> URL: https://issues.apache.org/jira/browse/HBASE-27247
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0-alpha-4
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> HBASE-27203 has modified
> {{ReplicationPeerConfigUtil.parseTableCFsFromConfig}} which causes
> {{TestPerTableCFReplication.testParseTableCFsFromConfig}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27254) Clean up error-prone findings in hbase-mapreduce
Andrew Kyle Purtell created HBASE-27254: --- Summary: Clean up error-prone findings in hbase-mapreduce Key: HBASE-27254 URL: https://issues.apache.org/jira/browse/HBASE-27254 Project: HBase Issue Type: Sub-task Reporter: Andrew Kyle Purtell Assignee: Andrew Kyle Purtell Fix For: 3.0.0-alpha-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27253) Make slow log configs updatable with configuration observer
Bryan Beaudreault created HBASE-27253: - Summary: Make slow log configs updatable with configuration observer Key: HBASE-27253 URL: https://issues.apache.org/jira/browse/HBASE-27253 Project: HBase Issue Type: Improvement Reporter: Bryan Beaudreault It would be very useful to be able to turn slow log on or off, change thresholds, etc on demand as needed when diagnosing a traffic issue. Should be a simple matter of moving the configs into RpcServer#onConfigurationChange -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27252) Clean up error-prone findings in hbase-it
Andrew Kyle Purtell created HBASE-27252: --- Summary: Clean up error-prone findings in hbase-it Key: HBASE-27252 URL: https://issues.apache.org/jira/browse/HBASE-27252 Project: HBase Issue Type: Sub-task Reporter: Andrew Kyle Purtell Assignee: Andrew Kyle Purtell Fix For: 2.5.0, 3.0.0-alpha-4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-15383) Load distribute across secondary read replicas for meta
[ https://issues.apache.org/jira/browse/HBASE-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Beaudreault resolved HBASE-15383. --- Resolution: Duplicate I believe this is a duplicate of the already implemented HBASE-25126. If I'm wrong feel free to reopen > Load distribute across secondary read replicas for meta > --- > > Key: HBASE-15383 > URL: https://issues.apache.org/jira/browse/HBASE-15383 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: Ashu Pachauri >Assignee: Ashu Pachauri >Priority: Major > > Right now, we always hit the primary replica for meta and fallback to the > secondary replicas in case of a timeout. This can hamper performance in > scenarios where meta becomes a hot region e.g. cluster ramp up..clients > dropping connections etc. > It's good to have a load distribution approach on meta's secondary replicas > with fallback to primary if we read stale data. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27251) Rolling back from 2.5.0-SNAPSHOT to 2.4.13 fails due to `File does not exist: /hbase/MasterData/data/master/store/.initialized/.regioninfo`
Nick Dimiduk created HBASE-27251:
Summary: Rolling back from 2.5.0-SNAPSHOT to 2.4.13 fails due to
`File does not exist:
/hbase/MasterData/data/master/store/.initialized/.regioninfo`
Key: HBASE-27251
URL: https://issues.apache.org/jira/browse/HBASE-27251
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 2.5.0
Reporter: Nick Dimiduk
I was doing some perf testing with builds of 2.5.0. I rolled back to 2.4.13 and
the master won't start. Stack trace ends in,
{noformat}
java.io.FileNotFoundException: File does not exist:
/hbase/MasterData/data/master/store/.initialized/.regioninfo
at
org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:86)
at
org.apache.hadoop.hdfs.server.namenode.INodeFile.valueOf(INodeFile.java:76)
at
org.apache.hadoop.hdfs.server.namenode.FSDirStatAndListingOp.getBlockLocations(FSDirStatAndListingOp.java:156)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:2089)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getBlockLocations(NameNodeRpcServer.java:762)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getBlockLocations(ClientNamenodeProtocolServerSideTranslatorPB.java:458)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:604)
at
org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:572)
at
org.apache.hadoop.ipc.ProtobufRpcEngine2$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine2.java:556)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1093)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:1043)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:971)
at
java.base/java.security.AccessController.doPrivileged(AccessController.java:712)
at java.base/javax.security.auth.Subject.doAs(Subject.java:439)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1878)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2976)
{noformat}
When I examine the on-disk file system, I see,
{noformat}
nonroot@namenode-0:~$ hdfs dfs -ls /hbase/MasterData/data/master/store/
Found 3 items
drwxr-xr-x - nonroot supergroup 0 2022-07-19 17:37
/hbase/MasterData/data/master/store/.initialized
drwxr-xr-x - nonroot supergroup 0 2022-07-19 17:37
/hbase/MasterData/data/master/store/.tabledesc
drwxr-xr-x - nonroot supergroup 0 2022-07-27 16:25
/hbase/MasterData/data/master/store/1595e783b53d99cd5eef43b6debb2682
nonroot@namenode-0:~$ hdfs dfs -ls
/hbase/MasterData/data/master/store/.initialized/
nonroot@namenode-0:~$
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27250) MasterRpcService#setRegionStateInMeta does not support replica region encodedNames or region names
Huaxiang Sun created HBASE-27250: Summary: MasterRpcService#setRegionStateInMeta does not support replica region encodedNames or region names Key: HBASE-27250 URL: https://issues.apache.org/jira/browse/HBASE-27250 Project: HBase Issue Type: Bug Affects Versions: 2.4.13 Reporter: Huaxiang Sun Assignee: Huaxiang Sun MasterRpcServices#setRegionStateInMeta does not support replica region names, it assumes the primary region only. This makes HBCK2's setRegionState for replica region fails. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27249) Remove invalid peer RegionServer crash
zhengsicheng created HBASE-27249: Summary: Remove invalid peer RegionServer crash Key: HBASE-27249 URL: https://issues.apache.org/jira/browse/HBASE-27249 Project: HBase Issue Type: Bug Reporter: zhengsicheng Assignee: zhengsicheng -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27248) WALPrettyPrinter add print timestamp
zhengsicheng created HBASE-27248: Summary: WALPrettyPrinter add print timestamp Key: HBASE-27248 URL: https://issues.apache.org/jira/browse/HBASE-27248 Project: HBase Issue Type: Task Reporter: zhengsicheng Assignee: zhengsicheng -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27247) TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of ReplicationPeerConfigUtil.parseTableCFsFromConfig
[
https://issues.apache.org/jira/browse/HBASE-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-27247.
---
Fix Version/s: 3.0.0-alpha-4
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to master.
Thanks [~comnetwork] for the quick fix.
[~apurtell] FYI. Please condiser including this fix in the PR for branch-2.x.
Thanks.
> TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of
> ReplicationPeerConfigUtil.parseTableCFsFromConfig
> -
>
> Key: HBASE-27247
> URL: https://issues.apache.org/jira/browse/HBASE-27247
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0-alpha-4
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 3.0.0-alpha-4
>
>
> HBASE-27203 has modified
> {{ReplicationPeerConfigUtil.parseTableCFsFromConfig}} which causes
> {{TestPerTableCFReplication.testParseTableCFsFromConfig}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27247) TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of ReplicationPeerConfigUtil.parseTableCFsFromConfig
chenglei created HBASE-27247: Summary: TestPerTableCFReplication.testParseTableCFsFromConfig is broken because of ReplicationPeerConfigUtil.parseTableCFsFromConfig Key: HBASE-27247 URL: https://issues.apache.org/jira/browse/HBASE-27247 Project: HBase Issue Type: Improvement Components: Replication Affects Versions: 3.0.0-alpha-4 Reporter: chenglei -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27246) RSGroupMappingScript#getRSGroup should be synchronised
Yutong Xiao created HBASE-27246:
---
Summary: RSGroupMappingScript#getRSGroup should be synchronised
Key: HBASE-27246
URL: https://issues.apache.org/jira/browse/HBASE-27246
Project: HBase
Issue Type: Bug
Reporter: Yutong Xiao
Assignee: Yutong Xiao
Attachments: Test.java
We are using version 1.4.12 and met a problem in table creation phase some
time. The error message is:
{code:java}
2022-07-26 19:26:20.122 [http-nio-8078-exec-24,d2ad4b13b542b6fb] ERROR
HBaseServiceImpl - hbase create table: xxx: failed.
(HBaseServiceImpl.java:116)
java.lang.RuntimeException:
org.apache.hadoop.hbase.constraint.ConstraintException:
org.apache.hadoop.hbase.constraint.ConstraintException: Default RSGroup (default
default) for this table's namespace does not exist.
{code}
The rsgroup here should be one 'default' but not two consecutive 'default'.
The code to get RSGroup from a mapping script is:
{code:java}
String getRSGroup(String namespace, String tablename) {
if (rsgroupMappingScript == null) {
return null;
}
String[] exec = rsgroupMappingScript.getExecString();
exec[1] = namespace;
exec[2] = tablename;
try {
rsgroupMappingScript.execute();
} catch (IOException e) {
// This exception may happen, like process doesn't have permission to
run this script.
LOG.error("{}, placing {} back to default rsgroup", e.getMessage(),
TableName.valueOf(namespace, tablename));
return RSGroupInfo.DEFAULT_GROUP;
}
return rsgroupMappingScript.getOutput().trim();
}
{code}
here the rsgourpMappingScript could be executed by multi-threads.
To test it is a multi-thread issue, I ran a piece of code locally and found
that the hadoop ShellCommandExecutor is not thread-safe (I run the code with
hadoop 2.10.0 and 3.3.2). So that we should make this method synchronized.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
