[
https://issues.apache.org/jira/browse/HBASE-24304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24304.
---
Hadoop Flags: Reviewed
Release Note: Added a new hbase-asyncfs module to hold the asynchronous df
Duo Zhang created HBASE-24333:
-
Summary: Backport HBASE-24304 "Separate a hbase-asyncfs module" to
branch-2.x
Key: HBASE-24333
URL: https://issues.apache.org/jira/browse/HBASE-24333
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-23976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-23976.
---
Fix Version/s: 2.3.0
3.0.0-alpha-1
Hadoop Flags: Reviewed
As
[
https://issues.apache.org/jira/browse/HBASE-24307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24307.
---
Assignee: Michael Stack
Resolution: Fixed
Pushed on branch-2.3+
> [Flakey Tests] krb
[
https://issues.apache.org/jira/browse/HBASE-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24118.
---
Resolution: Fixed
Re-resolving.
For those trying to follow-behind, there were FOUR commits
[
https://issues.apache.org/jira/browse/HBASE-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-24118:
---
Reopening. I needed to undo more; add back the problematic bit:
diff --git
a/hbase-server/src/
Update: The patch is now in all repos except hbase-site. As always, speak
up if you see something odd.
I plan to commit the hbase-site patch over the coming weekend so that I
have some time to fix/revert changes if something goes wrong (will put it
up for review before then). Let me know if anyone
[
https://issues.apache.org/jira/browse/HBASE-24273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-24273:
---
Whoop. Premature close by me. Reopening. Close when backports done. Sorry about
that [~huaxiang
[
https://issues.apache.org/jira/browse/HBASE-19146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-19146.
---
Resolution: Not A Problem
Resolving as no-longer a problem after purge of pb2.5 from master
[
https://issues.apache.org/jira/browse/HBASE-24273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24273.
---
Resolution: Fixed
Merged. Resolving. Shout if its off [~timoha]
> HBCK's "Orphan Regions on
[
https://issues.apache.org/jira/browse/HBASE-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-24323.
--
Resolution: Duplicate
> Avoid two parallel running of GCMulitpleMergedRegionsProcedure over th
[
https://issues.apache.org/jira/browse/HBASE-24284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24284.
---
Assignee: Michael Stack
Resolution: Fixed
Merged to branch-2.3.
> [h3/jdk11] REST ser
Mark Robert Miller created HBASE-24332:
--
Summary: TestJMXListener.setupBeforeClass can fail due to not
getting a random port.
Key: HBASE-24332
URL: https://issues.apache.org/jira/browse/HBASE-24332
Michael Stack created HBASE-24331:
-
Summary: [Flakey Test] TestJMXListener rmi port clash
Key: HBASE-24331
URL: https://issues.apache.org/jira/browse/HBASE-24331
Project: HBase
Issue Type: Su
Yes, Peter. We need to do the same for other repos. The problem here is
that (IIUC), there is no way to know whether a particular change works
without actually committing it to the repo. So, there is a chance that
things could go wrong. So far it looks like it is working, so I'll make the
github/ji
The dockerfile on branch-2.3+ were rewritten in order to support multiple
JDKs. These changes should be compatible with branch-2.2, other than they
no longer set JAVA_HOME in the Dockerfiles itself. Backport with a little
tweaking to the Dockerfiles or the build script should be fine.
I'm not cert
I believe Bharath's plan is to check out how things go on the main repo and
then roll out to the others.
On Tue, May 5, 2020 at 10:06 AM Peter Somogyi wrote:
> That's great!
> Do we need to do the same for the other repositories?
>
>
> On Tue, May 5, 2020 at 12:03 AM Stack wrote:
>
> > Good stu
Nick Dimiduk created HBASE-24330:
Summary: [fakey test] TestInfoServersACL testJmxAvailableForAdmin
Key: HBASE-24330
URL: https://issues.apache.org/jira/browse/HBASE-24330
Project: HBase
Issu
That's great!
Do we need to do the same for the other repositories?
On Tue, May 5, 2020 at 12:03 AM Stack wrote:
> Good stuff Bharath,
> S
>
> On Mon, May 4, 2020 at 12:48 PM Bharath Vissapragada
> wrote:
>
> > Hi,
> >
> > I just committed this change
> > <
> >
> https://github.com/apache/hbas
[
https://issues.apache.org/jira/browse/HBASE-24314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24314.
---
Fix Version/s: 2.2.5
2.3.0
3.0.0-alpha-1
Hadoop Flags: Rev
Jan Hentschel created HBASE-24329:
-
Summary: Remove deprecated CoprocessorService
Key: HBASE-24329
URL: https://issues.apache.org/jira/browse/HBASE-24329
Project: HBase
Issue Type: Improvemen
For branch-2.3+ we pinned all the dependencies with a specific version,
maybe we should backport the dockerfile to branch-2.2?
Jan Hentschel 于2020年5月5日周二 下午9:58写道:
> I thought we are already pinned the Rubocop version, but not sure about
> branch-2.2.
>
> From: Duo Zhang
> Reply-To: "dev@hbase.
I thought we are already pinned the Rubocop version, but not sure about
branch-2.2.
From: Duo Zhang
Reply-To: "dev@hbase.apache.org"
Date: Tuesday, May 5, 2020 at 2:38 PM
To: HBase Dev List
Subject: Nightly job for branch-2.2 is failing
Because of failing to build the dockerfile.
The error m
niuyulin created HBASE-24328:
Summary: skip duplicate GCMultipleMergedRegionsProcedure while
previous finished
Key: HBASE-24328
URL: https://issues.apache.org/jira/browse/HBASE-24328
Project: HBase
Because of failing to build the dockerfile.
The error message is
*18:52:25* [91mERROR: Error installing rubocop:*18:52:25*rubocop
requires Ruby version >= 2.4.0.
IIRC we have discussed this before that we should keep the rubocop at a
specific version to prevent it being upgraded accident
[
https://issues.apache.org/jira/browse/HBASE-24169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24169.
---
Resolution: Fixed
> Drop hadoop 2 support for hbase 3.x
> ---
>
>
[
https://issues.apache.org/jira/browse/HBASE-24315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24315.
---
Hadoop Flags: Reviewed
Resolution: Fixed
> Remove hadoop-two-compat.xml in hbase-assembly
> --
[
https://issues.apache.org/jira/browse/HBASE-24311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John resolved HBASE-24311.
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2 and master. Thanks all f
Hi *!
I submited PR few weeks ago, could someone help to review?
https://issues.apache.org/jira/browse/HBASE-23887
https://github.com/apache/hbase/pull/1257
Thanks very much!
вт, 5 мая 2020 г., 13:36 HBase Robot :
> 🎊 *+1 overall*
> Vote Subsystem Runtime Comment
> +0 🆗 reexec 1m 22s Docker
29 matches
Mail list logo