fengxianjing created HBASE-26351:
Summary: Implement a table-based region grouping strategy for
RegionGroupingProvider
Key: HBASE-26351
URL: https://issues.apache.org/jira/browse/HBASE-26351
Project:
HBASE-26329 (formerly HBASE-26291) has landed, it's the only issue I was
waiting for. I've confirmed my release environment. I'll create the RC
tomorrow. Please pause commits to branch-2.3 by around 2021-10-11T12:00 UTC.
Thanks,
Nick
On Wed, Oct 6, 2021 at 8:01 AM Nick Dimiduk wrote:
> Hello
Josh Elser created HBASE-26350:
--
Summary: Missing server side debugging on failed SASL handshake
Key: HBASE-26350
URL: https://issues.apache.org/jira/browse/HBASE-26350
Project: HBase
Issue
[
https://issues.apache.org/jira/browse/HBASE-26338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-26338.
--
Fix Version/s: hbase-operator-tools-1.2.0
Release Note:
To set the replica region's
Andrew Kyle Purtell created HBASE-26349:
---
Summary: Revert and improve recent change to
IntegrationTestLoadCommonCrawl
Key: HBASE-26349
URL: https://issues.apache.org/jira/browse/HBASE-26349
To give you a clearer sense of timeline, I am thinking we branch for 2.5 at
the end of this current month (October), so we can have a month to
stabilize, then try a 2.5.0RC0 in December.
On Thu, Oct 7, 2021 at 10:36 AM Andrew Purtell wrote:
> We are thinking about bringing backup back to
Please vote on this Apache hbase release candidate, hbase-2.4.7RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase 2.4.7
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.4.7RC0:
I like Nick's elucidation.
+1 from me.
As 2.4 RM I've had good experiences with it in chaos testing and have found
nothing that would not recommend it.
On Mon, Oct 11, 2021 at 7:58 AM Nick Dimiduk wrote:
> On Sun, Oct 10, 2021 at 1:16 PM Sean Busbey wrote:
>
> >
> > Personally, I view the
Duo Zhang created HBASE-26348:
-
Summary: Implement a special procedure to migrate rs group
information when upgrading
Key: HBASE-26348
URL: https://issues.apache.org/jira/browse/HBASE-26348
Project:
I was thinking we can add these things to the upgrade section.
https://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades
Nick Dimiduk 于2021年10月11日周一 下午10:59写道：
> On Mon, Oct 11, 2021 at 2:24 AM 张铎(Duo Zhang)
> wrote:
>
> > Could you please file an issue to add these to our ref guide? I
I'm not very familiar with github packages. Can we use github packages on
asf jenkins?
Nick Dimiduk 于2021年10月11日周一 下午10:43写道：
> Given that these images are for consumption by our build and not public
> consumption, and that our build revolves around Github, does it make sense
> to use Github
On Mon, Oct 11, 2021 at 2:24 AM 张铎(Duo Zhang) wrote:
> Could you please file an issue to add these to our ref guide? I think these
> are all very important experiences for our end users.
>
Question: Is the ref guide the place where we want to document what
community testing has been performed
On Sun, Oct 10, 2021 at 1:16 PM Sean Busbey wrote:
>
> Personally, I view the "stable" pointer as simply a way to say "if you
> are new to our community we'd like you to use this release." I
> personally think 2.4.z currently meets that standard and we need not
> block updating on something more
Given that these images are for consumption by our build and not public
consumption, and that our build revolves around Github, does it make sense
to use Github Packages instead?
https://github.com/features/packages
On Mon, Oct 11, 2021 at 6:51 AM 张铎(Duo Zhang) wrote:
> For me, uploading the
+1
I'm in favor of moving the stable pointer to 2.4.
On Mon, Oct 11, 2021 at 11:24 AM 张铎(Duo Zhang)
wrote:
> Could you please file an issue to add these to our ref guide? I think these
> are all very important experiences for our end users.
>
> Thanks.
>
> Viraj Jasani 于2021年10月11日周一 下午3:46写道：
For me, uploading the image to docker hub could save us time on rebuilding
it every time when the cache is expired, and also the problem here can be
solved too as we do not need to download the findbugs any more.
It is for internal use.
Sean Busbey 于2021年10月11日周一 下午9:26写道：
> we'd need to have
we'd need to have a discussion about pushing to docker hub, esp what
our intentions are (i.e. publishing for downstream vs internal use)
and how we communicate that via docker hub. The mechanisms for
publishing to docker hub are relatively straightforward.
On Sun, Oct 10, 2021 at 10:35 PM 张铎(Duo
Xiaolin Ha created HBASE-26347:
--
Summary: Support detect and exclude slow DNs in fan-out of WAL
Key: HBASE-26347
URL: https://issues.apache.org/jira/browse/HBASE-26347
Project: HBase
Issue
So I think in this thread, the only concern is about performance issues, so
we decided to make new releases on branch-1.
But at least I think we all agree to EOL other 1.x release lines,
especially branch-1.4 right?
If no other concerns, let's do a final 1.4.14 release and then mark
branch-1.4
Could you please file an issue to add these to our ref guide? I think these
are all very important experiences for our end users.
Thanks.
Viraj Jasani 于2021年10月11日周一 下午3:46写道：
> Moreover, I have also tested rollback from 2.4 to 1.6 and after taking care
> of some rsgroup ordering issues as
Mallikarjun created HBASE-26346:
---
Summary: Design support for rsgroup data isolation
Key: HBASE-26346
URL: https://issues.apache.org/jira/browse/HBASE-26346
Project: HBase
Issue Type: New
+1 on moving to 2.4.
Viraj Jasani 于2021年10月11日周一 下午3:40写道：
> I have done some chaos testing as well as ingestion testing 3-4 times on
> the recent 2.4 versions, each spanning the duration of around 8-10 hr. And
> also tested rolling upgrade from 1.6 to 2.4 a couple of times after
> applying the
Moreover, I have also tested rollback from 2.4 to 1.6 and after taking care
of some rsgroup ordering issues as part of the downgrade, we have seen
smooth downgrade as well (with the only exception that last RS that stays
on 2.4 needs to be shutdown non-gracefully or killed, because of
I have done some chaos testing as well as ingestion testing 3-4 times on
the recent 2.4 versions, each spanning the duration of around 8-10 hr. And
also tested rolling upgrade from 1.6 to 2.4 a couple of times after
applying the recent fixes on adding missing CFs in meta table as part of
the
24 matches
Mail list logo
