[jira] [Reopened] (HBASE-28947) Backport "HBASE-27598 Upgrade mockito to 4.x" to branch-2.5
[ https://issues.apache.org/jira/browse/HBASE-28947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain reopened HBASE-28947: > Backport "HBASE-27598 Upgrade mockito to 4.x" to branch-2.5 > --- > > Key: HBASE-28947 > URL: https://issues.apache.org/jira/browse/HBASE-28947 > Project: HBase > Issue Type: Improvement > Components: dependencies, test >Affects Versions: 2.5.10 >Reporter: Duo Zhang >Assignee: Nihal Jain >Priority: Major > Labels: pull-request-available > Fix For: 2.5.11 > > > Mockito 2.28.2 is release May 29, 2019, which is very old now. Let's upgrade > to the latest 4.x version, as mockito 5.0.0 requires java 11, which is not > suitable for us. > Need to backport this to branch-2.5 as we face > https://issues.apache.org/jira/browse/HBASE-28944 w/o this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28968) Bump jruby to 9.4.9.0 to fix rexml CVE
Nihal Jain created HBASE-28968:
--
Summary: Bump jruby to 9.4.9.0 to fix rexml CVE
Key: HBASE-28968
URL: https://issues.apache.org/jira/browse/HBASE-28968
Project: HBase
Issue Type: Task
Components: jruby, security, shell
Reporter: Nihal Jain
Assignee: Nihal Jain
Fix For: 2.7.0, 3.0.0-beta-2
As a follow up of HBASE-28249, we want to bump to latest 9.4.x line here.
This release line drops critical snakeyaml CVE ({*}org.yaml : snakeyaml :
1.33{*} having [CVE-2022-1471|https://nvd.nist.gov/vuln/detail/CVE-2022-1471])
from our classpath with following change along with several other bugs/fixes:
* The Psych YAML library is updated to 5.1.0. This version switches the JRuby
extension to SnakeYAML Engine, avoiding CVEs against the original SnakeYAML and
updating YAML compatibility to specification version 1.2.
[#6365|https://github.com/jruby/jruby/issues/6365],
[#7570|https://github.com/jruby/jruby/issues/7570],
[#7626|https://github.com/jruby/jruby/pull/7626]
NOTE: JRuby 9.4.x targets Ruby 3.1 compatibility instead of Ruby 2.6 which
9.3.x were having!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28961) Add missing plugins from hbase-diagnostics
Nihal Jain created HBASE-28961: -- Summary: Add missing plugins from hbase-diagnostics Key: HBASE-28961 URL: https://issues.apache.org/jira/browse/HBASE-28961 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain Seems I missed to add some essential / required plugin while adding the new module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28947) Backport "HBASE-27598 Upgrade mockito to 4.x" to branch-2.5
Nihal Jain created HBASE-28947: -- Summary: Backport "HBASE-27598 Upgrade mockito to 4.x" to branch-2.5 Key: HBASE-28947 URL: https://issues.apache.org/jira/browse/HBASE-28947 Project: HBase Issue Type: Improvement Components: dependencies, test Reporter: Duo Zhang Assignee: Duo Zhang Fix For: 2.6.0, 3.0.0-alpha-4 Mockito 2.28.2 is release May 29, 2019, which is very old now. Let's upgrade to the latest 4.x version, as mockito 5.0.0 requires java 11, which is not suitable for us. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28946) Update nightlies to run with HADOOP2_VERSION = 2.10.2
Nihal Jain created HBASE-28946: -- Summary: Update nightlies to run with HADOOP2_VERSION = 2.10.2 Key: HBASE-28946 URL: https://issues.apache.org/jira/browse/HBASE-28946 Project: HBase Issue Type: Bug Affects Versions: 2.5.10 Reporter: Nihal Jain Assignee: Nihal Jain We are running nighlies with older hadoop2 and hadoop3 on branch-2.5 and hence expected failures are not seen: * I see hadoop distributed 2.10.0 installed for last run at [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/lastCompletedBuild/execution/node/121/ws/hadoop-2/share/hadoop/hdfs/] ** Ref: [https://github.com/apache/hbase/blob/master/dev-support/Jenkinsfile#L133] * Also I see hadoop 3.1.1 for hadoop3 at [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/lastCompletedBuild/execution/node/121/ws/hadoop-3/share/hadoop/client/] ** Ref: [https://github.com/apache/hbase/blob/branch-2.5/dev-support/Jenkinsfile#L157] IMO they are wrong should be 2.10.2 and 3.2.4 for branch-2.5 CC: [~stoty] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28945) Update nightlies to run with hadoop2 = 2.10.2 and hadoop3 = 3.2.4
Nihal Jain created HBASE-28945: -- Summary: Update nightlies to run with hadoop2 = 2.10.2 and hadoop3 = 3.2.4 Key: HBASE-28945 URL: https://issues.apache.org/jira/browse/HBASE-28945 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28944) TestShadedHBaseTestingUtility fails with NCDFE: org/mockito/stubbing/Answer
Nihal Jain created HBASE-28944:
--
Summary: TestShadedHBaseTestingUtility fails with NCDFE:
org/mockito/stubbing/Answer
Key: HBASE-28944
URL: https://issues.apache.org/jira/browse/HBASE-28944
Project: HBase
Issue Type: Bug
Components: test
Affects Versions: 2.5.10
Reporter: Nihal Jain
Assignee: Nihal Jain
While working on https://github.com/apache/hbase/pull/6413 found we have
following pre-existing test failure:
{code:java}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.hbase.shaded.TestShadedHBaseTestingUtility
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.006 s
<<< FAILURE! - in org.apache.hbase.shaded.TestShadedHBaseTestingUtility
[ERROR] org.apache.hbase.shaded.TestShadedHBaseTestingUtility Time elapsed:
0.002 s <<< ERROR!
java.lang.NoClassDefFoundError: org/mockito/stubbing/Answer
at
org.apache.hadoop.hdfs.MiniDFSCluster.isNameNodeUp(MiniDFSCluster.java:2590)
at
org.apache.hadoop.hdfs.MiniDFSCluster.isClusterUp(MiniDFSCluster.java:2604)
at
org.apache.hadoop.hdfs.MiniDFSCluster.waitClusterUp(MiniDFSCluster.java:1479)
at
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:958)
at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:849)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:689)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:669)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1141)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1116)
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:46)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.ClassNotFoundException: org.mockito.stubbing.Answer
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:527)
... 24 more
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] TestShadedHBaseTestingUtility.setUp:46 » NoClassDefFound
org/mockito/stubbing/Answer
[INFO]
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 16.878 s (Wall Clock)
[INFO] Finished at: 2024-10-30T07:43:39Z
[INFO]
{code}
Seems related to https://issues.apache.org/jira/browse/HDFS-15915
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28928) Handle NPE in Split/Merge table when getMasterQuotaManager returns null
[
https://issues.apache.org/jira/browse/HBASE-28928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28928.
Fix Version/s: 2.7.0
3.0.0-beta-2
2.5.11
2.6.2
Hadoop Flags: Reviewed
Resolution: Fixed
> Handle NPE in Split/Merge table when getMasterQuotaManager returns null
> ---
>
> Key: HBASE-28928
> URL: https://issues.apache.org/jira/browse/HBASE-28928
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
>Affects Versions: 2.5.8
>Reporter: Aman Poonia
>Assignee: Aman Poonia
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.5.11, 2.6.2
>
>
> Currently when doing splits or merge we notify quota manager about the same.
> But if quota instance is null on below call
> {code:java}
> // code placeholder
> env.getMasterServices().getMasterQuotaManager() {code}
> So the below two lines will throw unexpected exception which ideally can be
> handled.
> {code:java}
> // SplitTableRegionProcedure.java
> env.getMasterServices().getMasterQuotaManager().onRegionSplit(this.getParentRegion());
> {code}
> {code:java}
> // MergeTableRegionProcedure.java
>
> env.getMasterServices().getMasterQuotaManager().onRegionMerged(this.mergedRegion);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28943) Remove all jackson 1.x dependencies from hadoop-3 profile, since all jackson 1.x versions have vulnerabilities
Nihal Jain created HBASE-28943: -- Summary: Remove all jackson 1.x dependencies from hadoop-3 profile, since all jackson 1.x versions have vulnerabilities Key: HBASE-28943 URL: https://issues.apache.org/jira/browse/HBASE-28943 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28927) Fix spotbugs issues introduced by refactoring to hbase-diagnostics with HBASE-28432
Nihal Jain created HBASE-28927: -- Summary: Fix spotbugs issues introduced by refactoring to hbase-diagnostics with HBASE-28432 Key: HBASE-28927 URL: https://issues.apache.org/jira/browse/HBASE-28927 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain Seeing a lot of spotbugs issues across PRs lately. These are coming due to newly added main code refactored as part of https://issues.apache.org/jira/browse/HBASE-28432 I was not aware these issues will be on complete code and not just PR code change. As now code sits inside main and not test, we should try to fix all the spotbugs issues. CC: [~ndimiduk], [~stoty] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28921) Skip bundling hbase-webapps folder in jars
Nihal Jain created HBASE-28921: -- Summary: Skip bundling hbase-webapps folder in jars Key: HBASE-28921 URL: https://issues.apache.org/jira/browse/HBASE-28921 Project: HBase Issue Type: Improvement Components: security, UI Reporter: Nihal Jain Assignee: Nihal Jain Bootstrap 3.4.1 was released in 13 Feb, 2019 and there has been no new 3.x release since then. This version of bootstrap has multiple medium CVEs reported recently. See [https://security.snyk.io/package/npm/bootstrap/3.4.1] for details. CVE List: * [https://www.cve.org/CVERecord?id=CVE-2024-6484] * [https://www.cve.org/CVERecord?id=CVE-2024-6485] Related Github Issue/Advisory: * [https://github.com/twbs/bootstrap/issues/40692] * [https://github.com/advisories/GHSA-9mvj-f7w8-pvh2] Based on synk.io the only non-vulnerable version seems to be in 5.x line. Upgrading from 3.x to 4.x itself would be substantial work. So may be we would have to move step by step i.e. migrate from 3.x to 4.x and then 4.x to 5.x. This JIRA is to capture all sub-task needed to achieve same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28916) Refactor chaos monkey related code to a new module hbase-chaos
Nihal Jain created HBASE-28916:
--
Summary: Refactor chaos monkey related code to a new module
hbase-chaos
Key: HBASE-28916
URL: https://issues.apache.org/jira/browse/HBASE-28916
Project: HBase
Issue Type: Improvement
Affects Versions: 3.0.0-beta-2
Reporter: Nihal Jain
Assignee: Nihal Jain
As part of this Jira we will create a new module named {{hbase-chaos}} and
optionally include it in the assembly. This change is necessary because we will
be removing all test jars from our assembly (with HBASE-28433), resulting in
the removal of chaos monkey and all its code, which may need to be manually
copied by operators. Currently, all the code resides in {{{}hbase-it{}}}.
CC: [~stoty], [~ndimiduk]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28913) LoadBalancerPerformanceEvaluation fails with NPE
Nihal Jain created HBASE-28913:
--
Summary: LoadBalancerPerformanceEvaluation fails with NPE
Key: HBASE-28913
URL: https://issues.apache.org/jira/browse/HBASE-28913
Project: HBase
Issue Type: Task
Reporter: Nihal Jain
Assignee: Nihal Jain
While testing [https://github.com/apache/hbase/pull/6258] found that
LoadBalancerPerformanceEvaluation fails with NPE, not related to PR as fails
for master as well. This Jira is to track and fix this issue.
{code:java}
bin % ./hbase
org.apache.hadoop.hbase.master.balancer.LoadBalancerPerformanceEvaluation
-regions 3 -servers 10
2024-10-14T01:48:06,772 INFO [main {}] metrics.MetricRegistries: Loaded
MetricRegistries class org.apache.hadoop.hbase.metrics.impl.MetricRegistriesImpl
2024-10-14T01:48:06,841 INFO [main {}]
balancer.LoadBalancerPerformanceEvaluation: Calling roundRobinAssignment
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 0
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 1
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 2
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 3
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 4
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 5
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 6
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 7
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 8
is on rack 0
2024-10-14T01:48:06,850 INFO [main {}] balancer.BalancerClusterState: server 9
is on rack 0
Time for roundRobinAssignment : 238ms
2024-10-14T01:48:07,079 INFO [main {}]
balancer.LoadBalancerPerformanceEvaluation: Calling retainAssignment
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 0
is on rack 0
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 1
is on rack 0
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 2
is on rack 0
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 3
is on rack 0
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 4
is on rack 0
2024-10-14T01:48:07,091 INFO [main {}] balancer.BalancerClusterState: server 5
is on rack 0
2024-10-14T01:48:07,092 INFO [main {}] balancer.BalancerClusterState: server 6
is on rack 0
2024-10-14T01:48:07,092 INFO [main {}] balancer.BalancerClusterState: server 7
is on rack 0
2024-10-14T01:48:07,092 INFO [main {}] balancer.BalancerClusterState: server 8
is on rack 0
2024-10-14T01:48:07,092 INFO [main {}] balancer.BalancerClusterState: server 9
is on rack 0
2024-10-14T01:48:07,284 INFO [main {}] balancer.BaseLoadBalancer: Reassigned
3 regions. 0 retained the pre-restart assignment. 3 regions were
assigned to random hosts, since the old hosts for these regions are no longer
present in the cluster. These hosts were:
Time for retainAssignment : 204ms
2024-10-14T01:48:07,284 INFO [main {}]
balancer.LoadBalancerPerformanceEvaluation: Calling balanceCluster
2024-10-14T01:48:07,315 INFO [main {}] balancer.BalancerClusterState: server 0
is on rack 0
2024-10-14T01:48:07,315 INFO [main {}] balancer.BalancerClusterState: server 1
is on rack 0
2024-10-14T01:48:07,315 INFO [main {}] balancer.BalancerClusterState: server 2
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 3
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 4
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 5
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 6
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 7
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 8
is on rack 0
2024-10-14T01:48:07,323 INFO [main {}] balancer.BalancerClusterState: server 9
is on rack 0
2024-10-14T01:48:07,325 ERROR [main {}] util.AbstractHBaseTool: Error running
command-line tool
java.lang.NullPointerException: Cannot invoke "java.util.List.size()" because
"this.candidateGenerators" is null
at
org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer.initCosts(StochasticLoadBalancer.java:750)
~[hbase-balancer-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
at
org.apache.hadoop.hbase.master.balancer.StochasticLoadBalancer.balanceTable(StochasticLoadBalancer.java:475)
~[hbase-balancer-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
at
org.apache.hadoop.hbase.
[jira] [Created] (HBASE-28896) Use spotless to sort the dependency in specified order for our pom.xml's
Nihal Jain created HBASE-28896: -- Summary: Use spotless to sort the dependency in specified order for our pom.xml's Key: HBASE-28896 URL: https://issues.apache.org/jira/browse/HBASE-28896 Project: HBase Issue Type: Task Components: build, community Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28835) Make connector support for Decimal type
[ https://issues.apache.org/jira/browse/HBASE-28835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28835. Hadoop Flags: Reviewed Resolution: Fixed > Make connector support for Decimal type > --- > > Key: HBASE-28835 > URL: https://issues.apache.org/jira/browse/HBASE-28835 > Project: HBase > Issue Type: Improvement > Components: spark >Affects Versions: connector-1.0.0 >Reporter: yan.duan >Assignee: yan.duan >Priority: Minor > Labels: pull-request-available > Fix For: connector-1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28585) copy_tables_desc.rb script should handle scenarios where the namespace does not exist in the target cluster
[
https://issues.apache.org/jira/browse/HBASE-28585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28585.
Release Note: This change incorporate logic within the script for detecting
and handling scenarios where the namespace does not exist.
Resolution: Fixed
> copy_tables_desc.rb script should handle scenarios where the namespace does
> not exist in the target cluster
> ---
>
> Key: HBASE-28585
> URL: https://issues.apache.org/jira/browse/HBASE-28585
> Project: HBase
> Issue Type: Improvement
> Components: jruby, scripts
>Affects Versions: 2.4.17
>Reporter: wenhao
>Assignee: wenhao
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2
>
>
> When utilizing the {{copy_tables_desc.rb}} script to duplicate tables to a
> target cluster, if the specified table's namespace is nonexistent in the
> target cluster, the script fails to execute successfully. It is recommended
> to incorporate logic within the script for detecting and handling scenarios
> where the namespace does not exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-28585) copy_tables_desc.rb script should handle scenarios where the namespace does not exist in the target cluster
[
https://issues.apache.org/jira/browse/HBASE-28585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain reopened HBASE-28585:
> copy_tables_desc.rb script should handle scenarios where the namespace does
> not exist in the target cluster
> ---
>
> Key: HBASE-28585
> URL: https://issues.apache.org/jira/browse/HBASE-28585
> Project: HBase
> Issue Type: Improvement
> Components: jruby, scripts
>Affects Versions: 2.4.17
>Reporter: wenhao
>Assignee: wenhao
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> When utilizing the {{copy_tables_desc.rb}} script to duplicate tables to a
> target cluster, if the specified table's namespace is nonexistent in the
> target cluster, the script fails to execute successfully. It is recommended
> to incorporate logic within the script for detecting and handling scenarios
> where the namespace does not exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28888) Backport "HBASE-18382 [Thrift] Add transport type info to info server" to branch-2
Nihal Jain created HBASE-2:
--
Summary: Backport "HBASE-18382 [Thrift] Add transport type info to
info server" to branch-2
Key: HBASE-2
URL: https://issues.apache.org/jira/browse/HBASE-2
Project: HBase
Issue Type: Improvement
Components: Thrift
Reporter: Lars George
Assignee: Beata Sudi
Fix For: 3.0.0-alpha-1
It would be really helpful to know if the Thrift server was started using the
HTTP or binary transport. Any additional info, like QOP settings for SASL etc.
would be great too. Right now the UI is very limited and shows {{true/false}}
for, for example, {{Compact Transport}}. It'd suggest to change this to show
something more useful like this:
{noformat}
Thrift Impl Type: non-blocking
Protocol: Binary
Transport: Framed
QOP: Authentication & Confidential
{noformat}
or
{noformat}
Protocol: Binary + HTTP
Transport: Standard
QOP: none
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28887) Fix broken link to mailing lists page in reference guide
[ https://issues.apache.org/jira/browse/HBASE-28887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28887. Hadoop Flags: Reviewed Resolution: Fixed > Fix broken link to mailing lists page in reference guide > > > Key: HBASE-28887 > URL: https://issues.apache.org/jira/browse/HBASE-28887 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 4.0.0-alpha-1 >Reporter: Dávid Paksy >Assignee: Dávid Paksy >Priority: Minor > Labels: pull-request-available > > The Reference Guide (book) link to the mailing lists page -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28885) [hbase-thirdparty] Bump hbase.stable.version to 2.5.10 in hbase-noop-htrace
Nihal Jain created HBASE-28885: -- Summary: [hbase-thirdparty] Bump hbase.stable.version to 2.5.10 in hbase-noop-htrace Key: HBASE-28885 URL: https://issues.apache.org/jira/browse/HBASE-28885 Project: HBase Issue Type: Sub-task Components: thirdparty Reporter: Nihal Jain Assignee: Nihal Jain Fix For: thirdparty-4.1.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28868) Permission check is missing for updateRSGroupConfig in branch-2
Nihal Jain created HBASE-28868: -- Summary: Permission check is missing for updateRSGroupConfig in branch-2 Key: HBASE-28868 URL: https://issues.apache.org/jira/browse/HBASE-28868 Project: HBase Issue Type: Bug Affects Versions: 2.7.0 Reporter: Nihal Jain Assignee: Nihal Jain Found this during HBASE-28867, we do not have security check for updateRSGroupConfig in branch-2. See [https://github.com/apache/hbase/blob/0dc334f572329be7eb2455cec3519fc820c04c25/hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java#L450] Same check exists in master [https://github.com/apache/hbase/blob/52082bc5b80a60406bfaaa630ed5cb23027436c1/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java#L2279] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28867) Backport "HBASE-20653 Add missing observer hooks for region server group to MasterObserver" to branch-2
Nihal Jain created HBASE-28867: -- Summary: Backport "HBASE-20653 Add missing observer hooks for region server group to MasterObserver" to branch-2 Key: HBASE-28867 URL: https://issues.apache.org/jira/browse/HBASE-28867 Project: HBase Issue Type: Bug Reporter: Ted Yu Assignee: Nihal Jain Fix For: 3.0.0-alpha-1 Currently the following region server group operations don't have corresponding hook in MasterObserver : * getRSGroupInfo * getRSGroupInfoOfServer * getRSGroupInfoOfTable * listRSGroup This JIRA is to * add them to MasterObserver * add pre/post hook calls in RSGroupAdminEndpoint thru master.getMasterCoprocessorHost for the above operations * add corresponding tests to TestRSGroups (in similar manner to that of HBASE-20627) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28843) Support for RS group endpoints in HBase REST
Nihal Jain created HBASE-28843: -- Summary: Support for RS group endpoints in HBase REST Key: HBASE-28843 URL: https://issues.apache.org/jira/browse/HBASE-28843 Project: HBase Issue Type: Umbrella Components: REST Reporter: Nihal Jain *Description:* Currently, the HBase REST server does not support endpoints for region server grouping. This feature request is to add new endpoints that will allow users to interact with and manage region server groups through the HBase REST API. *Goals:* # Expose endpoints to create, list, update, and delete region server groups along with other APIs as necessary, supported by Java client # Ensure endpoints support necessary authentication and authorization. # Provide appropriate error handling and logging for the new endpoints. *Acceptance Criteria:* # New endpoints for region server grouping are added to the HBase REST server. # Endpoints are thoroughly documented. # Unit and integration tests are created and passing. # Performance benchmarks are conducted to ensure minimal impact on existing functionalities. *Technical Details:* * New endpoints should follow RESTful principles. * Authentication/authorization mechanisms must be consistent with existing endpoints. * Ensure compatibility with existing HBase version and REST server. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-28070) Replace javax.servlet.jsp dependency with tomcat-jasper
[
https://issues.apache.org/jira/browse/HBASE-28070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain reopened HBASE-28070:
> Replace javax.servlet.jsp dependency with tomcat-jasper
>
>
> Key: HBASE-28070
> URL: https://issues.apache.org/jira/browse/HBASE-28070
> Project: HBase
> Issue Type: Improvement
> Components: security, UI
>Reporter: Nikita Pande
>Assignee: Nihal Jain
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2
>
>
> *Problem Statement*
> HBase has to explicitly depends on org.glassfish:javax.el:jar:3.0.1-b08 as
> this dependency is needed by javax.servlet.jsp. This direct dependency was
> added due to https://issues.apache.org/jira/browse/HBASE-18831
> mvn dependency tree shows below
> {code:java}
> [INFO] | +- org.glassfish.web:javax.servlet.jsp:jar:2.3.2:compile
> [INFO] | | \- org.glassfish:javax.el:jar:3.0.1-b08:compile
> {code}
> org.glassfish:javax.el:jar:3.0.1-b08:compile has
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15250]
> We have ton of Jiras and HBase around glass fish and issues caused due to it.
> With this Jira I plan to completely remove
> org.glassfish:javax.el:jar:3.0.1-b08 from our dependency tree. Also
> org.glassfish:javax.el is EOL and needs migration to jakarta-el which is not
> trivial. See [https://mvnrepository.com/artifact/org.glassfish/javax.el]
> *Proposed Solution*
> This Jira aims to replace javax.servlet.jsp dependency with tomcat-jasper (as
> javax.servlet.jsp strictly needs glassfish) and this requires minimal change
> wrt to migrating to jakarta-el.
> Also, we use javax.servlet.jsp to generate/build JSP and same can be achieved
> via tomcat-jasper.
> CC: [~zhangduo]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28832) Upgrade from bootstrap 3.4.1 to {a_non_vulnerable_version}
Nihal Jain created HBASE-28832:
--
Summary: Upgrade from bootstrap 3.4.1 to {a_non_vulnerable_version}
Key: HBASE-28832
URL: https://issues.apache.org/jira/browse/HBASE-28832
Project: HBase
Issue Type: Improvement
Components: security, UI
Reporter: Nihal Jain
Bootstrap 3.4.1 was released in 13 Feb, 2019 and there has been no new 3.x
release since then. This version of bootstrap has multiple medium CVEs reported
recently.
See https://security.snyk.io/package/npm/bootstrap/3.4.1 for details.
CVE List:
* https://www.cve.org/CVERecord?id=CVE-2024-6484
* https://www.cve.org/CVERecord?id=CVE-2024-6485
Based on synk.io the only non-vulnerable version seems to be in 5.x line.
Upgrading from 3.x to 4.x itself would be substantial work. So may be we would
have to move step by step i.e. migrate from 3.x to 4.x and then 4.x to 5.x.
This JIRA is to capture all sub-task needed to achieve same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-27817) Migrate javax.el:3.0.1-b08 to jakarta.el-4.0.2
[ https://issues.apache.org/jira/browse/HBASE-27817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-27817. Resolution: Won't Fix We have fixed this indirectly via HBASE-28070! > Migrate javax.el:3.0.1-b08 to jakarta.el-4.0.2 > -- > > Key: HBASE-27817 > URL: https://issues.apache.org/jira/browse/HBASE-27817 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0-alpha-4, 2.5.5, 2.4.18 >Reporter: Wes Schuitema >Priority: Trivial > > The javax.el artifact contains a CVE: [CVE-2021-28170. > |https://nvd.nist.gov/vuln/detail/CVE-2021-28170]The CVE itself is not a big > issue since we're pre-compiling our JSP pages when building HBase, no user > input is parsed which reduces the risk considerably. > The org.glassfish:javax.el artifact was moved to org.glassfish:jakarta.el, > which means a migration to get rid of the CVE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28807) Remove some useless code and add some logs for CanaryTool
[ https://issues.apache.org/jira/browse/HBASE-28807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28807. Fix Version/s: 4.0.0-alpha-1 2.7.0 3.0.0-beta-2 Hadoop Flags: Reviewed Resolution: Fixed > Remove some useless code and add some logs for CanaryTool > - > > Key: HBASE-28807 > URL: https://issues.apache.org/jira/browse/HBASE-28807 > Project: HBase > Issue Type: Improvement > Components: canary >Reporter: MisterWang >Assignee: MisterWang >Priority: Minor > Labels: pull-request-available > Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2 > > > Remove some useless code in CanaryTool.sniff. > Add some logs when get null location for table region. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28794) [hbase-thirdparty] Enable infra automation: autolink to Jira and 'pull-request-available' label
[
https://issues.apache.org/jira/browse/HBASE-28794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28794.
Resolution: Fixed
> [hbase-thirdparty] Enable infra automation: autolink to Jira and
> 'pull-request-available' label
> ---
>
> Key: HBASE-28794
> URL: https://issues.apache.org/jira/browse/HBASE-28794
> Project: HBase
> Issue Type: Task
> Components: community
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: thirdparty-4.1.9
>
> Attachments: Screenshot 2024-08-21 at 7.38.46 PM.png, Screenshot
> 2024-08-21 at 7.39.25 PM.png
>
>
> Patterns like HBASE-28786 will be clickable, so it's easier to go to the Jira
> page.
> {{.asf.yaml}} provides an option to do this via config: See
> [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AutolinksforJira]
> Even without manual configuring this already works for hbase somehow. See
> [https://github.com/apache/hbase/commits/master/]
> Maybe configured at repo level in INFRA?
> But same does not work for hbase-connectors and other repos. Will use this
> config to fix the issue.
> Also will enable label feature for 'pull-request-available', same as hbase
> main repo: HBASE-28325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28795) [hbase-operator-tools] Enable infra automation: autolink to Jira and 'pull-request-available' label
[
https://issues.apache.org/jira/browse/HBASE-28795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28795.
Resolution: Fixed
Merged to codebase. Verified that we have proper link back of commits to jira,
see [https://github.com/apache/hbase-operator-tools/commits/master/]
Thank you [~vjasani] for reviewing.
> [hbase-operator-tools] Enable infra automation: autolink to Jira and
> 'pull-request-available' label
> ---
>
> Key: HBASE-28795
> URL: https://issues.apache.org/jira/browse/HBASE-28795
> Project: HBase
> Issue Type: Task
> Components: community
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: hbase-operator-tools-1.3.0
>
>
> Patterns like HBASE-28786 will be clickable, so it's easier to go to the Jira
> page.
> {{.asf.yaml}} provides an option to do this via config: See
> [https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AutolinksforJira]
> Even without manual configuring this already works for hbase somehow. See
> [https://github.com/apache/hbase/commits/master/]
> Maybe configured at repo level in INFRA?
> But same does not work for hbase-connectors and other repos. Will use this
> config to fix the issue.
> Also will enable label feature for 'pull-request-available', same as hbase
> main repo: HBASE-28325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28791) [hbase-connectors] GitHub: Enable autolink to Jira
Nihal Jain created HBASE-28791:
--
Summary: [hbase-connectors] GitHub: Enable autolink to Jira
Key: HBASE-28791
URL: https://issues.apache.org/jira/browse/HBASE-28791
Project: HBase
Issue Type: Task
Components: community
Reporter: Nihal Jain
Assignee: Nihal Jain
Patterns like HBASE-28786 will be clickable, so it's easier to go to the Jira
page.
{{.asf.yaml }} provides an option to do this via config: See
[https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AutolinksforJira]
Even without manual configuraing this already works for hbase somehow. See
[https://github.com/apache/hbase/commits/master/]
Maybe configured at repo level in INFRA?
But same does not work for hbase-connectors and other repos. Will use this
config to fix the issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28790) hbase-connectors fails to build with hbase 2.6.0
Nihal Jain created HBASE-28790:
--
Summary: hbase-connectors fails to build with hbase 2.6.0
Key: HBASE-28790
URL: https://issues.apache.org/jira/browse/HBASE-28790
Project: HBase
Issue Type: Bug
Components: build, hbase-connectors
Reporter: Nihal Jain
Assignee: Nihal Jain
hbase-connectors fails to build with hbase 2.6.0
{code:java}
[INFO] Reactor Summary for Apache HBase Connectors 1.1.0-SNAPSHOT:
[INFO]
[INFO] Apache HBase Connectors SUCCESS [ 4.377 s]
[INFO] Apache HBase - Kafka ... SUCCESS [ 0.116 s]
[INFO] Apache HBase - Model Objects for Kafka Proxy ... SUCCESS [ 3.222 s]
[INFO] Apache HBase - Kafka Proxy . FAILURE [ 8.305 s]
[INFO] Apache HBase - Spark ... SKIPPED
[INFO] Apache HBase - Spark Protocol .. SKIPPED
[INFO] Apache HBase - Spark Protocol (Shaded) . SKIPPED
[INFO] Apache HBase - Spark Connector . SKIPPED
[INFO] Apache HBase - Spark Integration Tests . SKIPPED
[INFO] Apache HBase Connectors - Assembly . SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 16.703 s
[INFO] Finished at: 2024-08-17T11:29:20Z
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile)
on project hbase-kafka-proxy: Compilation failure
[ERROR]
/workspaces/hbase-connectors/kafka/hbase-kafka-proxy/src/main/java/org/apache/hadoop/hbase/kafka/KafkaBridgeConnection.java:[169,31]
is not
abstract and does not override abstract method
setRequestAttribute(java.lang.String,byte[]) in
org.apache.hadoop.hbase.client.TableBuilder {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28789) [JDK17] Jenkins build support for hbase-connectors
Nihal Jain created HBASE-28789: -- Summary: [JDK17] Jenkins build support for hbase-connectors Key: HBASE-28789 URL: https://issues.apache.org/jira/browse/HBASE-28789 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28788) Support JDK17 for hbase-connectors
Nihal Jain created HBASE-28788: -- Summary: Support JDK17 for hbase-connectors Key: HBASE-28788 URL: https://issues.apache.org/jira/browse/HBASE-28788 Project: HBase Issue Type: Umbrella Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28787) Support JDK17 for hbase-operator-tools
Nihal Jain created HBASE-28787: -- Summary: Support JDK17 for hbase-operator-tools Key: HBASE-28787 URL: https://issues.apache.org/jira/browse/HBASE-28787 Project: HBase Issue Type: Umbrella Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28786) Fix classname for command: copyreppeers
Nihal Jain created HBASE-28786: -- Summary: Fix classname for command: copyreppeers Key: HBASE-28786 URL: https://issues.apache.org/jira/browse/HBASE-28786 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain Stumbled upon this. Dug deeper seems during review we missed to rename the classname in bin/hbase when the actual class was renamed from ReplicationPeerMigrationTool -> CopyReplicationPeers See https://github.com/apache/hbase/compare/69603351b3f2817c74d869d32da0596bab3c409e..1d11ce96c44277df6ccdd16ae2c9d8a1c419f3da [hbase@hostname~]$ hbase copyreppeers Error: Could not find or load main class org.apache.hadoop.hbase.replication.ReplicationPeerMigrationTool Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.replication.ReplicationPeerMigrationTool FYI [~zhangduo] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28784) Exclude samples and release-documentation zip of jaxws-ri from output tarball
Nihal Jain created HBASE-28784: -- Summary: Exclude samples and release-documentation zip of jaxws-ri from output tarball Key: HBASE-28784 URL: https://issues.apache.org/jira/browse/HBASE-28784 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain Found this while I was checking lib folder for extracted assembly for master. I guess this must be a problem for all branches fixed for HBASE-28070. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28532) Remove vulnerable dependencies: slf4j-log4j12 and log4j:log4j
[ https://issues.apache.org/jira/browse/HBASE-28532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28532. Fix Version/s: hbase-operator-tools-1.3.0 Hadoop Flags: Reviewed Resolution: Fixed Thanks [~nikitapande] for the PR. Merged to codebase! > Remove vulnerable dependencies: slf4j-log4j12 and log4j:log4j > - > > Key: HBASE-28532 > URL: https://issues.apache.org/jira/browse/HBASE-28532 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools >Reporter: Nikita Pande >Assignee: Nikita Pande >Priority: Major > Fix For: hbase-operator-tools-1.3.0 > > > slf4j-log4j12 is a bridge from SLF4J to Log4j 1.x. > Since log4j 1.x is vulnerable , so this needs to be removed. > > It is to be replaced with the log4j-slf4j-impl dependency, which is a bridge > from SLF4J to Log4j 2.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28606) [hbase-connectors] Support for build on mac M1
[ https://issues.apache.org/jira/browse/HBASE-28606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28606. Fix Version/s: hbase-connectors-1.1.0 Hadoop Flags: Reviewed Resolution: Fixed Merged to code base. Thanks for your contribution [~nikitapande] ! > [hbase-connectors] Support for build on mac M1 > -- > > Key: HBASE-28606 > URL: https://issues.apache.org/jira/browse/HBASE-28606 > Project: HBase > Issue Type: Improvement >Reporter: Nikita Pande >Assignee: Nikita Pande >Priority: Major > Fix For: hbase-connectors-1.1.0 > > > [INFO] --- protobuf:0.6.1:compile (compile-protoc) @ hbase-spark-protocol --- > [ERROR] PROTOC FAILED: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-18570) Fix NPE when HBaseContext was never initialized
[
https://issues.apache.org/jira/browse/HBASE-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-18570.
Fix Version/s: hbase-connectors-1.1.0
Hadoop Flags: Reviewed
Resolution: Fixed
> Fix NPE when HBaseContext was never initialized
> ---
>
> Key: HBASE-18570
> URL: https://issues.apache.org/jira/browse/HBASE-18570
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0
>Reporter: Yuexin Zhang
>Assignee: Junegunn Choi
>Priority: Minor
> Fix For: hbase-connectors-1.1.0
>
>
> I recently run into the same issue as described in stackoverflow :
> https://stackoverflow.com/questions/38865558/sparksql-dataframes-does-not-work-in-spark-shell-and-application#
> If we don't explicitly initialize a HBaseContext and don't set
> hbase.use.hbase.context option to false, it will run into NPE at:
> {code}
> val wrappedConf = new SerializableConfiguration(hbaseContext.config)
> {code}
> https://github.com/apache/hbase/blob/master/hbase-spark/src/main/scala/org/apache/hadoop/hbase/spark/DefaultSource.scala#L140
> Should we safe guard with a NULL validation on hbaseContext?
> Something like:
> {code}
> //create or get latest HBaseContext
> val hbaseContext:HBaseContext = if (useHBaseContext && null !=
> LatestHBaseContextCache.latest) {
> LatestHBaseContextCache.latest
> } else {
> val config = HBaseConfiguration.create()
> configResources.split(",").foreach( r => config.addResource(r))
> new HBaseContext(sqlContext.sparkContext, config)
> }
> {code}
> Or maybe it's better to make sure the HBaseContext is instantiated properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28768) hbase-table-reporter shoud use the hbase.version declared in the parent pom.xml and use junit for UT
[ https://issues.apache.org/jira/browse/HBASE-28768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28768. Fix Version/s: hbase-operator-tools-1.3.0 Hadoop Flags: Reviewed Resolution: Fixed > hbase-table-reporter shoud use the hbase.version declared in the parent > pom.xml and use junit for UT > > > Key: HBASE-28768 > URL: https://issues.apache.org/jira/browse/HBASE-28768 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools >Affects Versions: 1.2.0 >Reporter: guluo >Assignee: guluo >Priority: Major > Fix For: hbase-operator-tools-1.3.0 > > > In hbase-operator-tools project, the submodule hbase-table-reporter shoud use > the hbase.version declared in the parent pom, rather than using 2.1.1 defined > by itself. > And, we need to add junit dependency and use junit for UT in this submodule. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28434) Update assembly to create a tarball with hadoop and without hadoop
Nihal Jain created HBASE-28434: -- Summary: Update assembly to create a tarball with hadoop and without hadoop Key: HBASE-28434 URL: https://issues.apache.org/jira/browse/HBASE-28434 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain The goal of this task is to update the HBase assembly by providing two distinct variants - one that includes Hadoop and one that does not. Currently, our assembly includes a substantial amount of the Hadoop distribution. This task involves modifying our build and assembly process to create two separate distributions of HBase: * A variant that includes Hadoop, serving as a complete package for users who do not have a pre-existing Hadoop installation. * A leaner variant without Hadoop, suitable for environments where Hadoop is already installed and configured. This change aims to reduce the distribution size, speed up startup times, and decrease the chance of conflicts with the Hadoop jars. It also aims to reduce the number of CVE-prone JARs in the binary assemblies. The task includes ensuring that both variants function correctly in their respective scenarios and that existing functionality is not negatively impacted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28433) Modify the assembly to not include test jars and their transitive dependencies
Nihal Jain created HBASE-28433: -- Summary: Modify the assembly to not include test jars and their transitive dependencies Key: HBASE-28433 URL: https://issues.apache.org/jira/browse/HBASE-28433 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28432) Move tools which are under test packaging to hbase-tools
Nihal Jain created HBASE-28432: -- Summary: Move tools which are under test packaging to hbase-tools Key: HBASE-28432 URL: https://issues.apache.org/jira/browse/HBASE-28432 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Initially will prepare a list of tools having HBaseInterfaceAudience.TOOLS under test like: * https://github.com/apache/hbase/blob/master/hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java * https://github.com/apache/hbase/blob/936d267d1094e37222b9b836ab068689ccce3574/hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java * https://github.com/apache/hbase/blob/936d267d1094e37222b9b836ab068689ccce3574/hbase-server/src/test/java/org/apache/hadoop/hbase/HFilePerformanceEvaluation.java * https://github.com/apache/hbase/blob/936d267d1094e37222b9b836ab068689ccce3574/hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/ScanPerformanceEvaluation.java * https://github.com/apache/hbase/blob/936d267d1094e37222b9b836ab068689ccce3574/hbase-balancer/src/test/java/org/apache/hadoop/hbase/master/balancer/LoadBalancerPerformanceEvaluation.java Above is a list on 1st analysis. Will check more. CC: [~stoty], [~zhangduo], [~ndimiduk], [~bbeaudreault] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28418) [JDK17] Jenkins build support for hbase-operator-tools
Nihal Jain created HBASE-28418: -- Summary: [JDK17] Jenkins build support for hbase-operator-tools Key: HBASE-28418 URL: https://issues.apache.org/jira/browse/HBASE-28418 Project: HBase Issue Type: Improvement Components: hbase-operator-tools, java Reporter: Nihal Jain Assignee: Nihal Jain Fix For: hbase-operator-tools-1.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27814) Add support for dump and process metrics servlet in REST InfoServer
[ https://issues.apache.org/jira/browse/HBASE-27814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-27814. Resolution: Fixed > Add support for dump and process metrics servlet in REST InfoServer > --- > > Key: HBASE-27814 > URL: https://issues.apache.org/jira/browse/HBASE-27814 > Project: HBase > Issue Type: Sub-task > Components: REST >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Minor > Labels: pull-request-available > Fix For: 2.6.0, 4.0.0-alpha-1, 3.0.0-beta-2 > > > Unlike other HBase Master/RS Info Servers, HBase REST Server does not provide > a way to: > * Get debug dump for quick access to stacks, logs etc. > * Get process metrics like threads, gc collectors etc. > This task is add the above in HBase REST InfoServer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-27814) Add support for dump and process metrics servlet in REST InfoServer
[ https://issues.apache.org/jira/browse/HBASE-27814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain reopened HBASE-27814: > Add support for dump and process metrics servlet in REST InfoServer > --- > > Key: HBASE-27814 > URL: https://issues.apache.org/jira/browse/HBASE-27814 > Project: HBase > Issue Type: Sub-task > Components: REST >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2 > > > Unlike other HBase Master/RS Info Servers, HBase REST Server does not provide > a way to: > * Get debug dump for quick access to stacks, logs etc. > * Get process metrics like threads, gc collectors etc. > This task is add the above in HBase REST InfoServer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28408) Confusing logging during backup restore
[
https://issues.apache.org/jira/browse/HBASE-28408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28408.
Fix Version/s: 2.6.0
4.0.0-alpha-1
3.0.0-beta-2
Hadoop Flags: Reviewed
Resolution: Fixed
> Confusing logging during backup restore
> ---
>
> Key: HBASE-28408
> URL: https://issues.apache.org/jira/browse/HBASE-28408
> Project: HBase
> Issue Type: Bug
> Components: backup&restore
>Affects Versions: 2.6.0
>Reporter: Dieter De Paepe
>Assignee: Dieter De Paepe
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.6.0, 4.0.0-alpha-1, 3.0.0-beta-2
>
>
> Encountered this while experimenting with the backup/restore functionality.
> My setup was as follows:
> * Took several backups (Full1, inc2, inc3)
> * Changed an entry in the "lily_tenant_acme:LILY_SETTINGS" table
> * Attempt a restore (to test if my changed entry is reverted):
> {code:java}
> $ hbase restore -conf backup-conf.xml s3a://backuprestore-experiments/hbase
> backup_1709123740345 -t "lily_tenant_acme:LILY_SETTINGS" -m
> "lily_tenant_acme:LILY_SETTINGS-restored1" -o
> 24/02/28 16:15:41 WARN org.apache.hadoop.hbase.mapreduce.TableMapReduceUtil:
> The addDependencyJars(Configuration, Class...) method has been deprecated
> since it is easy to use incorrectly. Most users should rely on
> addDependencyJars(Job) instead. See HBASE-8386 for more details.
> 24/02/28 16:15:58 WARN org.apache.hadoop.hbase.tool.LoadIncrementalHFiles:
> Skipping non-directory
> hdfs://hdfsns/user/lily/hbase-staging/bulk_output-lily_tenant_acme-LILY_SETTINGS-restored1-1709136941410/_SUCCESS
> 24/02/28 16:15:59 WARN
> org.apache.hadoop.hbase.backup.impl.RestoreTablesClient: Nothing has changed,
> so there is no need to restore 'lily_tenant_acme:LILY_SETTINGS'
> {code}
> Based on the final logging line, I presumed my restore operation had failed.
> After some investigation however, I found that this was not the case: my
> change was reverted as expected.
> Some code investigation learned me this log message is shown because I was
> restoring backup `inc3`, and there were no changes between `full1` and `inc3`.
> I suggest rephrasing this log message, and changing it to a INFO level.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28393) Update Apache Parent POM to version 31
Nihal Jain created HBASE-28393: -- Summary: Update Apache Parent POM to version 31 Key: HBASE-28393 URL: https://issues.apache.org/jira/browse/HBASE-28393 Project: HBase Issue Type: Task Components: build, dependencies Reporter: Nihal Jain Assignee: Nihal Jain Bump to https://github.com/apache/maven-apache-parent/releases/tag/apache-31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28392) Bump jackson version to 2.16.1
Nihal Jain created HBASE-28392: -- Summary: Bump jackson version to 2.16.1 Key: HBASE-28392 URL: https://issues.apache.org/jira/browse/HBASE-28392 Project: HBase Issue Type: Task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28388) Field sorting is broken in HBase Web UI
Nihal Jain created HBASE-28388: -- Summary: Field sorting is broken in HBase Web UI Key: HBASE-28388 URL: https://issues.apache.org/jira/browse/HBASE-28388 Project: HBase Issue Type: Bug Affects Versions: 2.6.0 Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28383) Update hbase-env.sh with alternates to JVM flags which are no longer supported with JDK17
Nihal Jain created HBASE-28383:
--
Summary: Update hbase-env.sh with alternates to JVM flags which
are no longer supported with JDK17
Key: HBASE-28383
URL: https://issues.apache.org/jira/browse/HBASE-28383
Project: HBase
Issue Type: Improvement
Reporter: Nihal Jain
Assignee: Nihal Jain
Some JVM flags like {{{}-XX:+PrintGCDetails{}}}, {{-XX:+PrintGCDateStamps}}
etc. are no longer supported with JDK 17 and hbase would fail to start if these
are passed.
We should do an audit and update
[https://github.com/apache/hbase/blob/master/conf/hbase-env.sh] to capture
alternate/fix.
Will refer following for a fix/repalacement:
*
[https://stackoverflow.com/questions/54144713/is-there-a-replacement-for-the-garbage-collection-jvm-args-in-java-11]
*
[https://docs.oracle.com/javase/9/tools/java.htm#GUID-BE93ABDC-999C-4CB5-A88B-1994AAAC74D5__CONVERTGCLOGGINGFLAGSTOXLOG-A5046BD1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28382) Build hbase-connectors with JDK17
Nihal Jain created HBASE-28382: -- Summary: Build hbase-connectors with JDK17 Key: HBASE-28382 URL: https://issues.apache.org/jira/browse/HBASE-28382 Project: HBase Issue Type: Improvement Components: java, thirdparty Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28381) Build hbase-operator-tools with JDK17
Nihal Jain created HBASE-28381: -- Summary: Build hbase-operator-tools with JDK17 Key: HBASE-28381 URL: https://issues.apache.org/jira/browse/HBASE-28381 Project: HBase Issue Type: Improvement Components: java, thirdparty Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28380) Build hbase-thirdparty with JDK17
Nihal Jain created HBASE-28380: -- Summary: Build hbase-thirdparty with JDK17 Key: HBASE-28380 URL: https://issues.apache.org/jira/browse/HBASE-28380 Project: HBase Issue Type: Task Components: java, thirdparty Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28142) Region Server Logs getting spammed with warning when storefile has no reader
[ https://issues.apache.org/jira/browse/HBASE-28142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-28142. Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.6+. Thanks for the PR [~anchalk1]. Thanks for the review [~chrajeshbab...@gmail.com]. Thanks for reporting [~nikitapande]! > Region Server Logs getting spammed with warning when storefile has no reader > > > Key: HBASE-28142 > URL: https://issues.apache.org/jira/browse/HBASE-28142 > Project: HBase > Issue Type: Improvement >Reporter: Nikita Pande >Assignee: Anchal Kejriwal >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0, 2.7.0, 3.0.0-beta-2 > > > Hbase tables which have IS_MOB set as TRUE and table metrics is enabled, > there are warning logs getting generated "StoreFile has a null > Reader on hbase region server. > After setting IS_MOB as false for a table, this logs are not visible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28375) HBase Operator Tools fails to compile with hbase 2.6.0
[
https://issues.apache.org/jira/browse/HBASE-28375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28375.
Hadoop Flags: Reviewed
Resolution: Fixed
> HBase Operator Tools fails to compile with hbase 2.6.0
> --
>
> Key: HBASE-28375
> URL: https://issues.apache.org/jira/browse/HBASE-28375
> Project: HBase
> Issue Type: Bug
> Components: hbase-operator-tools
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
> Fix For: hbase-operator-tools-1.3.0
>
>
> HBase Operator Tools fails to compile with hbase 2.6.0.
> {code:java}
> [ERROR]
> /file_path/hbase-operator-tools/hbase-hbck2/src/main/java/org/apache/hbase/hbck1/ReplicationChecker.java:[59,49]
> method getReplicationPeerStorage in class
> org.apache.hadoop.hbase.replication.ReplicationStorageFactory cannot be
> applied to given types;
> [ERROR] required:
> org.apache.hadoop.fs.FileSystem,org.apache.hadoop.hbase.zookeeper.ZKWatcher,org.apache.hadoop.conf.Configuration
> [ERROR] found:
> org.apache.hadoop.hbase.zookeeper.ZKWatcher,org.apache.hadoop.conf.Configuration
> [ERROR] reason: actual and formal argument lists differ in length {code}
> Seems there is a breaking change between
> [https://github.com/apache/hbase/blob/branch-2.5/hbase-replication/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStorageFactory.java]
> vs
> [https://github.com/apache/hbase/blob/branch-2.6/hbase-replication/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStorageFactory.java]
> where a public method has been dropped, which is used by operator tools and
> hence the build will fail for it. See
> [https://github.com/apache/hbase-operator-tools/blob/master/hbase-hbck2/src/main/java/org/apache/hbase/hbck1/ReplicationChecker.java#L58]
> where the effected method is invoked.
> Since ReplicationStorageFactory is @InterfaceAudience.Private so maybe it is
> fine.
> Will try to fix and make changes in hbase-operator-tools to fall back to new
> method, in case if build with branch-2.6
> CC: [~zhangduo]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28375) Build HBase Operator tool with hbase 2.6.0
Nihal Jain created HBASE-28375:
--
Summary: Build HBase Operator tool with hbase 2.6.0
Key: HBASE-28375
URL: https://issues.apache.org/jira/browse/HBASE-28375
Project: HBase
Issue Type: Task
Reporter: Nihal Jain
Assignee: Nihal Jain
HBase Operator Tools fails to compile with hbase 2.6.0.
{code:java}
[ERROR]
/Users/nihjain/code/visa/hbase-operator-tools/hbase-hbck2/src/main/java/org/apache/hbase/hbck1/ReplicationChecker.java:[59,49]
method getReplicationPeerStorage in class
org.apache.hadoop.hbase.replication.ReplicationStorageFactory cannot be applied
to given types;
[ERROR] required:
org.apache.hadoop.fs.FileSystem,org.apache.hadoop.hbase.zookeeper.ZKWatcher,org.apache.hadoop.conf.Configuration
[ERROR] found:
org.apache.hadoop.hbase.zookeeper.ZKWatcher,org.apache.hadoop.conf.Configuration
[ERROR] reason: actual and formal argument lists differ in length {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28368) Backport "HBASE-27693 Support for Hadoop's LDAP Authentication mechanism (Web UI only)" to branch-2
Nihal Jain created HBASE-28368: -- Summary: Backport "HBASE-27693 Support for Hadoop's LDAP Authentication mechanism (Web UI only)" to branch-2 Key: HBASE-28368 URL: https://issues.apache.org/jira/browse/HBASE-28368 Project: HBase Issue Type: New Feature Reporter: Yash Dodeja Assignee: Yash Dodeja Fix For: 3.0.0-alpha-4 Hadoop's AuthenticationFilter has changed and now has support for ldap mechanism too. HBase still uses an older version tightly coupled with kerberos and spnego as the only auth mechanisms. HADOOP-12082 has added support for multiple auth handlers including LDAP. On trying to use Hadoop's AuthenticationFilterInitializer in hbase.http.filter.initializers, there is a casting exception as HBase requires it to extend org.apache.hadoop.hbase.http.FilterInitializer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28367) Backport "HBASE-27811 Enable cache control for logs endpoint and set max age as 0" to branch-2
Nihal Jain created HBASE-28367: -- Summary: Backport "HBASE-27811 Enable cache control for logs endpoint and set max age as 0" to branch-2 Key: HBASE-28367 URL: https://issues.apache.org/jira/browse/HBASE-28367 Project: HBase Issue Type: Improvement Reporter: Yash Dodeja Assignee: Yash Dodeja Fix For: 3.0.0-alpha-4 Not setting the proper header values may cause browsers to store pages within their respective caches. On public, shared, or any other non-private computers, a malicious person may search through the browser cache to locate sensitive information cached during another user's session. /logs endpoint contains sensitive information that an attacker can exploit. Any page with sensitive information needs to have the following headers in response: Cache-Control: no-cache, no-store, max-age=0 Pragma: no-cache Expires: -1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28311) Few ITs (using MiniMRYarnCluster on hadoop-2) are failing due to NCDFE: com/sun/jersey/core/util/FeaturesAndProperties
Nihal Jain created HBASE-28311:
--
Summary: Few ITs (using MiniMRYarnCluster on hadoop-2) are failing
due to NCDFE: com/sun/jersey/core/util/FeaturesAndProperties
Key: HBASE-28311
URL: https://issues.apache.org/jira/browse/HBASE-28311
Project: HBase
Issue Type: Bug
Reporter: Nihal Jain
Assignee: Nihal Jain
Found this while trying to run tests for HBASE-28301 locally, On branch-2 where
hadoop 2 is default, the specified tests don't even run as MiniMRYarnCluster
itself fails to start.
For example saw this while trying to run IntegrationTestImportTsv:
{code:java}
2024-01-12T01:10:13,486 ERROR [Thread-221 {}] log.Slf4jLog(87): Error starting
handlers
java.lang.NoClassDefFoundError: com/sun/jersey/core/util/FeaturesAndProperties
at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_381]
at java.lang.ClassLoader.defineClass(ClassLoader.java:756) ~[?:1.8.0_381]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
~[?:1.8.0_381]
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
~[?:1.8.0_381]
at java.net.URLClassLoader.access$100(URLClassLoader.java:74) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:369) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:363) ~[?:1.8.0_381]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_381]
at java.net.URLClassLoader.findClass(URLClassLoader.java:362) ~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_381]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_381]
at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_381]
at java.lang.ClassLoader.defineClass(ClassLoader.java:756) ~[?:1.8.0_381]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
~[?:1.8.0_381]
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
~[?:1.8.0_381]
at java.net.URLClassLoader.access$100(URLClassLoader.java:74) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:369) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:363) ~[?:1.8.0_381]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_381]
at java.net.URLClassLoader.findClass(URLClassLoader.java:362) ~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_381]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_381]
at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_381]
at java.lang.ClassLoader.defineClass(ClassLoader.java:756) ~[?:1.8.0_381]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
~[?:1.8.0_381]
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
~[?:1.8.0_381]
at java.net.URLClassLoader.access$100(URLClassLoader.java:74) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:369) ~[?:1.8.0_381]
at java.net.URLClassLoader$1.run(URLClassLoader.java:363) ~[?:1.8.0_381]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_381]
at java.net.URLClassLoader.findClass(URLClassLoader.java:362) ~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:418) ~[?:1.8.0_381]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
~[?:1.8.0_381]
at java.lang.ClassLoader.loadClass(ClassLoader.java:351) ~[?:1.8.0_381]
at java.lang.Class.getDeclaredConstructors0(Native Method) ~[?:1.8.0_381]
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
~[?:1.8.0_381]
at java.lang.Class.getDeclaredConstructors(Class.java:2020) ~[?:1.8.0_381]
at
com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:243)
~[guice-3.0.jar:?]
at
com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:96)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:845)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:772)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:256)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:205)
~[guice-3.0.jar:?]
at
com.google.inject.internal.InjectorImpl.getBinding(InjectorImpl.java:146)
~[guice-3.0.jar:?]
at com.google.inject.internal.InjectorImpl.getBinding(InjectorImpl.java:66)
~[guice-3.0.
[jira] [Created] (HBASE-28301) IntegrationTestImportTsv fails with UnsupportedOperationException
Nihal Jain created HBASE-28301:
--
Summary: IntegrationTestImportTsv fails with
UnsupportedOperationException
Key: HBASE-28301
URL: https://issues.apache.org/jira/browse/HBASE-28301
Project: HBase
Issue Type: Bug
Reporter: Nihal Jain
Assignee: Nihal Jain
IntegrationTestImportTsv fails with UnsupportedOperationException
{code:java}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 337.526
s <<< FAILURE! - in org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
[ERROR]
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv.testGenerateAndLoad
Time elapsed: 279.783 s <<< ERROR!
java.lang.UnsupportedOperationException: Unable to find suitable constructor
for class org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv$2
at
org.apache.hadoop.hbase.util.ReflectionUtils.findConstructor(ReflectionUtils.java:133)
at
org.apache.hadoop.hbase.util.ReflectionUtils.newInstance(ReflectionUtils.java:98)
at
org.apache.hadoop.hbase.client.RawAsyncTableImpl.getScanner(RawAsyncTableImpl.java:628)
at
org.apache.hadoop.hbase.client.RawAsyncTableImpl.getScanner(RawAsyncTableImpl.java:90)
at
org.apache.hadoop.hbase.client.TableOverAsyncTable.getScanner(TableOverAsyncTable.java:198)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv.doLoadIncrementalHFiles(IntegrationTestImportTsv.java:156)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv.generateAndLoad(IntegrationTestImportTsv.java:206)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv.testGenerateAndLoad(IntegrationTestImportTsv.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]
IntegrationTestImportTsv.testGenerateAndLoad:187->generateAndLoad:206->doLoadIncrementalHFiles:156
» UnsupportedOperation Unable to find suitable constructor for class
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv$2
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#82
[jira] [Created] (HBASE-28300) Refactor GarbageCollectorMXBean instantiation in process*.jsp
Nihal Jain created HBASE-28300: -- Summary: Refactor GarbageCollectorMXBean instantiation in process*.jsp Key: HBASE-28300 URL: https://issues.apache.org/jira/browse/HBASE-28300 Project: HBase Issue Type: Improvement Reporter: Nihal Jain Assignee: Nihal Jain During review of https://github.com/apache/hbase/pull/5215/ we saw that beans are instantiated based on assumptions around JVM, it is a good idea to refactor code so that we don't get errors when JVM assumptions change in future. Review comment: https://github.com/apache/hbase/pull/5215/files#r1318304462 CC: [~ndimiduk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28299) Set proper error in response for all usages of HttpServer.isInstrumentationAccessAllowed()
Nihal Jain created HBASE-28299: -- Summary: Set proper error in response for all usages of HttpServer.isInstrumentationAccessAllowed() Key: HBASE-28299 URL: https://issues.apache.org/jira/browse/HBASE-28299 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain During review https://github.com/apache/hbase/pull/5215, it was found we simply return 200 even if instrumentation is not allowed. While at some places we set proper error. This JIRA is to fix usages of the method and set proper response code. CC: [~ndimiduk] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28297) IntegrationTestImportTsv is broken
Nihal Jain created HBASE-28297:
--
Summary: IntegrationTestImportTsv is broken
Key: HBASE-28297
URL: https://issues.apache.org/jira/browse/HBASE-28297
Project: HBase
Issue Type: Bug
Components: integration tests, test
Reporter: Nihal Jain
Assignee: Nihal Jain
While trying to fix HBASE-28295, found issues in IntegrationTestImportTsv
{code:java}
INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
org.apache.hadoop.hbase.mapreduce.IntegrationTestFileBasedSFTBulkLoad
[INFO] Running org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
[INFO] Running org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
[INFO] Running org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.78 s
<<< FAILURE! - in org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
[ERROR] org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv Time
elapsed: 0.772 s <<< ERROR!
java.lang.ExceptionInInitializerError
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv$1.(IntegrationTestImportTsv.java:90)
at
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv.(IntegrationTestImportTsv.java:83)
... 20 more[ERROR]
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv Time elapsed: 0.772
s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.hadoop.hbase.mapreduce.IntegrationTestImportTsv
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(
[jira] [Reopened] (HBASE-28295) Few tests are failing due to NCDFE: org/bouncycastle/operator/OperatorCreationException
[ https://issues.apache.org/jira/browse/HBASE-28295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain reopened HBASE-28295: Earlier reported tests have passed but a new one is coming in latest nightly build. Not sure how this was not reported in last build though: [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/24/] [Test Result|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/24/testReport/] (2 failures / -4) * [health checks / yetus jdk11 hadoop3 checks / org.apache.hadoop.hbase.backup.TestBackupSmallTests.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/24/testReport/junit/org.apache.hadoop.hbase.backup/TestBackupSmallTests/health_checks___yetus_jdk11_hadoop3_checks__/] Reopening for an addendum fix! > Few tests are failing due to NCDFE: > org/bouncycastle/operator/OperatorCreationException > --- > > Key: HBASE-28295 > URL: https://issues.apache.org/jira/browse/HBASE-28295 > Project: HBase > Issue Type: Bug > Components: build, dependencies, hadoop3 >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Major > Fix For: 2.6.0, 3.0.0-beta-2 > > > See [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/] for > branch-2.6 > * [Test > Result|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/] > (6 failures / +4) > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk11_hadoop3_checks___testMRYarnConfigsPopulation/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.replication/TestVerifyReplicationCrossDiffHdfs/health_checks___yetus_jdk11_hadoop3_checks__/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.snapshot/TestMobSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/] > See [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/] for > branch-2 > * [Test > Result|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/] > (8 failures / +7) > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk11_hadoop3_checks___testMRYarnConfigsPopulation/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.replication/TestVerifyReplicationCrossDiffHdfs/health_checks___yetus_jdk11_hadoop3_checks__/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestMobSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/] > ** [health checks / yetus jdk11 hadoop3 checks / > org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/] > ** [health checks / yetus jdk8 hadoop3 checks / > org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk8_hadoop3_checks___testMRYarnConfigsPopulation/] > ** [health checks / yetus jdk8 hadoop3 checks / > org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branc
[jira] [Created] (HBASE-28295) Fews tests are failing due to NCDFE: org/bouncycastle/operator/OperatorCreationException
Nihal Jain created HBASE-28295:
--
Summary: Fews tests are failing due to NCDFE:
org/bouncycastle/operator/OperatorCreationException
Key: HBASE-28295
URL: https://issues.apache.org/jira/browse/HBASE-28295
Project: HBase
Issue Type: Improvement
Reporter: Nihal Jain
Assignee: Nihal Jain
Fix For: 2.6.0, 3.0.0-beta-2
See [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/] for
branch-2.6
* [Test
Result|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/]
(6 failures / +4)
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk11_hadoop3_checks___testMRYarnConfigsPopulation/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.replication/TestVerifyReplicationCrossDiffHdfs/health_checks___yetus_jdk11_hadoop3_checks__/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.snapshot/TestMobSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/23/testReport/junit/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/]
See [https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/] for
branch-2
* [Test
Result|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/]
(8 failures / +7)
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk11_hadoop3_checks___testMRYarnConfigsPopulation/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.replication/TestVerifyReplicationCrossDiffHdfs/health_checks___yetus_jdk11_hadoop3_checks__/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestMobSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/]
** [health checks / yetus jdk11 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/health_checks___yetus_jdk11_hadoop3_checks__/]
** [health checks / yetus jdk8 hadoop3 checks /
org.apache.hadoop.hbase.mapreduce.TestHBaseMRTestingUtility.testMRYarnConfigsPopulation|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.mapreduce/TestHBaseMRTestingUtility/health_checks___yetus_jdk8_hadoop3_checks___testMRYarnConfigsPopulation/]
** [health checks / yetus jdk8 hadoop3 checks /
org.apache.hadoop.hbase.replication.TestVerifyReplicationCrossDiffHdfs.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.replication/TestVerifyReplicationCrossDiffHdfs/health_checks___yetus_jdk8_hadoop3_checks__/]
** [health checks / yetus jdk8 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestMobSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestMobSecureExportSnapshot/health_checks___yetus_jdk8_hadoop3_checks__/]
** [health checks / yetus jdk8 hadoop3 checks /
org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.(?)|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/956/testReport/junit/org.apache.hadoop.hbase.snapshot/TestSecureExportSnapshot/health_checks___yetus_jdk8_hadoop3_checks__/]
Also fails locally for me for master.
{code:java}
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
org.apache.hadoop.hbase.repli
[jira] [Created] (HBASE-28275) Flaky test: Fix 'list decommissioned regionservers' in admin2_test.rb
Nihal Jain created HBASE-28275: -- Summary: Flaky test: Fix 'list decommissioned regionservers' in admin2_test.rb Key: HBASE-28275 URL: https://issues.apache.org/jira/browse/HBASE-28275 Project: HBase Issue Type: Bug Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28273) region_status.rb is broken
Nihal Jain created HBASE-28273:
--
Summary: region_status.rb is broken
Key: HBASE-28273
URL: https://issues.apache.org/jira/browse/HBASE-28273
Project: HBase
Issue Type: Sub-task
Affects Versions: 2.5.7, 3.0.0-alpha-4, 2.6.0
Reporter: Nihal Jain
Assignee: Nihal Jain
{{region_status.rb}} which is broken by all ends on all active branches.
Need to thoroughly fix it as it has multiple errors.
Not sure who uses it though as this is broken in branch-2 as well. We should
maybe deprecate and remove it.
CC: [~zhangduo]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28269) Ruby scripts are broken as they reference class which do not exit
Nihal Jain created HBASE-28269:
--
Summary: Ruby scripts are broken as they reference class which do
not exit
Key: HBASE-28269
URL: https://issues.apache.org/jira/browse/HBASE-28269
Project: HBase
Issue Type: Bug
Affects Versions: 3.0.0-alpha-4
Reporter: Nihal Jain
Assignee: Nihal Jain
Some of the ruby scripts are broken in 3.x as they are referencing non-existent
classes:
* {{org.apache.hadoop.hbase.client.HBaseAdmin}}
* {{org.apache.hadoop.hbase.HTableDescriptor}}
Following 4 scripts are failing:
{code:java}
NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
method_missing at org/jruby/javasupport/JavaPackage.java:253
at region_status.rb:50
{code}
{code:java}
{NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
method_missing at org/jruby/javasupport/JavaPackage.java:253
at replication/copy_tables_desc.rb:30
{code}
{code:java}
NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
method_missing at org/jruby/javasupport/JavaPackage.java:253
at draining_servers.rb:28
{code}
{code:java}
NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
method_missing at org/jruby/javasupport/JavaPackage.java:253
at shutdown_regionserver.rb:27
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28250) Bump jruby to 9.4.5.0 and related joni and jcodings
Nihal Jain created HBASE-28250: -- Summary: Bump jruby to 9.4.5.0 and related joni and jcodings Key: HBASE-28250 URL: https://issues.apache.org/jira/browse/HBASE-28250 Project: HBase Issue Type: Task Reporter: Nihal Jain Assignee: Nihal Jain Given branch-2 including branch-2.6 is already on 9.3.9.0, we should bump to at least 9.3.13.0. This will fix the bundled *org.bouncycastle : bcprov-jdk18on : 1.71* having [CVE-2023-33201|https://nvd.nist.gov/vuln/detail/CVE-2023-33201] from out classpath for the least. As a follow up can try to bump to latest 9.4.x line, if others are fine with this. Please let me know what others think. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28249) Bump jruby to 9.3.13.0 and related joni and jcodings to 2.2.1 and 1.0.58 respectively
Nihal Jain created HBASE-28249: -- Summary: Bump jruby to 9.3.13.0 and related joni and jcodings to 2.2.1 and 1.0.58 respectively Key: HBASE-28249 URL: https://issues.apache.org/jira/browse/HBASE-28249 Project: HBase Issue Type: Task Reporter: Nihal Jain Assignee: Nihal Jain Given branch-2 including is already on 9.3.9.0, we should bump to atleast 9.3.13.0. This will fix the bundled *org.bouncycastle : bcprov-jdk18on : 1.71* having CVE-2023-33201 from out classpath for the least. As a follow up can try to bump to latest 9.4.x line, if others are fine with this. Please let me know what others think. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28245) Sync internal protobuf version for hbase to be same as hbase-thirdparty
Nihal Jain created HBASE-28245: -- Summary: Sync internal protobuf version for hbase to be same as hbase-thirdparty Key: HBASE-28245 URL: https://issues.apache.org/jira/browse/HBASE-28245 Project: HBase Issue Type: Task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28243) Bump jackson version to 2.15.2
Nihal Jain created HBASE-28243: -- Summary: Bump jackson version to 2.15.2 Key: HBASE-28243 URL: https://issues.apache.org/jira/browse/HBASE-28243 Project: HBase Issue Type: Improvement Reporter: Nihal Jain Assignee: Nihal Jain We should bump jackson to 2.15.2 as it is already move to this in hbase-thirdparty in HBASE-28093 Also 2.14.1 has [sonatype-2022-6438.|https://github.com/FasterXML/jackson-core/issues/861] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28173) Make use of assertThrows in TestShadeSaslAuthenticationProvider
Nihal Jain created HBASE-28173: -- Summary: Make use of assertThrows in TestShadeSaslAuthenticationProvider Key: HBASE-28173 URL: https://issues.apache.org/jira/browse/HBASE-28173 Project: HBase Issue Type: Task Components: security, test Reporter: Duo Zhang Assignee: Nihal Jain The testNegativeAuthentication method is completely different between master/branch-3 and branch-2.x, we should try to align the test for these branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28160) Build fails with Hadoop 3.3.5 and higher
[
https://issues.apache.org/jira/browse/HBASE-28160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-28160.
Resolution: Duplicate
Hi [~larsfrancke] this looks like a duplicate issue and has already been fixed
with HBASE-27860. This fix was released as part of 2.4.18.
Also the master failure I could not reproduce: Did you run with
{{-Dhadoop.profile=3.0}} by any chance? Could you try running below for master:
{code:java}
mvn clean install -DskipTests -Phadoop-3.0 -Dhadoop-three.version=3.3.5
{code}
Feel free to create another JIRA if {{(Found Banned Dependency:
org.bouncycastle:bcprov-jdk15on:jar:1.52)}} is still thrown.
> Build fails with Hadoop 3.3.5 and higher
>
>
> Key: HBASE-28160
> URL: https://issues.apache.org/jira/browse/HBASE-28160
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.4.17
>Reporter: Lars Francke
>Priority: Minor
>
> https://issues.apache.org/jira/browse/HADOOP-15983 changed dependencies and
> that makes our {{check-jar-contents-for-stuff-with-hadoop}} check fail:
> Excerpt:
> {noformat}
> [INFO] --- exec-maven-plugin:1.6.0:exec
> (check-jar-contents-for-stuff-with-hadoop) @
> hbase-shaded-with-hadoop-check-invariants ---
> [ERROR] Found artifact with unexpected contents:
> '/home/lars/Downloads/hbase/hbase-2.4.17-src/hbase-shaded/hbase-shaded-client/target/hbase-shaded-client-2.4.17.jar'
> Please check the following and either correct the build or update
> the allowed list with reasoning.
> com/
> com/sun/
> com/sun/jersey/
> com/sun/jersey/json/
> com/sun/jersey/json/impl/
> com/sun/jersey/json/impl/reader/
> com/sun/jersey/json/impl/reader/JsonXmlEvent$Attribute.class
> com/sun/jersey/json/impl/reader/JsonXmlStreamReader$1.class
> com/sun/jersey/json/impl/reader/XmlEventProvider$1.class
> com/sun/jersey/json/impl/reader/NaturalNotationEventProvider.class
> com/sun/jersey/json/impl/reader/XmlEventProvider.class
> com/sun/jersey/json/impl/reader/XmlEventProvider$ProcessingInfo.class
> com/sun/jersey/json/impl/reader/StartElementEvent.class
> com/sun/jersey/json/impl/reader/CharactersEvent.class
> com/sun/jersey/json/impl/reader/JacksonRootAddingParser$1.class
> com/sun/jersey/json/impl/reader/EndElementEvent.class
> com/sun/jersey/json/impl/reader/JsonXmlStreamReader.class
> com/sun/jersey/json/impl/reader/StaxLocation.class
> com/sun/jersey/json/impl/reader/JsonNamespaceContext.class
> com/sun/jersey/json/impl/reader/JsonXmlEvent.class
> com/sun/jersey/json/impl/reader/JacksonRootAddingParser.class
> com/sun/jersey/json/impl/reader/StartDocumentEvent.class
> com/sun/jersey/json/impl/reader/MappedNotationEventProvider.class
> com/sun/jersey/json/impl/reader/EndDocumentEvent.class
> com/sun/jersey/json/impl/reader/JsonFormatException.class
> com/sun/jersey/json/impl/reader/XmlEventProvider$CachedJsonParser.class
> com/sun/jersey/json/impl/reader/JacksonRootAddingParser$State.class
> com/sun/jersey/json/impl/JaxbRiXmlStructure.class
> com/sun/jersey/json/impl/ImplMessages.class
> com/sun/jersey/json/impl/JSONMarshallerImpl.class
> com/sun/jersey/json/impl/NameUtil.class
> com/sun/jersey/json/impl/FilteringInputStream.class
> com/sun/jersey/json/impl/JaxbProvider.class
> []
> {noformat}
> I'm afraid I'm a bit at a loss with the current Maven build system as to what
> the actual fix would be.
> I tested it against 2.4.17 as well as master as of today. Master already
> fails in an earlier step ({{Found Banned Dependency:
> org.bouncycastle:bcprov-jdk15on:jar:1.52}}) which I assume is a separate
> issue but I further assume that it would also fail at this step if it were to
> get this far.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28106) TestShadeSaslAuthenticationProvider fails for branch-2.5 and branch-2.4
Nihal Jain created HBASE-28106: -- Summary: TestShadeSaslAuthenticationProvider fails for branch-2.5 and branch-2.4 Key: HBASE-28106 URL: https://issues.apache.org/jira/browse/HBASE-28106 Project: HBase Issue Type: Bug Reporter: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28102) [hbase-thirdparty] Bump hbase.stable.version to 2.5.5 in hbase-noop-htrace
Nihal Jain created HBASE-28102: -- Summary: [hbase-thirdparty] Bump hbase.stable.version to 2.5.5 in hbase-noop-htrace Key: HBASE-28102 URL: https://issues.apache.org/jira/browse/HBASE-28102 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28089) Upgrade BouncyCastle to fix CVE-2023-33201
Nihal Jain created HBASE-28089:
--
Summary: Upgrade BouncyCastle to fix CVE-2023-33201
Key: HBASE-28089
URL: https://issues.apache.org/jira/browse/HBASE-28089
Project: HBase
Issue Type: Task
Reporter: Nihal Jain
Assignee: Nihal Jain
HBase has a dependency on BouncyCastle 1.70 which is vulnerable with
[CVE-2023-33201|https://nvd.nist.gov/vuln/detail/CVE-2023-33201]
Advisory: [https://github.com/bcgit/bc-java/wiki/CVE-2023-33201]
This JIRA's goal is to fix the following:
* Upgrade to v1.76, the latest version.
** This requires bcprov-jdk15on to be replaced with bcprov-jdk18on
** See [https://www.bouncycastle.org/latest_releases.html]
***
{quote}*Java Version Details* With the arrival of Java 15. jdk15 is not quite
as unambiguous as it was. The *jdk18on* jars are compiled to work with
*anything* from Java 1.8 up. They are also multi-release jars so do support
some features that were introduced in Java 9, Java 11, and Java 15. If you have
issues with multi-release jars see the jdk15to18 release jars below.
*Packaging Change (users of 1.70 or earlier):* BC 1.71 changed the jdk15on jars
to jdk18on so the base has now moved to Java 8. For earlier JVMs, or
containers/applications that cannot cope with multi-release jars, you should
now use the jdk15to18 jars.
{quote}
* Exclude bcprov-jdk15on from everywhere else to avoid conflicts with
bcprov-jdk18on
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28066) Move TestShellRSGroups.java inside /src/test/java
Nihal Jain created HBASE-28066:
--
Summary: Move TestShellRSGroups.java inside /src/test/java
Key: HBASE-28066
URL: https://issues.apache.org/jira/browse/HBASE-28066
Project: HBase
Issue Type: Test
Reporter: Nihal Jain
Assignee: Nihal Jain
Just noticed that {{TestShellRSGroups.java}} is at
{{hbase-shell/src/test/rsgroup/org/apache/hadoop/hbase/client/rsgroup/TestShellRSGroups.java,}}
but ideally it should be at
{{hbase-shell/src/test/java/org/apache/hadoop/hbase/client/rsgroup/TestShellRSGroups.java}}
instead.
Also because of same misplacement spotless skipped this file. Also need to run
spotless for the same.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-27976) [hbase-operator-tools] Add spotless for hbase-operator-tools
[ https://issues.apache.org/jira/browse/HBASE-27976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-27976. Fix Version/s: hbase-operator-tools-1.3.0 Release Note: Before creating a PR for hbase-operator-tools repo, developers can now run 'mvn spotless:apply' to fix code formatting issues . Resolution: Fixed All the sub-tasks are done, marking the Jira as resolved. > [hbase-operator-tools] Add spotless for hbase-operator-tools > > > Key: HBASE-27976 > URL: https://issues.apache.org/jira/browse/HBASE-27976 > Project: HBase > Issue Type: Umbrella > Components: build, hbase-operator-tools >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Major > Fix For: hbase-operator-tools-1.3.0 > > > HBase code repo has spotless plugin to check and fix spotless issues > seamlessly, making it easier for developers to fix issue in case the builds > fails due to code formatting. > The goal of this Jira is to integrate spotless with hbase-operator-tools. > * As a 1st step will try to add a plugin to run spotless check via maven > * Next will fix all spotless issues as part of same task or another (as > community suggests) > * Finally will integrate the same to pre-commit build to not let PRs wit > spotless issues get in. (Would need some support/direction on how to do this > as I am not much familiar with the Jenkins and related code.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28057) [hbase-operator-tools] Run spotless:apply and fix any existing spotless issues
Nihal Jain created HBASE-28057: -- Summary: [hbase-operator-tools] Run spotless:apply and fix any existing spotless issues Key: HBASE-28057 URL: https://issues.apache.org/jira/browse/HBASE-28057 Project: HBase Issue Type: Sub-task Components: build, hbase-operator-tools Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28054) [hbase-connectors] Add spotless in hbase-connectors pre commit build
Nihal Jain created HBASE-28054: -- Summary: [hbase-connectors] Add spotless in hbase-connectors pre commit build Key: HBASE-28054 URL: https://issues.apache.org/jira/browse/HBASE-28054 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28035) ConnectionFactory.createConnection does not work with anything except ThreadPoolExecutor
Nihal Jain created HBASE-28035: -- Summary: ConnectionFactory.createConnection does not work with anything except ThreadPoolExecutor Key: HBASE-28035 URL: https://issues.apache.org/jira/browse/HBASE-28035 Project: HBase Issue Type: Bug Reporter: Nihal Jain This looks like a regression where org.apache.hadoop.hbase.client.ConnectionFactory#createConnection(org.apache.hadoop.conf.Configuration, java.util.concurrent.ExecutorService) even though supports `ExecutorService` (but since HBASE-22244), has stopped working for `ForkJoinPool` and throws `java.lang.ClassCastException: java.util.concurrent.ForkJoinPool cannot be cast to java.util.concurrent.ThreadPoolExecutor` I have been able to write a UT to verify the same and ran it on a branch not having above change i.e. branch-2.1 where the test passes while for branch-2, having this change, the test fails. Also it worth noting that the issue does not exist in master, i think its because of HBASE-21723 which removes `ConnectionImplementation` from master. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28034) Rewrite hbck2 documentation using ChatGPT
Nihal Jain created HBASE-28034:
--
Summary: Rewrite hbck2 documentation using ChatGPT
Key: HBASE-28034
URL: https://issues.apache.org/jira/browse/HBASE-28034
Project: HBase
Issue Type: Improvement
Reporter: Nihal Jain
Assignee: Nihal Jain
Just a thought, could we re-write the operator tools
[README.md|https://github.com/apache/hbase-operator-tools/blob/master/README.md]
using ChatGPT and make it better?
A sample paragraph re-written by ChatGPT is as follows:
Original:
{quote}
h3. Some General Principals
When making repair, make sure hbase:meta is consistent first before you go
about fixing any other issue type such as a filesystem deviance. Deviance in
the filesystem or problems with assign should be addressed after the hbase:meta
has been put in order. If hbase:meta is out of whack, the Master cannot make
proper placements when adopting orphan filesystem data or making region
assignments.
Other general principles to keep in mind include a Region can not be assigned
if it is in _CLOSING_ state (or the inverse, unassigned if in _OPENING_ state)
without first transitioning via {_}CLOSED{_}: Regions must always move from
{_}CLOSED{_}, to {_}OPENING{_}, to {_}OPEN{_}, and then to {_}CLOSING{_},
{_}CLOSED{_}.
When making repair, do fixup of a table-at-a-time.
Also, if a table is {_}DISABLED{_}, you cannot assign a Region. In the Master
logs, you will see that the Master will report that the assign has been skipped
because the table is {_}DISABLED{_}. You may want to assign a Region because it
is currently in the _OPENING_ state and you want it in the _CLOSED_ state so it
agrees with the table's _DISABLED_ state. In this situation, you may have to
temporarily set the table status to {_}ENABLED{_}, just so you can do the
assign, and then set it back again after the unassign. _HBCK2_ has facility to
allow you do this. See the _HBCK2_ usage output.
What follows is a mix of notes and prescription that comes of experience
running hbase-2.x so far. The root issues that brought on states described
below has been fixed in later versions of hbase so upgrade if you can so as to
avoid scenarios described.
{quote}
Rephrased:
{quote}*Some Basic Principles*
Ensure hbase:meta's consistency before attempting to fix any other type of
problem, such as filesystem deviations. Issues related to filesystem or
assignment should be addressed once hbase:meta is sorted out. If hbase:meta is
awry, the Master cannot accurately allocate orphan filesystem data or region
assignments.
Remember that a Region cannot be assigned if it is in a CLOSING state (or
conversely, unassigned if in an OPENING state) without going through a CLOSED
state first. Regions must always progress from CLOSED, to OPENING, to OPEN, to
CLOSING, and then back to CLOSED.
Make repairs table-by-table.
Additionally, if a table is DISABLED, you cannot assign a Region. The Master
logs will indicate that the assignment has been bypassed due to the table's
DISABLED status. You might want to assign a Region because it is currently in
the OPENING state, but you want it in the CLOSED state to match the DISABLED
state of the table. In such cases, you might need to briefly change the table
status to ENABLED to make the assignment, then switch it back after the
unassignment. HBCK2 provides a facility for this. Please refer to the HBCK2
usage output.
The following notes and instructions come from the experience of running
hbase-2.x so far. The underlying issues causing the states described below have
been resolved in later versions of hbase, so upgrading is recommended to avoid
these scenarios.
{quote}
Is this worth the effort? Or do others feel current doc is good and does not
need any refinement?
It may require some effort, as we may only start with first commit with
untouched document generated by ChatGPT, but then the draft would need to be
worked upon, based on some proofreading by the contributor and reviewers.
Curious to know how others feel.
Also, Apache has some guidelines around using of generative ai tools at
[https://www.apache.org/legal/generative-tooling.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28032) Fix ChaosMonkey documentation code block rendering
Nihal Jain created HBASE-28032: -- Summary: Fix ChaosMonkey documentation code block rendering Key: HBASE-28032 URL: https://issues.apache.org/jira/browse/HBASE-28032 Project: HBase Issue Type: Task Components: documentation Reporter: Nihal Jain Assignee: Nihal Jain The code blocks in document for ChaosMonkey isnot rendered correctly. Fix them and also add few more example. See [https://hbase.apache.org/book.html#_chaosmonkey_without_ssh] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28026) DefaultMetricsSystemInitializer should be called during HMaster or HRegionServer creation
Nihal Jain created HBASE-28026: -- Summary: DefaultMetricsSystemInitializer should be called during HMaster or HRegionServer creation Key: HBASE-28026 URL: https://issues.apache.org/jira/browse/HBASE-28026 Project: HBase Issue Type: Bug Components: metrics Reporter: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28007) [hbase-connectors] Manually fix javadoc messed due to spotless
Nihal Jain created HBASE-28007: -- Summary: [hbase-connectors] Manually fix javadoc messed due to spotless Key: HBASE-28007 URL: https://issues.apache.org/jira/browse/HBASE-28007 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28006) [hbase-connectors] Run spotless:apply on code base
Nihal Jain created HBASE-28006: -- Summary: [hbase-connectors] Run spotless:apply on code base Key: HBASE-28006 URL: https://issues.apache.org/jira/browse/HBASE-28006 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27980) Sync the hbck2 README page with hbck2 command help output
Nihal Jain created HBASE-27980:
--
Summary: Sync the hbck2 README page with hbck2 command help output
Key: HBASE-27980
URL: https://issues.apache.org/jira/browse/HBASE-27980
Project: HBase
Issue Type: Task
Components: hbase-operator-tools, hbck2
Reporter: Nihal Jain
Assignee: Nihal Jain
There are major differences in the hbck2
[README.md|https://github.com/apache/hbase-operator-tools/blob/master/hbase-hbck2/README.md]
and the command help output, hence we should sync them across all command.
It should be same as the output of hbck2 help command for ease of maintenance.
Also few new commands like {{recoverUnknown}} and {{regionInfoMismatch}} are
missing, making users unaware of existence of those.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-27906) Fix the javadoc for SyncFutureCache
[
https://issues.apache.org/jira/browse/HBASE-27906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-27906.
Fix Version/s: 4.0.0-alpha-1
Hadoop Flags: Reviewed
Resolution: Fixed
Thanks for your first contribution [~dimitrios.efthymiou]. The PR has been
merged to codebase.
> Fix the javadoc for SyncFutureCache
> ---
>
> Key: HBASE-27906
> URL: https://issues.apache.org/jira/browse/HBASE-27906
> Project: HBase
> Issue Type: Improvement
> Components: documentation
>Reporter: Duo Zhang
>Assignee: Dimitrios Efthymiou
>Priority: Minor
> Fix For: 4.0.0-alpha-1
>
>
> It does not have any html markers so spotless messed it up...
> We should add html markers so it could keep the format after 'spotless:apply'
> {code}
> /**
> * A cache of {@link SyncFuture}s. This class supports two methods
> * {@link SyncFutureCache#getIfPresentOrNew()} and {@link
> SyncFutureCache#offer()}.
> *
> * Usage pattern:
> *
> *
> * SyncFuture sf = syncFutureCache.getIfPresentOrNew();
> * sf.reset(...);
> * // Use the sync future
> * finally: syncFutureCache.offer(sf);
> *
> *
> * Offering the sync future back to the cache makes it eligible for reuse
> within the same thread
> * context. Cache keyed by the accessing thread instance and automatically
> invalidated if it remains
> * unused for {@link SyncFutureCache#SYNC_FUTURE_INVALIDATION_TIMEOUT_MINS}
> minutes.
> */
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27978) [hbase-operator-tools] Add spotless in hbase-operator-tools pre-commit build
Nihal Jain created HBASE-27978: -- Summary: [hbase-operator-tools] Add spotless in hbase-operator-tools pre-commit build Key: HBASE-27978 URL: https://issues.apache.org/jira/browse/HBASE-27978 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27977) [hbase-operator-tools] Add spotless plugin to hbase-operator-tools pom
Nihal Jain created HBASE-27977: -- Summary: [hbase-operator-tools] Add spotless plugin to hbase-operator-tools pom Key: HBASE-27977 URL: https://issues.apache.org/jira/browse/HBASE-27977 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27976) [hbase-operator-tools] Add spotless for hbase-operator-tools
Nihal Jain created HBASE-27976: -- Summary: [hbase-operator-tools] Add spotless for hbase-operator-tools Key: HBASE-27976 URL: https://issues.apache.org/jira/browse/HBASE-27976 Project: HBase Issue Type: Task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27966) HBase Master/RS JVM metrics populated incorrectly
Nihal Jain created HBASE-27966:
--
Summary: HBase Master/RS JVM metrics populated incorrectly
Key: HBASE-27966
URL: https://issues.apache.org/jira/browse/HBASE-27966
Project: HBase
Issue Type: Bug
Components: metrics
Affects Versions: 2.0.0-alpha-4
Reporter: Nihal Jain
Assignee: Nihal Jain
HBase Master/RS JVM metrics populated incorrectly due to regression causing
ambari metrics system to not able to capture them.
Based on my analysis the issue is relevant for all release post 2.0.0-alpha-4
and seems to be caused due to HBASE-18846.
Have been able to compare the JVM metrics across 3 versions of HBase and
attaching results of same below:
HBase: 1.1.2
{code:java}
{
"name" : "Hadoop:service=HBase,name=JvmMetrics",
"modelerType" : "JvmMetrics",
"tag.Context" : "jvm",
"tag.ProcessName" : "RegionServer",
"tag.SessionId" : "",
"tag.Hostname" : "HOSTNAME",
"MemNonHeapUsedM" : 196.05664,
"MemNonHeapCommittedM" : 347.60547,
"MemNonHeapMaxM" : 4336.0,
"MemHeapUsedM" : 7207.315,
"MemHeapCommittedM" : 66080.0,
"MemHeapMaxM" : 66080.0,
"MemMaxM" : 66080.0,
"GcCount" : 3953,
"GcTimeMillis" : 662520,
"ThreadsNew" : 0,
"ThreadsRunnable" : 214,
"ThreadsBlocked" : 0,
"ThreadsWaiting" : 626,
"ThreadsTimedWaiting" : 78,
"ThreadsTerminated" : 0,
"LogFatal" : 0,
"LogError" : 0,
"LogWarn" : 0,
"LogInfo" : 0
},
{code}
HBase 2.0.2
{code:java}
{
"name" : "Hadoop:service=HBase,name=JvmMetrics",
"modelerType" : "JvmMetrics",
"tag.Context" : "jvm",
"tag.ProcessName" : "IO",
"tag.SessionId" : "",
"tag.Hostname" : "HOSTNAME",
"MemNonHeapUsedM" : 203.86688,
"MemNonHeapCommittedM" : 740.6953,
"MemNonHeapMaxM" : -1.0,
"MemHeapUsedM" : 14879.477,
"MemHeapCommittedM" : 31744.0,
"MemHeapMaxM" : 31744.0,
"MemMaxM" : 31744.0,
"GcCount" : 75922,
"GcTimeMillis" : 5134691,
"ThreadsNew" : 0,
"ThreadsRunnable" : 90,
"ThreadsBlocked" : 3,
"ThreadsWaiting" : 158,
"ThreadsTimedWaiting" : 36,
"ThreadsTerminated" : 0,
"LogFatal" : 0,
"LogError" : 0,
"LogWarn" : 0,
"LogInfo" : 0
},
{code}
HBase: 2.5.2
{code:java}
{
"name": "Hadoop:service=HBase,name=JvmMetrics",
"modelerType": "JvmMetrics",
"tag.Context": "jvm",
"tag.ProcessName": "IO",
"tag.SessionId": "",
"tag.Hostname": "HOSTNAME",
"MemNonHeapUsedM": 192.9798,
"MemNonHeapCommittedM": 198.4375,
"MemNonHeapMaxM": -1.0,
"MemHeapUsedM": 773.23584,
"MemHeapCommittedM": 1004.0,
"MemHeapMaxM": 1024.0,
"MemMaxM": 1024.0,
"GcCount": 2048,
"GcTimeMillis": 25440,
"ThreadsNew": 0,
"ThreadsRunnable": 22,
"ThreadsBlocked": 0,
"ThreadsWaiting": 121,
"ThreadsTimedWaiting": 49,
"ThreadsTerminated": 0,
"LogFatal": 0,
"LogError": 0,
"LogWarn": 0,
"LogInfo": 0
},
{code}
It can be observed that 2.0.x onwards the field "tag.ProcessName" is populating
as "IO" instead of expected "RegionServer" or "Master".
Ambari relies on this field process name to create a metric
'jvm.RegionServer.JvmMetrics.GcTimeMillis' etc. See
[code.|https://github.com/apache/ambari/blob/2ec4b055d99ec84c902da16dd57df91d571b48d6/ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java#L722]
But post 2.0.x the field is getting populated as 'IO' and hence a metric with
name 'jvm.JvmMetrics.GcTimeMillis' is created instead of expected
'jvm.RegionServer.JvmMetrics.GcTimeMillis', thus mixing up the metric with
various other metrics coming from rs, master, spark executor etc. running on
same host.
*Expected*
Field "tag.ProcessName" should be populated as "RegionServer" or "Master"
instead of "IO".
*Actual*
Field "tag.ProcessName" is populating as "IO" instead of expected
"RegionServer" or "Master" causing incorrect metric being published by ambari
and thus mixing up all metrics and raising various alerts around JVM metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27961) [HBCK2] Running assigns/unassigns command with large number of files/regions throws CallTimeoutException
Nihal Jain created HBASE-27961: -- Summary: [HBCK2] Running assigns/unassigns command with large number of files/regions throws CallTimeoutException Key: HBASE-27961 URL: https://issues.apache.org/jira/browse/HBASE-27961 Project: HBase Issue Type: Bug Components: hbck2 Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27811) Enable cache control for logs endpoint and set max age as 0
[ https://issues.apache.org/jira/browse/HBASE-27811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-27811. Fix Version/s: 3.0.0-alpha-4 Hadoop Flags: Reviewed Resolution: Fixed Will reopen, if back port jira is raised. > Enable cache control for logs endpoint and set max age as 0 > --- > > Key: HBASE-27811 > URL: https://issues.apache.org/jira/browse/HBASE-27811 > Project: HBase > Issue Type: Improvement >Reporter: Yash Dodeja >Assignee: Yash Dodeja >Priority: Minor > Fix For: 3.0.0-alpha-4 > > > Not setting the proper header values may cause browsers to store pages within > their respective caches. On public, shared, or any other non-private > computers, a malicious person may search through the browser cache to locate > sensitive information cached during another user's session. > /logs endpoint contains sensitive information that an attacker can exploit. > Any page with sensitive information needs to have the following headers in > response: > Cache-Control: no-cache, no-store, max-age=0 > Pragma: no-cache > Expires: -1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27815) Add support for process metrics servlet in REST InfoServer
[ https://issues.apache.org/jira/browse/HBASE-27815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain resolved HBASE-27815. Resolution: Duplicate > Add support for process metrics servlet in REST InfoServer > -- > > Key: HBASE-27815 > URL: https://issues.apache.org/jira/browse/HBASE-27815 > Project: HBase > Issue Type: Sub-task > Components: REST >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Minor > > Unlike other HBase Master/RS Info Servers, REST Server UI does not provide a > way to get process metrics like threads, gc collectors etc. This task is add > same in HBase REST. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27815) Add support for process metrics servlet in REST InfoServer
Nihal Jain created HBASE-27815: -- Summary: Add support for process metrics servlet in REST InfoServer Key: HBASE-27815 URL: https://issues.apache.org/jira/browse/HBASE-27815 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27816) Support option to auto bind to an available port for REST Info Server
Nihal Jain created HBASE-27816: -- Summary: Support option to auto bind to an available port for REST Info Server Key: HBASE-27816 URL: https://issues.apache.org/jira/browse/HBASE-27816 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27814) Add support for dump servlet in REST InfoServer
Nihal Jain created HBASE-27814: -- Summary: Add support for dump servlet in REST InfoServer Key: HBASE-27814 URL: https://issues.apache.org/jira/browse/HBASE-27814 Project: HBase Issue Type: Sub-task Reporter: Nihal Jain Assignee: Nihal Jain -- This message was sent by Atlassian Jira (v8.20.10#820010)
