[jira] [Resolved] (HBASE-25246) Backup/Restore hbase cell tags.
[ https://issues.apache.org/jira/browse/HBASE-25246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-25246. -- Resolution: Fixed Thanks for the contribution [~shahrs87]. > Backup/Restore hbase cell tags. > --- > > Key: HBASE-25246 > URL: https://issues.apache.org/jira/browse/HBASE-25246 > Project: HBase > Issue Type: Improvement > Components: backup&restore >Reporter: Rushabh Shah >Assignee: Rushabh Shah >Priority: Major > Fix For: 3.0.0-alpha-1, 1.7.0, 2.2.7, 2.3.4, 2.5.0, 2.4.1 > > > In PHOENIX-6213 we are planning to add cell tags for Delete mutations. After > having a discussion with hbase community via dev mailing thread, it was > decided that we will pass the tags via an attribute in Mutation object and > persist them to hbase via phoenix co-processor. The intention of PHOENIX-6213 > is to store metadata in Delete marker so that while running Restore tool we > can selectively restore certain Delete markers and ignore others. For that to > happen we need to persist these tags in Backup and retrieve them in Restore > MR jobs (Import/Export tool). > Currently we don't persist the tags in Backup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Move the stable pointer to 2.3.x and EOM for branch-2.2?
Cool, Thanks Stack :) On Thu, 17 Dec 2020 at 3:53 AM, Stack wrote: > On Tue, Dec 15, 2020 at 9:14 PM Viraj Jasani wrote: > > > I believe last time when we discussed this, we were considering stability > > of migration from MasterProcWAL to MasterProc directory (WAL to region > > based procedure store) during rolling upgrade from 2.2.x to 2.3.x. I hope > > we are good with this. > > > > > Seem to work smoothly, at least in my experience Viraj. > S > > > > > > > On Wed, 16 Dec 2020 at 10:27 AM, Viraj Jasani > wrote: > > > > > +1 > > > > > > On Wed, 16 Dec 2020 at 6:38 AM, Guanghao Zhang > > wrote: > > > > > >> Hi folks! > > >> > > >> Now we cut new branch-2.4 and the 2.4.0 will be released. We can EOM > for > > >> branch-2.2 to reduce the maintenance work. Meanwhile, I thought > > branch-2.3 > > >> is more stable than branch-2.2 because you guys take great test work > > when > > >> release 2.3.0. And for branch-2.2, the 2.2.7 may be the last of the > > 2.2.x > > >> releases. > > >> > > >> Any thoughts? > > >> > > > > > >
Re: [DISCUSS] Move the stable pointer to 2.3.x and EOM for branch-2.2?
On Tue, Dec 15, 2020 at 9:14 PM Viraj Jasani wrote: > I believe last time when we discussed this, we were considering stability > of migration from MasterProcWAL to MasterProc directory (WAL to region > based procedure store) during rolling upgrade from 2.2.x to 2.3.x. I hope > we are good with this. > > Seem to work smoothly, at least in my experience Viraj. S > > On Wed, 16 Dec 2020 at 10:27 AM, Viraj Jasani wrote: > > > +1 > > > > On Wed, 16 Dec 2020 at 6:38 AM, Guanghao Zhang > wrote: > > > >> Hi folks! > >> > >> Now we cut new branch-2.4 and the 2.4.0 will be released. We can EOM for > >> branch-2.2 to reduce the maintenance work. Meanwhile, I thought > branch-2.3 > >> is more stable than branch-2.2 because you guys take great test work > when > >> release 2.3.0. And for branch-2.2, the 2.2.7 may be the last of the > 2.2.x > >> releases. > >> > >> Any thoughts? > >> > > >
[jira] [Created] (HBASE-25406) [Flakey Tests] branch-2 TestShadedHBaseTestingUtility
Michael Stack created HBASE-25406:
-
Summary: [Flakey Tests] branch-2 TestShadedHBaseTestingUtility
Key: HBASE-25406
URL: https://issues.apache.org/jira/browse/HBASE-25406
Project: HBase
Issue Type: Bug
Components: flakies
Reporter: Michael Stack
Odd. TestShadedHBaseTestingUtility fails reliably if run with lots of
concurrency; when I run on its own, its fine. Failure says:
{code}
java.io.IOException: Shutting down
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
Caused by: java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasterMultiple exceptions
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
Caused by: java.io.IOException: Problem starting http server
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
Caused by: org.apache.hbase.thirdparty.org.eclipse.jetty.util.MultiException:
Multiple exceptions
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
Caused by: java.lang.NoSuchMethodError:
javax.servlet.ServletContext.createFilter(Ljava/lang/Class;)Ljavax/servlet/Filter;
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
{code}
In test run log, I see this kinda stuff:
{code}
2020-12-16 13:14:57,649 INFO [Listener at localhost/52473] http.HttpServer
(HttpServer.java:openListeners(1137)) - Jetty bound to port 52491
2020-12-16 13:14:57,654 INFO [Listener at localhost/52473] server.Server
(Server.java:doStart(375)) - jetty-9.4.34.v20201102; built:
2020-11-02T14:15:39.302Z; git: e46af88704a893fc12cb0e3bf46e2c7b48a009e7; jvm
1.8.0_102-b14
2020-12-16 13:14:57,765 INFO [Listener at localhost/52473] http.HttpServer
(HttpServer.java:start(1083)) - HttpServer.start() threw a MultiException
MultiException[java.lang.NoSuchMethodError:
javax.servlet.ServletContext.createFilter(Ljava/lang/Class;)Ljavax/servlet/Filter;,
java.lang.NoSuchMethodError:
javax.servlet.ServletContext.createFilter(Ljava/lang/Class;)Ljavax/
servlet/Filter;, java.lang.NoSuchMethodError:
javax.servlet.ServletContext.createFilter(Ljava/lang/Class;)Ljavax/servlet/Filter;,
java.lang.NoSuchMethodError:
javax.servlet.ServletContext.createFilter(Ljava/lang/Class;)Ljavax/
servlet/Filter;]
at
org.apache.hbase.thirdparty.org.eclipse.jetty.util.MultiException.ifExceptionThrow(MultiException.java:122)
at
org.apache.hbase.thirdparty.org.eclipse.jetty.server.Server.doStart(Server.java:413)
at
org.apache.hbase.thirdparty.org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at org.apache.hadoop.hbase.http.HttpServer.start(HttpServer.java:1078)
at org.apache.hadoop.hbase.http.InfoServer.start(InfoServer.java:150)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.putUpWebUI(HRegionServer.java:2200)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:687)
at org.apache.hadoop.hbase.master.HMaster.(HMaster.java:414)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:132)
at
org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:239)
at
org.apache.hadoop.hbase.LocalHBaseCluster.(LocalHBaseCluster.java:181)
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:245)
at org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:115)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1177)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1140)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1104)
at
org.apache.hbase.shaded.TestShadedHBaseTestingUtility.setUp(TestShadedHBaseTestingUtility.java:47)
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.invokeExplos
[jira] [Created] (HBASE-25405) Backport HBASE-25287 to branch-1
Wei-Chiu Chuang created HBASE-25405: --- Summary: Backport HBASE-25287 to branch-1 Key: HBASE-25405 URL: https://issues.apache.org/jira/browse/HBASE-25405 Project: HBase Issue Type: Sub-task Reporter: Wei-Chiu Chuang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25334) TestRSGroupsFallback.testFallback is flaky
[ https://issues.apache.org/jira/browse/HBASE-25334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HBASE-25334. --- Fix Version/s: 2.4.1 2.5.0 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed branch-2 PR to branch-2.4 and branch-2 (Another PR had already been applied to master). Resolving after testing locally against branch-2. This patch seems to have cured the failure I've been seeing running unit tests locally. Thanks [~Xiaolin Ha] for the gnarly fix. > TestRSGroupsFallback.testFallback is flaky > -- > > Key: HBASE-25334 > URL: https://issues.apache.org/jira/browse/HBASE-25334 > Project: HBase > Issue Type: Test >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.1 > > Attachments: 1607918235175-image.png, > image-2020-12-13-10-15-55-445.png > > > Like in CI test results of PR [https://github.com/apache/hbase/pull/2699] > failed UTs site is > [https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2699/3/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt] > > In this unit test, it checks if all table regions assigned after balance, and > then assert for the RS group of regions. > But balance() uses aync move, and will throttle move regions, sleeping > between all the table regions are moved to its RSGroup. > If waiting time is not longer than the region movement duration, the > assertion will be fail. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[ANNOUNCE] Apache HBase 2.4.0 is now available for download
The HBase team is happy to announce the immediate availability of HBase 2.4.0. Apache HBase™ is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To learn more about HBase, see https://hbase.apache.org/. HBase 2.4.0 is the fifth minor release in the HBase 2.x line, which aims to improve the stability and reliability of HBase. The full list of issues can be found in the included CHANGES.md and RELEASENOTES.md, or via our issue tracker: https://s.apache.org/hbase-2.4.0-jira To download please follow the links and instructions on our website: https://hbase.apache.org/downloads.html Questions, comments, and problems are always welcome at: dev@hbase.apache.org. Thanks to all who contributed and made this release possible. Cheers, The HBase Dev Team
[jira] [Resolved] (HBASE-25400) [Flakey Tests] branch-2 TestRegionMoveAndAbandon
[ https://issues.apache.org/jira/browse/HBASE-25400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HBASE-25400. --- Fix Version/s: 2.4.1 2.5.0 2.3.4 3.0.0-alpha-1 Hadoop Flags: Reviewed Assignee: Michael Stack Resolution: Fixed Thanks for review [~huaxiangsun]. Merged to branch-2.3+. > [Flakey Tests] branch-2 TestRegionMoveAndAbandon > > > Key: HBASE-25400 > URL: https://issues.apache.org/jira/browse/HBASE-25400 > Project: HBase > Issue Type: Task >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.4, 2.5.0, 2.4.1 > > > Looks to be same as 'HBASE-25389 [Flakey Tests] branch-2 > TestMetaShutdownHandler (#2773)' One-liner seems to shut this flakey down > (I'm running unit tests locally.. it has failed a few times on me). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25404) Procedures table Id under master web UI gets word break to single character
Akshay Sudheer created HBASE-25404: -- Summary: Procedures table Id under master web UI gets word break to single character Key: HBASE-25404 URL: https://issues.apache.org/jira/browse/HBASE-25404 Project: HBase Issue Type: Bug Components: UI Reporter: Akshay Sudheer Under master web UI -> Procedures & Locks, *Procedures table* columns Errors and Parameters occupy larger width making Id and others word break more. Specially on Id where it breaks to single characters. Planning to make word break only on Errors and Parameters columns leaving the others normal in this table. So that we dont have to apply any changes on width/padding to get this fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25403) Cookie and Referrer policy vulnerabilities reported by scanner tool
Akshay Sudheer created HBASE-25403:
--
Summary: Cookie and Referrer policy vulnerabilities reported by
scanner tool
Key: HBASE-25403
URL: https://issues.apache.org/jira/browse/HBASE-25403
Project: HBase
Issue Type: Bug
Components: REST
Reporter: Akshay Sudheer
Vulnerability scanner has reported the following:
1.Cookies with missing, inconsistent or contradictory properties i)cookie
without SameSite attribute
Remediation: To ensure that the cookies configuration complies with the
applicable standards, Setting Same-Site attribute to
Set-Cookie[{{}}|https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie]
HTTP response header
Plan: Make Same-Site Configurable
2.Insecure Referrer Policy
Remediation: Consider setting Referrer-Policy header to
'strict-origin-when-cross-origin' or a stricter value
Plan: Make Referrer-Policy header Configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-25402) HBase UI: sorting order by start key or end key is not considering empty start key/end key
Ajeet Rai created HBASE-25402: - Summary: HBase UI: sorting order by start key or end key is not considering empty start key/end key Key: HBASE-25402 URL: https://issues.apache.org/jira/browse/HBASE-25402 Project: HBase Issue Type: Bug Components: UI Affects Versions: 2.2.3 Reporter: Ajeet Rai HBase UI: sorting order by start key or end key is not considering empty start key/end key. Steps: 1: Open any table page having multiple regions 2: click on sort button of start key/end key 3: Observed that sorting doesn't consider start and end key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25401) Add trace support for async call in rpc client
Duo Zhang created HBASE-25401: - Summary: Add trace support for async call in rpc client Key: HBASE-25401 URL: https://issues.apache.org/jira/browse/HBASE-25401 Project: HBase Issue Type: Sub-task Components: Client, tracing Reporter: Duo Zhang For verifying that OpenTelemetry can deal with async operations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25373) Remove HTrace completely in code base and try to make use of OpenTelemetry
[ https://issues.apache.org/jira/browse/HBASE-25373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25373. --- Fix Version/s: HBASE-22120 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch HBASE-22120. Thanks [~stack] for reviewing. > Remove HTrace completely in code base and try to make use of OpenTelemetry > -- > > Key: HBASE-25373 > URL: https://issues.apache.org/jira/browse/HBASE-25373 > Project: HBase > Issue Type: Sub-task > Components: tracing >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: HBASE-22120 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
