Re: [ANNOUNCE] Please welcome Viraj Jasani to the Apache HBase PMC

[Sakthi]

Congrats Viraj! Well deserved one.

- Sakthi
On Mon, Oct 5, 2020 at 8:34 PM Geoffrey Jacoby  wrote:

> Congrats, Viraj!
>
> Geoffrey
>
> On Mon, Oct 5, 2020 at 10:03 PM Pankaj kr  wrote:
>
> > Congratulations Viraj...!!
> >
> > Regards,
> > Pankaj
> >
> > -Original Message-
> > From: Andrew Purtell [mailto:apurt...@apache.org]
> > Sent: Monday, October 5, 2020 10:28 PM
> > To: dev ; Hbase-User 
> > Subject: [ANNOUNCE] Please welcome Viraj Jasani to the Apache HBase PMC
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that Viraj
> > Jasani has accepted our invitation to become a PMC member on the HBase
> > project. We appreciate Viraj stepping up to take more responsibility for
> > the project.
> >
> > Please join me in welcoming Viraj to the HBase PMC!
> >
> >
> > As a reminder, if anyone would like to nominate another person as a
> > committer or PMC member, even if you are not currently a committer or PMC
> > member, you can always drop a note to priv...@hbase.apache.org to let us
> > know.
> >
> > --
> > Best regards,
> > Andrew
> >
>

[jira] [Resolved] (HBASE-23295) hbase-connectors HBaseContext should use most recent delegation token

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23295.

Resolution: Fixed

> hbase-connectors HBaseContext should use most recent delegation token
> -
>
> Key: HBASE-23295
> URL: https://issues.apache.org/jira/browse/HBASE-23295
> Project: HBase
>  Issue Type: Bug
>  Components: hbase-connectors
>Affects Versions: connector-1.0.0
>Reporter: István Adamcsik
>Assignee: István Adamcsik
>Priority: Major
> Fix For: connector-1.0.1
>
> Attachments: HBASE-23295.patch
>
>
> For a long-running HBaseContext, it keeps referring to the persisting 
> credential instead of the most recent token. This would cause the Spark job 
> failed due to "token has expired" issue if the HBaseContext's lifetime is 
> longer than the token's lifetime.



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

[jira] [Resolved] (HBASE-23743) Release 1.4.13

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23743.

Resolution: Fixed

> Release 1.4.13
> --
>
> Key: HBASE-23743
> URL: https://issues.apache.org/jira/browse/HBASE-23743
> Project: HBase
>  Issue Type: Task
>  Components: build, community
>Affects Versions: 1.4.13
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 1.4.13
>
>
> over due for 1.4.13. I'll try to use the release manager scripts this time.



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

[jira] [Resolved] (HBASE-22827) Expose multi-region merge in shell and Admin API

[Sakthi (Jira)]

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

Sakthi resolved HBASE-22827.

Resolution: Fixed

> Expose multi-region merge in shell and Admin API
> 
>
> Key: HBASE-22827
> URL: https://issues.apache.org/jira/browse/HBASE-22827
> Project: HBase
>  Issue Type: Improvement
>  Components: Admin, shell
>Reporter: Michael Stack
>Assignee: Sakthi
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.4
>
> Attachments: hbase-22827.branch-2.001.patch
>
>
> HBASE-22777 adds being able to merge more than two regions at once. It is 
> only available internally currently for use by hbck2 doing fixup of overlaps 
> in hbase:meta. This issue is about exposing it via the Admin Interface and in 
> turn, via the shell. Probably best if old two region merge method is 
> deprecated.



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

[ANNOUNCE] Apache HBase 1.4.13 is now available for download.

[Sakthi]

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

Download from http://hbase.apache.org/downloads

Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware. To learn more
about HBase, see https://hbase.apache.org/.

HBase 1.4.13 is a maintenance release in HBase's current stable-1 release
line, continuing on the theme of bringing a stable, reliable database to the
Hadoop and NoSQL communities.

All users of previous releases are encouraged to upgrade to this release.

The full list of fixes included in this release is available at
https://s.apache.org/s8i5w and in the CHANGES.txt file
included in the distribution.

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

Thanks to all the contributors who made this release possible!
Question, comments, and problems are always welcome at: dev@hbase.apache.org

Cheers,
The HBase Dev Team

Re: [VOTE] First Release Candidate for HBase 1.4.13 is available for download

[Sakthi]

+1 (binding) from me as well!

With 7 binding votes & 3 non-binding votes, the vote passed.

Thanks to everyone, who voted. Let me do the needful to push out the
release.

-Sakthi

On Fri, Feb 28, 2020 at 11:44 AM Xu Cang 
wrote:

> +1 (non-binding)
>
> * Signature: pass
> * Checksum : pass
> * Rat check (1.8.0_152-b16): pass
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_152-b16): pass
>  - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_152-b16): pass
>  - mvn package -P runSmallTests
>  * Tested basic WebUI: pass
>
>
> Xu
>
> On Thu, Feb 27, 2020 at 2:07 PM Jan Hentschel
>  wrote:
> >
> > +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
> >
> > Also checked the compatibility report and the release notes.
> >
> > From: Sakthi 
> > Reply-To: "dev@hbase.apache.org" 
> > Date: Monday, February 24, 2020 at 12:20 PM
> > To: HBase Dev List 
> > Subject: [VOTE] First Release Candidate for HBase 1.4.13 is available
> for download
> >
> > Please vote on this release candidate (RC0) for Apache HBase 1.4.13.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 1.4.13
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is '1.4.13RC0' (38bf65a
> > <
> https://github.com/apache/hbase/commit/38bf65a22b7e9320f07aeb27677e4533b9a77ef4
> >
> > ):
> > https://github.com/apache/hbase/tree/1.4.13RC0
> >
> > It's available for download at:
> > https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachehbase-1384/
> >
> > Artifacts are signed with my key (851528A6) published in our KEYS file
> at:
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > A list of the 13 issues resolved in this release can be found at:
> > https://s.apache.org/s8i5w
> >
> > A list of exclude patters for the known flakey tests can be found at:
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.4/
> >
> > A detailed source and binary compatibility report for this release is
> > available at:
> >
> https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/compat-check-report.html
> >
> >
> > *PREFLIGHT CHECKS DONE:*
> > Java Version - Zulu 1.7.0_232-b6
> >
> > Fully-Distributed Mode (3 Nodes)
> >
> > Hadoop Version - 2.7.7
> >
> >
> >
> >-
> >
> >Built bin tarball tarball from Source
> >-
> >
> >Checksums & Signatures - OK
> >-
> >
> >RAT check - OK
> >-
> >
> >ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
> >-
> >
> >LTT (5M) rows - OK
> >-
> >
> >Shell [CRUD Operations] - OK
> >-
> >
> >Web UI, Logs - OK
> >-
> >
> >REST Server - OK
> >-
> >
> >   CRUD Operations, Web UI, Logs - OK
> >   -
> >
> >Thrift Server - OK
> >-
> >
> >   CRUD Operations, Web UI, Logs - OK
> >   -
> >
> >Compatibility Report - OK
> >-
> >
> >HDFS directory structure - OK
> >
> > Java Version - Corretto 1.8.0_222-b10
> > Standalone mode
> >
> >- Built bin tarball from Source
> >-
> >
> >Shell [CRUD Operations] - OK
> >-
> >
> >Web UI, Logs - OK
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Sakthi
> >
>

[jira] [Resolved] (HBASE-23878) Backport HBASE-22040 to branch-2.1

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23878.

Resolution: Fixed

> Backport HBASE-22040 to branch-2.1
> --
>
> Key: HBASE-23878
> URL: https://issues.apache.org/jira/browse/HBASE-23878
> Project: HBase
>  Issue Type: Task
>Reporter: Sakthi
>    Assignee: Sakthi
>Priority: Major
> Fix For: 2.1.10
>
> Attachments: hbase-23878.branch-2.1.001.patch
>
>
> This fix went in to 2.2+. But I feel like it's applicable and could be used 
> in 2.1 as well.



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

Re: [VOTE] First Release Candidate for HBase 1.4.13 is available for download

[Sakthi]

If anyone is in the middle of testing out the RC and would like me to hold
on to the RC for some more time, please call out. Else, I plan to close
this RC by EOD Feb 27th PST.

On Thu, Feb 27, 2020 at 8:22 AM Andrew Purtell  wrote:

> +1 (binding)
>
> * 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): failed, one flake
>  - mvn package -P runAllTests
>
> Flakes:
>
>
> org.apache.hadoop.hbase.regionserver.TestRegionServerAbort.testAbortFromRPC(org.apache.hadoop.hbase.regionserver.TestRegionServerAbort)
>Run 1: TestRegionServerAbort.testAbortFromRPC:138 » IndexOutOfBounds
> Index: 0, Size: ...
>   Run 2: PASS
>
> On Mon, Feb 24, 2020 at 3:20 AM Sakthi  wrote:
>
> > Please vote on this release candidate (RC0) for Apache HBase 1.4.13.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 1.4.13
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is '1.4.13RC0' (38bf65a
> > <
> >
> https://github.com/apache/hbase/commit/38bf65a22b7e9320f07aeb27677e4533b9a77ef4
> > >
> > ):
> > https://github.com/apache/hbase/tree/1.4.13RC0
> >
> > It's available for download at:
> > https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachehbase-1384/
> >
> > Artifacts are signed with my key (851528A6) published in our KEYS file
> at:
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > A list of the 13 issues resolved in this release can be found at:
> > https://s.apache.org/s8i5w
> >
> > A list of exclude patters for the known flakey tests can be found at:
> >
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.4/
> >
> > A detailed source and binary compatibility report for this release is
> > available at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/compat-check-report.html
> >
> >
> > *PREFLIGHT CHECKS DONE:*
> > Java Version - Zulu 1.7.0_232-b6
> >
> > Fully-Distributed Mode (3 Nodes)
> >
> > Hadoop Version - 2.7.7
> >
> >
> >
> >-
> >
> >Built bin tarball tarball from Source
> >-
> >
> >Checksums & Signatures - OK
> >-
> >
> >RAT check - OK
> >-
> >
> >ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
> >-
> >
> >LTT (5M) rows - OK
> >-
> >
> >Shell [CRUD Operations] - OK
> >-
> >
> >Web UI, Logs - OK
> >-
> >
> >REST Server - OK
> >-
> >
> >   CRUD Operations, Web UI, Logs - OK
> >   -
> >
> >Thrift Server - OK
> >-
> >
> >   CRUD Operations, Web UI, Logs - OK
> >   -
> >
> >Compatibility Report - OK
> >-
> >
> >HDFS directory structure - OK
> >
> > Java Version - Corretto 1.8.0_222-b10
> > Standalone mode
> >
> >- Built bin tarball from Source
> >-
> >
> >Shell [CRUD Operations] - OK
> >-
> >
> >Web UI, Logs - OK
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Sakthi
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

[jira] [Reopened] (HBASE-22827) Expose multi-region merge in shell and Admin API

[Sakthi (Jira)]

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

Sakthi reopened HBASE-22827:


> Expose multi-region merge in shell and Admin API
> 
>
> Key: HBASE-22827
> URL: https://issues.apache.org/jira/browse/HBASE-22827
> Project: HBase
>  Issue Type: Improvement
>  Components: Admin, shell
>Reporter: Michael Stack
>Assignee: Sakthi
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: hbase-22827.branch-2.001.patch
>
>
> HBASE-22777 adds being able to merge more than two regions at once. It is 
> only available internally currently for use by hbck2 doing fixup of overlaps 
> in hbase:meta. This issue is about exposing it via the Admin Interface and in 
> turn, via the shell. Probably best if old two region merge method is 
> deprecated.



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

[VOTE] First Release Candidate for HBase 1.4.13 is available for download

[Sakthi]

Please vote on this release candidate (RC0) for Apache HBase 1.4.13.

The VOTE will remain open for at least 72 hours.

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

The tag to be voted on is '1.4.13RC0' (38bf65a
<https://github.com/apache/hbase/commit/38bf65a22b7e9320f07aeb27677e4533b9a77ef4>
):
https://github.com/apache/hbase/tree/1.4.13RC0

It's available for download at:
https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/

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

Artifacts are signed with my key (851528A6) published in our KEYS file at:
https://dist.apache.org/repos/dist/release/hbase/KEYS

A list of the 13 issues resolved in this release can be found at:
https://s.apache.org/s8i5w

A list of exclude patters for the known flakey tests can be found at:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.4/

A detailed source and binary compatibility report for this release is
available at:
https://dist.apache.org/repos/dist/dev/hbase/1.4.13RC0/compat-check-report.html


*PREFLIGHT CHECKS DONE:*
Java Version - Zulu 1.7.0_232-b6

Fully-Distributed Mode (3 Nodes)

Hadoop Version - 2.7.7



   -

   Built bin tarball tarball from Source
   -

   Checksums & Signatures - OK
   -

   RAT check - OK
   -

   ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
   -

   LTT (5M) rows - OK
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK
   -

   REST Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Thrift Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Compatibility Report - OK
   -

   HDFS directory structure - OK

Java Version - Corretto 1.8.0_222-b10
Standalone mode

   - Built bin tarball from Source
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK

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

Thanks,
Sakthi

[jira] [Created] (HBASE-23883) HBase Precommit builds are broken due to some docker/java issue.

[Sakthi (Jira)]

Sakthi created HBASE-23883:
--

 Summary: HBase Precommit builds are broken due to some docker/java 
issue.
 Key: HBASE-23883
 URL: https://issues.apache.org/jira/browse/HBASE-23883
 Project: HBase
  Issue Type: Task
  Components: build
Reporter: Sakthi


For example see: 
https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/1136/console



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

[jira] [Created] (HBASE-23878) Backport HBASE-22040 to branch-2.1

[Sakthi (Jira)]

Sakthi created HBASE-23878:
--

 Summary: Backport HBASE-22040 to branch-2.1
 Key: HBASE-23878
 URL: https://issues.apache.org/jira/browse/HBASE-23878
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


This fix went in to 2.2+. But I feel like it's applicable and could be used in 
2.1 as well.



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

[jira] [Created] (HBASE-23862) Fix flaky TestSnapshotFromMaster in 1.x versions

[Sakthi (Jira)]

Sakthi created HBASE-23862:
--

 Summary: Fix flaky TestSnapshotFromMaster in 1.x versions
 Key: HBASE-23862
 URL: https://issues.apache.org/jira/browse/HBASE-23862
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


HBASE-23658 was about fixing this flakey ut in branch-2+. I think it can be 
backported to branch-1s as well. 18/30 times this test has failed in branch-1, 
10/30 in 1.4 and 3/30 in 1.3.



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

[jira] [Created] (HBASE-23827) Add mergeRegions method to hbck service

[Sakthi (Jira)]

Sakthi created HBASE-23827:
--

 Summary: Add mergeRegions method to hbck service
 Key: HBASE-23827
 URL: https://issues.apache.org/jira/browse/HBASE-23827
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi
 Fix For: 3.0.0, 2.3.0, 2.1.9, 2.2.4


Let's add the mergeRegions method to the hbck service so that hbck2 can use it 
from the client side.



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

[jira] [Created] (HBASE-23826) [HBCK2] Expose Multi-Region merge feature via hbck2

[Sakthi (Jira)]

Sakthi created HBASE-23826:
--

 Summary: [HBCK2] Expose Multi-Region merge feature via hbck2
 Key: HBASE-23826
 URL: https://issues.apache.org/jira/browse/HBASE-23826
 Project: HBase
  Issue Type: Task
  Components: hbase-operator-tools
Reporter: Sakthi
Assignee: Sakthi
 Fix For: hbase-operator-tools-1.1.0


HBase Master can do multi-region merge from: 2.0.6,2.1.6,2.2.1,2.3.0,3.0.0

HBASE-22827 aims at exposing the feature via shell from: 2.3.0 & 3.0.0

Let's use this Jira to track, exposing the access to the multi-region merge 
feature from hbck2 for the versions where shell feature isn't available but the 
master supports the feature: i.e. 2.0.6+,2.1.6+, 2.2.1+



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

[jira] [Resolved] (HBASE-23180) Add a hbck2 testing tool

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23180.

Resolution: Fixed

> Add a hbck2 testing tool
> 
>
> Key: HBASE-23180
> URL: https://issues.apache.org/jira/browse/HBASE-23180
> Project: HBase
>  Issue Type: Task
>Reporter: Sakthi
>    Assignee: Sakthi
>Priority: Major
>  Labels: hbck2
> Fix For: hbase-operator-tools-1.1.0
>
>
> Quoting myself from the discussion thread from the dev mailing list "*How do 
> we test hbck2?*" -
> "Planning to start working on a nightly build that can spin up a 
> mini-cluster, load some data into it, do some actions to bring the cluster 
> into an undesirable state that hbck2 can fix and then invoke the hbck2 to see 
> if things work well.
>  
> Plan is to start small with one of the hbck2 commands and remaining ones can 
> be added incrementally. As of now I would like to start with making sure the 
> job uses one of the hbase versions (probably 2.1.x/2.2.x), we can discuss 
> about the need to run the job against all the present hbase versions/taking 
> in a bunch of hbase versions as input and running against them/or just a 
> single version.
>  
> The job script would be located in our operator-tools repo."



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

[jira] [Created] (HBASE-23748) Include HBASE-21284 to branch-2.2

[Sakthi (Jira)]

Sakthi created HBASE-23748:
--

 Summary: Include HBASE-21284 to branch-2.2
 Key: HBASE-23748
 URL: https://issues.apache.org/jira/browse/HBASE-23748
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


HBASE-21284 was ought to be present in 2.2. But by the time the commit was 
done, the branch had been cut already. Hence this Jira to track it's inclusion.



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

[jira] [Created] (HBASE-23728) Include HBASE-21018 in 2.2 & 2.3

[Sakthi (Jira)]

Sakthi created HBASE-23728:
--

 Summary: Include HBASE-21018 in 2.2 & 2.3
 Key: HBASE-23728
 URL: https://issues.apache.org/jira/browse/HBASE-23728
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi
 Fix For: 2.3.0, 2.2.3


HBASE-21018 is missing from 2.2 & 2.3. This Jira tracks it's addition to these 
branches.



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

[jira] [Created] (HBASE-23727) Port HBASE-20981 in 2.2 & 2.3

[Sakthi (Jira)]

Sakthi created HBASE-23727:
--

 Summary: Port HBASE-20981 in 2.2 & 2.3
 Key: HBASE-23727
 URL: https://issues.apache.org/jira/browse/HBASE-23727
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


HBASE-20981 is present in 2.0, 2.1 & 3. But is missing from 2.2 and 2.3. This 
Jira tracks the addition of that commit.



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

[jira] [Created] (HBASE-23726) Forward-port HBASE-21345 to branch-2.2 & 2.3 as well.

[Sakthi (Jira)]

Sakthi created HBASE-23726:
--

 Summary: Forward-port HBASE-21345 to branch-2.2 & 2.3 as well.
 Key: HBASE-23726
 URL: https://issues.apache.org/jira/browse/HBASE-23726
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


HBASE-21345 is a good addition to branch-2.2 and 2.3. This Jira tracks the 
forward-porting.



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

Re: [DISCUSS] EOM branch-1.3

[Sakthi]

+1

On Sun, Dec 1, 2019 at 6:28 PM Andrew Purtell 
wrote:

> +1 for EOL of 1.3.
>
> Onward to 1.6!
>
>
> > On Dec 1, 2019, at 5:38 PM, Sean Busbey  wrote:
> >
> > Hi folks!
> >
> > It's been about a month since the last 1.3.z release came out. We've
> > been talking about EOM for branch-1.3 for about a year. Most recently,
> > we had a growing consensus[1] to EOM after getting the 1.3.6 release
> > out with the fixes for Jackson in HBASE-22728 out.
> >
> > Looking at the things that have since landed in branch-1.3 and nothing
> > looks critical (these are all Major or Minor)[2]:
> >
> >  - HBASE-23149 hbase shouldPerformMajorCompaction logic is not correct
> >  - HBASE-23185 High cpu usage because getTable()#put() gets config
> > value every time
> >  - HBASE-23261 Region stuck in transition while splitting
> >  - HBASE-18439 Subclasses of o.a.h.h.chaos.actions.Action all use the
> > same logger
> >  - HBASE-23207 Log a region open journal
> >  - HBASE-23250 Log message about CleanerChore delegate initialization
> > should be at INFO
> >
> > Someone on 1.3.6 can get all these same things fixed by upgrading to
> > our current stable release.
> >
> > Releases on 1.3.z started in 2017. The branch has only averaged ~2
> > maintenance releases a year; I think reflecting a lack of community
> > interest in maintaining the branch. For comparison 1.4 started about a
> > year later and has already had twice as many maintenance releases.
> >
> >  - 1.3.0: 2017-01-16
> >  - 1.3.1: 2017-04-21
> >  - 1.3.2: 2018-03-07
> >  - 1.3.2.1: 2018-06-13
> >  - 1.3.3: 2018-12-21
> >  - 1.3.5: 2019-06-10
> >  - 1.3.6: 2019-10-20
> >
> > Any objections to shutting branch-1.3 down? If folks show up down the
> > road and want to do the work of maintaining it for some reason, we can
> > always spin it up again.
> >
> > [1]:
> >
> > There's more background if you search farther back, but most recently:
> >
> > * "Considering immediate EOL of branch-1.3 and branch-1.4"
> > https://s.apache.org/f32d0
> > * https://issues.apache.org/jira/browse/HBASE-22728
> > * https://issues.apache.org/jira/browse/HBASE-22835
> > * ANNOUNCE for 1.3.6 included a warning
> > "This is ought to be the last release in the 1.3 line unless something
> > critical comes up within in the next month or so."
> >
> > [2]:
> >
> > https://issues.apache.org/jira/projects/HBASE/versions/12346250
>

Re: [ANNOUNCE] New HBase committer Ankit Singhal

[Sakthi]

Congrats Ankit!

On Tue, Nov 12, 2019 at 10:26 PM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:

> Wow, congratulations and welcome, Ankit!
>
> Em ter, 12 de nov de 2019 às 16:39, Josh Elser 
> escreveu:
>
> > On behalf of the Apache HBase PMC, I'm pleased to announce that Ankit
> > Singhal has accepted our invitation to become an HBase committer.
> >
> > Thanks for all of your contributions to the HBase project and we look
> > forward to your continued growth and participation.
> >
> > Congratulations!
> >
>

Re: [ANNOUNCE] Please welcome Balazs Meszaros to the Apache HBase PMC

[Sakthi]

Congrats Balazs! Well done.

On Thu, Oct 24, 2019 at 7:52 AM Guangxu Cheng 
wrote:

> Congratulations, Balazs!
>
> Wellington Chevreuil  于2019年10月24日周四
> 下午10:47写道：
>
> > Congratulations, Balazs!
> >
> > Em qui, 24 de out de 2019 às 15:34, Sean Busbey 
> > escreveu:
> >
> > > On behalf of the Apache HBase PMC I am pleased to announce that
> > > Balazs Meszaros has accepted our invitation to become a PMC member on
> the
> > > HBase project. We appreciate Balazs stepping up to take more
> > > responsibility in the HBase project.
> > >
> > > Please join me in welcoming Balazs to the HBase PMC!
> > >
> > >
> > >
> > > As a reminder, if anyone would like to nominate another person as a
> > > committer or PMC member, even if you are not currently a committer or
> > > PMC member, you can always drop a note to priv...@hbase.apache.org to
> > > let us know.
> > >
> >
>

[jira] [Created] (HBASE-23215) Consider branch-1.3 for EOL status

[Sakthi (Jira)]

Sakthi created HBASE-23215:
--

 Summary: Consider branch-1.3 for EOL status
 Key: HBASE-23215
 URL: https://issues.apache.org/jira/browse/HBASE-23215
 Project: HBase
  Issue Type: Task
Affects Versions: 1.3.6
Reporter: Sakthi


1.3.6 was released on 10th Oct 2019. In around a month or so let's visit the 
status of 1.3 to consider it for EOL. 



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

[jira] [Resolved] (HBASE-23012) Release 1.3.6

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23012.

Resolution: Fixed

> Release 1.3.6
> -
>
> Key: HBASE-23012
> URL: https://issues.apache.org/jira/browse/HBASE-23012
> Project: HBase
>  Issue Type: Task
>  Components: community
>    Reporter: Sakthi
>Assignee: Sakthi
>Priority: Major
> Fix For: 1.3.6
>
>




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

[ANNOUNCE] Apache HBase 1.3.6 is now available for download

[Sakthi]

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

Download from http://hbase.apache.org/downloads

Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware. To learn more
about HBase, see https://hbase.apache.org/.

HBase 1.3.6 is a maintenance release in the HBase 1.3 line,
continuing on the theme of bringing a stable, reliable database to the
Hadoop and NoSQL communities. This is ought to be the last release in the
1.3
line unless something critical comes up within in the next month or so.

All users of previous 1.3.z releases are encouraged to upgrade to either
this release or the latest in our stable release line, which is currently
1.4.10.

The full list of fixes included in this release is available at
https://s.apache.org/0amqk and in the CHANGES.txt file
included in the distribution.

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

Thanks to all the contributors who made this release possible!
Question, comments, and problems are always welcome at: dev@hbase.apache.org

Cheers,
The HBase Dev Team

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

[Sakthi]

+1 (binding)

Java Version - Corretto 1.8.0_222-b10

Fully-Distributed Mode (3 Nodes)

Hadoop Version - 2.8.5



   -

   Built bin tarball tarball from Source
   -

   Checksums & Signatures - OK
   -

   RAT check - OK
   -

   ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK
   -

   REST Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Thrift Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   HDFS directory structure - OK
   -

   CHANGES, RELEASENOTES - *OK*

Just to make sure, the incompatible change in "ClusterMetrics" is being
allowed just because the @InterfaceStability annotation is not used in the
interface because of which the default annotation defaults to "unstable"?

On Thu, Oct 24, 2019 at 1:10 AM Guanghao Zhang  wrote:

> +1 (binding)
>
> hbase-2.2.2-bin.tar.gz (openjdk 1.8.0_202)
> - Verified sha512: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/get/put/scan/delete/disable/drop: ok
> - Checked master/regionserver/table/region Web UI: ok
>
> hbase-2.2.2-src.tar.gz (openjdk 1.8.0_202)
> - Verified sha512: ok
> - Build tarball: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/get/put/scan/delete/disable/drop: ok
> - Checked master/regionserver/table/region Web UI: ok
>
> hbase-2.2.2-client-bin.tar.gz
> - Verified sha512: ok
>
> Sakthi  于2019年10月24日周四 上午11:06写道：
>
> > Will be casting a Vote soon, Duo
> >
> > On Wed, Oct 23, 2019 at 7:54 PM Duo Zhang  wrote:
> >
> > > Reminder. We need more votes here.
> > >
> > > Thanks.
> > >
> > > Duo Zhang  于2019年10月20日周日 下午8:09写道：
> > >
> > > > Note that TestRSGroupsKillRS is broken, but I think it is only a test
> > > > issue, the ConnectionImplementation has been like this for a long
> time
> > > so I
> > > > do not think it is enough to sink an RC.
> > > >
> > > > Filed HBASE-23193 for this. Thanks.
> > > >
> > > > Duo Zhang  于2019年10月20日周日 下午2:16写道：
> > > >
> > > >> Please vote on this Apache hbase release candidate,
> > > >> hbase-2.2.2RC0
> > > >>
> > > >> The VOTE will remain open for at least 72 hours.
> > > >>
> > > >> [ ] +1 Release this package as Apache hbase 2.2.2
> > > >> [ ] -1 Do not release this package because ...
> > > >>
> > > >> The tag to be voted on is 2.2.2RC0:
> > > >>
> > > >> https://github.com/apache/hbase/tree/2.2.2RC0
> > > >>
> > > >> 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.2.2RC0/
> > > >>
> > > >> Maven artifacts are available in a staging repository at:
> > > >>
> > > >>
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1370/
> > > >>
> > > >> Artifacts were signed with the 9AD2AE49 key which can be found in:
> > > >>
> > > >>  https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > >>
> > > >> 2.2.2 includes ~71 bug and improvement fixes done since the 2.2.1.
> We
> > > >> upgrade jackson to 2.9.10 due to CVE-2019-16335 and CVE-2019-14540.
> > > There
> > > >> is also a very nice new feature hbtop, please see HBASE-11062 for
> more
> > > >> details.
> > > >>
> > > >>  To learn more about apache hbase, please see
> > > >> http://hbase.apache.org/
> > > >>
> > > >> Thanks,
> > > >> Your HBase Release Manager
> > > >>
> > > >
> > >
> >
>

Re: [VOTE] First release candidate for Apache HBase 1.4.11

[Sakthi]

+1 (binding)

Java Version - Zulu 1.7.0_232-b6

Fully-Distributed Mode (3 Nodes)

Hadoop Version - 2.7.7



   -

   Built bin tarball tarball from Source
   -

   Checksums & Signatures - OK
   -

   RAT check - OK
   -

   ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
   -

   LTT (5M) rows - OK
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK
   -

   REST Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Thrift Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Compatibility Report - OK
   -

   HDFS directory structure - OK

I think we need more visibility of the some of Interface classifications
(CONFIG, TOOLS etc) in our doc. Have filed HBASE-23214 for that.

-Sakthi

On Wed, Oct 23, 2019 at 5:35 PM Sean Busbey  wrote:

> No worries, will do.
>
> On Wed, Oct 23, 2019, 19:25 Sakthi  wrote:
>
> > Yes Sean. If you could do that, it would be great.
> >
> > Sakthi
> >
> > On Wed, Oct 23, 2019 at 5:23 PM Sean Busbey  wrote:
> >
> > > Anyone in the middle of testing and want me to hold off until tomorrow
> to
> > > close the vote?
> > >
> > > On Fri, Oct 18, 2019, 01:56 Sean Busbey  wrote:
> > >
> > > > Hi folks!
> > > >
> > > > The first release candidate for HBase 1.4.11 is available for
> download:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.11RC0/
> > > >
> > > > Maven artifacts are also available in a staging repository at:
> > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1369/
> > > >
> > > > Artifacts are signed with my key (0D80DB7C) published in our KEYS
> > > > file at http://www.apache.org/dist/hbase/KEYS
> > > >
> > > > The RC corresponds to the signed tag 1.4.11RC0, which currently
> points
> > > > to commit ref
> > > >
> > > > 927981c8a0367b6d0ec2e6c94f12d57592dfa5e3
> > > >
> > > > HBase 1.4.11 is the next maintenance release in the HBase 1.4 line,
> > > > continuing on the theme of bringing a stable, reliable database to
> the
> > > > Hadoop and NoSQL communities. This release includes approximately one
> > > > hundred fixes and improvements done by the HBase community in the
> four
> > > > months since the prior release.
> > > >
> > > > The detailed source and binary compatibility report vs 1.4.10 has
> been
> > > > published for your review, at:
> > > >
> > > > https://s.apache.org/hbase-1.4.11-rc0-compat-report
> > > >
> > > > The report shows some binary incompatible changes to two interfaces
> > > > marked as LimitedPrivate. One set is to interfaces that are marked
> for
> > > > the CONFIG audience, which should mean only their class names needs
> to
> > > > remain the same (and they do) . The other change is to the Region
> > > > interface in order to solve a critical error in the way bulkloaded
> > files
> > > > are handled by the replication system.
> > > >
> > > > Critical changes include:
> > > >
> > > > * HBASE-22784 Clusters in a cyclical replication topology that only
> > have
> > > >   incoming writes from replication never clean out WALs.
> > > > * HBASE-23101 replication of bulkloaded files must handle cyclical
> > > >   topologies. Includes binary incompatible change to
> Region
> > > >   interface.
> > > > * HBASE-23015 Stop including Jackson libraries in classpaths except
> > when
> > > >   needed by the HBase REST Proxy or by Apache Hadoop.
> > > > * HBASE-22728, HBASE-23174 update HBase REST Proxy to use Jackson 2
> for
> > > >   serialization (CVEs).
> > > > * HBASE-22627 Recovered WAL directories not getting cleaned up when
> > > >   running different WAL and base filesystems.
> > > > * HBASE-15666 New utility artifact for testing shaded client:
> > > >   hbase-shaded-testing-util.
> > > > * HBASE-22874 Define a public interface for Canary and move existing
> > > >   implementation to LimitedPrivate
> > > >
> > > > The full set of fixes in this release can be found here:
> > > >
> > > > https://s.apache.org/hbase-1.4.11-jira-release-notes
> > > >
> > > > and in the CHAN

[jira] [Created] (HBASE-23214) Update "Interface Classifications" section of the doc

[Sakthi (Jira)]

Sakthi created HBASE-23214:
--

 Summary: Update "Interface Classifications" section of the doc
 Key: HBASE-23214
 URL: https://issues.apache.org/jira/browse/HBASE-23214
 Project: HBase
  Issue Type: Task
  Components: documentation
Affects Versions: 2.1.7, 1.3.6, 2.2.1, 1.4.10, 1.5.0, 3.0.0, 2.3.0
Reporter: Sakthi


The "Interface Classifications" section of the doc needs to be updated with 
newly added classifications (or the left ones) such as CONFIG, TOOLS etc.



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

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

[Sakthi]

Will be casting a Vote soon, Duo

On Wed, Oct 23, 2019 at 7:54 PM Duo Zhang  wrote:

> Reminder. We need more votes here.
>
> Thanks.
>
> Duo Zhang  于2019年10月20日周日 下午8:09写道：
>
> > Note that TestRSGroupsKillRS is broken, but I think it is only a test
> > issue, the ConnectionImplementation has been like this for a long time
> so I
> > do not think it is enough to sink an RC.
> >
> > Filed HBASE-23193 for this. Thanks.
> >
> > Duo Zhang  于2019年10月20日周日 下午2:16写道：
> >
> >> Please vote on this Apache hbase release candidate,
> >> hbase-2.2.2RC0
> >>
> >> The VOTE will remain open for at least 72 hours.
> >>
> >> [ ] +1 Release this package as Apache hbase 2.2.2
> >> [ ] -1 Do not release this package because ...
> >>
> >> The tag to be voted on is 2.2.2RC0:
> >>
> >> https://github.com/apache/hbase/tree/2.2.2RC0
> >>
> >> 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.2.2RC0/
> >>
> >> Maven artifacts are available in a staging repository at:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachehbase-1370/
> >>
> >> Artifacts were signed with the 9AD2AE49 key which can be found in:
> >>
> >>  https://dist.apache.org/repos/dist/release/hbase/KEYS
> >>
> >> 2.2.2 includes ~71 bug and improvement fixes done since the 2.2.1. We
> >> upgrade jackson to 2.9.10 due to CVE-2019-16335 and CVE-2019-14540.
> There
> >> is also a very nice new feature hbtop, please see HBASE-11062 for more
> >> details.
> >>
> >>  To learn more about apache hbase, please see
> >> http://hbase.apache.org/
> >>
> >> Thanks,
> >> Your HBase Release Manager
> >>
> >
>

Re: [VOTE] First release candidate for Apache HBase 1.4.11

[Sakthi]

Yes Sean. If you could do that, it would be great.

Sakthi

On Wed, Oct 23, 2019 at 5:23 PM Sean Busbey  wrote:

> Anyone in the middle of testing and want me to hold off until tomorrow to
> close the vote?
>
> On Fri, Oct 18, 2019, 01:56 Sean Busbey  wrote:
>
> > Hi folks!
> >
> > The first release candidate for HBase 1.4.11 is available for download:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.11RC0/
> >
> > Maven artifacts are also available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1369/
> >
> > Artifacts are signed with my key (0D80DB7C) published in our KEYS
> > file at http://www.apache.org/dist/hbase/KEYS
> >
> > The RC corresponds to the signed tag 1.4.11RC0, which currently points
> > to commit ref
> >
> > 927981c8a0367b6d0ec2e6c94f12d57592dfa5e3
> >
> > HBase 1.4.11 is the next maintenance release in the HBase 1.4 line,
> > continuing on the theme of bringing a stable, reliable database to the
> > Hadoop and NoSQL communities. This release includes approximately one
> > hundred fixes and improvements done by the HBase community in the four
> > months since the prior release.
> >
> > The detailed source and binary compatibility report vs 1.4.10 has been
> > published for your review, at:
> >
> > https://s.apache.org/hbase-1.4.11-rc0-compat-report
> >
> > The report shows some binary incompatible changes to two interfaces
> > marked as LimitedPrivate. One set is to interfaces that are marked for
> > the CONFIG audience, which should mean only their class names needs to
> > remain the same (and they do) . The other change is to the Region
> > interface in order to solve a critical error in the way bulkloaded files
> > are handled by the replication system.
> >
> > Critical changes include:
> >
> > * HBASE-22784 Clusters in a cyclical replication topology that only have
> >   incoming writes from replication never clean out WALs.
> > * HBASE-23101 replication of bulkloaded files must handle cyclical
> >   topologies. Includes binary incompatible change to Region
> >   interface.
> > * HBASE-23015 Stop including Jackson libraries in classpaths except when
> >   needed by the HBase REST Proxy or by Apache Hadoop.
> > * HBASE-22728, HBASE-23174 update HBase REST Proxy to use Jackson 2 for
> >   serialization (CVEs).
> > * HBASE-22627 Recovered WAL directories not getting cleaned up when
> >   running different WAL and base filesystems.
> > * HBASE-15666 New utility artifact for testing shaded client:
> >   hbase-shaded-testing-util.
> > * HBASE-22874 Define a public interface for Canary and move existing
> >   implementation to LimitedPrivate
> >
> > The full set of fixes in this release can be found here:
> >
> > https://s.apache.org/hbase-1.4.11-jira-release-notes
> >
> > and in the CHANGES.txt file included in the distribution.
> >
> > Please try out this candidate and vote +1/-1 on whether we should
> > release these artifacts as Apache HBase 1.4.11.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > Prior to posting this RC:
> > * Untrusted test list looks normal
> >   https://s.apache.org/hbase-1.4.11-rc0-untrusted-test-list
> > * local build with Zulu JDK 1.7.0_232 and unit tests with Zulu
> >   JDK 1.8.0_222 passes, when using the above untrusted test list.
> > * using WIP pseudo distributed test from HBASE-23162 passes for use of
> >   shaded client and MR artifacts
> > * ltt 1m keys write and then read works. Zulu JDK 1.8.0_222.
> >
> > Thanks!
> >
> > --busbey
> >
> > as of this email the posted artifacts have the following SHA512:
> >
> > hbase-1.4.11-src.tar.gz:
> >
> > 2B45368F 5D0A109D F3101E9F 05FE0ADE 7AE634D9 AFC83AB0
> > B540AFCF 2C64CE9A 7122649E E3CCD6FF 72EDCBDD 2350D4C4
> > 45F96BF2 292BE810 F957A791 581DB1C8
> >
> > hbase-1.4.11-bin.tar.gz:
> >
> > D9006D31 D3B4641B 061F908D D7F4AD13 D041C454 E0FA3383
> > 5109B878 81DB591D 69DDA6DB DC22A88D 16E6C45A FEF69245
> > CF28D4AF 87B83F7C 12578042 0BFB2236
> >
>

Re: [ANNOUNCE] Please welcome Wellington Chevreuil to the Apache HBase PMC

[Sakthi]

Congrats Wellington!

Sakthi

On Wed, Oct 23, 2019 at 1:16 PM Sean Busbey  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Wellington Chevreuil has accepted our invitation to become a PMC member on
> the
> HBase project. We appreciate Wellington stepping up to take more
> responsibility in the HBase project.
>
> Please join me in welcoming Wellington to the HBase PMC!
>
>
>
> As a reminder, if anyone would like to nominate another person as a
> committer or PMC member, even if you are not currently a committer or
> PMC member, you can always drop a note to priv...@hbase.apache.org to
> let us know.
>

Re: [VOTE] Second Release Candidate for HBase 1.3.6 is available for download

[Sakthi]

+1 (non-binding) from me as well!

With 5 binding votes & 3 non-binding votes, the vote passed.

Thanks to everyone, who voted. Let me do the needful to push out the
release.

-Sakthi

On Fri, Oct 18, 2019 at 1:34 AM Francis Christopher Liu <
toffer@gmail.com> wrote:

> +1 (Binding)
>
> Checked:
>
> - Signature & checksums
> - built from source
> - ran unit tests
> - web ui
> - some shell commands
>
> Oddly enough org.apache.hadoop.hbase.ipc.TestIPC fails when run in the
> docker container, even when run individually but passes when I ran it
> individually on my mac.
>
> Also thanks for taking care of the release Sakhti. I was unexpected swamped
> last September.
>
> Thanks,
> Francis
>
>
>
> On Thu, Oct 17, 2019 at 7:16 PM Guangxu Cheng 
> wrote:
>
> > +1
> >
> > - signatures & checksums & rat: OK
> > - built from source (8u102): OK
> > - unit tests: OK
> > - web UI: OK
> > - shell basic commands: OK
> >
> > Andrew Purtell  于2019年10月18日周五 上午1:20写道：
> >
> > > +1 (binding)
> > >
> > > * Signature: ok
> > > * Checksum : ok
> > > * Rat check (1.8.0_172): ok
> > >  - mvn clean apache-rat:check
> > > * Built from source (1.8.0_172): ok
> > >  - mvn clean install -DskipTests
> > > * Unit tests pass (1.8.0_172): failed
> > >  - mvn package -P runAllTests
> > >
> > > TestRegionReplicaFailover ran into trouble with minicluster management
> > > issues (e.g. "IllegalStateException: A mini-cluster is already
> running")
> > > but passed standalone.
> > >
> > >
> > > On Tue, Oct 15, 2019 at 11:42 AM Sakthi  wrote:
> > >
> > > > Please vote on this release candidate (RC1) for Apache HBase 1.3.6.
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache HBase 1.3.6
> > > > [ ] -1 Do not release this package because ...
> > > >
> > > > The tag to be voted on is '1.3.6RC1' (806dc36
> > > > <
> > > >
> > >
> >
> https://github.com/apache/hbase/commit/806dc3625c96fe2cfc03048f3c54a0b38bc9e984
> > > > >
> > > > ):
> > > > https://github.com/apache/hbase/tree/1.3.6RC1
> > > >
> > > > It's available for download at:
> > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC1/
> > > >
> > > > Maven artifacts are available in a staging repository at:
> > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1368/
> > > >
> > > > Artifacts are signed with my key (851528A6) published in our KEYS
> file
> > > at:
> > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > >
> > > > A list of the 73 issues resolved in this release can be found at:
> > > > https://s.apache.org/0amqk
> > > >
> > > > A list of exclude patters for the known flakey tests can be found at:
> > > >
> > > >
> > >
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/
> > > >
> > > > A detailed source and binary compatibility report for this release is
> > > > available at:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC1/compat-check-report.html
> > > >
> > > > The RC includes 1 incompatible change
> > > > - Changes were made to the "Region" public interface to make sure a
> > list
> > > of
> > > > clusterIDs can be passed to the "bulkLoadHFiles" function to break
> > circle
> > > > replication during bulk load.
> > > >
> > > > *PREFLIGHT CHECKS DONE:*
> > > > Java Version - Zulu 1.7.0_232-b6
> > > >
> > > > Fully-Distributed Mode (3 Nodes)
> > > >
> > > > Hadoop Version - 2.7.7
> > > >
> > > >
> > > >
> > > >-
> > > >
> > > >Built bin tarball tarball from Source
> > > >    -
> > > >
> > > >Checksums & Signatures - OK
> > > >-
> > > >
> > > >RAT check - OK
> > > >-
> > > >
> > > >ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) -
> OK
> > > >-
> > > >
> > > >LTT (5M) rows - OK
> > > >-
> > > >
> > > >Shell [CRUD Operations] - OK
> > > >-
> > > >
> > > >Web UI, Logs - OK
> > > >-
> > > >
> > > >REST Server - OK
> > > >-
> > > >
> > > >   CRUD Operations, Web UI, Logs - OK
> > > >   -
> > > >
> > > >Thrift Server - OK
> > > >-
> > > >
> > > >   CRUD Operations, Web UI, Logs - OK
> > > >   -
> > > >
> > > >Compatibility Report - OK
> > > >-
> > > >
> > > >HDFS directory structure - OK
> > > >
> > > > Java Version - Corretto 1.8.0_222-b10
> > > > Standalone mode
> > > >
> > > >- Built bin tarball from Source
> > > >-
> > > >
> > > >Shell [CRUD Operations] - OK
> > > >-
> > > >
> > > >Web UI, Logs - OK
> > > >
> > > > To learn more about Apache HBase, please see
> http://hbase.apache.org/
> > > >
> > > > Thanks,
> > > > Sakthi
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>

Re: [DISCUSS] How do we test hbck2?

[Sakthi]

Sure Peter. Created HBASE-23180 for this.

On Wed, Oct 16, 2019 at 12:33 AM Peter Somogyi  wrote:

> Sounds good!
>
> I'd prefer to run HBCK against 2.2 latest version since that is planned to
> get the stable pointer soon. It is also fine to run the test for 2.1 and
> 2.2 HBase versions.
> Currently there is only a Yetus based pre-commit job for
> hbase-operator-tools. Similarly to the main HBase repository,
> the Jenkinsfile can be stored in hbase-operator-tools.
> In case you need access to builds.a.o for this work you can request access
> from the PMC.
>
> Peter
>
> On Wed, Oct 16, 2019 at 12:02 AM Sakthi  wrote:
>
> > I'm planning to start working on a nightly build that can spin up a
> > mini-cluster, load some data into it, do some actions to bring the
> cluster
> > into an undesirable state that hbck2 can fix and then invoke the hbck2 to
> > see if things work well.
> >
> > Plan is to start small with one of the hbck2 commands and remaining ones
> > can be added incrementally. As of now I would like to start with making
> > sure the job uses one of the hbase versions (probably 2.1.x), we can
> > discuss about the need to run the job against all the present hbase
> > versions/taking in a bunch of hbase versions as input and running against
> > them/or just a single version.
> >
> > The job script would be located in our operator-tools repo. Let me start
> > digging into creation of a nightly job in the operator-tools (I don't
> think
> > we have any as of now). Will create a tracking jira for this. Further
> > discussions regarding this can be delegated to the jira if deemed more
> > convenient.
> >
> > -Sakthi
> >
> > On Mon, Oct 7, 2019 at 11:51 AM Andrew Purtell 
> > wrote:
> >
> > > > We need something different from the chaos monkeys. in this case
> we're
> > > not trying to peturb the cluster in ways we think it should handle;
> we're
> > > setting up a state we already know requires an outside tool.
> > >
> > > Not sure this really falls outside the framework. Add an action that
> > > invokes hbck. Then, add a policy that schedules the hbck invocation as
> > part
> > > of the schedule. That policy would also include the destructive actions
> > > breaking things in a way the tool needs to fix (or HBase can handle
> > > intrinsically...)
> > >
> > > On Tue, Oct 1, 2019 at 2:11 AM Sean Busbey  wrote:
> > >
> > > > I was chatting with Sakthi about automating some testing of hbck2
> > > commands.
> > > > Nothing too fancy, I just want some assurance that they ought to
> work.
> > > >
> > > > This got us talking about how we might purposefully break a cluster
> to
> > > meet
> > > > a set of symptoms that hbck2 knows how to correct. We need something
> > > > different from the chaos monkeys. in this case we're not trying to
> > peturb
> > > > the cluster in ways we think it should handle; we're setting up a
> state
> > > we
> > > > already know requires an outside tool.
> > > >
> > > > Where should this kind of tooling live? Main repo next to the
> monkeys?
> > > > Alongside hbck2 in operator tools? Somewhere else entirely?
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>

[jira] [Created] (HBASE-23180) Create a nightly build to verify hbck2

[Sakthi (Jira)]

Sakthi created HBASE-23180:
--

 Summary: Create a nightly build to verify hbck2
 Key: HBASE-23180
 URL: https://issues.apache.org/jira/browse/HBASE-23180
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


Quoting myself from the discussion thread from the dev mailing list "*How do we 
test hbck2?*" -

"Planning to start working on a nightly build that can spin up a mini-cluster, 
load some data into it, do some actions to bring the cluster into an 
undesirable state that hbck2 can fix and then invoke the hbck2 to see if things 
work well.
 
Plan is to start small with one of the hbck2 commands and remaining ones can be 
added incrementally. As of now I would like to start with making sure the job 
uses one of the hbase versions (probably 2.1.x/2.2.x), we can discuss about the 
need to run the job against all the present hbase versions/taking in a bunch of 
hbase versions as input and running against them/or just a single version.
 
The job script would be located in our operator-tools repo."



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

Re: [DISCUSS] How do we test hbck2?

[Sakthi]

I'm planning to start working on a nightly build that can spin up a
mini-cluster, load some data into it, do some actions to bring the cluster
into an undesirable state that hbck2 can fix and then invoke the hbck2 to
see if things work well.

Plan is to start small with one of the hbck2 commands and remaining ones
can be added incrementally. As of now I would like to start with making
sure the job uses one of the hbase versions (probably 2.1.x), we can
discuss about the need to run the job against all the present hbase
versions/taking in a bunch of hbase versions as input and running against
them/or just a single version.

The job script would be located in our operator-tools repo. Let me start
digging into creation of a nightly job in the operator-tools (I don't think
we have any as of now). Will create a tracking jira for this. Further
discussions regarding this can be delegated to the jira if deemed more
convenient.

-Sakthi

On Mon, Oct 7, 2019 at 11:51 AM Andrew Purtell  wrote:

> > We need something different from the chaos monkeys. in this case we're
> not trying to peturb the cluster in ways we think it should handle; we're
> setting up a state we already know requires an outside tool.
>
> Not sure this really falls outside the framework. Add an action that
> invokes hbck. Then, add a policy that schedules the hbck invocation as part
> of the schedule. That policy would also include the destructive actions
> breaking things in a way the tool needs to fix (or HBase can handle
> intrinsically...)
>
> On Tue, Oct 1, 2019 at 2:11 AM Sean Busbey  wrote:
>
> > I was chatting with Sakthi about automating some testing of hbck2
> commands.
> > Nothing too fancy, I just want some assurance that they ought to work.
> >
> > This got us talking about how we might purposefully break a cluster to
> meet
> > a set of symptoms that hbck2 knows how to correct. We need something
> > different from the chaos monkeys. in this case we're not trying to peturb
> > the cluster in ways we think it should handle; we're setting up a state
> we
> > already know requires an outside tool.
> >
> > Where should this kind of tooling live? Main repo next to the monkeys?
> > Alongside hbck2 in operator tools? Somewhere else entirely?
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

[VOTE] Second Release Candidate for HBase 1.3.6 is available for download

[Sakthi]

Please vote on this release candidate (RC1) for Apache HBase 1.3.6.

The VOTE will remain open for at least 72 hours.

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

The tag to be voted on is '1.3.6RC1' (806dc36
<https://github.com/apache/hbase/commit/806dc3625c96fe2cfc03048f3c54a0b38bc9e984>
):
https://github.com/apache/hbase/tree/1.3.6RC1

It's available for download at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC1/

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

Artifacts are signed with my key (851528A6) published in our KEYS file at:
https://dist.apache.org/repos/dist/release/hbase/KEYS

A list of the 73 issues resolved in this release can be found at:
https://s.apache.org/0amqk

A list of exclude patters for the known flakey tests can be found at:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/

A detailed source and binary compatibility report for this release is
available at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC1/compat-check-report.html

The RC includes 1 incompatible change
- Changes were made to the "Region" public interface to make sure a list of
clusterIDs can be passed to the "bulkLoadHFiles" function to break circle
replication during bulk load.

*PREFLIGHT CHECKS DONE:*
Java Version - Zulu 1.7.0_232-b6

Fully-Distributed Mode (3 Nodes)

Hadoop Version - 2.7.7



   -

   Built bin tarball tarball from Source
   -

   Checksums & Signatures - OK
   -

   RAT check - OK
   -

   ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
   -

   LTT (5M) rows - OK
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK
   -

   REST Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Thrift Server - OK
   -

  CRUD Operations, Web UI, Logs - OK
  -

   Compatibility Report - OK
   -

   HDFS directory structure - OK

Java Version - Corretto 1.8.0_222-b10
Standalone mode

   - Built bin tarball from Source
   -

   Shell [CRUD Operations] - OK
   -

   Web UI, Logs - OK

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

Thanks,
Sakthi

[jira] [Resolved] (HBASE-23101) Backport HBASE-22380 to branch-1

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23101.

Resolution: Fixed

> Backport HBASE-22380 to branch-1
> 
>
> Key: HBASE-23101
> URL: https://issues.apache.org/jira/browse/HBASE-23101
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Wellington Chevreuil
>Assignee: Wellington Chevreuil
>Priority: Blocker
> Fix For: 1.3.6, 1.4.11, 1.5.0
>
>




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

[jira] [Resolved] (HBASE-23128) Restore Region interface compatibility

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23128.

Resolution: Fixed

> Restore Region interface compatibility 
> ---
>
> Key: HBASE-23128
> URL: https://issues.apache.org/jira/browse/HBASE-23128
> Project: HBase
>  Issue Type: Bug
>Reporter: Andrew Kyle Purtell
>Assignee: Andrew Kyle Purtell
>Priority: Blocker
> Fix For: 1.3.6, 1.4.11, 1.5.0
>
>
> Adding methods to a Public interface is ok for a minor release, removing 
> methods is not. We need to restore 
> {code}
> abstract method boolean bulkLoadHFiles (
> Collection>, boolean, Region.BulkLoadListener)
> {code}
> to the Region interface in order to maintain binary compatibility. 



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

[jira] [Reopened] (HBASE-23128) Restore Region interface compatibility

[Sakthi (Jira)]

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

Sakthi reopened HBASE-23128:


> Restore Region interface compatibility 
> ---
>
> Key: HBASE-23128
> URL: https://issues.apache.org/jira/browse/HBASE-23128
> Project: HBase
>  Issue Type: Bug
>Reporter: Andrew Kyle Purtell
>Assignee: Andrew Kyle Purtell
>Priority: Blocker
> Fix For: 1.5.0, 1.4.11
>
>
> Adding methods to a Public interface is ok for a minor release, removing 
> methods is not. We need to restore 
> {code}
> abstract method boolean bulkLoadHFiles (
> Collection>, boolean, Region.BulkLoadListener)
> {code}
> to the Region interface in order to maintain binary compatibility. 



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

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

[Sakthi]

The ITBLL passed. Would definitely need HBASE-23139 in the release to
enable users to run MapReduce jobs. Will sink RC0. RC1 will be out soon.

-Sakthi

On Wed, Oct 9, 2019 at 11:58 PM Sakthi  wrote:

> Tried the ITBLL with this one, failed with "Error:
> java.lang.ClassNotFoundException:
> org.apache.hbase.thirdparty.com.google.gson.GsonBuilder". HBASE-23139
> addresses the issue. Trying out with its inclusion. If it works, will sink
> this RC and create a new one.
>
> On Tue, Oct 8, 2019 at 6:55 PM Sakthi  wrote:
>
>> Please vote on this release candidate (RC0) for Apache HBase 1.3.6.
>>
>> The VOTE will remain open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache HBase 1.3.6
>> [ ] -1 Do not release this package because ...
>>
>> The tag to be voted on is '1.3.6RC0' (69cf8a7bd2):
>> https://github.com/apache/hbase/tree/1.3.6RC0
>>
>> It's available for download at:
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/
>>
>> Maven artifacts are available in a staging repository at:
>> https://repository.apache.org/content/repositories/orgapachehbase-1363/
>>
>> Artifacts are signed with my key (851528A6) published in our KEYS file at:
>> https://dist.apache.org/repos/dist/release/hbase/KEYS
>>
>> A list of the 68 issues resolved in this release can be found at:
>> https://s.apache.org/0amqk
>>
>> A detailed source and binary compatibility report for this release is
>> available at:
>>
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/compat-check-report.html
>>
>> To learn more about Apache HBase, please see http://hbase.apache.org/
>>
>> Thanks,
>> Sakthi
>>
>

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

[Sakthi]

Tried the ITBLL with this one, failed with "Error:
java.lang.ClassNotFoundException:
org.apache.hbase.thirdparty.com.google.gson.GsonBuilder". HBASE-23139
addresses the issue. Trying out with its inclusion. If it works, will sink
this RC and create a new one.

On Tue, Oct 8, 2019 at 6:55 PM Sakthi  wrote:

> Please vote on this release candidate (RC0) for Apache HBase 1.3.6.
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 1.3.6
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is '1.3.6RC0' (69cf8a7bd2):
> https://github.com/apache/hbase/tree/1.3.6RC0
>
> It's available for download at:
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachehbase-1363/
>
> Artifacts are signed with my key (851528A6) published in our KEYS file at:
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> A list of the 68 issues resolved in this release can be found at:
> https://s.apache.org/0amqk
>
> A detailed source and binary compatibility report for this release is
> available at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/compat-check-report.html
>
> To learn more about Apache HBase, please see http://hbase.apache.org/
>
> Thanks,
> Sakthi
>

[VOTE] First release candidate for HBase 1.3.6 is available for download

[Sakthi]

Please vote on this release candidate (RC0) for Apache HBase 1.3.6.

The VOTE will remain open for at least 72 hours.

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

The tag to be voted on is '1.3.6RC0' (69cf8a7bd2):
https://github.com/apache/hbase/tree/1.3.6RC0

It's available for download at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/

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

Artifacts are signed with my key (851528A6) published in our KEYS file at:
https://dist.apache.org/repos/dist/release/hbase/KEYS

A list of the 68 issues resolved in this release can be found at:
https://s.apache.org/0amqk

A detailed source and binary compatibility report for this release is
available at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.6RC0/compat-check-report.html

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

Thanks,
Sakthi

Re: PLEASE FLUSH ALL PENDING COMMITS TO BRANCH-1 TODAY

[Sakthi]

Do RMs need to send out an email saying they are planning to cut out an RC
soon so people need to tag any new upcoming jiras with the next version
(which the RM might have already created?). For 1.3.6 I was blocked on the
canary change. Meanwhile HBASE-23116
 popped up. Because it
was just logging change I didn't mind excluding it from the RC. So I had
bumped up the version to 1.3.7. I was thinking what could be a more cleaner
way of communication?

On Fri, Oct 4, 2019 at 2:42 PM Andrew Purtell  wrote:

> Just to be clear, the commits arent' the issue, backports aren't the issue,
> coordination with the RM is the issue.
>
> On Fri, Oct 4, 2019 at 2:38 PM Andrew Purtell  wrote:
>
> > Got blocked on a couple of half done commits in progress when trying to
> > spin the 1.5.0 RC this afternoon.
> >
> > Going forward we have to be better about this.
> >
> > --
> > 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] [Created] (HBASE-23120) Fix ref guide - example 47

[Sakthi (Jira)]

Sakthi created HBASE-23120:
--

 Summary: Fix ref guide - example 47
 Key: HBASE-23120
 URL: https://issues.apache.org/jira/browse/HBASE-23120
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi
 Fix For: 3.0.0, 1.5.0, 2.3.0, 2.1.7, 2.2.2


The example is of a sample ~/.m2/settings.xml file.
{code:java}

{code}
 is not a proper comment. 

Also I think here,
{code:java}

{code}
the double hyphened --list-keys shouldn't be used. It leads to FATAL error like 
the one below: 
{code:java}
[FATAL] Non-parseable settings
{code}



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

[jira] [Resolved] (HBASE-22735) list_regions may throw an error if a region is RIT

[Sakthi (Jira)]

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

Sakthi resolved HBASE-22735.

Resolution: Fixed

> list_regions may throw an error if a region is RIT
> --
>
> Key: HBASE-22735
> URL: https://issues.apache.org/jira/browse/HBASE-22735
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 1.5.0
>Reporter: Andrew Kyle Purtell
>Assignee: Viraj Jasani
>Priority: Minor
> Fix For: 3.0.0, 1.5.0, 2.3.0, 1.4.11, 2.1.6, 2.2.1
>
> Attachments: HBASE-22735-master-tmp-justforreview.patch, 
> HBASE-22735.branch-1.01.patch, HBASE-22735.branch-1.02.patch, 
> HBASE-22735.branch-1.03.patch, HBASE-22735.branch-1.04.patch, 
> HBASE-22735.master.01.patch, HBASE-22735.master.02.patch, 
> HBASE-22735.master.03.patch, HBASE-22735.master.04.patch, Screen Shot 
> 2019-07-30 at 11.53.53 PM.png
>
>
> The 'list_regions' shell command gets a list of regions for a given table and 
> then prints them and some attributes such as the server where they are 
> located, current request count, data locality, and such. 
> However if a region is in transition the command might fail with
> {{ERROR: undefined method `getDataLocality' for nil:NilClass}}
> and there may be other ways this can happen. Protect against use of nil 
> references and just display what we can. 



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

[jira] [Reopened] (HBASE-22735) list_regions may throw an error if a region is RIT

[Sakthi (Jira)]

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

Sakthi reopened HBASE-22735:


> list_regions may throw an error if a region is RIT
> --
>
> Key: HBASE-22735
> URL: https://issues.apache.org/jira/browse/HBASE-22735
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 1.5.0
>Reporter: Andrew Kyle Purtell
>Assignee: Viraj Jasani
>Priority: Minor
> Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11
>
> Attachments: HBASE-22735-master-tmp-justforreview.patch, 
> HBASE-22735.branch-1.01.patch, HBASE-22735.branch-1.02.patch, 
> HBASE-22735.branch-1.03.patch, HBASE-22735.branch-1.04.patch, 
> HBASE-22735.master.01.patch, HBASE-22735.master.02.patch, 
> HBASE-22735.master.03.patch, HBASE-22735.master.04.patch, Screen Shot 
> 2019-07-30 at 11.53.53 PM.png
>
>
> The 'list_regions' shell command gets a list of regions for a given table and 
> then prints them and some attributes such as the server where they are 
> located, current request count, data locality, and such. 
> However if a region is in transition the command might fail with
> {{ERROR: undefined method `getDataLocality' for nil:NilClass}}
> and there may be other ways this can happen. Protect against use of nil 
> references and just display what we can. 



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

Re: [DISCUSS] How do we test hbck2?

[Sakthi]

Thanks for starting the discussion Sean! Would really like to know what do
folks think about this. I think most of the magic of our hbck tool is left
un-appreciated because of the lack of the proof of correctness that we can
provide along in the form of a constructive “destruction” tool that can be
standalone one or something that takes in a cluster id/zk quorum and do the
same on the cluster.

While trying to test out our operator tools rc, this is one of the friction
that I faced, which I think many other enthusiasts would have probably
faced.

I think for starters, there could be a doc that could just list out the
steps for each of our hbck commands that would bring the cluster in a state
from where hbck could take it further! A tool to follow up would be a great
addition.

-Sakthi

On Tue, Oct 1, 2019 at 2:11 AM Sean Busbey  wrote:

> I was chatting with Sakthi about automating some testing of hbck2 commands.
> Nothing too fancy, I just want some assurance that they ought to work.
>
> This got us talking about how we might purposefully break a cluster to meet
> a set of symptoms that hbck2 knows how to correct. We need something
> different from the chaos monkeys. in this case we're not trying to peturb
> the cluster in ways we think it should handle; we're setting up a state we
> already know requires an outside tool.
>
> Where should this kind of tooling live? Main repo next to the monkeys?
> Alongside hbck2 in operator tools? Somewhere else entirely?
>

Re: [VOTE] HBase Thirdparty 3.0.0 RC0

[Sakthi]

+1 (Non-Binding)

   - Build from Source - *OK*
   - Checksums & Signatures - *OK*
   - RAT check - *OK*
   - Integration with HBase main - *OK*
  - master branch
 - Built with change in the hbase-common pointing to the
 hbase-shaded-gson
 - Build with  Java "1.8.0_201" - *OK*
 - branch-1.3 branch
 - Applied HBASE-23015.branch-1.3.001.patch
 - Changed to use hbase-shaded-gson instead of
 hbase-shaded-miscellaneous in the patch
 - Build with  Java "1.8.0_201" & "1.7.0_80" - *OK*

- Sakthi

On Tue, Sep 24, 2019 at 11:22 PM Ankit Singhal 
wrote:

> @Stack, it seems gson is excluded from miscellaneous[1] so you may require
> new hbase-shaded-gson dependency in hbase-common/pom.xml to get it actually
> working.
>
> [1]
>
> https://github.com/apache/hbase-thirdparty/blame/master/hbase-shaded-miscellaneous/pom.xml#L107
>
> On Tue, Sep 24, 2019 at 8:18 PM Stack  wrote:
>
> > I tried to build against the thirdparty pom but got the below failure:
> >
> > Here is how I changed pom:
> >
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time:  44.578 s
> > [INFO] Finished at: 2019-09-24T20:15:51-07:00
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile
> > (default-compile) on project hbase-common: Compilation failure:
> Compilation
> > failure:
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[24,51]
> > package org.apache.hbase.thirdparty.com.google.gson does not exist
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[25,51]
> > package org.apache.hbase.thirdparty.com.google.gson does not exist
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[26,51]
> > package org.apache.hbase.thirdparty.com.google.gson does not exist
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[27,58]
> > package org.apache.hbase.thirdparty.com.google.gson.stream does not exist
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[28,58]
> > package org.apache.hbase.thirdparty.com.google.gson.stream does not exist
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[44,17]
> > cannot find symbol
> > [ERROR]   symbol:   class GsonBuilder
> > [ERROR]   location: class org.apache.hadoop.hbase.util.GsonUtil
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[46,49]
> > cannot find symbol
> > [ERROR]   symbol:   class TypeAdapter
> > [ERROR]   location: class org.apache.hadoop.hbase.util.GsonUtil
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[45,57]
> > cannot find symbol
> > [ERROR]   symbol:   variable LongSerializationPolicy
> > [ERROR]   location: class org.apache.hadoop.hbase.util.GsonUtil
> > [ERROR]
> >
> >
> /Users/stack/checkouts/hbase.apache.git/hbase-common/src/main/java/org/apache/hadoop/hbase/util/GsonUtil.java:[45,16]
> > cannot find symbol
> > [ERROR]   symbol:   class GsonBuilder
> > [ERROR]   location: class org.apache.hadoop.hbase.util.GsonUtil
> > [ERROR] -> [Help 1]
> > [ERROR]
> >
> >
> > $ git diff pom.xml
> > diff --git a/pom.xml b/pom.xml
> > index 0c1eb0f559..c61b255d85 100755
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -1368,7 +1368,7 @@
> >  2.22.2
> >  2.12
> >  1.0.1
> > -2.2.1
> > +3.0.0
> >  
> >  
> > @@ -3874,4 +3874,11 @@
> >file:///tmp
> >  
> >
> > +
> > +
> > +  test
> > +  test
> > +  
> > https://repository.apache.org/content/repositories/orgapachehbase-1350/
> > 
> > +
> > +  
> >  
> &g

[jira] [Resolved] (HBASE-23000) Backport HBASE-18150 to branch-1.3 to fix consistently failing tests

[Sakthi (Jira)]

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

Sakthi resolved HBASE-23000.

Fix Version/s: 1.3.6
   Resolution: Fixed

> Backport HBASE-18150 to branch-1.3 to fix consistently failing tests
> 
>
> Key: HBASE-23000
> URL: https://issues.apache.org/jira/browse/HBASE-23000
> Project: HBase
>  Issue Type: Sub-task
>  Components: test
>Affects Versions: 1.3.6
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Blocker
>  Labels: backport
> Fix For: 1.3.6
>
>
> Flaky test report: 
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/Flaky_20Test_20Report/dashboard.html#job_2
> In last 30 builds this test failed all 30 times.
> Here is the stack trace: 
> {noformat}
> Stacktrace
> java.io.IOException: Shutting down
>   at 
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> Caused by: java.lang.RuntimeException: Master not initialized after 20ms 
> seconds
>   at 
> org.apache.hadoop.hbase.fs.TestBlockReorder.testBlockLocation(TestBlockReorder.java:428)
> {noformat}
> Link to latest jenkins build: 
> https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-1.3/9351/testReport/org.apache.hadoop.hbase.fs/TestBlockReorder/testBlockLocation/



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HBASE-23013) Please add my public key to committer keys

[Sakthi (Jira)]

Sakthi created HBASE-23013:
--

 Summary: Please add my public key to committer keys
 Key: HBASE-23013
 URL: https://issues.apache.org/jira/browse/HBASE-23013
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
 Attachments: sakthi.asc





--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: Request for assistance with September branch-1.3 and branch-1.4 release candidates

[Sakthi]

Have filed HBASE-23012 to track a 1.3 release and am planning to start the
process soon.

-Sakthi

On Mon, Sep 9, 2019 at 2:01 PM Andrew Purtell  wrote:

> Thanks Rushabh!
>
>
> On Mon, Sep 9, 2019 at 10:19 AM Rushabh Shah
>  wrote:
>
> > Looks like underlying issue for all the failing tests is same. Looks like
> > one change/commit caused failures in all these tests.
> >
> > java.io.IOException: Shutting down
> > at
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad.testAtomicBulkLoad(TestHRegionServerBulkLoad.java:347)
> > Caused by: java.lang.RuntimeException: Master not initialized after
> > 20ms seconds
> > at
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad.testAtomicBulkLoad(TestHRegionServerBulkLoad.java:347)
> >
> >
> > Created https://issues.apache.org/jira/browse/HBASE-23000 for tracking
> > purpose and assigned to myself.
> >
> >
> >
> > Rushabh Shah
> >
> >- Software Engineering SMTS | Salesforce
> >-
> >   - Mobile: 213 422 9052
> >
> >
> >
> > On Sun, Sep 8, 2019 at 6:47 PM Andrew Purtell 
> > wrote:
> >
> > > File a JIRA for each constant failure? Then we can divide up the work.
> At
> > > the least, the task of bisecting to find the breaking change.
> > >
> > > > On Sep 8, 2019, at 6:00 PM, Sean Busbey  wrote:
> > > >
> > > > I've filed HBASE-22991 to track a 1.4 release and have started the
> > > process.
> > > >
> > > > For others looking to help out, branch-1.3 has a few tests that show
> up
> > > as
> > > > always failing according to the flakey report:
> > > >
> > > >
> > >
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.3/Flaky_20Test_20Report/
> > > >
> > > >
> > > >> On Fri, Sep 6, 2019, 20:53 Andrew Purtell 
> > wrote:
> > > >>
> > > >> I have been pretty busy with work and life so haven't had the
> > bandwidth
> > > to
> > > >> make the next set of 1.3 and 1.4 releases, nor another 1.5.0
> candidate
> > > >> either. I have started a few times. I will get as far as observing
> > some
> > > >> issues still in progress targeting the respective release(s) on
> JIRA,
> > or
> > > >> finding that looped unit suite execution reveals a flaky unit test
> or
> > > two
> > > >> deserving of a bit of investigation.
> > > >>
> > > >> Next week I am heading out for vacation for two weeks. Therefore It
> is
> > > >> unlikely I will have any time in the entire month of September for
> > > >> branch-1.3, branch-1.4, or branch-1 release candidates.
> > > >>
> > > >> If someone else would like to contribute time and attention to
> release
> > > >> management, especially for branch-1.3 (1.3.6) and branch-1.4
> (1.4.11),
> > > that
> > > >> would be great. Both of these branches need releasing to get the bug
> > fix
> > > >> out for those code lines where recovered.edits files may be
> misplaced
> > > when
> > > >> root FS != wal FS.
> > > >>
> > > >> If not I'll spin a set when I return, end of September maybe, or
> early
> > > >> October.
> > > >>
> > > >> --
> > > >> 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] [Created] (HBASE-23012) Release 1.3.6

[Sakthi (Jira)]

Sakthi created HBASE-23012:
--

 Summary: Release 1.3.6
 Key: HBASE-23012
 URL: https://issues.apache.org/jira/browse/HBASE-23012
 Project: HBase
  Issue Type: Task
  Components: community
Reporter: Sakthi
Assignee: Sakthi
 Fix For: 1.3.6






--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: Can anyone add 'sandeep.pal' to HBASE contributor on JIRA

[Sakthi]

Done, Xu Cang.

Thanks.

On Mon, Sep 9, 2019 at 2:59 PM Xu Cang  wrote:

> Hi,
> Can anyone add my coworker 'sandeep.pal'  (this is his apache id) to HBASE
> contributor list on JIRA in order for him to be able to assign JIRAs to
> himself?
> Thank you in advance.
>
> Best,
> Xu
>

Re: [VOTE] The second HBase 2.2.1 release candidate (RC1) is available

[Sakthi]

+1 (Non-Binding)

Java Version - java-1.8.0-amazon-corretto-jdk_8.222.10-1

Cluster - Fully-Distributed (3 Nodes)

Hadoop Version - 3.1.2

   - Built bin tarball & client tarball from Source
   - Checksums & Signatures - *OK*
   - RAT check - *OK*
   - ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - *OK*
   - LTT (1M) rows - *OK*
   - Shell [CRUD Operations] - *OK*
   - Web UI, Logs - *OK*
   - REST Server - *OK*
  - CRUD Operations, Web UI, Logs - *OK*
   - Thrift Server - *OK*
  - CRUD Operations, Web UI, Logs - *OK*
   - RS Groups - *OK*
   - CHANGES, RELEASENOTES & Compatibility Report - *OK*
   - HDFS directory structure - *OK*

-Sakthi

On Thu, Sep 5, 2019 at 6:35 PM Guanghao Zhang  wrote:

> +1 from me.
>
> hbase-2.2.1-bin.tar.gz (openjdk 1.8.0_202)
> - Verified sha512sum: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
> - Checked master/regionserver/table/region Web UI: ok
>
> hbase-2.2.1-src.tar.gz (openjdk 1.8.0_202)
> - Verified sha512sum: ok
> - Build tarball: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
> - Checked master/regionserver/table/region Web UI: ok
>
> Guanghao Zhang  于2019年9月4日周三 下午5:52写道：
>
> > Please vote on this release candidate (RC1) for Apache HBase 2.2.1.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 2.2.1
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.2.1RC1. The release files, including
> > signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.1RC1/
> >
> > Maven artifacts are available in a staging repository at:
> > https://repository.apache.org/content/repositories/orgapachehbase-1332/
> >
> > 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.1 can be found in included
> > CHANGES.md and RELEASENOTES.md available here:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.1RC1/CHANGES.md
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.1RC1/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.1RC1/api_compare_2.2.1RC1_to_2.2.0.html
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Guanghao Zhang
> >
>

[jira] [Created] (HBASE-22974) Show Space quotas in the newly added "Quotas" section in the web UI

[Sakthi (Jira)]

Sakthi created HBASE-22974:
--

 Summary: Show Space quotas in the newly added "Quotas" section in 
the web UI
 Key: HBASE-22974
 URL: https://issues.apache.org/jira/browse/HBASE-22974
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


HBASE-22945 added a "Quotas" section in the web ui for the table/user 
throttles. Let's make this a unified place to show all the quotas in hbase. 
This Jira tracks the addition of space quotas info in this web ui.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: Flaky test and HBase-adhoc-run-tests job

[Sakthi]

Thank you for all of your replies. I had a downstream discussion with Sean
regarding this and went ahead with the branch creation. After the jira went
in, i cleaned up the branch, Nick. I'll keep in mind what Peter suggested.
So that means by default nightly and flakies would run on such branches
unless the jenkins file is removed.

Sakthi

On Mon, Sep 2, 2019 at 8:57 AM Sean Busbey  wrote:

> Yep, a branch in the repo is currently needed to test a specific
> change. We could update the job to allow alternative repos, but my
> read of recent rumblings from the ASF infra team is that we'd have to
> lock it down to some particular set of vetted people (i.e. committers
> on the project or a whitelist the PMC maintains).
>
> On Sat, Aug 31, 2019 at 11:02 AM Nick Dimiduk  wrote:
> >
> > Hi Sakthi,
> >
> > I apologize for the delay of reply. I’m not familiar with the details of
> > this job, nor am I a recent participant in the community, so I was hoping
> > someone with more recent experience would answer these questions.
> >
> > To the best of my knowledge, we have no objection to creating
> jira-specific
> > branches in the repo, there are plenty of examples of this in our past.
> > Usually they’re done as a means of multi-developer collaboration, but
> > that’s not by policy. I think what you propose is a fine use-case for
> > pushing a branch. Please observe good hygiene in the shared space and
> clean
> > up after yourself when finished.
> >
> > Thanks,
> > Nick
> >
> > On Thu, Aug 22, 2019 at 14:23 Sakthi  wrote:
> >
> > > Hello,
> > >
> > > I would like to test the fix to one of the flakies (HBASE-22895). For
> that,
> > > I want to utilize our HBase-adhoc-run-tests job to run the test
> repeatedly
> > > (~50 times) with the fix and see if it helps before pushing in the
> fix. I
> > > see that currently we only allow any of the branches from the hbase
> repo to
> > > be used for the testing in the job.
> > >
> > > Does that mean that I can create a branch(HBASE-22895) in the repo,
> push
> > > the fix there, run the job & when the issue is rectified, push the fix
> &
> > > delete the branch? Or is creation of new ad_hoc branches in the repo
> not
> > > really necessary or isn't the right way?
> > >
> > > Would appreciate your suggestions.
> > >
> > > -Sakthi
> > >
>

Re: [DISCUSS] HBCK2 compatibility

[Sakthi]

I like the last idea suggested by Stack. This way the core idea of keeping
both the dev process separate stays intact and also the operators have a
version of hbck to fix their clusters without worrying about compatibility
issues.

On Thu, Aug 29, 2019 at 2:03 PM Stack  wrote:

> Could also just make a release now of hbase-operator-tools (or in a week or
> so when we should have hbck1+ coverage in place) built against an
> up-to-date hbase release. It has the check version before running a feature
> in place where it matters. Operators could use this on all currently
> shipping hbase2s?
>
> S
>
> On Thu, Aug 29, 2019 at 11:42 AM Stack  wrote:
>
> > On Thu, Aug 29, 2019 at 7:34 AM Wellington Chevreuil <
> > wellington.chevre...@gmail.com> wrote:
> >
> >> >
> >> > I do not think we need to compile HBCK2 with every releases?
> >> >
> >> Well, not with every release, was thinking in doing it whenever an hbase
> >> release breaks compatibility.
> >>
> >> We just need
> >> > make sure that it can work with all the releases.
> >>
> >> This could be a solution as well, but I believe it would be harder to
> >> guarantee. Here the problem is:
> >> 1) A new hbase release changes one or more interfaces currently used by
> >> hbck2;
> >> 2) We update hbck2 to depend on this new hbase release, and change hbck2
> >> accordingly;
> >> 3) Operators need to run hbck2 to a previous hbase release. If they try
> to
> >> build hbck2 against that version, it won't compile. If they build it
> with
> >> latest hbase version, it may give a runtime error, and now they have no
> >> working tool to fix the problem.
> >> To avoid #3, we would need to add extra checks on the changes applied on
> >> #2. Might become too complex.
> >>
> >> Thanks Wellington for above. I see issue now.
> >
> > So, we should make retroactive releases of hbase-operator-tools at points
> > just before compat broke? Release could be named for the hbase2 versions
> > supported. Releases would make it easier on operators making it so they
> > don't have to build themselves? There'd be one only? Two maybe?
> >
> > Looking at changes to the Hbck Interface -- using this as gauge for
> > possible breakage points -- there aren't many. One release? Maybe two?
> >
> > S
> >
> >
> >
> >> If there are missing
> >> > methods, we just tell users you can not use several features.
> >>
> >> Fine for new fix options added, but what if some changes break basic,
> >> already working hbck2 methods.
> >>
> >>
> >> Em qui, 29 de ago de 2019 às 14:51, 张铎(Duo Zhang) <
> palomino...@gmail.com>
> >> escreveu:
> >>
> >> > I do not think we need to compile HBCK2 with every releases? We just
> >> need
> >> > make sure that it can work with all the releases. If there are missing
> >> > methods, we just tell users you can not use several features.
> >> >
> >> > Wellington Chevreuil  于2019年8月29日周四
> >> > 下午9:39写道：
> >> >
> >> > > >
> >> > > > bq. what would folks think about going with an hbck2 alpha
> release?
> >> > > > I'm fine with an alpha release but since "HBCK2 should
> continuously
> >> > > evolve"
> >> > > > it might be better to always use the latest codebase whenever you
> >> need
> >> > to
> >> > > > use the tool.
> >> > > >
> >> > > Ideally yes, but that might not always be possible, as hbase API
> might
> >> > > change ahead of hbck2. Operators could then have problems to get a
> >> > working
> >> > > version of hbck2. Since hbck2 already has now many equivalent
> options
> >> for
> >> > > the ones from hbck1, I guess a first release would provide a working
> >> > hbck2
> >> > > that already brings a considerable number of fix methods to help
> with
> >> > most
> >> > > common inconsistencies issues seen in hbase 2 so far. And we could
> >> still
> >> > > fulfil the "HBCK2 should continuously evolve" principle by building
> >> from
> >> > > its master branch, in scenarios where a new fix was needed and
> >> > implemented
> >> > > back into hbck2.
> >> > >
> >> > > Em qui, 29 de ago de 2019 às 14:09, Peter Somogyi <
> >> psomo...@apache.org>
> >> > > escreveu:
> >> > >
> >> > > > bq. Is it possible to put some hacks into HBCK2 to work around
> >> > > > the compatibility to fix the current state
> >> > > >
> >> > > > There are some classes around Replication which were introduced in
> >> > 2.1.0+
> >> > > > so I don't think we could easily solve it for 2.0.
> >> > > > For 2.1.1 the missing method is Hbck#scheduleServerCrashProcedure,
> >> > > probably
> >> > > > that could be solved with some workarounds or using reflection.
> >> > > >
> >> > > > bq. focus more on automation to let us know the next time we
> >> inevitably
> >> > > > break it again? ;)
> >> > > >
> >> > > > Sure! Based on this I think it should be a strong goal. We can set
> >> up
> >> > > > nightly builds for hbase-operator-tools repo that builds against
> the
> >> > > latest
> >> > > > development branches as well as checking compatibility with
> released
> >> > > > versions.
> >> > > >
> >> > > > bq. what 

[jira] [Reopened] (HBASE-22893) Change the comment in HBaseClassTestRule to reflect change in default test timeouts

[Sakthi (Jira)]

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

Sakthi reopened HBASE-22893:


In the section : [http://hbase.apache.org/book.html#hbase.unittests] , 
"Categorizing Tests" -> "Large Tests" needs to be updated to 13 mins. 
[~rabikumar.kc] please do the needful.

> Change the comment in HBaseClassTestRule to reflect change in default test 
> timeouts
> ---
>
> Key: HBASE-22893
> URL: https://issues.apache.org/jira/browse/HBASE-22893
> Project: HBase
>      Issue Type: Bug
>Reporter: Sakthi
>Assignee: Rabi Kumar K C
>Priority: Trivial
>  Labels: beginner, noob
> Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.6
>
>
> The default timeout is 13 minutes. Change the comment accordingly.
> {code}
> // All tests have a 10minute timeout.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (HBASE-22893) Change the comment in HBaseClassTestRule to reflect change in default test timeouts

[Sakthi (Jira)]

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

Sakthi resolved HBASE-22893.

Resolution: Fixed

> Change the comment in HBaseClassTestRule to reflect change in default test 
> timeouts
> ---
>
> Key: HBASE-22893
> URL: https://issues.apache.org/jira/browse/HBASE-22893
> Project: HBase
>  Issue Type: Bug
>    Reporter: Sakthi
>Assignee: Rabi Kumar K C
>Priority: Trivial
>  Labels: beginner, noob
> Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.6
>
>
> The default timeout is 13 minutes. Change the comment accordingly.
> {code}
> // All tests have a 10minute timeout.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HBASE-22927) Upgrade mockito version for Java 11 compatibility

[Sakthi (Jira)]

Sakthi created HBASE-22927:
--

 Summary: Upgrade mockito version for Java 11 compatibility
 Key: HBASE-22927
 URL: https://issues.apache.org/jira/browse/HBASE-22927
 Project: HBase
  Issue Type: Task
Reporter: Sakthi


Pasting the discussion from HBASE-22534 here:

"Currently mockito-core version is at 2.1.0. According to 
[https://github.com/mockito/mockito/blob/release/2.x/doc/release-notes/official.md],
 looks like Java 11 compatibility was introduced in 2.19+. And 2.23.2 claims to 
have full java 11 support after byte-buddy fix etc."



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HBASE-22914) Backport HBASE-20662 to branch-2.2

[Sakthi (Jira)]

Sakthi created HBASE-22914:
--

 Summary: Backport HBASE-20662 to branch-2.2
 Key: HBASE-22914
 URL: https://issues.apache.org/jira/browse/HBASE-22914
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


HBASE-20662 listst 2.2.0 as one of the fix versions, but the release 2.2.0 
doesn't contain the commit as seen here: 
[https://github.com/apache/hbase/commits/rel/2.2.0/hbase-server/src/test/java/org/apache/hadoop/hbase/quotas/TestSpaceQuotas.java]
 here TestSpaceQuotas was actually changed in HBASE-20662 but the release tag 
doesn't list that. Removing the fix version of 2.2.0 from the parent Jira and 
opening thisJira for the missing backport.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Resolved] (HBASE-22910) Enable TestMultiVersionConcurrencyControl

[Sakthi (Jira)]

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

Sakthi resolved HBASE-22910.

Resolution: Fixed

> Enable TestMultiVersionConcurrencyControl
> -
>
> Key: HBASE-22910
> URL: https://issues.apache.org/jira/browse/HBASE-22910
> Project: HBase
>  Issue Type: Task
>  Components: test
>    Reporter: Sakthi
>Assignee: Sakthi
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.6
>
>
> The TestMultiVersionConcurrencyControl doesn't have the test annotation. Not 
> sure why.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HBASE-22910) Enable TestMultiVersionConcurrencyControl

[Sakthi (Jira)]

Sakthi created HBASE-22910:
--

 Summary: Enable TestMultiVersionConcurrencyControl
 Key: HBASE-22910
 URL: https://issues.apache.org/jira/browse/HBASE-22910
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


The TestMultiVersionConcurrencyControl doesn't have the test annotation. Not 
sure why.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Flaky test and HBase-adhoc-run-tests job

[Sakthi]

Hello,

I would like to test the fix to one of the flakies (HBASE-22895). For that,
I want to utilize our HBase-adhoc-run-tests job to run the test repeatedly
(~50 times) with the fix and see if it helps before pushing in the fix. I
see that currently we only allow any of the branches from the hbase repo to
be used for the testing in the job.

Does that mean that I can create a branch(HBASE-22895) in the repo, push
the fix there, run the job & when the issue is rectified, push the fix &
delete the branch? Or is creation of new ad_hoc branches in the repo not
really necessary or isn't the right way?

Would appreciate your suggestions.

-Sakthi

[jira] [Created] (HBASE-22895) Fix the flakey TestSpaceQuotas

[Sakthi (Jira)]

Sakthi created HBASE-22895:
--

 Summary: Fix the flakey TestSpaceQuotas
 Key: HBASE-22895
 URL: https://issues.apache.org/jira/browse/HBASE-22895
 Project: HBase
  Issue Type: Task
  Components: Quotas, test
Reporter: Sakthi
Assignee: Sakthi


branch-2.2 shows this tests frequent failure in one of the rest precommit jobs 
(808,809). Also master branch has this test on it's flakey list. Looks like our 
TestSpaceQuotas is pretty overloaded because of all the sleeps(of 5 seconds) in 
the write-until-policy-violated attempts. Also to verify the violation, our 
number of retries is 10 and each time we sleep 5 secs before checking again. So 
we could often cross the 13 mins limit and get timeout eventually leading to 
appearance of TestSpaceQuotas in the flakey list.

An e.g. here: 
[https://builds.apache.org/view/H-L/view/HBase/job/HBase-adhoc-run-tests/27/]

 

Let's refactor & break TestSpaceQuotas into more tests so that none of the 
tests cross the 13 min limit as we cannot make this into an IntegrationTest.

 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (HBASE-22893) Change to comment in HBaseClassTestRule to reflect change in default test timeouts

[Sakthi (Jira)]

Sakthi created HBASE-22893:
--

 Summary: Change to comment in HBaseClassTestRule to reflect change 
in default test timeouts
 Key: HBASE-22893
 URL: https://issues.apache.org/jira/browse/HBASE-22893
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi


The default timeout is 13 minutes. Change the comment accordingly.

{code}
// All tests have a 10minute timeout.
{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

[Sakthi]

+1 (non-binding)

Java version: Amazon Corretto 8 - Corretto-8.222.10.1 (build 1.8.0_222-b10)

   1. Checksums and signatures(both src and bin): OK
   2. Rat Check: OK
   3. Built from source: OK
   4. Basic Shell CRUD commands: OK
   5. Local Installation mode:
  1. Web UI: OK
  2. LTT with 1M rows: OK

- Sakthi

On Mon, Aug 19, 2019 at 12:08 PM Artem Ervits  wrote:

> changing my vote to +1, recompiled with Hadoop 2.8 and was able to run
> through some shell, MR, etc. Logs, UI look good.
>
> On Sun, Aug 18, 2019 at 12:41 PM Andrew Purtell 
> wrote:
>
> > Like I said on the JIRA I’d approve a patch that splits the canary API we
> > need from a tool chassis. We have used and contributed to Canary for a
> long
> > time and changing the annotation was simply acknowledging our use and
> > continued contribution to this code. We can also just copy Canary into
> our
> > monitoring tool suite and fork it but prefer to continue contributing
> > canary improvements to open source.
> >
> > > On Aug 18, 2019, at 6:03 AM, 张铎(Duo Zhang) 
> > wrote:
> > >
> > > Due to HBASE-22823 I plan to sink this RC and find a way to deal with
> the
> > > IA.Public Canary.
> > >
> > > OpenInx  于2019年8月18日周日 下午4:09写道：
> > >
> > >> See the previous failed UT, it says  address already bind. And run the
> > UT
> > >> several times under a new host again,
> > >> seems all works fine.  So +1.
> > >>
> > >>> On Sun, Aug 18, 2019 at 3:56 PM OpenInx  wrote:
> > >>>
> > >>> Let me try the TestJMXConnectorServer locally again, although it
> failed
> > >>> now, it should not effect the rc vote.
> > >>> Give my +1,  will take a look about that UT.
> > >>>
> > >>>> On Sun, Aug 18, 2019 at 3:15 PM OpenInx  wrote:
> > >>>>
> > >>>>
> > >>>>* 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
> > >>>>* Unit tests pass (1.8.0_202): failed
> > >>>> - mvn test -P runAllTests
> > >>>>
> > >>>> The failed UT are:
> > >>>>
> > >>>> [INFO]
> > >>>> [ERROR] Errors:
> > >>>> [ERROR]
> > >>>>
> > >>
> >
> org.apache.hadoop.hbase.TestJMXConnectorServer.testHMConnectorServerWhenShutdownCluster(org.apache.hadoop.hbase.TestJMXConnectorServer)
> > >>>> [ERROR]   Run 1:
> > >>>> TestJMXConnectorServer.testHMConnectorServerWhenShutdownCluster:154
> »
> > IO
> > >>>> Shutt...
> > >>>> [ERROR]   Run 2: TestJMXConnectorServer.tearDown:73 NullPointer
> > >>>> [INFO]
> > >>>> [ERROR]
> > >>>>
> > >>
> >
> org.apache.hadoop.hbase.TestJMXConnectorServer.testHMConnectorServerWhenStopMaster(org.apache.hadoop.hbase.TestJMXConnectorServer)
> > >>>> [ERROR]   Run 1:
> > >>>> TestJMXConnectorServer.testHMConnectorServerWhenStopMaster:85 » IO
> > >> Shutting
> > >>>> do...
> > >>>> [ERROR]   Run 2: TestJMXConnectorServer.tearDown:73 NullPointer
> > >>>> [INFO]
> > >>>> [ERROR]
> > >>>>
> > >>
> >
> org.apache.hadoop.hbase.TestJMXConnectorServer.testRSConnectorServerWhenStopRegionServer(org.apache.hadoop.hbase.TestJMXConnectorServer)
> > >>>> [ERROR]   Run 1:
> > >>>>
> TestJMXConnectorServer.testRSConnectorServerWhenStopRegionServer:123 »
> > >> IO
> > >>>> Shut...
> > >>>> [ERROR]   Run 2: TestJMXConnectorServer.tearDown:73 NullPointer
> > >>>> [INFO]
> > >>>> [WARNING] Flakes:
> > >>>> [WARNING]
> > >>>>
> > >>
> >
> org.apache.hadoop.hbase.master.TestRestartCluster.testRetainAssignmentOnRestart(org.apache.hadoop.hbase.master.TestRestartCluster)
> > >>>> [ERROR]   Run 1:
> TestRestartCluster.testRetainAssignmentOnRestart:170
> > »
> > >>>> Runtime Failed construc...
> > >>>> [INFO]   Run 2: PASS
> > >>>> [INFO]
> > >>>> [WARNING]
> > >>>>
>

Re: [NOTICE] Reid Chan has been added to the HBASE PMC!

[Sakthi]

Congrats Reid!!

-Sakthi

On Fri, Aug 16, 2019 at 10:42 AM Tak-Lon (Stephen) Wu 
wrote:

> Congratulations Reid!
>
> -Stephen
>
> On Fri, Aug 16, 2019 at 10:30 AM Stack  wrote:
>
> > The mighty Reid Chan has been added to the hbase PMC. A bunch of us
> thought
> > he was on the PMC already but on a whim, I took a look and noticed that
> he
> > wasn't. Reid Chan has been a healthy influence about the place especially
> > contributing helping new contributors getting acclimatized to the ways
> and
> > means of hbase contribution helping keep up standards. He's a fabulous
> > resource to have about the project. Letting you all know he's been added
> to
> > the PMC.
> > Yours,
> > S
> >
>

[jira] [Created] (HBASE-22865) [HBCK2] shows the whole help/usage message after the error message

[Sakthi (JIRA)]

Sakthi created HBASE-22865:
--

 Summary: [HBCK2] shows the whole help/usage message after the 
error message
 Key: HBASE-22865
 URL: https://issues.apache.org/jira/browse/HBASE-22865
 Project: HBase
  Issue Type: Improvement
  Components: hbck2
Affects Versions: hbase-operator-tools-1.0.0
Reporter: Sakthi
Assignee: Sakthi


hbck2 shows the whole help/usage message after the error message. 
Operators/users need to scroll all the way up to find the error message. With 
the increasing client side support from hbck2 side, I reckon the usage message 
is only going to get bigger & bigger.

See an example here:
{code:java}
$ 
HBASE_CLASSPATH_PREFIX=~/dev/hbase-operator-tools/hbase-hbck2/target/hbase-hbck2-1.0.0-SNAPSHOT.jar
 ./bin/hbase org.apache.hbase.HBCK2 scheduleRecoveries
ERROR: scheduleRecoveries takes one or more serverNames
usage: HBCK2 [OPTIONS] COMMAND 
Options:
 -d,--debug   run with debug output
 -h,--helpoutput this help message
 -p,--hbase.zookeeper.property.clientPortport of hbase ensemble
 -q,--hbase.zookeeper.quorum hbase ensemble
 -s,--skipskip hbase version check
  (PleaseHoldException)
 -v,--version this hbck2 version
 -z,--zookeeper.znode.parent parent znode of hbase
  ensemble
Command:
 assigns [OPTIONS] ...
   Options:
-o,--override  override ownership by another procedure
   A 'raw' assign that can be used even during Master initialization (if
   the -skip flag is specified). Skirts Coprocessors. Pass one or more
   encoded region names. 1588230740 is the hard-coded name for the
   hbase:meta region and de00010733901a05f5a2a3a382e27dd4 is an example of
   what a user-space encoded region name looks like. For example:
 $ HBCK2 assign 1588230740 de00010733901a05f5a2a3a382e27dd4
   Returns the pid(s) of the created AssignProcedure(s) or -1 if none.

 bypass [OPTIONS] ...
   Options:
-o,--override   override if procedure is running/stuck
-r,--recursive  bypass parent and its children. SLOW! EXPENSIVE!
-w,--lockWait   milliseconds to wait before giving up; default=1
   Pass one (or more) procedure 'pid's to skip to procedure finish. Parent
   of bypassed procedure will also be skipped to the finish. Entities will
   be left in an inconsistent state and will require manual fixup. May
   need Master restart to clear locks still held. Bypass fails if
   procedure has children. Add 'recursive' if all you have is a parent pid
   to finish parent and children. This is SLOW, and dangerous so use
   selectively. Does not always work.

 filesystem [OPTIONS] [...]
   Options:
-f, --fixsideline corrupt hfiles, bad links, and references.
   Report on corrupt hfiles, references, broken links, and integrity.
   Pass '--fix' to sideline corrupt files and links. '--fix' does NOT
   fix integrity issues; i.e. 'holes' or 'orphan' regions. Pass one or
   more tablenames to narrow checkup. Default checks all tables and
   restores 'hbase.version' if missing. Interacts with the filesystem
only!
   Modified regions need to be reopened to pick-up changes.

 replication [OPTIONS] [...]
   Options:
-f, --fixfix any replication issues found.
   Looks for undeleted replication queues and deletes them if passed the
   '--fix' option. Pass a table name to check for replication barrier and
   purge if '--fix'.

 setRegionState  
   Possible region states:
OFFLINE, OPENING, OPEN, CLOSING, CLOSED, SPLITTING, SPLIT,
FAILED_OPEN, FAILED_CLOSE, MERGING, MERGED, SPLITTING_NEW,
MERGING_NEW, ABNORMALLY_CLOSED
   WARNING: This is a very risky option intended for use as last resort.
   Example scenarios include unassigns/assigns that can't move forward
   because region is in an inconsistent state in 'hbase:meta'. For
   example, the 'unassigns' command can only proceed if passed a region
   in one of the following states: SPLITTING|SPLIT|MERGING|OPEN|CLOSING
   Before manually setting a region state with this command, please
   certify that this region is not being handled by a running procedure,
   such as 'assign' or 'split'. You can get a view of running procedures
   in the hbase shell using the 'list_procedures' command. An example
   setting region 'de00010733901a05f5a2a3a382e27dd4' to CLOSING:
 $ HBCK2 setRegionState de00010733901a05f5a2a3a382e27dd4 CLOSING
   Returns "0" if region state changed and "1" otherwise.

 setTableState  
   Possible table states: ENABLED, DISABLED, DISABLING, ENABLING
   To read current table state, in the hbase shell run:
 hbase> get 'hbase:meta', '', 'table:state'
   A value of \x08\x00 == ENABLED, \x08\x

[jira] [Created] (HBASE-22864) Add detail in Space Quota section of the doc regarding "hbase.master.quotas.observer.report.percent"

[Sakthi (JIRA)]

Sakthi created HBASE-22864:
--

 Summary: Add detail in Space Quota section of the doc regarding 
"hbase.master.quotas.observer.report.percent"
 Key: HBASE-22864
 URL: https://issues.apache.org/jira/browse/HBASE-22864
 Project: HBase
  Issue Type: Improvement
  Components: documentation
Reporter: Sakthi
Assignee: Sakthi


Explanation regarding "hbase.master.quotas.observer.report.percent" is vital. 
Sometimes users tend to think quota system isn't working when the regions are 
offline.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (HBASE-22843) [HBCK2] Fix HBCK2 after HBASE-22777 & HBASE-22758

[Sakthi (JIRA)]

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

Sakthi resolved HBASE-22843.

   Resolution: Fixed
Fix Version/s: hbase-operator-tools-1.0.0

> [HBCK2] Fix HBCK2 after HBASE-22777 & HBASE-22758
> -
>
> Key: HBASE-22843
> URL: https://issues.apache.org/jira/browse/HBASE-22843
> Project: HBase
>  Issue Type: Sub-task
>  Components: hbase-operator-tools
>Reporter: Sakthi
>Assignee: Sakthi
>Priority: Blocker
> Fix For: hbase-operator-tools-1.0.0
>
>
> There were few changes made in HBASE-22777 & HBASE-22758, which would require 
> their propogation to HBCK2 as well to prevent compilation issues. These are 
> the ones:
> 1. MetaTableAccessor#makePutFromTableState was changed from public to 
> private. HBCK2 uses it in HBaseFsck#generatePuts() for rebuildMeta(). We 
> either need to revert the change to public or make similar adjustments in 
> HBCK2.
> 2.
> {code:java}
>  -PairOfSameType getMergeRegions(Result data) 
>  +List getMergeRegions(Cell[] cells){code}
> Due to this change, HBaseFsck was fixed accordingly but not HBCK2. Let's do 
> it there as well.
> 3. MetaTableAccessor#deleteRegion() was renamed to 
> MetaTableAccessor#deleteRegionInfo(). Even this should be integrated with 
> HBCK2.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22845) Revert MetaTableAccessor#makePutFromTableState access to public

[Sakthi (JIRA)]

Sakthi created HBASE-22845:
--

 Summary: Revert MetaTableAccessor#makePutFromTableState access to 
public
 Key: HBASE-22845
 URL: https://issues.apache.org/jira/browse/HBASE-22845
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


Discussions in HBASE-22843.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22843) [HBCK2] Fix HBCK2 after HBASE-22777 & HBASE-22758

[Sakthi (JIRA)]

Sakthi created HBASE-22843:
--

 Summary: [HBCK2] Fix HBCK2 after HBASE-22777 & HBASE-22758
 Key: HBASE-22843
 URL: https://issues.apache.org/jira/browse/HBASE-22843
 Project: HBase
  Issue Type: Sub-task
  Components: hbase-operator-tools
Reporter: Sakthi
Assignee: Sakthi


There were few changes made in HBASE-22777 & HBASE-22758, which would require 
their propogation to HBCK2 as well to prevent compilation issues. These are the 
ones:

1. MetaTableAccessor#makePutFromTableState was changed from public to private. 
HBCK2 uses it in HBaseFsck#generatePuts() for rebuildMeta(). We either need to 
revert the change to public or make similar adjustments in HBCK2.

2.
{code:java}
 -PairOfSameType getMergeRegions(Result data) 
 +List getMergeRegions(Cell[] cells){code}
Due to this change, HBaseFsck was fixed accordingly but not HBCK2. Let's do it 
there as well.

3. MetaTableAccessor#deleteRegion() was renamed to 
MetaTableAccessor#deleteRegionInfo(). Even this should be integrated with HBCK2.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22825) Add a client-side to hbase-operator-tools that can exploit fixMeta added in server side

[Sakthi (JIRA)]

Sakthi created HBASE-22825:
--

 Summary: Add a client-side to hbase-operator-tools that can 
exploit fixMeta added in server side
 Key: HBASE-22825
 URL: https://issues.apache.org/jira/browse/HBASE-22825
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi


fixMeta was added in server side in HBASE-22771. Let's add the client side to 
the hbase-operator-tools to utilize that.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22815) mvn build throws a repeated "pattern never triggered..."

[Sakthi (JIRA)]

Sakthi created HBASE-22815:
--

 Summary: mvn build throws a repeated "pattern never triggered..." 
 Key: HBASE-22815
 URL: https://issues.apache.org/jira/browse/HBASE-22815
 Project: HBase
  Issue Type: Task
Reporter: Sakthi


{code:java}
$mvn clean package assembly:single install -DskipTests
...
...
[INFO] --- maven-assembly-plugin:3.0.0:single (default-cli) @ hbase-assembly ---
[INFO] Reading assembly descriptor: src/main/assembly/hadoop-two-compat.xml
[INFO] Reading assembly descriptor: src/main/assembly/client.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'

[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  'org.apache.htrace:htrace-core'
...{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (HBASE-22812) InterfaceAudience annotation in CatalogJanitor uses fully-qualified name

[Sakthi (JIRA)]

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

Sakthi resolved HBASE-22812.

Resolution: Fixed

> InterfaceAudience annotation in CatalogJanitor uses fully-qualified name
> 
>
> Key: HBASE-22812
> URL: https://issues.apache.org/jira/browse/HBASE-22812
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>Reporter: Peter Somogyi
>Assignee: Murtaza Hassan
>Priority: Minor
>  Labels: beginner
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> CatalogJanitor class's InterfaceAudience annotation uses the fully-qualified 
> name instead of just @InterfaceAudience.Private.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (HBASE-22800) Add mapreduce dependencies to hbase-shaded-testing-util

[Sakthi (JIRA)]

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

Sakthi resolved HBASE-22800.

Resolution: Fixed

> Add mapreduce dependencies to hbase-shaded-testing-util
> ---
>
> Key: HBASE-22800
> URL: https://issues.apache.org/jira/browse/HBASE-22800
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 3.0.0, 2.2.1, 2.1.6
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.6
>
>
> {{MiniMRCluster}} is missing from the generated {{hbase-shaded-testing-util}} 
> artifact.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (HBASE-15666) shaded dependencies for hbase-testing-util

[Sakthi (JIRA)]

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

Sakthi resolved HBASE-15666.

Resolution: Fixed

> shaded dependencies for hbase-testing-util
> --
>
> Key: HBASE-15666
> URL: https://issues.apache.org/jira/browse/HBASE-15666
> Project: HBase
>  Issue Type: New Feature
>  Components: test
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Sean Busbey
>Assignee: Balazs Meszaros
>Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11
>
>
> Folks that make use of our shaded client but then want to test things using 
> the hbase-testing-util end up getting all of our dependencies again in the 
> test scope.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Reopened] (HBASE-15666) shaded dependencies for hbase-testing-util

[Sakthi (JIRA)]

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

Sakthi reopened HBASE-15666:


> shaded dependencies for hbase-testing-util
> --
>
> Key: HBASE-15666
> URL: https://issues.apache.org/jira/browse/HBASE-15666
> Project: HBase
>  Issue Type: New Feature
>  Components: test
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Sean Busbey
>Assignee: Balazs Meszaros
>Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.1, 2.1.6, 1.4.11
>
>
> Folks that make use of our shaded client but then want to test things using 
> the hbase-testing-util end up getting all of our dependencies again in the 
> test scope.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Reopened] (HBASE-22800) Add mapreduce dependencies to hbase-shaded-testing-util

[Sakthi (JIRA)]

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

Sakthi reopened HBASE-22800:


Reopening for pushing to branch-2

> Add mapreduce dependencies to hbase-shaded-testing-util
> ---
>
> Key: HBASE-22800
> URL: https://issues.apache.org/jira/browse/HBASE-22800
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 3.0.0, 2.2.1, 2.1.6
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0, 2.2.1, 2.1.6
>
>
> {{MiniMRCluster}} is missing from the generated {{hbase-shaded-testing-util}} 
> artifact.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (HBASE-22800) Add mapreduce dependencies to hbase-shaded-testing-util

[Sakthi (JIRA)]

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

Sakthi resolved HBASE-22800.

   Resolution: Fixed
Fix Version/s: 2.1.6
   2.2.1
   3.0.0

> Add mapreduce dependencies to hbase-shaded-testing-util
> ---
>
> Key: HBASE-22800
> URL: https://issues.apache.org/jira/browse/HBASE-22800
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 3.0.0, 2.2.1, 2.1.6
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 3.0.0, 2.2.1, 2.1.6
>
>
> {{MiniMRCluster}} is missing from the generated {{hbase-shaded-testing-util}} 
> artifact.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22803) Add a config to turn off the hbck chore

[Sakthi (JIRA)]

Sakthi created HBASE-22803:
--

 Summary: Add a config to turn off the hbck chore
 Key: HBASE-22803
 URL: https://issues.apache.org/jira/browse/HBASE-22803
 Project: HBase
  Issue Type: Sub-task
Reporter: Sakthi
Assignee: Sakthi


hbck chore was added in HBASE-22709. To trigger it we can use the shell cmd 
added in HBASE-22737. Also by default the chore runs every 1 hour. Let's add a 
config to turn it off so that operators can use it and do rolling restart when 
they want to stop this chore.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [ANNOUNCE] New HBase committer Tak-Lon (Stephen) Wu

[Sakthi]

Congrats Stephen and welcome!

Sakthi

On Mon, Aug 5, 2019 at 12:49 PM Esteban Gutierrez
 wrote:

> Woot! Congrats Stephen! and welcome!
>
> --
> Cloudera, Inc.
>
>
>
> On Mon, Aug 5, 2019 at 2:04 PM Jan Hentschel <
> jan.hentsc...@ultratendency.com> wrote:
>
> > Congratulations and welcome!
> > From: Sean Busbey 
> > Reply-To: "u...@hbase.apache.org" 
> > Date: Monday, August 5, 2019 at 8:53 PM
> > To: dev , "u...@hbase.apache.org" <
> > u...@hbase.apache.org>
> > Subject: [ANNOUNCE] New HBase committer Tak-Lon (Stephen) Wu
> >
> > On behalf of the Apache HBase PMC I am super pleased to announce that
> > Tak-Lon (Stephen) Wu has accepted the PMC's invitation to become a
> > commiter on the project.
> >
> > Thanks so much for the work you've been contributing. We look forward
> > to your continued involvement.
> >
> > Congratulations and welcome!
> >
> > -busbey
> >
> >
>

Re: [ANNOUNCE] Please welcome Zheng Hu to the HBase PMC

[Sakthi]

Congrats Zheng!

Sakthi

On Sun, Aug 4, 2019 at 7:17 PM Andrew Purtell 
wrote:

> Congratulations, Zheng.
>
>
> > On Aug 4, 2019, at 7:07 PM, Duo Zhang  wrote:
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that Zheng Hu
> > has accepted our invitation to become a PMC member on the Apache HBase
> > project. We appreciate Zheng Hu stepping up to take more responsibility
> in
> > the HBase project.
> >
> > Please join me in welcoming Zheng Hu to the HBase PMC!
>

Re: [ANNOUNCE] new HBase committer Sakthi

[Sakthi]

Thank you all, for your warm wishes. Hope to continue contributing to the
project!

Cheers,
Sakthi

On Thu, Aug 1, 2019 at 2:15 PM Zach York 
wrote:

> Congrats Sakthi! Welcome!
>
> On Thu, Aug 1, 2019 at 11:07 AM Jesse Yates 
> wrote:
>
> > Congrats sakthi!
> >
> >
> >
> > On Thu, Aug 1, 2019 at 10:02 AM Ankit Singhal 
> > wrote:
> >
> > > Congratulations Sakthi !!
> > >
> > > On Thu, Aug 1, 2019 at 7:15 AM Toshihiro Suzuki 
> > > wrote:
> > >
> > > > Congratulations! Sakthi
> > > >
> > > > On Thu, Aug 1, 2019 at 9:49 PM Guanghao Zhang 
> > > wrote:
> > > >
> > > > > Congratulations!
> > > > >
> > > > > Allan Yang  于2019年8月1日周四 下午8:46写道：
> > > > >
> > > > > > Congratulations Sakthi !
> > > > > >
> > > > > > Best Regards
> > > > > > Allan Yang
> > > > > >
> > > > > >
> > > > > > Nihal Jain  于2019年8月1日周四 下午8:40写道：
> > > > > >
> > > > > > > Congrats Sakthi. More power to you!
> > > > > > >
> > > > > > > On Thu, 1 Aug, 2019, 4:42 PM ramkrishna vasudevan, <
> > > > > > > ramkrishna.s.vasude...@gmail.com> wrote:
> > > > > > >
> > > > > > > > Congratulations Sakthi !!!
> > > > > > > >
> > > > > > > > On Thu, Aug 1, 2019 at 3:34 PM 张铎(Duo Zhang) <
> > > > palomino...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations!
> > > > > > > > >
> > > > > > > > > Pankaj kr  于2019年8月1日周四 下午5:56写道：
> > > > > > > > >
> > > > > > > > > > Congratulation Sakthi..!!
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Pankaj
> > > > > > > > > >
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Sean Busbey [mailto:bus...@apache.org]
> > > > > > > > > > Sent: 01 August 2019 05:35
> > > > > > > > > > To: u...@hbase.apache.org; dev 
> > > > > > > > > > Subject: [ANNOUNCE] new HBase committer Sakthi
> > > > > > > > > >
> > > > > > > > > > On behalf of the HBase PMC, I'm pleased to announce that
> > > Sakthi
> > > > > has
> > > > > > > > > > accepted our invitation to become an HBase committer.
> > > > > > > > > >
> > > > > > > > > > We'd like to thank Sakthi for all of his diligent
> > > contributions
> > > > > to
> > > > > > > the
> > > > > > > > > > project thus far. We look forward to his continued
> > > > participation
> > > > > in
> > > > > > > our
> > > > > > > > > > community.
> > > > > > > > > >
> > > > > > > > > > Congrats and welcome Sakthi!
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (HBASE-22747) Update the CopyTable section in the doc

[Sakthi (JIRA)]

Sakthi created HBASE-22747:
--

 Summary: Update the CopyTable section in the doc
 Key: HBASE-22747
 URL: https://issues.apache.org/jira/browse/HBASE-22747
 Project: HBase
  Issue Type: Improvement
Reporter: Sakthi
Assignee: Sakthi


bulkload and snapshot options needs to be added.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (HBASE-22734) Format error message in create_namespace command to avoid stacktrace

[Sakthi (JIRA)]

Sakthi created HBASE-22734:
--

 Summary: Format error message in create_namespace command to avoid 
stacktrace
 Key: HBASE-22734
 URL: https://issues.apache.org/jira/browse/HBASE-22734
 Project: HBase
  Issue Type: Improvement
Reporter: Sakthi


This is what it looks like currently:

 
{code:java}
hbase(main):003:0> create_namespace 'ns1:t2'

ERROR: java.io.IOException: Illegal character <:> at 3. Namespaces may only 
contain 'alphanumeric characters' from any language and digits: ns1:t2
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:472)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:132)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338)
at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)
Caused by: java.lang.IllegalArgumentException: Illegal character <:> at 3. 
Namespaces may only contain 'alphanumeric characters' from any language and 
digits: ns1:t2
at org.apache.hadoop.hbase.TableName.isLegalNamespaceName(TableName.java:251)
at org.apache.hadoop.hbase.TableName.isLegalNamespaceName(TableName.java:225)
at org.apache.hadoop.hbase.master.HMaster.createNamespace(HMaster.java:3267)
at 
org.apache.hadoop.hbase.master.MasterRpcServices.createNamespace(MasterRpcServices.java:649)
at 
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
... 3 more

For usage try 'help "create_namespace"'

Took 8.2554 seconds{code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [Announce] 张铎 (Duo Zhang) is Apache HBase PMC chair

[Sakthi]

Thanks Misty for handling the role so well!
Congratulations Duo.

Sakthi

On Fri, Jul 19, 2019 at 11:48 AM Ankit Singhal 
wrote:

> Congratulations Duo!!
> And, thank you Misty for all your great contributions to the project.
>
> On Fri, Jul 19, 2019 at 11:36 AM Xu Cang  wrote:
>
> > Thank you Misty!
> > Congratulations Duo, thanks for taking extra work!
> >
> > On Fri, Jul 19, 2019 at 11:23 AM Zach York  >
> > wrote:
> >
> > > Congratulations Duo! Thanks for offering to take on the additional
> work!
> > >
> > > On Fri, Jul 19, 2019 at 10:34 AM Stack  wrote:
> > >
> > > > Thank you Misty for your years of service (FYI, for non-PMCers, the
> > > reports
> > > > Misty wrote to the Apache Board on our behalf were repeatedly called
> > out
> > > > for their quality and thoughtfulness).
> > > >
> > > > Duo Zhang, thank you for taking on the mantle.
> > > >
> > > > S
> > > >
> > > > On Thu, Jul 18, 2019 at 10:46 AM Misty Linville 
> > > wrote:
> > > >
> > > > > Each Apache project has a project management committee (PMC) that
> > > > oversees
> > > > > governance of the project, votes on new committers and PMC members,
> > and
> > > > > ensures that the software we produce adheres to the standards of
> the
> > > > > Foundation. One of the roles on the PMC is the PMC chair. The PMC
> > chair
> > > > > represents the project as a Vice President of the Foundation and
> > > > > communicates to the board about the project's health, once per
> > quarter
> > > > and
> > > > > at other times as needed.
> > > > >
> > > > > It's been my honor to serve as your PMC chair since 2017, when I
> took
> > > > over
> > > > > from Andrew Purtell. I've decided to step back from my volunteer
> ASF
> > > > > activities to leave room in my life for other things. The HBase PMC
> > > > > nominated Duo for this role, and Duo has kindly agreed! The board
> > > passed
> > > > > this resolution in its meeting yesterday[1] and it is already
> > > > official[2].
> > > > > Congratulations, Duo, and thank you for continuing to honor the
> > project
> > > > > with your dedication.
> > > > >
> > > > > Misty
> > > > >
> > > > > [1] The minutes have not yet posted at the time of this email, but
> > will
> > > > be
> > > > > available at
> http://www.apache.org/foundation/records/minutes/2019/.
> > > > > [2] https://www.apache.org/foundation/#who-runs-the-asf
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (HBASE-22645) Backport HBASE-19893 to all 2.x branches

[Sakthi (JIRA)]

Sakthi created HBASE-22645:
--

 Summary: Backport HBASE-19893 to all 2.x branches
 Key: HBASE-22645
 URL: https://issues.apache.org/jira/browse/HBASE-22645
 Project: HBase
  Issue Type: Task
Reporter: Sakthi
Assignee: Sakthi






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-22587) Add a REST server to the nightly test that uses a cluster for simple operations

[Sakthi (JIRA)]

Sakthi created HBASE-22587:
--

 Summary: Add a REST server to the nightly test that uses a cluster 
for simple operations
 Key: HBASE-22587
 URL: https://issues.apache.org/jira/browse/HBASE-22587
 Project: HBase
  Issue Type: Task
  Components: REST, test
Reporter: Sakthi


Let's add rest server to the nightly test that uses a cluster for simple 
operations to catch any possible rest server issues related to dependencies, 
cnfe, npe etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-22585) Branch-2 build fails on Java 11

[Sakthi (JIRA)]

Sakthi created HBASE-22585:
--

 Summary: Branch-2 build fails on Java 11
 Key: HBASE-22585
 URL: https://issues.apache.org/jira/browse/HBASE-22585
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi


Branch-2 build fails on Java 11. Complaints about the 
hbase-shaded-check-invariants. Will paste the stacktrace if needed in the 
comments. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Sakthi]

Duo,

What version on Hadoop did you use in the 5 node cluster for your
comparisons? For what it's worth, I would also like to try out the PE/LTT
comparison of both the clients. Or, if any other form of comparison would
be helpful then I'm open for suggestions and would like to give it a try.

Sakthi

On Thu, Jun 13, 2019 at 4:55 PM 张铎(Duo Zhang)  wrote:

> It will be transparent, mostly, the interface is still kept. There are some
> incompatible behaviors, for example, now admin.split will wait till the
> split is actually done, while in the old time it will return immediately
> after we send the request to master.
>
> Jean-Marc Spaggiari 于2019年6月13日 周四23:26写道：
>
> > Hi,
> >
> > Is this going to change the way the client should be called? Or it will
> be
> > mostly transparent replacement?
> >
> > Thanks,
> >
> > JMS
> >
> > Le jeu. 13 juin 2019 à 02:13, 张铎(Duo Zhang)  a
> > écrit :
> >
> > > Josh Elser  于2019年6月12日周三 下午10:00写道：
> > >
> > > > Nice perf results!
> > > >
> > > > https://issues.apache.org/jira/browse/HBASE-22237 looks like it's
> also
> > > > good to be resolved, given
> > > >
> > > >
> > >
> >
> https://builds.apache.org/job/HBASE%20Nightly/job/HBASE-21512/279/testReport/
> > > > (TestLogLevel will be fixed on your rebase/merge).
> > > >
> > > > Poking through the PR, it looks like the big change is that we're
> also
> > > > defaulting over to use the [sync]ConnectionOverAsyncConnection. Good
> to
> > > > do it now to help iron things out more. Calling it out to make sure
> > > > others see this. Is it still possible to use the old Connection impl?
> > (I
> > > > think the answer is "no").
> > > >
> > > No, all the code have been purged...
> > >
> > > >
> > > > Only other question: are there updates for the book that should
> happen
> > > > before you move past this? What about "knobs" for configuring
> retries,
> > > > internal thread pool(s)? Anything like that you think would be
> > important
> > > > for people to tweak?
> > > >
> > >  Will fill a 'fat' release note soon. I think there will be less
> > parameters
> > > to tune, as we do not need any thread pools unless you are using
> > > coprocessor related methods(which are deprecated and we recommend users
> > to
> > > use the ones in async client interface). The retry config is still the
> > same
> > > with the old sync client.
> > >
> > > >
> > > > +1
> > > >
> > > > On 6/11/19 5:48 AM, 张铎(Duo Zhang) wrote:
> > > > > Filed  https://issues.apache.org/jira/browse/HBASE-22564
> > > > >
> > > > > 张铎(Duo Zhang)  于2019年6月11日周二 下午3:53写道：
> > > > >
> > > > >> Let me do a YCSB test about the performance.
> > > > >>
> > > > >> Stack  于2019年6月11日周二 下午1:15写道：
> > > > >>
> > > > >>> +1 on merge from me.
> > > > >>>
> > > > >>> It removes the complicated multi-threaded edifice we'd built
> > > > client-side
> > > > >>> to
> > > > >>> fake an async behavior replacing it with an actual async
> > > > implementation.
> > > > >>> Users will immediately notice a radical plummet in working thread
> > > > count on
> > > > >>> the client side.
> > > > >>>
> > > > >>> For the cleanup of old idioms alone, in test code in particular,
> > the
> > > > patch
> > > > >>> is worth merging.
> > > > >>>
> > > > >>> Any perf numbers to share comparing old sync and async?
> > > > >>>
> > > > >>> What about difference in operation? Is there any commentary or
> doc
> > or
> > > > >>> release note to point at?
> > > > >>>
> > > > >>> Thanks,
> > > > >>> S
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On Mon, Jun 10, 2019 at 6:59 PM 张铎(Duo Zhang) <
> > palomino...@gmail.com
> > > >
> > > > >>> wrote:
> > > > >>>
> > > > >>>> https://issues.apache.org/jira/browse/HBASE-21512
> > >

Re: [ANNOUNCE] New Committer: Wellington Chevreuil

[Sakthi]

Hurray! Congrats Wellington. Well deserved one!

Sakthi

On Fri, Jun 7, 2019 at 12:58 PM Wei-Chiu Chuang
 wrote:

> Yay!! Congrats for the achievement!
>
> On Fri, Jun 7, 2019 at 12:56 PM Andrew Purtell 
> wrote:
>
> > Congratulations and welcome, Wellington.
> >
> > > On Jun 7, 2019, at 3:11 AM, Peter Somogyi  wrote:
> > >
> > > On behalf of the HBase PMC, I'm pleased to announce that Wellington
> > > Chevreuil has accepted our invitation to become an HBase committer.
> > >
> > > Thanks for all your hard work Wellington; we look forward to more
> > > contributions!
> > >
> > > Please join me in extending congratulations to Wellington!
> >
>

Re: [ANNOUNCE] Apache HBase 2.1.5 is now available for download

[Sakthi]

I hope users don't get confused by different version numbers in the subject
and in the first para. :) Though a very minor thing.

Sakthi

On Wed, Jun 5, 2019 at 8:21 AM stack  wrote:

> The HBase team is happy to announce the immediate availability of Apache
> HBase 2.1.4.
>
> Download from https://hbase.apache.org/downloads.html
>
> Apache HBase is an open-source, distributed, versioned, non-relational
> database. Apache HBase gives you low latency random access to billions of
> rows with millions of columns atop non-specialized hardware. To learn more
> about HBase, see https://hbase.apache.org/.
>
> HBase 2.1.5 is the latest release on the HBase 2.1 line, continuing on the
> theme of bringing a stable, reliable database to the Apache Big Data
> ecosystem and beyond.  It includes 97 fixes since 2.1.4, ~ nine weeks ago.
>
> 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
>
> Thanks to all the contributors who made this release possible!
>
> Best,
> The HBase Dev Team
>

[jira] [Created] (HBASE-22536) TestForeignExceptionSerialization fails when run on JDK11

[Sakthi (JIRA)]

Sakthi created HBASE-22536:
--

 Summary: TestForeignExceptionSerialization fails when run on JDK11
 Key: HBASE-22536
 URL: https://issues.apache.org/jira/browse/HBASE-22536
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi
Assignee: Sakthi


When built on Java 8 and unit tests are run on Java 11, 
TestForeignExceptionSerialization fails. A sample stacktrace:
{code}
 Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.546 s <<< 
FAILURE! - in 
org.apache.hadoop.hbase.errorhandling.TestForeignExceptionSerialization
testRemoteFromLocal(org.apache.hadoop.hbase.errorhandling.TestForeignExceptionSerialization)
 Time elapsed: 0.084 s <<< FAILURE!
org.junit.internal.ArrayComparisonFailure: Local stack trace got corrupted: 
arrays first differed at element [0]; expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at 
org.apache.hadoop.hbase.errorhandling.TestForeignExceptionSerialization.testRemoteFromLocal(TestForeignExceptionSerialization.java:78)
Caused by: java.lang.AssertionError: expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at 
org.apache.hadoop.hbase.errorhandling.TestForeignExceptionSerialization.testRemoteFromLocal(TestForeignExceptionSerialization.java:78){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-22535) TestShellRSGroups fails when run on JDK11

[Sakthi (JIRA)]

Sakthi created HBASE-22535:
--

 Summary: TestShellRSGroups fails when run on JDK11
 Key: HBASE-22535
 URL: https://issues.apache.org/jira/browse/HBASE-22535
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi
Assignee: Sakthi


When built on Java 8 and unit tests are run on Java 11, TestShellRSGroups 
fails. A sample stacktrace:
{code}
 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 19.293 s <<< 
FAILURE! - in org.apache.hadoop.hbase.client.rsgroup.TestShellRSGroups
testRunShellTests(org.apache.hadoop.hbase.client.rsgroup.TestShellRSGroups) 
Time elapsed: 2.879 s <<< ERROR!
org.jruby.embed.EvalFailedException: (RuntimeError) Shell unit tests failed. 
Check output file for details.
at 
org.apache.hadoop.hbase.client.rsgroup.TestShellRSGroups.testRunShellTests(TestShellRSGroups.java:102)
Caused by: org.jruby.exceptions.RaiseException: (RuntimeError) Shell unit tests 
failed. Check output file for details.

Error: 
^[[48;5;16;38;5;226;1mtest_Test_bogus_arguments(Hbase::RSGroupShellTest)^[[0m: 
TypeError: illegal access on constructor for type 'RSGroupAdminClient': class 
org.jruby.javasupport.JavaConstructor cannot access a member of class 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminClient with modifiers "public"
/Users/jatsakthi/dev/hbase/hbase-shell/src/test/ruby/shell/rsgroup_shell_test.rb:30:in
 `setup'
org/jruby/RubyArray.java:1735:in `each'{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-22534) TestCellUtil fails when run on JDK11

[Sakthi (JIRA)]

Sakthi created HBASE-22534:
--

 Summary: TestCellUtil fails when run on JDK11
 Key: HBASE-22534
 URL: https://issues.apache.org/jira/browse/HBASE-22534
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi
Assignee: Sakthi


When built on Java 8 and unit tests are run on Java 11, TestCellUtil fails. A 
sample stacktrace:
{code}
 Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.096 s <<< 
FAILURE! - in org.apache.hadoop.hbase.TestCellUtil
testGetType(org.apache.hadoop.hbase.TestCellUtil) Time elapsed: 0.544 s <<< 
ERROR!
org.mockito.exceptions.base.MockitoException:

Cannot call abstract real method on java object!
Calling real methods is only possible when mocking non abstract method.
//correct example:
when(mockOfConcreteClass.nonAbstractMethod()).thenCallRealMethod();
at org.apache.hadoop.hbase.TestCellUtil.testGetType(TestCellUtil.java:543){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-22458) TestClassFinder fails when run on JDK11

[Sakthi (JIRA)]

Sakthi created HBASE-22458:
--

 Summary: TestClassFinder fails when run on JDK11
 Key: HBASE-22458
 URL: https://issues.apache.org/jira/browse/HBASE-22458
 Project: HBase
  Issue Type: Bug
Reporter: Sakthi


When built on Java 8 and unit tests are run on Java 11, TestClassFinder fails. 
A sample stacktrace:
{code:java}
java.lang.ClassCastException: class 
jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class 
java.net.URLClassLoader (jdk.internal.loader.ClassLoaders$AppClassLoader and 
java.net.URLClassLoader are in module java.base of loader 'bootstrap')
at 
org.apache.hadoop.hbase.TestClassFinder.packageAndLoadJar(TestClassFinder.java:418)
at 
org.apache.hadoop.hbase.TestClassFinder.createAndLoadJar(TestClassFinder.java:193)
at 
org.apache.hadoop.hbase.TestClassFinder.testClassFinderCanFindClassesInDirs(TestClassFinder.java:233){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] Moving IA.Public class LossyCounting to IA.Private in all maintenance branches

[Sakthi]

Looks good to me.

Sakthi

On Fri, May 10, 2019 at 6:18 AM 张铎(Duo Zhang)  wrote:

> +1.
>
> Jan Hentschel  于2019年5月10日周五 下午9:08写道：
>
> > Also +1 for making it IA.Private.
> >
> > From: Peter Somogyi 
> > Reply-To: "dev@hbase.apache.org" 
> > Date: Friday, May 10, 2019 at 1:41 PM
> > To: "dev@hbase.apache.org" 
> > Subject: Re: [DISCUSS] Moving IA.Public class LossyCounting to IA.Private
> > in all maintenance branches
> >
> > +1 on moving LossyCounting to IA.Private
> >
> > On Fri, May 10, 2019 at 7:54 AM Stack  > st...@duboce.net>> wrote:
> >
> > Looks good to me.
> > S
> >
> > On Thu, May 9, 2019 at 7:02 PM Sean Busbey  > bus...@apache.org>> wrote:
> >
> > > Hi folks!
> > >
> > > just a heads up that a few of us are planning to move a class out of
> > > the public API without a deprecation cycle.
> > >
> > > From the planned release note:
> > >
> > > > The class LossyCounting was unintentionally marked Public but was
> never
> > > > intended to be part of our public API. This oversight has been
> > corrected
> > > > and LossyCounting is now marked as Private and going forward may be
> > > > subject to additional breaking changes or removal without notice. If
> > you
> > > > have taken a dependency on this class we recommend cloning it locally
> > > into
> > > > your project before upgrading to this release.
> > >
> > > This class was came in via HBASE-19722 and was published in HBase
> > > 1.4.6, 2.0.2, and 2.1.3 (and depending on RC timing might be in
> > > 2.2.0).
> > >
> > > It will move to IA.Private as of 1.4.10, 1.5.0, 2.0.6, 2.1.5 and later
> > > (maybe 2.2.1 depending on RC timing). The class already has
> > > backwards-incompatible changes set to happen in upcoming releases
> > > 1.4.10, 1.5.0, and 2.2.0.
> > >
> > > Please speak up sooner rather than later if you'll have a problem
> > > voting on RCs that include this change, either here or on HBASE-21991.
> > >
> >
> >
> >
>