Re: [VOTE] First release candidate for hbase 3.0.0-alpha-4 is available for download

[Guanghao Zhang]

+1 (binding)

* Checksum : ok
* Rat check (1.8.0_362): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_362): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_362): ok
 - mvn clean package -P runSmallTests
 -Dsurefire.rerunFailingTestsCount=3

Shanmukha Haripriya Kota  于2023年6月7日周三 08:17写道：

> +1
>
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
> [INFO] Total time:  33:55 min
> [INFO] Finished at: 2023-06-06T19:00:23-05:00
> [INFO]
> 
> ~/Desktop/hbase300/hbase-3.0.0-alpha-4/dev-support
> * Signature: ok
> * Checksum : ok
> * Rat check (11.0.10): ok
>  - mvn clean apache-rat:check
> * Built from source (11.0.10): ok
>  - mvn clean install  -DskipTests
> * Unit tests pass (11.0.10): ok
>  - mvn clean package -P runSmallTests
>  -Dsurefire.rerunFailingTestsCount=3
>
> [1]  + 19163 done   ./hbase-vote.sh -s  -f
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> On Tue, Jun 6, 2023 at 10:22 AM Andrew Purtell 
> wrote:
>
> > +1 (binding)
> >
> > * Signature: ok
> > * Checksum : ok
> > * Rat check (11.0.19): ok
> >  - mvn clean apache-rat:check
> > * Built from source (11.0.19): ok
> >  - mvn clean install  -DskipTests
> > * Unit tests pass (11.0.19): failed
> >  - mvn clean package -P runAllTests
> >  -Dsurefire.rerunFailingTestsCount=3
> >
> > TestSpnegoHttpServer and TestProxyUserSpnegoHttpServer in hbase-http
> > consistently failed but it may be environmental, related to local keberos
> > configs.
> >
> > On Sun, May 28, 2023 at 8:13 AM Duo Zhang  wrote:
> >
> > > Please vote on this Apache hbase release candidate,
> > > hbase-3.0.0-alpha-4RC0
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache hbase 3.0.0-alpha-4
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 3.0.0-alpha-4RC0:
> > >
> > >   https://github.com/apache/hbase/tree/3.0.0-alpha-4RC0
> > >
> > > This tag currently points to git reference
> > >
> > >   e44cc02c75ecae7ece845f04722eb16b7528393f
> > >
> > > The release files, including signatures, digests, as well as CHANGES.md
> > > and RELEASENOTES.md included in this RC can be found at:
> > >
> > >   https://dist.apache.org/repos/dist/dev/hbase/3.0.0-alpha-4RC0/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1520/
> > >
> > > Maven artifacts for hadoop3 are available in a staging repository at:
> > >
> > >   https://repository.apache.org/content/repositories/not-applicable/
> > >
> > > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> > >
> > >   https://downloads.apache.org/hbase/KEYS
> > >
> > > 3.0.0-alpha-4 is the fourth alpha release for our 3.0.0 major release
> > line.
> > > HBase 3.0.0 includes the following big feature/changes:
> > >   Synchronous Replication
> > >   OpenTelemetry Tracing
> > >   Distributed MOB Compaction
> > >   Backup and Restore
> > >   Move RSGroup balancer to core
> > >   Reimplement sync client on async client
> > >   CPEPs on shaded protobuf
> > >   Move the logging framework from log4j to log4j2
> > >   Decouple region replication and general replication framework, and
> > >   also make region replication can work when SKIP_WAL is used
> > >   A new file system based replication peer storage
> > >   Used hbase table instead of zookeeper for tracking hbase replication
> > > queue
> > >
> > > Notice that this is not a production ready release. It is used to let
> our
> > > users try and test the new major release, to get feedback before the
> > final
> > > GA release is out.
> > > So please do NOT use it in production. Just try it and report back
> > > everything you find unusual.
> > >
> > > And this time we will not include CHANGES.md and RELEASENOTE.md
> > > in our source code, you can find it on the download site. For getting
> > these
> > > two files for old releases, please go to
> > >
> > >   https://archive.apache.org/dist/hbase/
> > >
> > > To learn more about Apache hbase, please see
> > >
> > >   http://hbase.apache.org/
> > >
> > > Thanks,
> > > Your HBase Release Manager
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Unrest, ignorance distilled, nihilistic imbeciles -
> > It's what we’ve earned
> > Welcome, apocalypse, what’s taken you so long?
> > Bring us the fitting end that we’ve been counting on
> >- A23, Welcome, Apocalypse
> >
>
>
> --
> Regards,
> Shanmukha Kota
>

Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

[Guanghao Zhang]

Did other projects have the same solution for this, sync github issues to
jira issues? Github issues will be useful to get more feedback.

张铎(Duo Zhang)  于2022年12月6日周二 00:13写道：

> The PR for HBASE-27513 is available
>
> https://github.com/apache/hbase/pull/4913
>
> Let's at least tell our users to send email to private@hbase for
> acquiring a jira account.
>
> Thanks.
>
> 张铎(Duo Zhang)  于2022年12月2日周五 12:46写道：
> >
> > Currently all the comment on github PR will be sent to issues@hbase,
> > like this one
> >
> > https://lists.apache.org/thread/jbfm269b4m24xl2r82l8b0t3pmqr44hr
> >
> > But I think this can only be used as an archive, to make sure that all
> > discussions are recorded on asf infrastructure.
> >
> > For github issues, I'm afraid we can only do the same thing. As the
> > format of github comment is different, it will be hard to read if we
> > just sync the message to jira...
> >
> > Thanks.
> >
> > Bryan Beaudreault  于2022年12月1日周四
> 21:30写道：
> > >
> > > Should we have them sent to private@? Just thinking in terms of
> reducing
> > > spam to users who put their email and full name on a public list.
> > >
> > > One thought I had about bug tracking is whether we could use some sort
> of
> > > github -> jira sync. I've seen them used before, where it automatically
> > > syncs issues and comments between the two systems. It's definitely not
> > > ideal, but maybe an option? I'm guessing it would require INFRA help.
> > >
> > > On Thu, Dec 1, 2022 at 5:47 AM 张铎(Duo Zhang) 
> wrote:
> > >
> > > > I've filed HBASE-27513 for changing the readme on github.
> > > >
> > > > At least let's reuse the existing mailing list for acquiring jira
> account.
> > > >
> > > > Thanks.
> > > >
> > > > 张铎(Duo Zhang)  于2022年11月29日周二 22:34写道：
> > > >
> > > > >
> > > > > Bump and also send this to user@hbase.
> > > > >
> > > > > We need to find a way to deal with the current situation where
> > > > > contributors can not create a Jira account on their own...
> > > > >
> > > > > At least, we need to change the readme on github page, web site and
> > > > > also the ref guide to tell users how to acquire a jira account...
> > > > >
> > > > > Thanks.
> > > > >
> > > > > 张铎(Duo Zhang)  于2022年11月27日周日 22:06写道：
> > > > > >
> > > > > > For me, I think most developers already have a github account, so
> > > > > > enabling it could help us get more feedback. For lots of younger
> > > > > > Chinese developers, they rarely use email in their daily life...
> > > > > > No doubt later we need to modify our readme on github. If we
> just let
> > > > > > users go to github issues on the readme, they will soon open an
> issue
> > > > > > there. But if we ask users to first send an email to a mailing
> list,
> > > > > > for acquiring a jira account, and then wait for a PMC member to
> submit
> > > > > > the request, and receive the email response, set up their
> account, and
> > > > > > then they can finally open an issue on jira. I'm afraid lots of
> users
> > > > > > will just give up, it is not very friendly...
> > > > > >
> > > > > > And I do not mean separate issue systems for users and devs.
> Users can
> > > > > > still open jira issues or ask in the mailing list if they want,
> github
> > > > > > issues is just another channel. If a user asks something in the
> > > > > > mailing list and we think it is a bug, we will ask the user to
> file an
> > > > > > issue or we will file an issue for it. It is just the same with
> github
> > > > > > issues.
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > Nick Dimiduk  于2022年11月24日周四 15:44写道：
> > > > > > >
> > > > > > > This new situation around JIRA seems very similar to the
> existing
> > > > situation
> > > > > > > around Slack. A new community member currently must acquire a
> Slack
> > > > invite
> > > > > > > somehow, usually by emailing one of the lists. Mailing lists
> > > > themselves
> > > > > > > involve a signup process, though it may be possible to email
> > > > user/-zh/dev
> > > > > > > without first subscribing to the list.
> > > > > > >
> > > > > > > I have a -0 opinion on using GitHub Issues to manage JIRA
> > > > subscription
> > > > > > > access. It seems like a comical cascade of complexity. I’d
> prefer to
> > > > keep
> > > > > > > GitHub Issues available to us as a future alternative to JIRA
> for
> > > > project
> > > > > > > issue tracking. I agree with you that migrating away from JIRA
> will
> > > > be
> > > > > > > painful.
> > > > > > >
> > > > > > > I’m not a big fan of having separate issue systems for users
> vs.
> > > > devs. It
> > > > > > > emphasizes the idea that users and devs are different groups of
> > > > people with
> > > > > > > unequal voice in the project direction. I suppose it could be
> done
> > > > well,
> > > > > > > but I think it is more likely to be done poorly.
> > > > > > >
> > > > > > > I follow the Infra list, but only casually. It seems there’s a
> plan
> > > > to
> > > > > > > eventually adopt some Atlassian Cloud service, which 

Re: [ANNOUNCE] New HBase Committer Liangjun He

[Guanghao Zhang]

Congratulations!

OpenInx  于2022年12月6日周二 19:03写道：

> Congrats and welcome !
>
> On Tue, Dec 6, 2022 at 2:21 AM Andrew Purtell  wrote:
>
> > Congratulations, and welcome!
> >
> > On Sat, Dec 3, 2022 at 5:51 AM Yu Li  wrote:
> >
> > > Hi All,
> > >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Liangjun
> > > He (heliangjun) has accepted the PMC's invitation to become a committer
> > on
> > > the project. We appreciate all of Liangjun's generous contributions
> thus
> > > far and look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Liangjun!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布 Liangjun He (何良均) 已接受我们的邀请，成为 Apache HBase
> 项目的
> > > Committer。感谢何良均一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
> > >
> > > 欢迎良均！
> > >
> > > Best Regards,
> > > Yu
> > > --
> > > Best Regards,
> > > Yu
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Unrest, ignorance distilled, nihilistic imbeciles -
> > It's what we’ve earned
> > Welcome, apocalypse, what’s taken you so long?
> > Bring us the fitting end that we’ve been counting on
> >- A23, Welcome, Apocalypse
> >
>

Re: [VOTE] The first release candidate for HBase 2.5.2 is available

[Guanghao Zhang]

+1 (binding)

* Checksum : ok
* Rat check (1.8.0_301): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_301): ok
 - mvn package -P runSmallTests

Duo Zhang  于2022年11月30日周三 23:37写道：

> Bump.
>
> The phoenix community has tested the hadoop3 artifacts and it works well.
>
> Let's get this release done~
>
> Thanks.
>
> Duo Zhang  于2022年11月24日周四 12:32写道：
> >
> > Please vote on this Apache hbase release candidate,
> > hbase-2.5.2RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.5.2
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.5.2RC0:
> >
> >   https://github.com/apache/hbase/tree/2.5.2RC0
> >
> > This tag currently points to git reference
> >
> >   3e28acf0b819f4b4a1ada2b98d59e05b0ef94f96
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/2.5.2RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1503/
> >
> > Maven artifacts for hadoop3 are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1504/
> >
> > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> >
> >   https://downloads.apache.org/hbase/KEYS
> >
> > 2.5.2 includes 28 bug and improvement fixes done since 2.5.1. And
> > starting from 2.5.2, we will publish dist and maven artifacts for both
> > hadoop2 and hadoop3. Feel free to report any issues for the newly
> > published hadoop3 dist and maven artifacts.
> >
> > To learn more about Apache hbase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
>

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download

[Guanghao Zhang]

+1 (binding)

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_301): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
 - mvn clean install  -DskipTests

张铎(Duo Zhang)  于2022年6月20日周一 23:40写道：

> See https://github.com/apache/hbase/pull/4552
>
> After modifying some code in HBase, mainly because of a behavior change in
> jetty, we can pass all the UTs when depending on hbase-thirdparty-4.1.1.
>
> 张铎(Duo Zhang)  于2022年6月18日周六 23:04写道：
>
> > Please vote on this Apache hbase thirdparty release candidate,
> > hbase-thirdparty-4.1.1RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.1.1RC0:
> >
> >   https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0
> >
> > This tag currently points to git reference
> >
> >   d674246a75e1d7d1d4c5ee09a2567bbfa1cec022
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-4.1.1RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1488/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> >   https://downloads.apache.org/hbase/KEYS
> >
> > To learn more about Apache hbase thirdparty, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>

Re: [ANNOUNCE] New HBase committer Bryan Beaudreault

[Guanghao Zhang]

Congratulations!

Tak Lon (Stephen) Wu  于2022年4月12日周二 02:29写道：

> Congrats Bryan!
>
> -Stephen
>
> On Mon, Apr 11, 2022 at 9:44 AM Pankaj Kumar 
> wrote:
> >
> > Congratulations & welcome Bryan..!!
> >
> > Regards,
> > Pankaj
> >
> > On Sat, Apr 9, 2022, 5:15 PM 张铎(Duo Zhang) 
> wrote:
> >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that Bryan
> > > Beaudreault(bbeaudreault) has accepted the PMC's invitation to become a
> > > committer on the project. We appreciate all of Bryan's generous
> > > contributions thus far and look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Bryan Beaudreault!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请，成为 Apache HBase
> 项目的
> > > Committer。感谢 Bryan Beaudreault 一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
> > >
> > > 欢迎 Bryan Beaudreault！
> > >
>

Re: [ANNOUNCE] Please welcome Xiaolin Ha(哈晓琳) to the HBase PMC

[Guanghao Zhang]

Congratulations!

Tak Lon (Stephen) Wu  于2022年4月12日周二 02:28写道：

> Congratulations Xiaolin!
>
> -Stephen
>
> On Mon, Apr 11, 2022 at 9:45 AM Pankaj Kumar 
> wrote:
> >
> > Congratulations Xiaolin..!!
> >
> > Regards,
> > Pankaj
> >
> > On Sat, Apr 9, 2022, 6:41 PM 张铎(Duo Zhang) 
> wrote:
> >
> > > On behalf of the Apache HBase PMC I am pleased to announce that
> Xiaolin Ha
> > > has accepted our invitation to become a PMC member on the Apache HBase
> > > project. We appreciate Xiaolin Ha stepping up to take more
> responsibility
> > > in
> > > the HBase project.
> > >
> > > Please join me in welcoming Xiaolin Ha to the HBase PMC!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布哈晓琳已接受我们的邀请，
> > > 成为 Apache HBase 项目的 PMC 成员。感谢哈晓琳愿意在 HBase 项目
> > > 中承担更大的责任。
> > >
> > > 欢迎哈晓琳！
> > >
>

Re: [VOTE] Merge feature branch HBASE-26233 back to master

[Guanghao Zhang]

+1 from me.

The idea and solution is great!

Thanks.

Duo Zhang  于2021年12月18日周六 16:31写道：

> There is a previous thread[1] to mention that the main development work on
> HBASE-26233[2] is done. And now the testing work has been done too, so I
> send this official vote to merge for HBASE-26233 back into master.
>
> For those who are not familiar with HBASE-26233, it is for re-implementing
> the region replication framework, to decouple with the general replication
> framework. You could see the design doc[3] for more details. I've also
> opened a PR against master[4], PTAL if you have interest.
>
> You can see the final test result on HBASE-26487[5].
> In conclusion, there is no regression on performance when running PE.
> Using the new tool introduced in HBASE-26540[6], the new implementation can
> perform much better than the old implementation. When inserting 1M rows,
> the max lag on secondary replica is 335ms, and the 99.9% lag is 3 only 3ms,
> while the lag of the old implementation highly depends on the
> replication.source.sleepforretries config but you should not set it to a
> very small value as it will waste a lot of resources.
> On IntegrationTestRegionReplicaReplication, both implementations can not
> pass but the problems are not related to the changing part, so should not
> be a blocker. Will file follow on issues to address these problems.
>
> The vote will open for at least 72 hours.
>
> Please vote:
> +1: Merge the changes from HBASE-26233 to master
> -1: Do not merge these changes because ...
>
> Thanks.
>
> 1. https://lists.apache.org/thread/t8w053kpy9pj1vg1x3c0kjjh4ongrxzy
> 2. https://issues.apache.org/jira/browse/HBASE-26233
> 3.
>
> https://docs.google.com/document/d/1WPSBwRqIPgTrPRM2wtzAe-3XUvA9S7auWy3Fy8xuZLc/edit
> 4. https://github.com/apache/hbase/pull/3891
> 5. https://issues.apache.org/jira/browse/HBASE-26487
> 6. https://issues.apache.org/jira/browse/HBASE-26540
>

Re: [VOTE] First release candidate for HBase 2.4.8 (RC0) is available

[Guanghao Zhang]

+1 (binding)

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_301): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_301): ok
- mvn package -P runSmallTests
* Started a mini cluster: ok
* Master, RegionServer, Table, Region UI: ok
* HBase Shell: ok

Andrew Purtell  于2021年10月28日周四 上午3:24写道：

> Please vote on this Apache HBase release candidate, hbase-2.4.8RC0
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 2.4.8
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.4.8RC0:
>
>   https://github.com/apache/hbase/tree/2.4.8RC0
>
> This tag currently points to git reference f844d09157.
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/2.4.8RC0/
>
> The API compatibility report can be found at:
>
>
>
> https://dist.apache.org/repos/dist/dev/hbase/2.4.8RC0/api_compare_2.4.7_to_2.4.8RC0.html
>
> There are no reported compatibility issues.
>
> This release fixes an important issue. Please see HBASE-26383 for more
> details. There are known flaky unit tests, see HBASE-26254.
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1469/
>
> Artifacts were signed with the 0xD5365CCD key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> To learn more about Apache HBase, please see http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>

Re: [VOTE] First release candidate for HBase 1.4.14 is available for download

[Guanghao Zhang]

Change my vote to +1.

Thanks.

张铎(Duo Zhang)  于2021年10月25日周一 下午11:19写道：

> OK, I got an error when upgrading to jdk8u312.
>
> TestLogLevel.testLogLevelByHttp:402 Expected to find 'Unrecognized SSL
> message' but got unexpected exception:javax.net.ssl.SSLException:
> Unsupported or unrecognized SSL message
>
> The actual testing code is
>
> try {
>   testDynamicLogLevel(LogLevel.PROTOCOL_HTTP, LogLevel.PROTOCOL_HTTPS,
> false);
>   fail("A HTTPS Client should not have succeeded in connecting to a
> HTTP server");
> } catch (SSLException e) {
>   GenericTestUtils.assertExceptionContains("Unrecognized SSL message",
> e);
> }
>   }
>
> So I think this is just a test issue, during upgrading the JDK has changed
> the error message from 'Unrecognized SSL message' to 'Unsupported or
> unrecognized SSL message'. It does not indicate any real problems in our
> non testing code.
>
> So I do not think this should be a blocker.
>
> WDYT Guanghao?
>
> Thanks.
>
> 张铎(Duo Zhang)  于2021年10月25日周一 下午11:04写道：
>
> > It passed for me with 8u252.
> >
> > What is the failure message?
> >
> > Guanghao Zhang  于2021年10月25日周一 下午6:48写道：
> >
> >> +0 from me as there was one UT failed. Will change the vote if it is
> not a
> >> blocker.
> >> *Signature: ok
> >> *Checksum : ok
> >> *Rat check (1.8.0_301): ok
> >> - mvn clean apache-rat:check
> >> *Built from source (1.8.0_301): ok
> >> - mvn clean install -DskipTests
> >> *Unit tests (1.8.0_301): TestLogLevel always failed
> >> - mvn package -P runSmallTests
> >> *Started a mini cluster, UI check: ok
> >> *Shell check: ok
> >>
> >> Reid Chan  于2021年10月21日周四 下午12:01写道：
> >>
> >> > +1
> >> > * Signature: ok
> >> > * Checksum : ok
> >> > * Rat check (1.8.0_232): ok
> >> >  - mvn clean apache-rat:check
> >> > * Built from source (1.8.0_232): ok
> >> >  - mvn clean install  -DskipTests
> >> > * Unit tests pass (1.8.0_232): ok
> >> >  - mvn package -P runSmallTests
> >> > -Dsurefire.rerunFailingTestsCount=3
> >> >
> >> >
> >> > On Thu, Oct 21, 2021 at 9:27 AM Duo Zhang 
> wrote:
> >> >
> >> > > Please vote on this Apache HBase release candidate,
> >> > > hbase-1.4.14RC0
> >> > >
> >> > > The VOTE will remain open for at least 72 hours.
> >> > >
> >> > > [ ] +1 Release this package as Apache HBase 1.4.14
> >> > > [ ] -1 Do not release this package because ...
> >> > >
> >> > > The tag to be voted on is 1.4.14RC0:
> >> > >
> >> > >   https://github.com/apache/hbase/tree/1.4.14RC0
> >> > >
> >> > > This tag currently points to git reference
> >> > >
> >> > >   e7cbc2debc11a01dd4f3e6f6d6992b7bd307bbcb
> >> > >
> >> > > The release files, including signatures, digests included
> >> > > in this RC can be found at:
> >> > >
> >> > >   https://dist.apache.org/repos/dist/dev/hbase/1.4.14RC0/
> >> > >
> >> > > The release notes can be found at:
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12346995
> >> > >
> >> > > Maven artifacts are available in a staging repository at:
> >> > >
> >> > >
> >> >
> https://repository.apache.org/content/repositories/orgapachehbase-1467/
> >> > >
> >> > > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >> > >
> >> > >   https://dist.apache.org/repos/dist/release/hbase/KEYS
> >> > >
> >> > > Notice that 1.4.14 will be the last release for the 1.4.x release
> >> line.
> >> > > Users
> >> > > are encouraged to upgrade to the 2.x stable release line.
> >> > >
> >> > > To learn more about Apache HBase, please see
> >> > >
> >> > >   http://hbase.apache.org/
> >> > >
> >> > > Thanks,
> >> > > Your HBase Release Manager
> >> > >
> >> >
> >>
> >
>

Re: [VOTE] First release candidate for HBase 1.4.14 is available for download

[Guanghao Zhang]

+0 from me as there was one UT failed. Will change the vote if it is not a
blocker.
*Signature: ok
*Checksum : ok
*Rat check (1.8.0_301): ok
- mvn clean apache-rat:check
*Built from source (1.8.0_301): ok
- mvn clean install -DskipTests
*Unit tests (1.8.0_301): TestLogLevel always failed
- mvn package -P runSmallTests
*Started a mini cluster, UI check: ok
*Shell check: ok

Reid Chan  于2021年10月21日周四 下午12:01写道：

> +1
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_232): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_232): ok
>  - mvn clean install  -DskipTests
> * Unit tests pass (1.8.0_232): ok
>  - mvn package -P runSmallTests
> -Dsurefire.rerunFailingTestsCount=3
>
>
> On Thu, Oct 21, 2021 at 9:27 AM Duo Zhang  wrote:
>
> > Please vote on this Apache HBase release candidate,
> > hbase-1.4.14RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 1.4.14
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 1.4.14RC0:
> >
> >   https://github.com/apache/hbase/tree/1.4.14RC0
> >
> > This tag currently points to git reference
> >
> >   e7cbc2debc11a01dd4f3e6f6d6992b7bd307bbcb
> >
> > The release files, including signatures, digests included
> > in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/1.4.14RC0/
> >
> > The release notes can be found at:
> >
> >
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12346995
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1467/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> >   https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > Notice that 1.4.14 will be the last release for the 1.4.x release line.
> > Users
> > are encouraged to upgrade to the 2.x stable release line.
> >
> > To learn more about Apache HBase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>

[ANNOUNCE] New HBase committer Zhuoyue Huang(GeorryHuang)

[Guanghao Zhang]

Folks,

On behalf of the Apache HBase PMC I am pleased to announce that Zhuoyue
Huang has accepted the PMC's invitation to become a committer on the
project.

We appreciate all of the great contributions Zhuoyue Huang has made to the
community thus far and we look forward to his continued involvement.

Allow me to be the first to congratulate Zhuoyue Huang on his new role!

Thanks.

Re: [VOTE] First release candidate for HBase 2.4.6 (RC0) is available

[Guanghao Zhang]

+1 (binding)

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_301): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_301): ok
 - mvn package -P runSmallTests
* HMaster, RS, Table, Region UI: ok
* HBase shell (list, create, disable, drop, get, put, scan,
delete): ok



张铎(Duo Zhang)  于2021年9月8日周三 上午10:12写道：

> +1(binding)
>
> Checked sigs and sums: Matched
> Rat check: Passed
> Built from source(AdoptOpenJDK-11.0.11+9): OK with -Dhadoop.profile=3.0
> Run UTs: Got some trouble in the hbase-server module,
> TestMasterAddressRefresher always failed but when running on other
> machines, it was fine, so should not be a blocker.
> Started a mini cluster: Run ./start-hbase.sh. succeeded, the web page looks
> fine
> Run basic shell commands: list, create, disable, drop, all fine
> Run ltt with 1 rows: Passed, count in hbase shell also returned 1
>
> Jan Hentschel  于2021年9月8日周三 上午5:11写道：
>
> > +1 (binding)
> >
> > * Signature: ok
> > * Checksum : ok
> > * Rat check (1.8.0_202-ea): ok
> >  - mvn clean apache-rat:check
> > * Built from source (1.8.0_202-ea): ok
> >  - mvn clean install  -DskipTests
> > * Unit tests pass (1.8.0_202-ea): ok
> >  - mvn package -P runSmallTests
> > -Dsurefire.rerunFailingTestsCount=3
> >
> > From: Andrew Purtell 
> > Date: Saturday, September 4, 2021 at 3:31 AM
> > To: dev 
> > Subject: [VOTE] First release candidate for HBase 2.4.6 (RC0) is
> available
> > Please vote on this Apache hbase release candidate,
> > hbase-2.4.6RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.4.6
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.4.6RC0:
> >
> >   https://github.com/apache/hbase/tree/2.4.6RC0
> >
> > This tag currently points to git reference 7374d396c2.
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/2.4.6RC0/
> >
> > The API compatibility report can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.4.6RC0/api_compare_2.4.5_to_2.4.6RC0.html
> >
> > There are no reported compatibility issues.
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1464/
> >
> > Artifacts were signed with the code signing key 0xD5365CCD which can be
> > found in:
> >
> >   https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > Some pre-flight checks were made prior to release candidate generation,
> > including unit test execution. Some flaky tests were found, see
> > HBASE-26254.
> >
> > To learn more about Apache hbase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>

Re: [VOTE] Merge branch HBASE-22120 back to master

[Guanghao Zhang]

+1

Anoop John  于2021年4月25日周日 下午3:13写道：

> +1
>
> Anoop
>
>
> On Sat, Apr 24, 2021 at 9:31 PM 张铎(Duo Zhang) 
> wrote:
>
> > So we have 5 +1s now, it is enough to merge this feature branch back to
> > master.
> >
> > Will merge soon.
> >
> > Thanks all for voting!
> >
> > 张铎(Duo Zhang)  于2021年4月24日周六 下午11:54写道：
> >
> > > This is for merging a feature branch, not a release, so I do not think
> > > here we have binding or non-binding votes? Or at least, the vote from
> > > committers should also be considered as 'binding'.
> > >
> > > See this section in our ref guide.
> > >
> > > https://hbase.apache.org/book.html#_decisions
> > >
> > > When the feature is ready for commit, 3 +1s from committers will get
> your
> > >> feature merged.
> > >
> > >
> > > Anyway, I really think we should have a page like what the flink
> > community
> > > have
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026
> > >
> > > Bharath Vissapragada  于2021年4月22日周四 上午12:53写道：
> > >
> > >> +1, skimmed through the patch. Thanks for putting this together.
> > >>
> > >> On Tue, Apr 20, 2021 at 10:06 PM Tak-Lon (Stephen) Wu <
> > tak...@apache.org>
> > >> wrote:
> > >>
> > >> > +1 (non-binding)
> > >> >
> > >> > This is a great integration, thanks Duo.
> > >> >
> > >> > -Stephen
> > >> >
> > >> > On Tue, Apr 20, 2021 at 9:53 PM Pankaj Kumar <
> pankajku...@apache.org>
> > >> > wrote:
> > >> > >
> > >> > > +1(non-binding)
> > >> > >
> > >> > > Regards,
> > >> > > Pankaj
> > >> > >
> > >> > > On Tue, Apr 20, 2021, 8:28 AM 张铎(Duo Zhang) <
> palomino...@gmail.com>
> > >> > wrote:
> > >> > >
> > >> > > > HBASE-22120 aims to use OpenTelemetry to replace HTrace and
> bring
> > >> > tracing
> > >> > > > back to HBase.
> > >> > > >
> > >> > > > The discusson thread:
> > >> > > >
> > >> > > >
> > >> > > >
> > >> >
> > >>
> >
> https://lists.apache.org/thread.html/r31a147c184e379681987b536685db4260af16bbcb0f047ec966b22d5%40%3Cdev.hbase.apache.org%3E
> > >> > > >
> > >> > > > The PR
> > >> > > >
> > >> > > > https://github.com/apache/hbase/pull/2901
> > >> > > >
> > >> > > > Please vote:
> > >> > > > [+1] Agree
> > >> > > > [0] Neutral
> > >> > > > [-1] Disagree (please include actionable feedback)
> > >> > > >
> > >> > > > Thanks.
> > >> > > >
> > >> >
> > >>
> > >
> >
>

[ANNOUNCE] Apache HBase 2.2.7 is now available for download

[Guanghao Zhang]

The HBase team is happy to announce the immediate availability of HBase
2.2.7.

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/.
To download 2.2.7, visit our download page:
http://hbase.apache.org/downloads.html

HBase 2.2.7 is the final release of the HBase 2.2 release line, continuing
on the
theme of bringing a stable, reliable database to the Apache Big Data
ecosystem and beyond. 2.2.7 includes 138 bug fixes and improvements done
since the 2.2.6. The list of 138 changes made since 2.2.6 can be found here:
https://downloads.apache.org/hbase/2.2.7/CHANGES.md

For instructions on verifying ASF release downloads, please see
https://www.apache.org/dyn/closer.cgi#verify
Project member signature keys can be found at
https://www.apache.org/dist/hbase/KEYS
Question, comments, and problems are always welcome at:
dev@hbase.apache.org u...@hbase.apache.org user...@hbase.apache.org

Thanks to all who contributed and made this release possible.

Cheers,
The HBase Dev Team

[jira] [Resolved] (HBASE-25780) Add 2.2.7 to download page

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25780.

  Assignee: Guanghao Zhang
Resolution: Fixed

> Add 2.2.7 to download page
> --
>
> Key: HBASE-25780
> URL: https://issues.apache.org/jira/browse/HBASE-25780
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25780) Add 2.2.7 to download page

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25780:
--

 Summary: Add 2.2.7 to download page
 Key: HBASE-25780
 URL: https://issues.apache.org/jira/browse/HBASE-25780
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] The first HBase 2.2.7 release candidate (RC0) is available

[Guanghao Zhang]

+1 from me. With 6 binding +1 and 2 non-binding +1, the vote passed. Thanks
all for voting!


Andrew Purtell  于2021年4月16日周五 上午9:48写道：

> +1 (binding)
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_292): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_292): ok
>  - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_292): ok
>  - mvn package -P runAllTests
>
>
> On Sun, Apr 11, 2021 at 5:34 AM Guanghao Zhang  wrote:
>
> > Please vote on this release candidate (RC) for Apache HBase 2.2.7.
> > Meanwhile, as branch-2.2 will be EOL, please don't push new commits to
> it.
> > And this will be the last one of the 2.2.x releases. Thanks.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 2.2.7
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.2.7RC0. The release files, including
> > signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachehbase-1440/
> >
> > Signatures used for HBase RCs can be found in this file:
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > The list of bug fixes going into 2.2.7 can be found in included
> > CHANGES.md and RELEASENOTES.md available here:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/CHANGES.md
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/RELEASENOTES.md
> >
> > A detailed source and binary compatibility report for this release is
> > available at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/api_compare_2.2.7RC0_to_2.2.6.html
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Guanghao Zhang
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

[jira] [Resolved] (HBASE-25764) Generate CHANGES.md and RELEASENOTES.md for 2.2.7

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25764.

Resolution: Fixed

> Generate CHANGES.md and RELEASENOTES.md for 2.2.7
> -
>
> Key: HBASE-25764
> URL: https://issues.apache.org/jira/browse/HBASE-25764
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25765) Set version as 2.2.7 in branch-2.2

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25765.

Fix Version/s: 2.2.7
   Resolution: Fixed

> Set version as 2.2.7 in branch-2.2
> --
>
> Key: HBASE-25765
> URL: https://issues.apache.org/jira/browse/HBASE-25765
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.7
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[VOTE] The first HBase 2.2.7 release candidate (RC0) is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.7.
Meanwhile, as branch-2.2 will be EOL, please don't push new commits to it.
And this will be the last one of the 2.2.x releases. Thanks.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.2.7
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.2.7RC0. The release files, including
signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/

Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1440/

Signatures used for HBase RCs can be found in this file:
https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.7 can be found in included
CHANGES.md and RELEASENOTES.md available here:
https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/RELEASENOTES.md

A detailed source and binary compatibility report for this release is
available at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/api_compare_2.2.7RC0_to_2.2.6.html

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

[jira] [Created] (HBASE-25765) Set version as 2.2.7 in branch-2.2

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25765:
--

 Summary: Set version as 2.2.7 in branch-2.2
 Key: HBASE-25765
 URL: https://issues.apache.org/jira/browse/HBASE-25765
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25764) Generate CHANGES.md and RELEASENOTES.md for 2.2.7

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25764:
--

 Summary: Generate CHANGES.md and RELEASENOTES.md for 2.2.7
 Key: HBASE-25764
 URL: https://issues.apache.org/jira/browse/HBASE-25764
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25427) [branch-2.2] Fix the ruby problem for pre-commit

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25427.

Fix Version/s: 2.2.7
 Assignee: Guanghao Zhang
   Resolution: Fixed

> [branch-2.2] Fix the ruby problem for pre-commit
> 
>
> Key: HBASE-25427
> URL: https://issues.apache.org/jira/browse/HBASE-25427
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.6
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.7
>
>
> *00:33:07*  ERROR:  Error installing rubocop:*00:33:07*  
> parallel requires Ruby version >= 2.4.*00:33:08*  Successfully installed 
> jaro_winkler-1.5.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25605) Try ignore the ExportSnapshot related unit tests for branch-2.2

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25605.

  Assignee: Guanghao Zhang
Resolution: Fixed

> Try ignore the ExportSnapshot related unit tests for branch-2.2
> ---
>
> Key: HBASE-25605
> URL: https://issues.apache.org/jira/browse/HBASE-25605
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.7
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25605) Try ignore the ExportSnapshot related unit tests

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25605:
--

 Summary: Try ignore the ExportSnapshot related unit tests
 Key: HBASE-25605
 URL: https://issues.apache.org/jira/browse/HBASE-25605
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25545) Fix the build problem for branch-2.2

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25545.

Resolution: Fixed

Pushed to branch-2.2. Thanks [~meiyi] for reviewing.

> Fix the build problem for branch-2.2
> 
>
> Key: HBASE-25545
> URL: https://issues.apache.org/jira/browse/HBASE-25545
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 2.2.7
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25545) Fix the build problem for branch-2.2

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25545:
--

 Summary: Fix the build problem for branch-2.2
 Key: HBASE-25545
 URL: https://issues.apache.org/jira/browse/HBASE-25545
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.2.7
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25544) Release 2.2.7

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25544:
--

 Summary: Release 2.2.7
 Key: HBASE-25544
 URL: https://issues.apache.org/jira/browse/HBASE-25544
 Project: HBase
  Issue Type: Umbrella
Reporter: Guanghao Zhang


As discussed in [https://s.apache.org/7rqow] , the stable pointer had been 
moved to 2.3.x and the final release for 2.2.x will be 2.2.7.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25426) [branch-2.2] Fix the ruby problem for pre-commit

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25426.

Resolution: Duplicate

Duplicate with HBASE-25426.

> [branch-2.2] Fix the ruby problem for pre-commit
> 
>
> Key: HBASE-25426
> URL: https://issues.apache.org/jira/browse/HBASE-25426
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.6
>        Reporter: Guanghao Zhang
>Priority: Major
>
> *00:33:07*  ERROR:  Error installing rubocop:*00:33:07*  
> parallel requires Ruby version >= 2.4.*00:33:08*  Successfully installed 
> jaro_winkler-1.5.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25427) [branch-2.2] Fix the ruby problem for pre-commit

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25427:
--

 Summary: [branch-2.2] Fix the ruby problem for pre-commit
 Key: HBASE-25427
 URL: https://issues.apache.org/jira/browse/HBASE-25427
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Guanghao Zhang


*00:33:07*  ERROR:  Error installing rubocop:*00:33:07*parallel 
requires Ruby version >= 2.4.*00:33:08*  Successfully installed 
jaro_winkler-1.5.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25426) [branch-2.2] Fix the ruby problem for pre-commit

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25426:
--

 Summary: [branch-2.2] Fix the ruby problem for pre-commit
 Key: HBASE-25426
 URL: https://issues.apache.org/jira/browse/HBASE-25426
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Guanghao Zhang


*00:33:07*  ERROR:  Error installing rubocop:*00:33:07*parallel 
requires Ruby version >= 2.4.*00:33:08*  Successfully installed 
jaro_winkler-1.5.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[DISCUSS] Move the stable pointer to 2.3.x and EOM for branch-2.2?

[Guanghao Zhang]

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?

[ANNOUNCE] New HBase committer Xin Sun

[Guanghao Zhang]

Folks,

On behalf of the Apache HBase PMC I am pleased to announce that Xin Sun has
accepted the PMC's invitation to become a committer on the project.

We appreciate all of the great contributions Xin Sun has made to the
community thus far and we look forward to his continued involvement.

Allow me to be the first to congratulate Xin Sun on his new role!

Thanks.

[ANNOUNCE] New HBase committer Yulin Niu

[Guanghao Zhang]

Folks,

On behalf of the Apache HBase PMC I am pleased to announce that Yulin Niu
has accepted the PMC's invitation to become a committer on the project.

We appreciate all of the great contributions Yulin has made to the
community thus far and we look forward to his continued involvement.

Allow me to be the first to congratulate Yulin on his new role!

Thanks.

[jira] [Resolved] (HBASE-25324) Remove unnecessary array to list conversion in SplitLogManager

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25324.

Fix Version/s: 2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2 and master. Thanks [~yuqi] for contributing.

> Remove unnecessary array to list conversion in SplitLogManager
> --
>
> Key: HBASE-25324
> URL: https://issues.apache.org/jira/browse/HBASE-25324
> Project: HBase
>  Issue Type: Improvement
>Reporter: yuqi
>Assignee: yuqi
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> {code:java}
>   public static List getFileList(final Configuration conf, final 
> List logDirs,
>   final PathFilter filter)
>   throws IOException {
> List fileStatus = new ArrayList<>();
> 
> FileStatus[] a = new FileStatus[fileStatus.size()];
> //list to array
> return fileStatus.toArray(a);
>   }
>   public List getWALsToSplit(ServerName serverName, boolean 
> splitMeta)
>   throws IOException {
> List logDirs = 
> master.getMasterWalManager().getLogDirs(Collections.singleton(serverName));
> FileStatus[] fileStatuses =
> SplitLogManager.getFileList(this.conf, logDirs, splitMeta ? 
> META_FILTER : NON_META_FILTER);
> LOG.info("{} WAL count={}, meta={}", serverName, fileStatuses.length, 
> splitMeta);
> //array convert to list which is just contrary to the logic of  
> getFileList
> return Lists.newArrayList(fileStatuses);
>   
> {code}
> After judge the logic, there seems no need to make such a conversion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25323) Fix potential NPE when the zookeeper path of RegionServerTracker does not exist when start

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25323.

Fix Version/s: 2.3.4
   2.2.7
   2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~yuqi] for contributing.

> Fix potential NPE when the zookeeper path of RegionServerTracker does not 
> exist when start
> --
>
> Key: HBASE-25323
> URL: https://issues.apache.org/jira/browse/HBASE-25323
> Project: HBase
>  Issue Type: Improvement
>Reporter: yuqi
>Assignee: yuqi
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.4
>
> Attachments: image-2020-11-24-16-56-04-411.png, 
> image-2020-11-24-16-58-04-621.png
>
>
>  !image-2020-11-24-16-56-04-411.png! 
>  !image-2020-11-24-16-58-04-621.png! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25281) Bulkload split hfile too many times due to unreasonable split point

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25281.

Fix Version/s: 2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2 and master. Thanks [~niuyulin]  for contributing.

> Bulkload split hfile too many times due to unreasonable split point
> ---
>
> Key: HBASE-25281
> URL: https://issues.apache.org/jira/browse/HBASE-25281
> Project: HBase
>  Issue Type: Improvement
>  Components: tooling
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
> Attachments: bulkload.png
>
>
> [https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/tool/BulkLoadHFilesTool.java#L688]
> if hfile span multi regions, for example A,B,C,D,E,F(the start key of these 
> regions are in ascending order), we should use region C endkey to split, not 
> region A. In this way, we can get equal .top and .bottom hfiles, reduce time 
> complexity of split from O( n ) to O(logn),decrease invoke of {{bulkLoad}} 
> rpc to regionserver ,and also avoid write amplification during 
> {{copyHFileHalf}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25325) Remove unused class ClusterSchemaException

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25325.

Fix Version/s: 2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2 and master. Thanks [~yuqi] for contributing.

> Remove unused class ClusterSchemaException
> --
>
> Key: HBASE-25325
> URL: https://issues.apache.org/jira/browse/HBASE-25325
> Project: HBase
>  Issue Type: Improvement
>Reporter: yuqi
>Assignee: yuqi
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> Currently, ClusterSchemaException is useless, so we can freely delete it



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25282) Remove processingServers in DeadServer as we can get this information by Procedure of master

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25282.

Fix Version/s: 3.0.0-alpha-1
   Resolution: Fixed

Pushed to master. Thanks [~yuqi] for contributing.

> Remove processingServers in DeadServer as we can get this information by 
> Procedure of master
> 
>
> Key: HBASE-25282
> URL: https://issues.apache.org/jira/browse/HBASE-25282
> Project: HBase
>  Issue Type: Improvement
>Reporter: yuqi
>Assignee: yuqi
>Priority: Minor
> Fix For: 3.0.0-alpha-1
>
>
> We can directly get the servers in processing through proceduces in master as 
> long as proceduce is a instance of `ServerCrashProcedure`
> *Our final goal is to remove class `DeadServer`*, the next step is to remove 
> the deadServers attributes in DeadServer and then we can freely delete the 
> class



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25213) Should request Compaction when bulkLoadHFiles is done

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25213.

Resolution: Fixed

Pushed the addendum patch to branch-2 and master.

> Should request Compaction when bulkLoadHFiles is done
> -
>
> Key: HBASE-25213
> URL: https://issues.apache.org/jira/browse/HBASE-25213
> Project: HBase
>  Issue Type: Improvement
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-24654) Allow unset table's rsgroup

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24654.

Resolution: Fixed

Pushed to master. Thanks [~Ddupg] for contributing.

> Allow unset table's rsgroup
> ---
>
> Key: HBASE-24654
> URL: https://issues.apache.org/jira/browse/HBASE-24654
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> In TableDescriptorBuilder, we have only one method to set rsgroup, but have 
> no one to unset it. this unset method is necessary In some cases.
> If the table had rsgroup config before, but now I want to use the namespace 
> config. It doesn't work that I set table rsgroup config to default rsgroup, 
> must remove rsgroup config.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25113) [testing] HBaseCluster support ReplicationServer for UTs

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25113.

Resolution: Fixed

Merged. Thanks [~Ddupg] for contributing.

> [testing] HBaseCluster support ReplicationServer for UTs
> 
>
> Key: HBASE-25113
> URL: https://issues.apache.org/jira/browse/HBASE-25113
> Project: HBase
>  Issue Type: Sub-task
>  Components: Replication
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25213) Should request Compaction when bulkLoadHFiles is done

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25213.

Fix Version/s: 2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Merged. Thanks [~niuyulin] for contributing.

> Should request Compaction when bulkLoadHFiles is done
> -
>
> Key: HBASE-25213
> URL: https://issues.apache.org/jira/browse/HBASE-25213
> Project: HBase
>  Issue Type: Improvement
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25300) 'Unknown table hbase:quota' happens when desc table in shell if quota disabled

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25300.

Fix Version/s: 2.3.4
   2.2.7
   2.4.0
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~Ddupg] for contributing.

> 'Unknown table hbase:quota' happens when desc table in shell if quota disabled
> --
>
> Key: HBASE-25300
> URL: https://issues.apache.org/jira/browse/HBASE-25300
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.4
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] HBASE-25299 Scan#setRowPrefixFilter Unexpected behavior

[Guanghao Zhang]

I am +1 to deprecated setRowPrefixFilter method. This method name is
setRowPrefixFilter but not use filter and only set start row and end row. I
thought this could be done by user.

唐天航  于2020年11月19日周四 上午12:45写道：

> Hi,
>   I have opened an issue HBASE-25299
>  about
> Scan#setRowPrefixFilter
> Unexpected behavior.
>
> e.g.
>
> startRow : "112"
>
> rowPrefixFilter : "11"
>
> The Result of this scan might contain : "111", which is unexpected.
>
>   public Scan setRowPrefixFilter(byte[] rowPrefix) {
> if (rowPrefix == null) {
>   setStartRow(HConstants.EMPTY_START_ROW);
>   setStopRow(HConstants.EMPTY_END_ROW);
> } else {
>   this.setStartRow(rowPrefix);
>   this.setStopRow(calculateTheClosestNextRowKeyForPrefix(rowPrefix));
> }
> return this;
>   }
>
>  Scan#setRowPrefixFilter achieves this function by setting startRow and
> stopRow, ignoring the situation that startRow may have been set.
>
>
> I have discussed this issue with @infraio and he suggested to deprecate
> this method because modifying it may cause compatibility issues.
>
> Is this plan acceptable? Hope to get some suggestions.
>
>
> Thank you. Regards
>

[jira] [Resolved] (HBASE-25289) [testing] Clean up resources after tests in rsgroup_shell_test.rb

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25289.

Fix Version/s: 2.3.4
   2.4.0
   Resolution: Fixed

Pushed to branch-2.3 and branch-2. Thanks [~Ddupg] for contributing.

> [testing] Clean up resources after tests in rsgroup_shell_test.rb
> -
>
> Key: HBASE-25289
> URL: https://issues.apache.org/jira/browse/HBASE-25289
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup, test
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0, 2.3.4
>
>
> In rsgroup_shell_test.rb, some tests don't remove rsgroups and drop tables, 
> messing up adding new tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25296) [Documentation] fix duplicate conf entry

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25296.

Resolution: Fixed

Pushed to master. Thanks [~tangtianhang] for contributing.

> [Documentation] fix duplicate conf entry
> 
>
> Key: HBASE-25296
> URL: https://issues.apache.org/jira/browse/HBASE-25296
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: tianhang tang
>Assignee: tianhang tang
>Priority: Trivial
>
> [hbase.rolling.restart|https://hbase.apache.org/book.html#hbase.rolling.restart]
> {panel:title=HBase 2.0+ can no longer read Sequence File based WAL file.}
> HBase can no longer read the deprecated WAL files written in the Apache 
> Hadoop Sequence File format. The hbase.regionserver.hlog.reader.impl and 
> hbase.regionserver.hlog.reader.impl configuration entries should be set to 
> use the Protobuf based WAL reader / writer classes. This implementation has 
> been the default since HBase 0.96, so legacy WAL files should not be a 
> concern for most downstream users.
> {panel}
> It should be:
> "The _hbase.regionserver.hlog.reader.impl_ and 
> _hbase.regionserver.hlog.writer.impl_ "...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25295) Refactor the locate WAL logic in ReplicationSource

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25295:
--

 Summary: Refactor the locate WAL logic in ReplicationSource
 Key: HBASE-25295
 URL: https://issues.apache.org/jira/browse/HBASE-25295
 Project: HBase
  Issue Type: Bug
  Components: Replication
Reporter: Guanghao Zhang


When cluster replication enabled and one RegionServer crashed, its WALs will be 
move from WALs dir to oldWALs dir and its replication queue will moved to other 
RegionServer's replication queue.
 
HDFS layout (WAL Storage)
/hbase/WALs/RS1/1.log
/hbase/WALs/RS1/2.log
/hbase/WALs/RS1/3.log
ZooKeeper layout (Replication queue storage)
/hbase/replication/rs/RS1/peerId/1.log
/hbase/replication/rs/RS1/peerId/2.log
/hbase/replication/rs/RS1/peerId/3.log
 
Failover finished:
HDFS layout (WAL Storage)
/hbase/.oldWALs/1.log
/hbase/.oldWALs/2.log
/hbase/.oldWALs/3.log
ZooKeeper layout (Replication queue storage)
/hbase/replication/rs/RS2/peerId-RS1/1.log
/hbase/replication/rs/RS2/peerId-RS1/2.log
/hbase/replication/rs/RS2/peerId-RS1/3.log
 
And if enabled hbase.separate.oldlogdir.by.regionserver, the HDFS layout may be:
HDFS layout (WAL Storage)
/hbase/.oldWALs/RS1/1.log
/hbase/.oldWALs/RS1/2.log
/hbase/.oldWALs/RS1/3.log
 
Then if RS2 crashed, the HDFS layout will not change but ZooKeeper layout may 
changed.
ZooKeeper layout (Replication queue storage)
/hbase/replication/rs/RS3/peerId-RS1-RS2/1.log
/hbase/replication/rs/RS3/peerId-RS1-RS2/2.log
/hbase/replication/rs/RS3/peerId-RS1-RS2/3.log
 
So even the replication queue was transfered many times, the HDFS layout never 
change.
 
Another case is master-cluster disaster, the failover work not finished. Then 
ReplicationSyncUp tool can start replication source to replicate the WAL data. 
The HDFS layout need to consider two more case:
/hbase/WALs/RS1/1.log
/hbase/WALs/RS1/2.log
/hbase/WALs/RS1/3.log
or
/hbase/WALs/RS1-splitting/1.log
/hbase/WALs/RS1-splitting/2.log
/hbase/WALs/RS1-splitting/3.log



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25276) Need to throw the original exception in HRegion#openHRegion

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25276.

Fix Version/s: 2.3.4
   2.2.7
   2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~niuyulin] for contributing.

> Need to throw the original exception in HRegion#openHRegion
> ---
>
> Key: HBASE-25276
> URL: https://issues.apache.org/jira/browse/HBASE-25276
> Project: HBase
>  Issue Type: Bug
>    Reporter: Guanghao Zhang
>Assignee: niuyulin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.4
>
>
> {code:java}
> protected HRegion openHRegion(final CancelableProgressable reporter)
> throws IOException {
>   try {
> ..
>   } catch(Throwable t) {
> // By coprocessor path wrong region will open failed,
> // MetricsRegionWrapperImpl is already init and not close,
> // add region close when open failed
> this.close(); // This may throw IOException too.
> throw t;
>   }
>   return this;
> }
> {code}
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java#L8144
> this.close() may throw IOException too. The original exception will not be 
> recorded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25276) Need to throw the original exception in HRegion#openHRegion

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25276:
--

 Summary: Need to throw the original exception in 
HRegion#openHRegion
 Key: HBASE-25276
 URL: https://issues.apache.org/jira/browse/HBASE-25276
 Project: HBase
  Issue Type: Bug
Reporter: Guanghao Zhang


{code:java}
protected HRegion openHRegion(final CancelableProgressable reporter)
throws IOException {
  try {
..
  } catch(Throwable t) {
// By coprocessor path wrong region will open failed,
// MetricsRegionWrapperImpl is already init and not close,
// add region close when open failed
this.close(); // This may throw IOException too.
throw t;
  }
  return this;
}
{code}
https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java#L8144

this.close() may throw IOException too. The original exception will not be 
recorded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25071) ReplicationServer support start ReplicationSource internal

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25071.

Resolution: Fixed

Merged. Thanks all for reviewing.

> ReplicationServer support start ReplicationSource internal
> --
>
> Key: HBASE-25071
> URL: https://issues.apache.org/jira/browse/HBASE-25071
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-24999) Master manages ReplicationServers

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24999.

Resolution: Fixed

Merged. Thanks [~Ddupg] for contributing.

> Master manages ReplicationServers
> -
>
> Key: HBASE-24999
> URL: https://issues.apache.org/jira/browse/HBASE-24999
> Project: HBase
>  Issue Type: Sub-task
>  Components: Replication
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
>
> In [HBASE-24683|https://issues.apache.org/jira/browse/HBASE-24683] add an 
> isolated ReplicationServer.
> What this issue is to do: 
>  # ReplicationServer reports to Master periodically.
>  # Add a basic ReplicationServerManager in Master to manage ReplicationServer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25225) Create table very slowly if there are multi regions

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25225:
--

 Summary: Create table very slowly if there are multi regions
 Key: HBASE-25225
 URL: https://issues.apache.org/jira/browse/HBASE-25225
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Guanghao Zhang


Run the same UT TestRegionReplicaFailover on my local PC, mvn clean test 
-Dtest=TestRegionReplicaFailover, branch-2.2 takes 8 mins but branch-2.3 only 
needs 2 mins. 
 
I found the problem is related to procedure schedule. See the below log:
2020-10-21 13:52:28,097 INFO  [PEWorker-1] procedure2.ProcedureExecutor(1427): 
Finished pid=296, ppid=45, state=SUCCESS; 
org.apache.hadoop.hbase.master.assignment.OpenRegionProcedure in 1.6250sec
2020-10-21 13:52:28,538 INFO  [PEWorker-3] procedure2.ProcedureExecutor(1427): 
Finished pid=45, ppid=20, state=SUCCESS; TransitRegionStateProcedure 
table=testLotsOfRegionRepli2, region=50703895da3cb8c942d3197600d549bc, ASSIGN 
in 59.4330sec
 
The real assign procedure only cost 1.6 seconds but the 
TransitRegionStateProcedure cost 59.4 seconds. The pid=45 procedure was 
initialized at 2020-10-21 13:51:28,666. It was added to TableQueue at 
2020-10-21 13:51:28,789. But took xlock to run at 2020-10-21 13:52:24,761. See 
the below log:
{color:#ff}2020-10-21 13:51:28,789{color} DEBUG [PEWorker-4] 
procedure.MasterProcedureScheduler(352): Add TableQueue(testLotsOfRegionRepli2, 
xlock=true (20) sharedLock=0 size=25) to run queue because: pid=45, ppid=20, 
state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE; 
TransitRegionStateProcedure table=testLotsOfRegionRepli2, 
region=50703895da3cb8c942d3197600d549bc, ASSIGN has the excusive lock access
{color:#ff}2020-10-21 13:52:24,761{color} INFO  [PEWorker-2] 
procedure.MasterProcedureScheduler(737): Took xlock for pid=45, ppid=20, 
state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE; 
TransitRegionStateProcedure table=testLotsOfRegionRepli2, 
region=50703895da3cb8c942d3197600d549bc, ASSIGN
 
 
But when I tried this UT on another PC, it only cost 2 mins, which is the same 
with branch-2.3. It is weird.
 
Marked this as blocker for release 2.2.7.
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25128) RSGroupInfo's toString() and hashCode() does not take into account configuration map.

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25128.

Fix Version/s: 2.4.0
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2 and master. Thanks [~sanjeetnishad] for contributing.

> RSGroupInfo's toString() and hashCode() does not take into account 
> configuration map.
> -
>
> Key: HBASE-25128
> URL: https://issues.apache.org/jira/browse/HBASE-25128
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup
>Affects Versions: 2.2.3
>Reporter: Sanjeet Nishad
>Assignee: Sanjeet Nishad
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> RSGroupInfo's toString() and hashcode() methods should include Configurations 
> as well which is added as a part of HBASE-24431.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Procedure schedule slowly when run branch-2.2 UT TestRegionReplicaFailover

[Guanghao Zhang]

More procedure workers (hbase.master.procedure.threads 5 => 16) can reduce
the time from 8 mins to 6 mins. But branch-2.3 used the same 5 procedure
workers.

Guanghao Zhang  于2020年10月22日周四 下午2:22写道：

> And I am sure that it is not the lock problem, because there is no
> "Waiting on xlock for" log.
>
> LOG.info("Waiting on xlock for {} held by pid={}", procedure,
>   regionLocks[i].getExclusiveLockProcIdOwner());
>
> Guanghao Zhang  于2020年10月22日周四 下午2:12写道：
>
>> Run the same UT TestRegionReplicaFailover on my local PC, mvn clean test
>> -Dtest=TestRegionReplicaFailover, branch-2.2 takes 8 mins but branch-2.3
>> only needs 2 mins.
>>
>> I found the problem is related to procedure schedule. See the below log:
>> 2020-10-21 13:52:28,097 INFO  [PEWorker-1]
>> procedure2.ProcedureExecutor(1427): Finished pid=296, ppid=45,
>> state=SUCCESS;
>> org.apache.hadoop.hbase.master.assignment.OpenRegionProcedure in 1.6250sec
>> 2020-10-21 13:52:28,538 INFO  [PEWorker-3]
>> procedure2.ProcedureExecutor(1427): Finished pid=45, ppid=20,
>> state=SUCCESS; TransitRegionStateProcedure table=testLotsOfRegionRepli2,
>> region=50703895da3cb8c942d3197600d549bc, ASSIGN in 59.4330sec
>>
>> The real assign procedure only cost 1.6 seconds but
>> the TransitRegionStateProcedure cost 59.4 seconds. The pid=45 procedure was
>> initialized at 2020-10-21 13:51:28,666. It was added to TableQueue
>> at 2020-10-21 13:51:28,789. But took xlock to run at 2020-10-21
>> 13:52:24,761. See the below log:
>> 2020-10-21 13:51:28,789 DEBUG [PEWorker-4]
>> procedure.MasterProcedureScheduler(352): Add
>> TableQueue(testLotsOfRegionRepli2, xlock=true (20) sharedLock=0 size=25) to
>> run queue because: pid=45, ppid=20,
>> state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
>> TransitRegionStateProcedure table=testLotsOfRegionRepli2,
>> region=50703895da3cb8c942d3197600d549bc, ASSIGN has the excusive lock access
>> 2020-10-21 13:52:24,761 INFO  [PEWorker-2]
>> procedure.MasterProcedureScheduler(737): Took xlock for pid=45, ppid=20,
>> state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
>> TransitRegionStateProcedure table=testLotsOfRegionRepli2,
>> region=50703895da3cb8c942d3197600d549bc, ASSIGN
>>
>>
>> But when I tried this UT on another PC, it only cost 2 mins, which is the
>> same with branch-2.3. It is weird. Any ideas about this? Thanks.
>>
>

Re: Procedure schedule slowly when run branch-2.2 UT TestRegionReplicaFailover

[Guanghao Zhang]

And I am sure that it is not the lock problem, because there is no "Waiting
on xlock for" log.

LOG.info("Waiting on xlock for {} held by pid={}", procedure,
  regionLocks[i].getExclusiveLockProcIdOwner());

Guanghao Zhang  于2020年10月22日周四 下午2:12写道：

> Run the same UT TestRegionReplicaFailover on my local PC, mvn clean test
> -Dtest=TestRegionReplicaFailover, branch-2.2 takes 8 mins but branch-2.3
> only needs 2 mins.
>
> I found the problem is related to procedure schedule. See the below log:
> 2020-10-21 13:52:28,097 INFO  [PEWorker-1]
> procedure2.ProcedureExecutor(1427): Finished pid=296, ppid=45,
> state=SUCCESS;
> org.apache.hadoop.hbase.master.assignment.OpenRegionProcedure in 1.6250sec
> 2020-10-21 13:52:28,538 INFO  [PEWorker-3]
> procedure2.ProcedureExecutor(1427): Finished pid=45, ppid=20,
> state=SUCCESS; TransitRegionStateProcedure table=testLotsOfRegionRepli2,
> region=50703895da3cb8c942d3197600d549bc, ASSIGN in 59.4330sec
>
> The real assign procedure only cost 1.6 seconds but
> the TransitRegionStateProcedure cost 59.4 seconds. The pid=45 procedure was
> initialized at 2020-10-21 13:51:28,666. It was added to TableQueue
> at 2020-10-21 13:51:28,789. But took xlock to run at 2020-10-21
> 13:52:24,761. See the below log:
> 2020-10-21 13:51:28,789 DEBUG [PEWorker-4]
> procedure.MasterProcedureScheduler(352): Add
> TableQueue(testLotsOfRegionRepli2, xlock=true (20) sharedLock=0 size=25) to
> run queue because: pid=45, ppid=20,
> state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
> TransitRegionStateProcedure table=testLotsOfRegionRepli2,
> region=50703895da3cb8c942d3197600d549bc, ASSIGN has the excusive lock access
> 2020-10-21 13:52:24,761 INFO  [PEWorker-2]
> procedure.MasterProcedureScheduler(737): Took xlock for pid=45, ppid=20,
> state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
> TransitRegionStateProcedure table=testLotsOfRegionRepli2,
> region=50703895da3cb8c942d3197600d549bc, ASSIGN
>
>
> But when I tried this UT on another PC, it only cost 2 mins, which is the
> same with branch-2.3. It is weird. Any ideas about this? Thanks.
>

Procedure schedule slowly when run branch-2.2 UT TestRegionReplicaFailover

[Guanghao Zhang]

Run the same UT TestRegionReplicaFailover on my local PC, mvn clean test
-Dtest=TestRegionReplicaFailover, branch-2.2 takes 8 mins but branch-2.3
only needs 2 mins.

I found the problem is related to procedure schedule. See the below log:
2020-10-21 13:52:28,097 INFO  [PEWorker-1]
procedure2.ProcedureExecutor(1427): Finished pid=296, ppid=45,
state=SUCCESS;
org.apache.hadoop.hbase.master.assignment.OpenRegionProcedure in 1.6250sec
2020-10-21 13:52:28,538 INFO  [PEWorker-3]
procedure2.ProcedureExecutor(1427): Finished pid=45, ppid=20,
state=SUCCESS; TransitRegionStateProcedure table=testLotsOfRegionRepli2,
region=50703895da3cb8c942d3197600d549bc, ASSIGN in 59.4330sec

The real assign procedure only cost 1.6 seconds but
the TransitRegionStateProcedure cost 59.4 seconds. The pid=45 procedure was
initialized at 2020-10-21 13:51:28,666. It was added to TableQueue
at 2020-10-21 13:51:28,789. But took xlock to run at 2020-10-21
13:52:24,761. See the below log:
2020-10-21 13:51:28,789 DEBUG [PEWorker-4]
procedure.MasterProcedureScheduler(352): Add
TableQueue(testLotsOfRegionRepli2, xlock=true (20) sharedLock=0 size=25) to
run queue because: pid=45, ppid=20,
state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
TransitRegionStateProcedure table=testLotsOfRegionRepli2,
region=50703895da3cb8c942d3197600d549bc, ASSIGN has the excusive lock access
2020-10-21 13:52:24,761 INFO  [PEWorker-2]
procedure.MasterProcedureScheduler(737): Took xlock for pid=45, ppid=20,
state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
TransitRegionStateProcedure table=testLotsOfRegionRepli2,
region=50703895da3cb8c942d3197600d549bc, ASSIGN


But when I tried this UT on another PC, it only cost 2 mins, which is the
same with branch-2.3. It is weird. Any ideas about this? Thanks.

[jira] [Reopened] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang reopened HBASE-25186:


Reopen for branch-2. Failed to mvn package.

> TestMasterRegionOnTwoFileSystems is failing after HBASE-25065
> -
>
> Key: HBASE-25186
> URL: https://issues.apache.org/jira/browse/HBASE-25186
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Affects Versions: 3.0.0-alpha-1, 2.4.0
>Reporter: ramkrishna.s.vasudevan
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> After HBASE-25065, we are having a test case failure with 
> TestMasterRegionOnTwoFileSystems. 
> The reason is that we manually trigger a WAL roll on the master region. As 
> part of the WAL roll we expect the Master region's WAL will also be moved 
> from region oldWAL dir to the global oldWAL directory. This happens after 
> afterRoll() method in AbstractWALRoller. 
> Since  now the WAL archival is asynchronous the afterRoll() method does not 
> find any WAL file to be moved in the local region oldWAL dir. So the movement 
> to global oldWAL dir does not happen. 
> The test case checks for the file in the oldWAL dir and since it is not found 
> the test timesout. WE need a way to fix this. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25204) Nightly job failed as the name of jdk and maven changed

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25204.

Fix Version/s: 2.2.7
   1.4.14
   2.4.0
   1.7.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to all active branchs. Thanks [~zhangduo] for reviewing.

> Nightly job failed as  the name of jdk and maven changed
> 
>
> Key: HBASE-25204
> URL: https://issues.apache.org/jira/browse/HBASE-25204
> Project: HBase
>  Issue Type: Bug
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 1.7.0, 2.4.0, 1.4.14, 2.2.7
>
>
> See 
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/85/console]
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/103/console]
>  
> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
> failed: WorkflowScript: 508: Tool type "maven" does not have an install of 
> "Maven (latest)" configured - did you mean "maven_latest"? @ line 508, column 
> 19. maven 'Maven (latest)' ^ WorkflowScript: 510: Tool type "jdk" does not 
> have an install of "JDK 1.8 (latest)" configured - did you mean 
> "jdk_1.8_latest"? @ line 510, column 17. jdk "JDK 1.8 (latest)"
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: branch-2.2/branch-2.3 nightly jon failed to run

[Guanghao Zhang]

Opened HBASE-25204 to fix this.

张铎(Duo Zhang)  于2020年10月20日周二 下午12:40写道：

> Master is failing too, the same problem.
>
>
> https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/98/console
>
> I think it is what Nick said, the name of jdk and maven seems to be
> changed. Mind opening an issue to fix it Guanghao?
>
> Thanks.
>
>
>
> Sean Busbey  于2020年10月20日周二 上午11:42写道：
>
> > that sounds probable given the symptoms.
> >
> > On Mon, Oct 19, 2020 at 9:16 PM Nick Dimiduk 
> wrote:
> > >
> > > The Jenkins server was restarted within the last 24 hours, presumably
> for
> > > maintenance. Maybe they changed the name of this binary mapping without
> > > telling us?
> > >
> > > On Mon, Oct 19, 2020 at 17:42 Guanghao Zhang 
> wrote:
> > >
> > > > See
> > > >
> > > >
> >
> https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/85/console
> > > >
> > > >
> >
> https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/103/console
> > > >
> > > > org.codehaus.groovy.control.MultipleCompilationErrorsException:
> startup
> > > > failed:
> > > > WorkflowScript: 508: Tool type "maven" does not have an install of
> > > > "Maven (latest)" configured - did you mean "maven_latest"? @ line
> 508,
> > > > column 19.
> > > >maven 'Maven (latest)'
> > > >  ^
> > > >
> > > > WorkflowScript: 510: Tool type "jdk" does not have an install of "JDK
> > > > 1.8 (latest)" configured - did you mean "jdk_1.8_latest"? @ line 510,
> > > > column 17.
> > > >jdk "JDK 1.8 (latest)"
> > > >
> > > >
> > > > But the Jenkinsfile did not change recently. Any ideas?
> > > >
> >
> >
> >
> > --
> > Sean
> >
>

[jira] [Created] (HBASE-25204) Nightly job failed as the name of jdk and maven changed

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25204:
--

 Summary: Nightly job failed as  the name of jdk and maven changed
 Key: HBASE-25204
 URL: https://issues.apache.org/jira/browse/HBASE-25204
 Project: HBase
  Issue Type: Bug
Reporter: Guanghao Zhang


See 
[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/85/console]
[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/103/console]
 
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: 
WorkflowScript: 508: Tool type "maven" does not have an install of "Maven 
(latest)" configured - did you mean "maven_latest"? @ line 508, column 19. 
maven 'Maven (latest)' ^ WorkflowScript: 510: Tool type "jdk" does not have an 
install of "JDK 1.8 (latest)" configured - did you mean "jdk_1.8_latest"? @ 
line 510, column 17. jdk "JDK 1.8 (latest)"
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

branch-2.2/branch-2.3 nightly jon failed to run

[Guanghao Zhang]

See
https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/85/console
https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/103/console

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 508: Tool type "maven" does not have an install of
"Maven (latest)" configured - did you mean "maven_latest"? @ line 508,
column 19.
   maven 'Maven (latest)'
 ^

WorkflowScript: 510: Tool type "jdk" does not have an install of "JDK
1.8 (latest)" configured - did you mean "jdk_1.8_latest"? @ line 510,
column 17.
   jdk "JDK 1.8 (latest)"


But the Jenkinsfile did not change recently. Any ideas?

[jira] [Created] (HBASE-25200) Try enlarge the flaky test timeout for branch-2.2

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25200:
--

 Summary: Try enlarge the flaky test timeout for branch-2.2
 Key: HBASE-25200
 URL: https://issues.apache.org/jira/browse/HBASE-25200
 Project: HBase
  Issue Type: Bug
Reporter: Guanghao Zhang


Now there are too many flaky tests to run. And the flaky test job cannot 
finished. Then these tests will be marked to flaky again.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25177) Try create table with 100 regions for branch-2.2 nightly job's hadoop integration test

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25177.

Resolution: Won't Fix

> Try create table with 100 regions for branch-2.2 nightly job's hadoop 
> integration test
> --
>
> Key: HBASE-25177
> URL: https://issues.apache.org/jira/browse/HBASE-25177
> Project: HBase
>  Issue Type: Bug
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
>
> It still failed now.
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88/execution/node/171/log/]
>  
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88//artifact/output-integration/hadoop-2.log]
>  
> It failed when create table with 1000 regions. And not import the example TSV 
> to HDFS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25178) Remove the hadoop 3.3.0 personality hadoopcheck for branch-2.2/branch-2.3

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25178.

Resolution: Duplicate

Already fixed by HBASE-25144.

> Remove the hadoop 3.3.0 personality hadoopcheck for branch-2.2/branch-2.3
> -
>
> Key: HBASE-25178
> URL: https://issues.apache.org/jira/browse/HBASE-25178
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.6
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
>
> For branch-2.2, see 
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88/execution/node/163/log/]
>  It will fail when run "mvn clean install -DskipTests -DHBasePatchProcess 
> -Dhadoop-three.version=3.3.0 -Dhadoop.profile=3.0".
>  
> For branch-2.3, see HBASE-23834. HBase failed to start on hadoop 3.3.0 
> because the jetty problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25178) Fix the LICENSE error when branch-2.2 build with hadoop 3.3.0

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25178:
--

 Summary: Fix the LICENSE error when branch-2.2 build with hadoop 
3.3.0 
 Key: HBASE-25178
 URL: https://issues.apache.org/jira/browse/HBASE-25178
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.2.6
Reporter: Guanghao Zhang


See 
[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88/execution/node/163/log/]

 

It will fail when run "mvn clean install -DskipTests -DHBasePatchProcess 
-Dhadoop-three.version=3.3.0 -Dhadoop.profile=3.0".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25177) Try create table with 100 regions for branch-2.2 nightly job's hadoop integration test

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25177:
--

 Summary: Try create table with 100 regions for branch-2.2 nightly 
job's hadoop integration test
 Key: HBASE-25177
 URL: https://issues.apache.org/jira/browse/HBASE-25177
 Project: HBase
  Issue Type: Bug
Reporter: Guanghao Zhang


It still failed now.

[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88/execution/node/171/log/]

 

[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/88//artifact/output-integration/hadoop-2.log]

 

It failed when create table with 1000 regions. And not import the example TSV 
to HDFS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25172) No need timelineservice for branch-2.2 nightly job's hadoop integration test

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25172.

Resolution: Fixed

> No need timelineservice for branch-2.2 nightly job's hadoop integration test
> 
>
> Key: HBASE-25172
> URL: https://issues.apache.org/jira/browse/HBASE-25172
> Project: HBase
>  Issue Type: Bug
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.7
>
>
> [https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/86/execution/node/171/log/]
>  
>  
> /home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_branch-2.2/component/dev-support/hbase_nightly_pseudo-distributed-test.sh
>  --single-process --working-dir output-integration/hadoop-2 
> --hbase-client-install hbase-client hbase-install hadoop-2/bin/hadoop 
> {color:#ff}hadoop-2/share/hadoop/yarn/timelineservice{color} 
> hadoop-2/share/hadoop/yarn/test/hadoop-yarn-server-tests-2.8.5-tests.jar 
> hadoop-2/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.8.5-tests.jar
>  hadoop-2/bin/mapred
>   
> branch-2.2 still use hadoop 2.8.5 and hadoop 2.8.5 doesn't have 
> timelineservice. The dev-support/hbase_nightly_pseudo-distributed-test.sh not 
> consider this timelineservice and only consider 5 paramerters. But 
> branch-2.3+ use 2.10.x hadoop, so they consider 6 parameters.
>  
> And for hadoop-3, the timelineservice is not used, too. See 
> [https://github.com/apache/hbase/blob/master/dev-support/hbase_nightly_pseudo-distributed-test.sh#L286]
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25172) No need timelineservice for branch-2.2 nightly job's hadoop integration test

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25172:
--

 Summary: No need timelineservice for branch-2.2 nightly job's 
hadoop integration test
 Key: HBASE-25172
 URL: https://issues.apache.org/jira/browse/HBASE-25172
 Project: HBase
  Issue Type: Bug
Reporter: Guanghao Zhang


[https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/86/execution/node/171/log/]

 
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_branch-2.2/component/dev-support/hbase_nightly_pseudo-distributed-test.sh
 --single-process --working-dir output-integration/hadoop-2 
--hbase-client-install hbase-client hbase-install hadoop-2/bin/hadoop 
hadoop-2/share/hadoop/yarn/timelineservice 
hadoop-2/share/hadoop/yarn/test/hadoop-yarn-server-tests-2.8.5-tests.jar 
hadoop-2/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.8.5-tests.jar
 hadoop-2/bin/mapred
 

branch-2.2 still use hadoop 2.8.5 and doesn't have timelineservice. The 
dev-support/hbase_nightly_pseudo-distributed-test.sh not consider this.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25110) Add heartbeat for ReplicationServer and dispatch replication sources to ReplicationServer

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25110:
--

 Summary: Add heartbeat for ReplicationServer and dispatch 
replication sources to ReplicationServer
 Key: HBASE-25110
 URL: https://issues.apache.org/jira/browse/HBASE-25110
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-24684) Fetch ReplicationSink servers list from HMaster instead of ZooKeeper

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24684.

Resolution: Fixed

Merged to HBASE-24666.

> Fetch ReplicationSink servers list from HMaster instead of ZooKeeper
> 
>
> Key: HBASE-24684
> URL: https://issues.apache.org/jira/browse/HBASE-24684
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>Assignee: Sun Xin
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25100) conf and conn are assigned twice in HBaseReplicationEndpoint and HBaseInterClusterReplicationEndpoint

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25100.

Resolution: Fixed

Pushed to master. Thanks [~Ddupg] for contributing.

> conf and conn are assigned twice in HBaseReplicationEndpoint and 
> HBaseInterClusterReplicationEndpoint
> -
>
> Key: HBASE-25100
> URL: https://issues.apache.org/jira/browse/HBASE-25100
> Project: HBase
>  Issue Type: Bug
>  Components: Replication
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> In 
> [HBaseReplicationEndpoint.init()|https://github.com/apache/hbase/blob/c312760819ed185cab3a0717a1ea0ff6e8c47a23/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/HBaseReplicationEndpoint.java#L109]
>  and  
> [HBaseInterClusterReplicationEndpoint.init|https://github.com/apache/hbase/blob/c312760819ed185cab3a0717a1ea0ff6e8c47a23/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java#L145]
>  , the latter is a sub-class of the former, conf and conn are assigned twice.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25077) hbck.jsp page loading fails, logs NPE in master log.

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25077.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~arshad.mohammad] for contributing.

> hbck.jsp page loading fails, logs NPE in master log.
> 
>
> Key: HBASE-25077
> URL: https://issues.apache.org/jira/browse/HBASE-25077
> Project: HBase
>  Issue Type: Bug
>  Components: hbck
>Affects Versions: 2.2.3
>Reporter: Ajeet Rai
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> While testing with large data, it is observed that some time hbck page was 
> not accessible and NPE was thrown in log.
>  
> 【Test step】Excat Steps are not known. Observed this while executing below 
> steps
> 1: Test data: 9K regions,~300 issues in my test setup
> 2: run hbck_chore and catalogjanitor_run multiple times 
> 3: Also run balancer so that region movement is happening.
> 4: Observe that HBCK page not available
>  
> 2020-09-21 20:05:31,706 WARN [qtp1698322791-94] server.HttpChannel: /hbck.jsp
>  java.lang.NullPointerException
>  at 
> org.apache.hadoop.hbase.generated.master.hbck_jsp.formatServerName(hbck_jsp.java:37)
>  at 
> org.apache.hadoop.hbase.generated.master.hbck_jsp._jspService(hbck_jsp.java:144)
>  at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:844)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25098) ReplicationStatisticsChore runs in wrong time unit

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25098.

Resolution: Fixed

Pushed to master. Thanks [~Ddupg] for contributing.

> ReplicationStatisticsChore runs in wrong time unit
> --
>
> Key: HBASE-25098
> URL: https://issues.apache.org/jira/browse/HBASE-25098
> Project: HBase
>  Issue Type: Bug
>  Components: Replication
>Affects Versions: 3.0.0-alpha-1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25074) Refactor ReplicationSinkManager: reduce code and make it easy to understand

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25074.

Fix Version/s: 3.0.0-alpha-1
   Resolution: Fixed

Pushed to master. Thanks [~zhangduo] and [~wchevreuil] for reviewing.

> Refactor ReplicationSinkManager: reduce code and make it easy to understand
> ---
>
> Key: HBASE-25074
> URL: https://issues.apache.org/jira/browse/HBASE-25074
> Project: HBase
>  Issue Type: Improvement
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> ReplicationSinkManager only used in HBaseReplicationEndpoint. Move its logic 
> to HBaseReplicationEndpoint inside.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25086) Refactor Replication: move the default ReplicationSinkService implementation out

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25086.

Fix Version/s: 3.0.0-alpha-1
   Resolution: Fixed

Pushed to master. Thanks [~Ddupg] and [~meiyi] for reviewing.

> Refactor Replication: move the default ReplicationSinkService implementation 
> out
> 
>
> Key: HBASE-25086
> URL: https://issues.apache.org/jira/browse/HBASE-25086
> Project: HBase
>  Issue Type: Improvement
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> Now the Replication implements both ReplicationSourceService and 
> ReplicationSinkService interface. But most of code is only related to 
> ReplicationSourceService. Meanwhile, there is a bug when 
> HRegionServer#buildServerLoad, as it not consider the case: 
> ReplicationSourceService implementation is different with 
> ReplicationSinkService.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [ANNOUNCE] New HBase Committer Zheng Wang(王正)

[Guanghao Zhang]

Congratulations and welcome!

Viraj Jasani  于2020年9月24日周四 下午3:24写道：

> Congratulations Zheng Wang. Very well deserved !
>
> On 2020/09/24 02:24:16, 张铎(Duo Zhang)  wrote:
> > On behalf of the Apache HBase PMC, I am pleased to announce that Zheng
> Wang
> > has accepted the PMC's invitation to become a committer on the project.
> We
> > appreciate all of Zheng's generous contributions thus far and look
> forward
> > to his continued involvement.
> >
> > Congratulations and welcome, Zheng Wang!
> >
> > 我很高兴代表Apache HBase PMC宣布王正已接受我们的邀请，成为Apache
> > HBase项目的Committer。感谢王正一直以来为HBase项目做出的贡献，并期待他在未来继续承担更多的责任。
> >
> > 欢迎王正！
> >
>

[jira] [Created] (HBASE-25086) Refactor Replication: move the default ReplicationSinkService implementation out

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25086:
--

 Summary: Refactor Replication: move the default 
ReplicationSinkService implementation out
 Key: HBASE-25086
 URL: https://issues.apache.org/jira/browse/HBASE-25086
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang


Now the Replication implements both ReplicationSourceService and 
ReplicationSinkService interface. But most of code is only related to 
ReplicationSourceService. Meanwhile, there is a bug when buildServerLoad, as it 
not consider the case: ReplicationSourceService implementation is different 
with ReplicationSinkService.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Third HBase 2.3.2 release candidate (RC4) is available

[Guanghao Zhang]

+1(binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_202): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_202): ok
 - mvn clean install -DskipTests
* nightly job: ok
* flaky dashboard: ok, only few flaky tests.


Nick Dimiduk  于2020年9月23日周三 上午5:56写道：

> +1
>
> * API compatibility report looks good: ok
> * Changelog and Jira line up: ok
> * Deployed to a small cluster and ran ITBLL with serverkilling chaos monkey
> for several hours: ok
> * Nightlies up on ci-hadoop are looking solid: ok
>
> I also ran hbase-vote.sh against the artifacts mirrored to svn (at
> https://dist.apache.org/repos/dist/dev/hbase/2.3.2RC4), using both
> Hadoop2 + JDK88 and Hadoop3 + JDK11 (using the patch posted on
> HBASE-25085).
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_222): ok
>  - mvn clean apache-rat:check
> * Rat check (11.0.4): ok
>  - mvn clean apache-rat:check "-D hadoop.profile=3.0"
> * Built from source (1.8.0_222): ok
>  - mvn clean install -DskipTests
> * Built from source (11.0.4): ok
>  - mvn clean install -DskipTests "-D hadoop.profile=3.0"
> * Unit tests pass (1.8.0_222): ok
>  - mvn package -P runSmallTests
> * Unit tests pass (11.0.4): ok
>  - mvn package -P runSmallTests "-D hadoop.profile=3.0"
>
>
> On Sun, Sep 20, 2020 at 10:51 AM Viraj Jasani  wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.3.2RC4
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.3.2
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.3.2RC4:
> >
> >   https://github.com/apache/hbase/tree/2.3.2RC4
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   http://home.apache.org/~vjasani/2.3.2RC4/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1409/
> >
> > Artifacts were signed with the 1C8ADFD5 key which can be found in:
> >
> >   https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > To learn more about Apache hbase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>

[jira] [Created] (HBASE-25074) Refactor ReplicationSinkManager: reduce code and make it easy to understand

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25074:
--

 Summary: Refactor ReplicationSinkManager: reduce code and make it 
easy to understand
 Key: HBASE-25074
 URL: https://issues.apache.org/jira/browse/HBASE-25074
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25071) ReplicationServer support start ReplicationSource internal

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25071:
--

 Summary: ReplicationServer support start ReplicationSource internal
 Key: HBASE-25071
 URL: https://issues.apache.org/jira/browse/HBASE-25071
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-24998) Introduce a ReplicationSourceController interface and decouple ReplicationSourceManager and ReplicationSource

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24998.

  Assignee: Guanghao Zhang
Resolution: Fixed

> Introduce a  ReplicationSourceController interface and decouple 
> ReplicationSourceManager and ReplicationSource
> --
>
> Key: HBASE-24998
> URL: https://issues.apache.org/jira/browse/HBASE-24998
> Project: HBase
>  Issue Type: Sub-task
>        Reporter: Guanghao Zhang
>    Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25069) Display region name instead of encoded region name in HBCK report page.

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25069.

Fix Version/s: 2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.3+. Thanks [~arshad.mohammad] for contributing.

>  Display region name instead of encoded region name in HBCK report page.
> 
>
> Key: HBASE-25069
> URL: https://issues.apache.org/jira/browse/HBASE-25069
> Project: HBase
>  Issue Type: Improvement
>  Components: hbck
>Affects Versions: 3.0.0-alpha-1, 2.3.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0
>
> Attachments: image-2020-09-19-11-39-01-755.png
>
>
> In HMaster UI, in HBCK report, holes, overlaps and unknown server display 
> only encoded region names. 
> In display region encode name does not give any information. like which 
> table, what's the start key etc. 
> I think it is better to display the region name instead of region encoded 
> name.
> !image-2020-09-19-11-39-01-755.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-24991) Replace MovedRegionsCleaner with guava cache

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24991.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~Joseph295] for contributing.

> Replace MovedRegionsCleaner with guava cache
> 
>
> Key: HBASE-24991
> URL: https://issues.apache.org/jira/browse/HBASE-24991
> Project: HBase
>  Issue Type: Improvement
>Reporter: Junhong Xu
>Assignee: Junhong Xu
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Chore is a task executed periodically, here a cache with expired time is 
> enough.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25057) Fix typo "memeber"

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25057.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~doll6777] for contributing.

> Fix typo "memeber"
> --
>
> Key: HBASE-25057
> URL: https://issues.apache.org/jira/browse/HBASE-25057
> Project: HBase
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Hyeran Lee
>Assignee: Hyeran Lee
>Priority: Trivial
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> Fix typo
> Memeber -> Member in several comments



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25047) WAL split edits number is negative in RegionServerUI

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25047.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~Joseph295] for contributing.

> WAL split edits number is negative in RegionServerUI
> 
>
> Key: HBASE-25047
> URL: https://issues.apache.org/jira/browse/HBASE-25047
> Project: HBase
>  Issue Type: Bug
>  Components: UI, wal
>Reporter: Yi Mei
>Assignee: Junhong Xu
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
> Attachments: 2020-09-16 11-38-13屏幕截图.png
>
>
> !2020-09-16 11-38-13屏幕截图.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[ANNOUNCE] Apache HBase 2.2.6 is now available for download

[Guanghao Zhang]

The HBase team is happy to announce the immediate availability of HBase
2.2.6.

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/.

To download 2.2.6, visit our download page:
http://hbase.apache.org/downloads.html

HBase 2.2.6 is the latest release of the HBase 2.2 line, continuing on the
theme of bringing a stable, reliable database to the Apache Big Data
ecosystem and beyond. 2.2.6 includes 124 bug fixes and improvements  done
since the 2.2.5.
The list of 124 changes made since 2.2.5 can be found here:
https://downloads.apache.org/hbase/2.2.6/CHANGES.md

For instructions on verifying ASF release downloads, please see
https://www.apache.org/dyn/closer.cgi#verify

Project member signature keys can be found at
https://www.apache.org/dist/hbase/KEYS

Question, comments, and problems are always welcome at:
dev@hbase.apache.org
u...@hbase.apache.org
user...@hbase.apache.org

Thanks to all who contributed and made this release possible.

Cheers,
The HBase Dev Team

[jira] [Resolved] (HBASE-24584) Release 2.2.6

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24584.

Resolution: Fixed

> Release 2.2.6
> -
>
> Key: HBASE-24584
> URL: https://issues.apache.org/jira/browse/HBASE-24584
> Project: HBase
>  Issue Type: Umbrella
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25036) Set version as 2.2.7-SNAPSHOT in branch-2.2

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25036.

Fix Version/s: 2.2.7
   Resolution: Fixed

Merged. Thanks all for reviewing.

> Set version as 2.2.7-SNAPSHOT in branch-2.2
> ---
>
> Key: HBASE-25036
> URL: https://issues.apache.org/jira/browse/HBASE-25036
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
> Fix For: 2.2.7
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25035) Add 2.2.6 to download page

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25035.

Resolution: Fixed

Merged. Thanks all for reviewing.

> Add 2.2.6 to download page
> --
>
> Key: HBASE-25035
> URL: https://issues.apache.org/jira/browse/HBASE-25035
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guanghao Zhang
>        Assignee: Guanghao Zhang
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25012) HBASE-24359 causes replication missed log of some RemoteException

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25012.

Fix Version/s: 2.4.0
   2.3.3
   Resolution: Fixed

Pushed to branch-2.3+. Thanks [~Ddupg] for contributing.

> HBASE-24359 causes replication missed log of some RemoteException
> -
>
> Key: HBASE-25012
> URL: https://issues.apache.org/jira/browse/HBASE-25012
> Project: HBase
>  Issue Type: Bug
>  Components: Replication
>Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.3.1
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0
>
> Attachments: image-2020-09-11-14-30-27-898.png
>
>
> HBASE-24359 broken the logic of handling exception. In branch2, it even 
> causes some RemoteException log missed.
> [File 
> changed|[https://github.com/apache/hbase/pull/1855/files#diff-1e3f171b19474698601a0752b618af0eL435]]
>  in branch2.
> !image-2020-09-11-14-30-27-898.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25009) Hbck chore logs wrong message when loading regions from RS report

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25009.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+. Thanks [~arshad.mohammad] for contributing.

> Hbck chore logs wrong message when loading regions from RS report
> -
>
> Key: HBASE-25009
> URL: https://issues.apache.org/jira/browse/HBASE-25009
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.3.1
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> {code:java}
> LOG.info("Loaded {} regions from {} regionservers' reports and found {} 
> orphan regions",
> numRegions, rsReports.size(), orphanRegionsOnFS.size());
> {code}
> In above log message orphanRegionsOnFS.size() should be replaced with 
> orphanRegionsOnRS.size() as the regions are loaded from RS not form FS



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25014) ScheduledChore is never triggered when initalDelay > 1.5*period

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-25014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-25014.

Fix Version/s: 2.2.7
   2.4.0
   2.3.3
   Resolution: Fixed

> ScheduledChore is never triggered when initalDelay > 1.5*period
> ---
>
> Key: HBASE-25014
> URL: https://issues.apache.org/jira/browse/HBASE-25014
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.2.3, 2.2.4, 2.2.5
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> In our recent tests, ScheduledChore is never triggered when initalDelay > 
> 1.5*period.
> The cause of the bug is the following:
> The trigger time for a ScheduleChore must be within an acceptable time window 
> that is 1.5 * period. see 
> [here|https://github.com/apache/hbase/blob/e5ca9adc54f9f580f85d21d38217afa97aa79d68/hbase-common/src/main/java/org/apache/hadoop/hbase/ScheduledChore.java#L234]
> timeOfLastRun and timeOfThisRun are two variables that record two adjacent 
> trigger time. [The first initialization of 
> timeOfThisRun|https://github.com/apache/hbase/blob/e5ca9adc54f9f580f85d21d38217afa97aa79d68/hbase-common/src/main/java/org/apache/hadoop/hbase/ScheduledChore.java#L273]
>  is when the ScheduleChore is created, it's not a real trigger time.
> If we set initialDelay > 1.5 period , after initialDelay, the first time when 
> chore is triggered has exceeded the allowed window. Then [cancel the chore 
> and schedule it 
> again|https://github.com/apache/hbase/blob/e5ca9adc54f9f580f85d21d38217afa97aa79d68/hbase-common/src/main/java/org/apache/hadoop/hbase/ChoreService.java#L176].
> So it's stuck in loop when initialDelay > 1.5 period :
> 1.  init timeOfThisRun at a wrong time.
> 2. wait initalDelay
> 3. chore trigger, but exceeded the allowed window.
> 4. cancel chore and schedule it again
> 5. go step 1.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25036) Set version as 2.2.7-SNAPSHOT in branch-2.2

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25036:
--

 Summary: Set version as 2.2.7-SNAPSHOT in branch-2.2
 Key: HBASE-25036
 URL: https://issues.apache.org/jira/browse/HBASE-25036
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-25035) Add 2.2.6 to download page

[Guanghao Zhang (Jira)]

Guanghao Zhang created HBASE-25035:
--

 Summary: Add 2.2.6 to download page
 Key: HBASE-25035
 URL: https://issues.apache.org/jira/browse/HBASE-25035
 Project: HBase
  Issue Type: Sub-task
Reporter: Guanghao Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Move stable pointer to the latest 2.3.x release

[Guanghao Zhang]

I am +1 to move the stable pointer to 2.3.x. For upgrading from 2.2.x to
2.3.x, I thought the key difference is about the ProcedureStore, which is
implemented by "master local region" in 2.3.x. I can take a try for this.

Sean Busbey  于2020年9月1日周二 下午10:27写道：

> I agree that while the perf issues are important they should not hold up
> moving the stable pointer from one minor version to another when both would
> benefit from the changes.
>
> How smooth is the upgrade process from 2.2.x to 2.3.x? The upgrade section
> for it in the ref guide[1] suggests it should smoothly "just work"? How
> confident are we about that in the face of failures?
>
>
> [1]: http://hbase.apache.org/book.html#upgrade2.3
>
> On Tue, Sep 1, 2020 at 3:09 AM 张铎(Duo Zhang) 
> wrote:
>
> > But there is no difference betwee 2.2.x and 2.3.x? The stable pointer is
> > already on 2.2.x now.
> >
> > Pankaj kr  于2020年9月1日周二 上午11:58写道：
> >
> > > We have observed performance degrade in Scan and Bulk load as compared
> to
> > > 1.x, there are couple of JIRAs already in-progress to handle them
> > > HBASE-24754, HBASE-24637 & HBASE-24850.
> > > IMO we should move stable pointer after fixing these important issues.
> > >
> > > Regards,
> > > Pankaj
> > >
> > > -Original Message-
> > > From: Viraj Jasani [mailto:vjas...@apache.org]
> > > Sent: Tuesday, September 1, 2020 12:12 AM
> > > To: dev@hbase.apache.org
> > > Subject: [DISCUSS] Move stable pointer to the latest 2.3.x release
> > >
> > > Hello everyone,
> > >
> > > While voting for 2.2.6 RC0, we had a short discussion reg moving stable
> > > pointer to the latest 2.3.x and the decision was to initiate the
> discuss
> > > thread when 2.3.1 and 2.2.6 are out.
> > >
> > > Since 2.3.1 is already out and our RM is busy with 2.2.6 release
> process,
> > > I am initiating this thread to discuss the same.
> > >
> > > Would you all like to consider moving stable release pointer to 2.3.x
> > > release line?
> > > Given the stabilization efforts and some latest features available with
> > > stable tests, I am +1 for the same.
> > >
> > >
> >
>

Re: [VOTE] The third HBase 2.2.6 release candidate (RC2) is available

[Guanghao Zhang]

Update the bin tar in https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/ as
the revision and the UI language problem. But the
dev-support/create-release scripts still not worked for me. It always
failed in "gpg sign" step.. Sorry for take so long time to release
2.2.6.

For this vote, +1 from me. With 3 binding +1 and 1 non-binging +1. The vote
passed. Thanks all for voting.





Andrew Purtell  于2020年9月11日周五 上午1:07写道：

> [resending to dev@, sorry]
>
> +1 (binding)
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_272): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_272): ok
>  - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_272): ok
>  - mvn package -P runAllTests
>
> On Thu, Sep 3, 2020 at 8:32 PM Guanghao Zhang  wrote:
> >
> >> Please vote on this release candidate (RC2) for Apache HBase 2.2.6.
> >>
> >> The VOTE will remain open for at least 72 hours.
> >>
> >> [ ] +1 Release this package as Apache HBase 2.2.6
> >> [ ] -1 Do not release this package because ...
> >>
> >> The tag to be voted on is 2.2.6RC2. The release files, including
> >> signatures, digests, etc. can be found at:
> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/
> >>
> >> Maven artifacts are available in a staging repository at:
> >> https://repository.apache.org/content/repositories/orgapachehbase-1407
> >>
> >> Signatures used for HBase RCs can be found in this file:
> >> https://dist.apache.org/repos/dist/release/hbase/KEYS
> >>
> >> The list of bug fixes going into 2.2.6 can be found in included
> >> CHANGES.md and RELEASENOTES.md available here:
> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/CHANGES.md
> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/RELEASENOTES.md
> >>
> >> A detailed source and binary compatibility report for this release is
> >> available at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/api_compare_2.2.6RC2_to_2.2.5.html
> >>
> >> To learn more about Apache HBase, please see http://hbase.apache.org/
> >>
> >> Thanks,
> >> Guanghao Zhang
> >>
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

[jira] [Resolved] (HBASE-24982) Disassemble the method replicateWALEntry from AdminService to a new interface ReplicationServerService

[Guanghao Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-24982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang resolved HBASE-24982.

Resolution: Fixed

Merged. Thanks [~Ddupg] for contributing.

> Disassemble the method replicateWALEntry from AdminService to a new interface 
> ReplicationServerService
> --
>
> Key: HBASE-24982
> URL: https://issues.apache.org/jira/browse/HBASE-24982
> Project: HBase
>  Issue Type: Sub-task
>  Components: Replication
>Reporter: Sun Xin
>Assignee: Sun Xin
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] The third HBase 2.2.6 release candidate (RC2) is available

[Guanghao Zhang]

>
> I believe this is already in place in the dev-support/create-release
> scripts.
>

So master branch's dev-support/create-release scripts can be used to
release any other branch's release? Thanks.

Nick Dimiduk  于2020年9月9日周三 上午2:19写道：

> On Mon, Sep 7, 2020 at 2:54 PM Andrew Purtell 
> wrote:
>
> > We should amend our build procedure and scripts to set TZ=UTC and LANG=C
> > in the environment, that should probably avoid such issues in the future.
> >
>
> I believe this is already in place in the dev-support/create-release
> scripts.
>
> > On Sep 7, 2020, at 7:31 AM, Wellington Chevreuil <
> > wellington.chevre...@gmail.com> wrote:
> > >
> > > I noticed Version info is showing Chinese characters in both the UI,
> and
> > > the CLI as well:
> > >
> > > Version 2.2.6, r88c9a386176e2c2b5fd9915d0e9d3ce17d0e456e, 2020年 09月 04日
> > 星期五
> > > 09:46:48 CST
> > >
> > > Would that be an issue for the RC?
> > >
> > >
> > >> Em seg., 7 de set. de 2020 às 08:35, Viraj Jasani  >
> > >> escreveu:
> > >>
> > >> +1 non-binding
> > >>
> > >> * Signature: ok
> > >> * Checksum : ok
> > >> * Rat check (1.8.0_251): ok
> > >> - mvn clean apache-rat:check
> > >> * Built from source (1.8.0_251): ok
> > >> - mvn clean install -DskipTests
> > >> * CRUD: ok
> > >> * Web UI: ok
> > >> * Load 2M rows using LTT on standalone server: ok
> > >> * Unit tests pass (1.8.0_251): ok
> > >> - mvn package -P runSmallTests
> > >>
> > >>
> > >>> On 2020/09/04 03:32:04, Guanghao Zhang  wrote:
> > >>> Please vote on this release candidate (RC2) for Apache HBase 2.2.6.
> > >>>
> > >>> The VOTE will remain open for at least 72 hours.
> > >>>
> > >>> [ ] +1 Release this package as Apache HBase 2.2.6
> > >>> [ ] -1 Do not release this package because ...
> > >>>
> > >>> The tag to be voted on is 2.2.6RC2. The release files, including
> > >>> signatures, digests, etc. can be found at:
> > >>> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/
> > >>>
> > >>> Maven artifacts are available in a staging repository at:
> > >>>
> https://repository.apache.org/content/repositories/orgapachehbase-1407
> > >>>
> > >>> Signatures used for HBase RCs can be found in this file:
> > >>> https://dist.apache.org/repos/dist/release/hbase/KEYS
> > >>>
> > >>> The list of bug fixes going into 2.2.6 can be found in included
> > >>> CHANGES.md and RELEASENOTES.md available here:
> > >>> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/CHANGES.md
> > >>>
> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/RELEASENOTES.md
> > >>>
> > >>> A detailed source and binary compatibility report for this release is
> > >>> available at:
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.6RC2/api_compare_2.2.6RC2_to_2.2.5.html
> > >>>
> > >>> To learn more about Apache HBase, please see
> http://hbase.apache.org/
> > >>>
> > >>> Thanks,
> > >>> Guanghao Zhang
> > >>>
> > >>
> >
>