Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)

2023-09-17 Thread Guangxu Cheng
Congratulations HuiRuan and welcome!


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


[jira] [Resolved] (HBASE-26562) Release hbase-operator-tools 1.2.0

2021-12-26 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26562.
---
Resolution: Resolved

> Release hbase-operator-tools 1.2.0
> --
>
> Key: HBASE-26562
> URL: https://issues.apache.org/jira/browse/HBASE-26562
> Project: HBase
>  Issue Type: Umbrella
>Reporter: Duo Zhang
>    Assignee: Guangxu Cheng
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Resolved] (HBASE-26627) [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master

2021-12-26 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26627.
---
Resolution: Fixed

> [hbase-operator-tools] Set version as 1.3.0-SNAPSHOT in master
> --
>
> Key: HBASE-26627
> URL: https://issues.apache.org/jira/browse/HBASE-26627
> Project: HBase
>  Issue Type: Sub-task
>  Components: hbase-operator-tools
>Affects Versions: hbase-operator-tools-1.2.0
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[ANNOUNCE] Apache HBase Operator Tools 1.2.0 is now available for download

2021-12-26 Thread Guangxu Cheng
The HBase team is happy to announce the immediate availability of Apache
HBase Operator Tools 1.2.0.

Apache HBase™ Operator Tools provides HBCK2 which is the repair tool for
Apache HBase 2 clusters.
To learn more about HBase and HBase Operator Tools, see
https://hbase.apache.org/.

The full list of issues can be found in the included CHANGES.md and
RELEASENOTES.md, or via our issue tracker:

 https://s.apache.org/hbase-operator-tools-1.2.0-jira

To download please follow the links and instructions on our website:

https://hbase.apache.org/downloads.html

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

Thanks to all who contributed and made this release possible.

Cheers,
The HBase Dev Team
--
Best Regards,
Guangxu


[jira] [Resolved] (HBASE-26626) Update download page for HBase Operator Tools to 1.2.0

2021-12-24 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26626.
---
Resolution: Fixed

> Update download page for HBase Operator Tools to 1.2.0
> --
>
> Key: HBASE-26626
> URL: https://issues.apache.org/jira/browse/HBASE-26626
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HBASE-26627) Set version as 1.3.0-SNAPSHOT in master

2021-12-24 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-26627:
-

 Summary: Set version as 1.3.0-SNAPSHOT in master
 Key: HBASE-26627
 URL: https://issues.apache.org/jira/browse/HBASE-26627
 Project: HBase
  Issue Type: Sub-task
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HBASE-26626) Update download page for HBase Operator Tools to 1.2.0

2021-12-24 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-26626:
-

 Summary: Update download page for HBase Operator Tools to 1.2.0
 Key: HBASE-26626
 URL: https://issues.apache.org/jira/browse/HBASE-26626
 Project: HBase
  Issue Type: Sub-task
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


Re: [VOTE] Second release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-23 Thread Guangxu Cheng
With 3 binding +1 votes, 1 non-binding +1 votes, and no 0 or -1 votes, the
vote passes.

Thanks to all who voted on the release candidate!

Let me push the release out.
--
Best Regards,
Guangxu


Guangxu Cheng  于2021年12月24日周五 15:39写道:

> +1 from me
> --
> Best Regards,
> Guangxu
>
>
> Josh Elser  于2021年12月23日周四 05:00写道:
>
>> +1 (binding)
>>
>> * xsums/sigs OK
>> * apache-rat:check OK
>> * Can build from src
>> * Ran all UT
>> * Log4j 2.17 in use
>>
>> Looks great, Guangxu!
>>
>> On 12/20/21 1:15 AM, Guangxu Cheng wrote:
>> > Please vote on this Apache hbase operator tools release candidate,
>> > hbase-operator-tools-1.2.0RC1
>> >
>> > The VOTE will remain open for at least 72 hours.
>> >
>> > [ ] +1 Release this package as Apache hbase operator tools 1.2.0
>> > [ ] -1 Do not release this package because ...
>> >
>> > The tag to be voted on is 1.2.0RC1:
>> >
>> >https://github.com/apache/hbase-operator-tools/tree/1.2.0RC1
>> >
>> > This tag currently points to git reference
>> >
>> >478af00af79f82624264fd2bb447b97fecc8e790
>> >
>> > The release files, including signatures, digests, as well as CHANGES.md
>> > and RELEASENOTES.md included in this RC can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC1
>> >
>> > Maven artifacts are available in a staging repository at:
>> >
>> >https://repository.apache.org/content/repositories/org apache
>> hbase-1479
>> > <https://repository.apache.org/content/repositories/orgapachehbase-1479
>> >
>> > Artifacts were signed with the 5EF3A66D57EC647A key which can be found
>> in:
>> >
>> >https://downloads.apache.org/hbase/KEYS
>> >
>> > hbase-operator-tools 1.2.0 contains a critical security fix for
>> addressing
>> > the log4j2
>> > CVE-2021-44228 and CVE-2021-45105. All users who use
>> hbase-operator-tools
>> > should upgrade to hbase-operator-tools 1.2.0 ASAP.
>> >
>> > To learn more about Apache hbase operator tools, please see
>> >
>> >http://hbase.apache.org/
>> >
>> > Thanks,
>> > Your HBase Release Manager
>> > --
>> > Best Regards,
>> > Guangxu
>> >
>>
>


Re: [VOTE] Second release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-23 Thread Guangxu Cheng
+1 from me
--
Best Regards,
Guangxu


Josh Elser  于2021年12月23日周四 05:00写道:

> +1 (binding)
>
> * xsums/sigs OK
> * apache-rat:check OK
> * Can build from src
> * Ran all UT
> * Log4j 2.17 in use
>
> Looks great, Guangxu!
>
> On 12/20/21 1:15 AM, Guangxu Cheng wrote:
> > Please vote on this Apache hbase operator tools release candidate,
> > hbase-operator-tools-1.2.0RC1
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase operator tools 1.2.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 1.2.0RC1:
> >
> >https://github.com/apache/hbase-operator-tools/tree/1.2.0RC1
> >
> > This tag currently points to git reference
> >
> >478af00af79f82624264fd2bb447b97fecc8e790
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC1
> >
> > Maven artifacts are available in a staging repository at:
> >
> >https://repository.apache.org/content/repositories/org apache
> hbase-1479
> > <https://repository.apache.org/content/repositories/orgapachehbase-1479>
> > Artifacts were signed with the 5EF3A66D57EC647A key which can be found
> in:
> >
> >https://downloads.apache.org/hbase/KEYS
> >
> > hbase-operator-tools 1.2.0 contains a critical security fix for
> addressing
> > the log4j2
> > CVE-2021-44228 and CVE-2021-45105. All users who use hbase-operator-tools
> > should upgrade to hbase-operator-tools 1.2.0 ASAP.
> >
> > To learn more about Apache hbase operator tools, please see
> >
> >http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> > --
> > Best Regards,
> > Guangxu
> >
>


[VOTE] Second release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-19 Thread Guangxu Cheng
Please vote on this Apache hbase operator tools release candidate,
hbase-operator-tools-1.2.0RC1

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache hbase operator tools 1.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 1.2.0RC1:

  https://github.com/apache/hbase-operator-tools/tree/1.2.0RC1

This tag currently points to git reference

  478af00af79f82624264fd2bb447b97fecc8e790

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC1

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/org apache hbase-1479

Artifacts were signed with the 5EF3A66D57EC647A key which can be found in:

  https://downloads.apache.org/hbase/KEYS

hbase-operator-tools 1.2.0 contains a critical security fix for addressing
the log4j2
CVE-2021-44228 and CVE-2021-45105. All users who use hbase-operator-tools
should upgrade to hbase-operator-tools 1.2.0 ASAP.

To learn more about Apache hbase operator tools, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager
--
Best Regards,
Guangxu


Re: [VOTE] First second candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-19 Thread Guangxu Cheng
Sorry, the title of the vote email is wrong, please ignore the email.
--
Best Regards,
Guangxu


Guangxu Cheng  于2021年12月20日周一 12:49写道:

> Please vote on this Apache hbase operator tools release candidate,
> hbase-operator-tools-1.2.0RC1
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase operator tools 1.2.0
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 1.2.0RC1:
>
>   https://github.com/apache/hbase-operator-tools/tree/1.2.0RC1
>
> This tag currently points to git reference
>
>   478af00af79f82624264fd2bb447b97fecc8e790
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC1
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/org apache hbase-1479
> <https://repository.apache.org/content/repositories/orgapachehbase-1479>
> Artifacts were signed with the 5EF3A66D57EC647A key which can be found in:
>
>   https://downloads.apache.org/hbase/KEYS
>
> hbase-operator-tools 1.2.0 contains a critical security fix for addressing
> the log4j2
> CVE-2021-44228 and CVE-2021-45105. All users who use hbase-operator-tools
> should upgrade to hbase-operator-tools 1.2.0 ASAP.
>
> To learn more about Apache hbase operator tools, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>
> --
> Best Regards,
> Guangxu
>


[VOTE] First second candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-19 Thread Guangxu Cheng
Please vote on this Apache hbase operator tools release candidate,
hbase-operator-tools-1.2.0RC1

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache hbase operator tools 1.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 1.2.0RC1:

  https://github.com/apache/hbase-operator-tools/tree/1.2.0RC1

This tag currently points to git reference

  478af00af79f82624264fd2bb447b97fecc8e790

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC1

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/org apache hbase-1479

Artifacts were signed with the 5EF3A66D57EC647A key which can be found in:

  https://downloads.apache.org/hbase/KEYS

hbase-operator-tools 1.2.0 contains a critical security fix for addressing
the log4j2
CVE-2021-44228 and CVE-2021-45105. All users who use hbase-operator-tools
should upgrade to hbase-operator-tools 1.2.0 ASAP.

To learn more about Apache hbase operator tools, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager

--
Best Regards,
Guangxu


Re: [VOTE] First release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-19 Thread Guangxu Cheng
Thanks duo and stephen!

Will make a new RC1 soon.
--
Best Regards,
Guangxu


Tak Lon (Stephen) Wu  于2021年12月19日周日 15:06写道:

> +1 on the log4j2 2.17.0
>
> -Stephen
>
> On Sat, Dec 18, 2021 at 10:14 PM 张铎(Duo Zhang) 
> wrote:
>
> > Let's also update log4j2 to 2.17.0 for hbase-oeprator-tools?
> >
> > Thanks.
> >
> > 张铎(Duo Zhang)  于2021年12月18日周六 17:07写道:
> >
> > > +1 (binding)
> > >
> > > Checked sigs and sums: Matched
> > > Rat check: Passed
> > > Built from src: Succeeded
> > > Run UTs: Passed
> > > CHANGES and RELEASENOTES: Missed two issues, for generating these two
> > > files and change version in pom. This is not an actual code problem so
> I
> > > always do not want to sink an RC due to the problems on these two
> files.
> > In
> > > the future hbase-operator-tools should consider removing these two
> files
> > > from git too.
> > > Log4j2: Checked the lib directory, the log4j2 version is 2.16.0, which
> is
> > > good.
> > > Run it against a hbase cluster: Use it with the cluster deployed by me
> > for
> > > testing HBASE-26233, the default command failed because of can
> > > not recognize the 'hdfs' protocol. I needed to manually prepend
> > > 'INTERNAL_CLASSPATH=true' when executing the command, like this
> > >   INTERNAL_CLASSPATH=true ./bin/hbase hbck -j
> > >
> >
> /home/sa/disk1/hbase-operator-tools-1.2.0/hbase-hbck2/hbase-hbck2-1.2.0.jar
> > > extraRegionsInMeta default:IntegrationTestRegionReplicaReplication
> > >   But this is not a problem of hbase-operator-tools, it is because we
> do
> > > not shade hadoop-hdfs in our shaded jar. And it is strange that why
> hbck
> > > uses hbase-shaded-client instead of hbase-shaded-mapreduce.
> > >   The stacktrace
> > > 17:04:41.024 [main] ERROR org.apache.hbase.HBCK2 - Error on checking
> > extra
> > > regions:
> > > org.apache.hadoop.fs.UnsupportedFileSystemException: No FileSystem for
> > > scheme "hdfs"
> > > at
> > >
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3281)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3301)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at
> > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3352)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3320)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:479)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hadoop.fs.Path.getFileSystem(Path.java:361)
> > > ~[hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hbase.HBCKFsUtils.getRootDir(HBCKFsUtils.java:106)
> > > ~[hbase-hbck2-1.2.0.jar:1.2.0]
> > > at
> > >
> >
> org.apache.hbase.FsRegionsMetaRecoverer.(FsRegionsMetaRecoverer.java:66)
> > > ~[hbase-hbck2-1.2.0.jar:1.2.0]
> > > at org.apache.hbase.HBCK2.extraRegionsInMeta(HBCK2.java:268)
> > > [hbase-hbck2-1.2.0.jar:1.2.0]
> > > at org.apache.hbase.HBCK2.doCommandLine(HBCK2.java:1020)
> > > [hbase-hbck2-1.2.0.jar:1.2.0]
> > > at org.apache.hbase.HBCK2.run(HBCK2.java:830)
> > [hbase-hbck2-1.2.0.jar:1.2.0]
> > > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> > > [hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> > > [hbase-shaded-client-3.0.0-alpha-2.jar:3.0.0-alpha-2]
> > > at org.apache.hbase.HBCK2.main(HBCK2.java:1145)
> > > [hbase-hbck2-1.2.0.jar:1.2.0
> > >
> > > 张铎(Duo Zhang)  于2021年12月18日周六 16:36写道:
> > >
> > >> The readme of the project says we have two tools, one is HBCK2, the
> > other
> > >> is TableReporter, but in the binary I can only see HBCK2...
> > >>
> > >> But anyway, checking the previous release, we did not include
> > >> TableReporter either, so not this release's fault...
> > >>
> > >> Josh Elser  于2021年12月17日周五 23:03写道:
> > >>
> > >>> +1 (binding)
> > >>>
>

Re: [VOTE] First release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-15 Thread Guangxu Cheng
Thanks for reminding me. I will correct it in the final announcement email

--
Best Regards,
Guangxu


张铎(Duo Zhang)  于2021年12月15日周三 15:24写道:

> The KEYS file should use download.a.o instead of dist.a.o. For the vote
> thread it is not a big deal, but please change it when sending the final
> announcement email, otherwise your email will be rejected by the moderator
> of the announce mailing list...
>
> Guangxu Cheng  于2021年12月15日周三 11:33写道:
>
> > Please vote on this Apache hbase operator tools release candidate,
> > hbase-operator-tools-1.2.0RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase operator tools 1.2.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 1.2.0RC0:
> >
> >   https://github.com/apache/hbase-operator-tools/tree/1.2.0RC0
> >
> > This tag currently points to git reference
> >
> >   76d68624cebb66ec0e509b0a4c0d96445a601685
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1474/
> > Artifacts were signed with the 5EF3A66D57EC647A key which can be found
> in:
> >
> >   https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > hbase-operator-tools 1.2.0 contains a critical security fix for
> addressing
> > the log4j2
> > CVE-2021-44228. All users who use hbase-operator-tools should upgrade
> > to hbase-operator-tools 1.2.0 ASAP.
> >
> > To learn more about Apache hbase operator tools, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
> > --
> > Best Regards,
> > Guangxu
> >
>


[jira] [Resolved] (HBASE-26574) [hbase-operator-tools] Set version as 1.2.0 in master

2021-12-14 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26574.
---
Fix Version/s: hbase-operator-tools-1.2.0
   Resolution: Resolved

> [hbase-operator-tools] Set version as 1.2.0 in master
> -
>
> Key: HBASE-26574
> URL: https://issues.apache.org/jira/browse/HBASE-26574
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: hbase-operator-tools-1.2.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[VOTE] First release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-14 Thread Guangxu Cheng
Please vote on this Apache hbase operator tools release candidate,
hbase-operator-tools-1.2.0RC0

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache hbase operator tools 1.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 1.2.0RC0:

  https://github.com/apache/hbase-operator-tools/tree/1.2.0RC0

This tag currently points to git reference

  76d68624cebb66ec0e509b0a4c0d96445a601685

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:


https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2.0RC0/

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachehbase-1474/
Artifacts were signed with the 5EF3A66D57EC647A key which can be found in:

  https://dist.apache.org/repos/dist/release/hbase/KEYS

hbase-operator-tools 1.2.0 contains a critical security fix for addressing
the log4j2
CVE-2021-44228. All users who use hbase-operator-tools should upgrade
to hbase-operator-tools 1.2.0 ASAP.

To learn more about Apache hbase operator tools, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager

--
Best Regards,
Guangxu


Re: [VOTE] First release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-14 Thread Guangxu Cheng
Sorry, some information is missing from the email. Please ignore the email.
--
Best Regards,
Guangxu


Guangxu Cheng  于2021年12月15日周三 11:25写道:

> Please vote on this Apache hbase operator tools release candidate,
> hbase-operator-tools-1.2.0RC0
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase operator tools 1.2.0
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 1.2.0RC0:
>
>   https://github.com/apache/hbase-operator-tools/tree/1.2.0RC0
>
> This tag currently points to git reference
>
>   76d68624cebb66ec0e509b0a4c0d96445a601685
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2
> .0RC0/
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1474/
> Artifacts were signed with the E65E11D40D80DB7C key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> hbase-operator-tools 1.2.0 contains a critical security fix for addressing
> the log4j2
> CVE-2021-44228. All users who already use hbase-operator-tools 1.1.0
> should upgrade
> to hbase-operator-tools 1.2.0 ASAP.
>
> To learn more about Apache hbase operator tools, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>
>


[VOTE] First release candidate for hbase-operator-tools 1.2.0 is available for download

2021-12-14 Thread Guangxu Cheng
Please vote on this Apache hbase operator tools release candidate,
hbase-operator-tools-1.2.0RC0

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache hbase operator tools 1.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 1.2.0RC0:

  https://github.com/apache/hbase-operator-tools/tree/1.2.0RC0

This tag currently points to git reference

  76d68624cebb66ec0e509b0a4c0d96445a601685

The release files, including signatures, digests, as well as CHANGES.md
and RELEASENOTES.md included in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/hbase/hbase-operator-tools-1.2
.0RC0/

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachehbase-1474/
Artifacts were signed with the E65E11D40D80DB7C key which can be found in:

  https://dist.apache.org/repos/dist/release/hbase/KEYS

hbase-operator-tools 1.2.0 contains a critical security fix for addressing
the log4j2
CVE-2021-44228. All users who already use hbase-operator-tools 1.1.0 should
upgrade
to hbase-operator-tools 1.2.0 ASAP.

To learn more about Apache hbase operator tools, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager


[jira] [Resolved] (HBASE-26573) [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0

2021-12-14 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26573.
---
Resolution: Resolved

> [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0
> 
>
> Key: HBASE-26573
> URL: https://issues.apache.org/jira/browse/HBASE-26573
> Project: HBase
>  Issue Type: Sub-task
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HBASE-26574) [hbase-operator-tools] Set version as 1.2.0 in master

2021-12-14 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-26574:
-

 Summary: [hbase-operator-tools] Set version as 1.2.0 in master
 Key: HBASE-26574
 URL: https://issues.apache.org/jira/browse/HBASE-26574
 Project: HBase
  Issue Type: Sub-task
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HBASE-26573) [hbase-operator-tools] Generate CHANGES.md and RELEASENOTES.md for 1.2.0

2021-12-14 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-26573:
-

 Summary: [hbase-operator-tools] Generate CHANGES.md and 
RELEASENOTES.md for 1.2.0
 Key: HBASE-26573
 URL: https://issues.apache.org/jira/browse/HBASE-26573
 Project: HBase
  Issue Type: Sub-task
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


Re: [NOTICE] Apache log4j2 security vulnerability

2021-12-13 Thread Guangxu Cheng
If there is no objection, I’ll volunteer to RM hbase-operation-tools 1.2.0
--
Best Regards,
Guangxu


张铎(Duo Zhang)  于2021年12月12日周日 22:37写道:

> Besides 3.0.0-alpha-2, we also need to make a new release for
> hbase-operation-tools, any volunteers?
>
> Thanks.
>
> 张铎(Duo Zhang)  于2021年12月10日周五 18:02写道:
>
> > Seems the 2.15.0 is already out. The log4j community decided to close the
> > vote earlier to solve the critical security issue.
> >
> > A developer in our community has already filed an issue and opened a PR.
> >
> > https://issues.apache.org/jira/browse/HBASE-26557
> > https://github.com/apache/hbase/pull/3933
> >
> > Let's get the PR merged and publish 3.0.-alpha-2 ASAP.
> >
> > Tak Lon (Stephen) Wu  于2021年12月10日周五 13:44写道:
> >
> >> Thanks for sharing! I found another post [2] that said how to perform
> such
> >> an attack.
> >>
> >> Should we have a JIRA and keep tracking the solution for it?
> >>
> >> [2] https://www.lunasec.io/docs/blog/log4j-zero-day/
> >>
> >> -Stephen
> >>
> >> On Thu, Dec 9, 2021 at 8:09 PM 张铎(Duo Zhang) 
> >> wrote:
> >>
> >> > See this PR
> >> >
> >> > https://github.com/apache/logging-log4j2/pull/608
> >> >
> >> > Although the final 2.15.0 release for log4j2 has not been published
> >> yet, at
> >> > least on the Chinese internet the details and how to make use of
> >> > this vulnerability has already been public[1].
> >> >
> >> > HBase 3.0.0-alpha-1 is affected, so once 2.15.0 is out, we will push a
> >> > 3.0.0-alpha-2 release out soon. And for those who already use HBase
> >> > 3.0.0-alpha-1, please consider using the following ways to disable
> JNDI
> >> >
> >> > Add '-Dlog4j2.formatMsgNoLookups=true' when starting JVM
> >> > Add 'log4j2.formatMsgNoLookups=True' to config file
> >> > 'export FORMAT_MESSAGES_PATTERN_DISABLE_LOOKUPS=true' before starting
> >> JVM
> >> >
> >> > Thanks.
> >> >
> >> > 1. https://nosec.org/home/detail/4917.html
> >> >
> >>
> >
>


[jira] [Resolved] (HBASE-26166) table list in master ui has a minor bug

2021-08-04 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-26166.
---
Fix Version/s: 2.3.7
   2.4.6
   3.0.0-alpha-2
   2.5.0
 Hadoop Flags: Reviewed
   Resolution: Fixed

> table list in master ui has a minor bug
> ---
>
> Key: HBASE-26166
> URL: https://issues.apache.org/jira/browse/HBASE-26166
> Project: HBase
>  Issue Type: Bug
>  Components: UI
>Affects Versions: 2.4.5
>Reporter: ruanhui
>Assignee: ruanhui
>Priority: Minor
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.6, 2.3.7
>
> Attachments: image-2021-08-03-20-20-25-352.png
>
>
> !image-2021-08-03-20-20-25-352.png|width=931,height=162!



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


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

2021-07-25 Thread Guangxu Cheng
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_201): ok
  - mvn clean apache-rat:check
* Built from source (1.8.0_201): ok
  - mvn clean install -DskipTests
* Unit tests pass (1.8.0_201): ok
  - mvn package -P runSmallTests
* Start in standalone mode: ok
* Basic shell commands (CRUD/flush/compact/split): ok
* Basic WEB UI: ok
--
Best Regards,
Guangxu


Andrew Purtell  于2021年7月24日周六 上午5:27写道:

> Please vote on this Apache hbase release candidate,
> hbase-2.4.4RC0
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase 2.4.4
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.4.5RC0:
>
>   https://github.com/apache/hbase/tree/2.4.5RC0
>
> This tag currently points to git reference 4a2828386.
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/2.4.5RC0/
>
> The API compatibility report can be found at:
>
>
> https://dist.apache.org/repos/dist/dev/hbase/2.4.5RC0/api_compare_2.4.4_to_2.4.5RC0.html
>
> HBASE-25986 intentionally removed the final boolean field
> 'DEFAULT_NORMALIZATION_ENABLED' from HTableDescriptor and
> TableDescriptorBuilder. The default setting represented by this field
> is preserved by a new entry in hbase-default.xml. I think the change
> is acceptable but please be aware of this change when considering your
> vote.
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1459/
>
> Artifacts were signed with the 0xD5365CCD key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> To learn more about Apache hbase, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>


[jira] [Resolved] (HBASE-24605) Break long region names in the web UI

2020-06-22 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-24605.
---
Fix Version/s: 2.2.6
   2.4.0
   2.3.1
   3.0.0-alpha-1
   Resolution: Fixed

Pushed to branch-2.2+, Thanks for your contributing.[~songxincun]

> Break long region names in the web UI
> -
>
> Key: HBASE-24605
> URL: https://issues.apache.org/jira/browse/HBASE-24605
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Affects Versions: 3.0.0-alpha-1
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6
>
> Attachments: image-2020-06-21-20-18-37-041.png, 
> image-2020-06-21-20-19-25-183.png, image-2020-06-21-20-20-02-782.png, 
> image-2020-06-21-20-27-23-474.png, image-2020-06-21-20-28-36-464.png, 
> image-2020-06-21-20-29-07-819.png
>
>
> Before this patch, when it comes to the long region name, the UI content will 
> be out of the screen, making it unreadable. Like this:
> !image-2020-06-21-20-18-37-041.png|width=542,height=50!
> !image-2020-06-21-20-19-25-183.png|width=531,height=23!
> !image-2020-06-21-20-20-02-782.png|width=542,height=146!
>  
> After this patch, the long region name wil be break to the new line, like 
> this:
> !image-2020-06-21-20-27-23-474.png|width=529,height=35!
> !image-2020-06-21-20-28-36-464.png|width=533,height=33!
> !image-2020-06-21-20-29-07-819.png|width=531,height=117!



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


[jira] [Resolved] (HBASE-24478) The regionInfo parameter for MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions should be plural

2020-06-16 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-24478.
---
Fix Version/s: 2.2.6
   2.4.0
   2.3.1
   3.0.0-alpha-1
   Resolution: Fixed

> The regionInfo parameter for MasterProcedureScheduler#waitRegions and 
> MasterProcedureScheduler#wakeRegions should be plural 
> 
>
> Key: HBASE-24478
> URL: https://issues.apache.org/jira/browse/HBASE-24478
> Project: HBase
>  Issue Type: Improvement
>  Components: proc-v2
>Affects Versions: 3.0.0-alpha-1
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6
>
>
> MasterProcedureScheduler#waitRegions and MasterProcedureScheduler#wakeRegions 
> deal with a list of regions, so the variable name of region info should be 
> plural



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


[jira] [Resolved] (HBASE-24417) update copyright notices year to 2020

2020-05-27 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-24417.
---
Fix Version/s: 2.4.0
   2.3.0
   3.0.0-alpha-1
 Assignee: Guangxu Cheng
   Resolution: Fixed

pushed to branch-2.3+

> update copyright notices year to 2020
> -
>
> Key: HBASE-24417
> URL: https://issues.apache.org/jira/browse/HBASE-24417
> Project: HBase
>  Issue Type: Task
>  Components: documentation
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0
>
>




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


Re: [ANNOUNCE] Please welcome Lijin Bin to the HBase PMC

2020-05-26 Thread Guangxu Cheng
Congratulations and welcome, Lijin.

Best Regards,
Guangxu


Allan Yang  于2020年5月26日周二 下午2:47写道:

> Congratulations and welcome, Lijin Bin!
>
> Best Regards
> Allan Yang
>
>
> Reid Chan  于2020年5月26日周二 上午10:14写道:
>
> >
> > Welcome Lijin!
> >
> >
> >
> > --
> >
> > Best regards,
> > R.C
> >
> >
> >
> > 
> > From: Guanghao Zhang 
> > Sent: 25 May 2020 22:22
> > To: HBase Dev List; Hbase-User
> > Subject: [ANNOUNCE] Please welcome Lijin Bin to the HBase PMC
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that Lijin Bin
> > has accepted our invitation to become a PMC member on the Apache HBase
> > project. We appreciate Lijin Bin stepping up to take more responsibility
> in
> > the HBase project.
> >
> > Please join me in welcoming Lijin Bin to the HBase PMC!
> >
>


[jira] [Created] (HBASE-24417) update copyright notices year to 2020

2020-05-22 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-24417:
-

 Summary: update copyright notices year to 2020
 Key: HBASE-24417
 URL: https://issues.apache.org/jira/browse/HBASE-24417
 Project: HBase
  Issue Type: Task
  Components: documentation
Reporter: Guangxu Cheng






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


Re: [ANNOUNCE] New HBase committer Wei-Chiu Chuang

2020-05-14 Thread Guangxu Cheng
Congratulations and welcome Wei-Chiu !!!
--
Best Regards,
Guangxu


Reid Chan  于2020年5月14日周四 下午6:59写道:

>
> Congratulations and welcome!
>
>
> --
>
> Best regards,
> R.C
>
>
>
> 
> From: ramkrishna vasudevan 
> Sent: 14 May 2020 13:42
> To: dev
> Subject: Re: [ANNOUNCE] New HBase committer Wei-Chiu Chuang
>
> Congratulations Wei-Chiu !!!
>
> Regards
> Ram
>
> On Thu, May 14, 2020 at 10:55 AM Viraj Jasani  wrote:
>
> > Congratulations Wei-Chiu !!
> >
> > On 2020/05/13 19:12:38, Sean Busbey  wrote:
> > > Folks,
> > >
> > > On behalf of the Apache HBase PMC I am pleased to announce that
> Wei-Chiu
> > > Chuang has accepted the PMC's invitation to become a committer on the
> > > project.
> > >
> > > We appreciate all of the great contributions Wei-Chiu has made to the
> > > community thus far and we look forward to his continued involvement.
> > >
> > > Allow me to be the first to congratulate Wei-Chiu on his new role!
> > >
> > > thanks,
> > > busbey
> > >
> >
>


[jira] [Resolved] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled

2020-04-22 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23896.
---
Resolution: Fixed

> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not 
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
>  Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot 
> delete the snapshot. This is because the owner of the snapshot cannot be 
> taken during permission verification. By investigation, found that only after 
> HBase has enabled security authentication, the owner will be set when doing 
> snapshot. 
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
>   if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
>   }
> });
> {code}
>  



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


[jira] [Resolved] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled

2020-04-19 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23896.
---
Fix Version/s: 2.2.5
   2.4.0
   2.3.0
   3.0.0
   Resolution: Fixed

> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not 
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
>  Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot 
> delete the snapshot. This is because the owner of the snapshot cannot be 
> taken during permission verification. By investigation, found that only after 
> HBase has enabled security authentication, the owner will be set when doing 
> snapshot. 
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
>   if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
>   }
> });
> {code}
>  



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


[jira] [Resolved] (HBASE-24176) user_permission '.*' command failed to show all table permissions

2020-04-13 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-24176.
---
Fix Version/s: 2.2.5
   2.4.0
   2.3.0
   3.0.0
   Resolution: Fixed

> user_permission '.*'  command failed to show all table permissions
> --
>
> Key: HBASE-24176
> URL: https://issues.apache.org/jira/browse/HBASE-24176
> Project: HBase
>  Issue Type: Bug
>Reporter: song XinCun
>Assignee: song XinCun
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When we grant somebody global permission, then we use '.*' as the argument of 
> user_permission to show all table permissions, the following exception 
> occurred:
> {code:java}
> hbase(main):001:0>  grant 'user3', 'RW'
> Took 0.4144 seconds   
>   
>
> hbase(main):002:0> user_permission 
> User 
> Namespace,Table,Family,Qualifier:Permission   
> 
>  user2   ,,,: [Permission: 
> actions=READ,WRITE]   
>   
>  user3   ,,,: [Permission: 
> actions=READ,WRITE]   
>   
>  hbaseadmin  ,,,: [Permission: 
> actions=READ,WRITE,EXEC,CREATE,ADMIN] 
>   
> 3 row(s)
> Took 0.0445 seconds   
>   
>
> hbase(main):003:0> user_permission '.*'
> User 
> Namespace,Table,Family,Qualifier:Permission   
> 
>  user1   default,t1,,: [Permission: 
> actions=READ,WRITE]   
>  
>  hbaseadmin  default,t1,,: [Permission: 
> actions=READ,WRITE,EXEC,CREATE,ADMIN] 
>  ERROR: failed to coerce 
> org.apache.hadoop.hbase.security.access.GlobalPermission to 
> org.apache.hadoop.hbase.security.access.TablePermissionFor usage try 'help 
> "user_permission"'Took 0.0940 seconds 
> {code}



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


[jira] [Created] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled

2020-02-26 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-23896:
-

 Summary: Snapshot owner cannot delete snapshot when ACL is enabled 
and Kerberos is not enabled
 Key: HBASE-23896
 URL: https://issues.apache.org/jira/browse/HBASE-23896
 Project: HBase
  Issue Type: Task
Affects Versions: 2.2.3, 3.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot 
delete the snapshot. This is because the owner of the snapshot cannot be taken 
during permission verification. By investigation, found that only after HBase 
has enabled security authentication, the owner will be set when doing snapshot. 

SnapshotManager#takeSnapshotInternal
{code:title=SnapshotManager.java|borderStyle=solid}
RpcServer.getRequestUser().ifPresent(user -> {
  if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
builder.setOwner(user.getShortName());
  }
});
{code}


 



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


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

2020-02-13 Thread Guangxu Cheng
+1 (binding)

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

  * Start in standalone mode: ok
  * Basic shell commands (CRUD/flush/compact/split): ok
  * LTT 2M rows:  ok
  * Basic WEB UI: ok

--
Best Regards,
Guangxu


Andrew Purtell  于2020年2月14日周五 上午6:01写道:

> +1 (binding)
>
> *Summary*
>
> * 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, see detail below
>  - mvn package -P runAllTests
>
> *Repeatable failures*
>
> TestServerSideScanMetricsFromClientSide
>
> Passes when run standalone. When run in suite there were these failures:
>
> [ERROR]   Run 1:
>
> TestServerSideScanMetricsFromClientSide.testRowsSeenMetricWithAsync:172->testRowsSeenMetric:196->testRowsSeenMetric:208->testMetric:336
> » TestTimedOut
> [ERROR]   Run 2: TestServerSideScanMetricsFromClientSide »  Appears to be
> stuck in thread RS-Ev...
> [ERROR]   Run 3:
> TestServerSideScanMetricsFromClientSide.setUpBeforeClass:92 » IllegalState
> A m...
> [ERROR]   Run 4:
> TestServerSideScanMetricsFromClientSide.setUpBeforeClass:92 »
> InconsistentFSState
> [ERROR]
>
> TestServerSideScanMetricsFromClientSide.testRowsFilteredMetric:248->testRowsFilteredMetric:267->testRowsFilteredMetric:322->testMetric:336
> » Runtime
> [ERROR]
> TestServerSideScanMetricsFromClientSide.testRowsSeenMetricWithAsync »
> NullPointer
> [ERROR]   TestScannersFromClientSide.tearDownAfterClass:110 » IO Waiting
> for shutdown of...
>
> TestRegionReplicas
>
> Passes when run standalone. When run in suite there were these failures:
>
> [ERROR]   Run 1:
> TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> TestTimedOut
> [ERROR]   Run 2: TestRegionReplicas »  Appears to be stuck in thread
> Default-IPC-NioEventLoopGr...
>
> *Flakes*
>
> TestHbckChore
>
> [ERROR]   Run 1: TestHbckChore.testForDisabledTable:168
> [INFO]   Run 2: PASS
>
> TestRegionMoveAndAbandon
>
> [ERROR]   Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> org.apache.hadoop.hbase.client.Ret...
> [INFO]   Run 2: PASS
>
> TestCellACLWithMultipleVersions
>
> [ERROR]   Run 1:
>
> TestCellACLWithMultipleVersions.testCellPermissionwithVersions:217->SecureTestUtil.verifyAllowed:213
> expected:<2> but was:<1>
> [INFO]   Run 2: PASS
>
>
> On Tue, Feb 11, 2020 at 6:53 PM Duo Zhang  wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.1.9RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.1.9
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.1.9RC0:
> >
> > https://github.com/apache/hbase/tree/2.1.9RC0
> >
> > 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.1.9RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1382/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > 2.1.9 includes ~62 bug and improvement fixes done since the 2.1.8.
> >
> >  To learn more about apache hbase, please see
> > http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


Re: [ANNOUNCE] Please welcome Guangxu Cheng the HBase PMC

2019-12-10 Thread Guangxu Cheng
Thanks everybody. It’s an honor to join the PMC and I’ll try to do my best
to help the project and the
community.

ramkrishna vasudevan  于2019年12月10日周二
下午12:26写道:

> Welcome and congratulations  Guangxu!!
>
> On Tue, Dec 10, 2019 at 2:48 AM Andrew Purtell 
> wrote:
>
> > Congratulations and welcome Guangxu!
> >
> > On Mon, Dec 9, 2019 at 1:47 AM Duo Zhang  wrote:
> >
> > > On behalf of the Apache HBase PMC I am pleased to announce that Guangxu
> > > Cheng has accepted our invitation to become a PMC member on the Apache
> > > HBase project. We appreciate Guangxu Cheng stepping up to take more
> > > responsibility in the HBase project.
> > >
> > > Please join me in welcoming Guangxu Cheng to the HBase PMC!
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>


[jira] [Resolved] (HBASE-20395) Displaying thrift server type on the thrift page

2019-11-28 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-20395.
---
Resolution: Fixed

pushed the addendum to branch-2 and master. Thanks @Beata Sudi

> Displaying thrift server type on the thrift page
> 
>
> Key: HBASE-20395
> URL: https://issues.apache.org/jira/browse/HBASE-20395
> Project: HBase
>  Issue Type: Improvement
>  Components: Thrift
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-20395.addendum.patch, 
> HBASE-20395.master.001.patch, HBASE-20395.master.002.patch, 
> HBASE-20395.master.003.patch, HBASE-20395.master.004.patch, 
> HBASE-20395.master.005.patch, HBASE-20395.master.005.patch, result.png
>
>
> HBase supports two types of thrift server: thrift and thrift2.
> But after start the thrift server successfully, we can not get the thrift 
> server type conveniently. 
> So, displaying thrift server type on the thrift page may provide some 
> convenience for the users.



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


[jira] [Reopened] (HBASE-20395) Displaying thrift server type on the thrift page

2019-11-28 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng reopened HBASE-20395:
---

> Displaying thrift server type on the thrift page
> 
>
> Key: HBASE-20395
> URL: https://issues.apache.org/jira/browse/HBASE-20395
> Project: HBase
>  Issue Type: Improvement
>  Components: Thrift
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HBASE-20395.master.001.patch, 
> HBASE-20395.master.002.patch, HBASE-20395.master.003.patch, 
> HBASE-20395.master.004.patch, HBASE-20395.master.005.patch, 
> HBASE-20395.master.005.patch, result.png
>
>
> HBase supports two types of thrift server: thrift and thrift2.
> But after start the thrift server successfully, we can not get the thrift 
> server type conveniently. 
> So, displaying thrift server type on the thrift page may provide some 
> convenience for the users.



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


[jira] [Resolved] (HBASE-23293) [REPLICATION] make ship edits timeout configurable

2019-11-27 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23293.
---
Fix Version/s: 2.2.3
   2.3.0
   3.0.0
   Resolution: Fixed

> [REPLICATION] make ship edits timeout configurable
> --
>
> Key: HBASE-23293
> URL: https://issues.apache.org/jira/browse/HBASE-23293
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication
>Reporter: chenxu
>Assignee: chenxu
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
>
> ReplicationSourceShipper#shipEdits may take a while if bulkload replication 
> enabled, since we should copy HFile from the source cluster, so i think there 
> is a need to make the timeout value configurable.



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


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

2019-11-27 Thread Guangxu Cheng
+1 (non-binding)
  Ran the vote script and the result is as follows. The reason why checksum
failed is that the format of
hbase-1.4.12-bin.tar.gz.sha512/hbase-1.4.12-src.tar.gz.sha512 are wrong,
checksum matching

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

  * Start in standalone mode: ok
  * Basic shell commands (CRUD/flush/compact/split): ok
  * LTT 2M rows:  ok
  * Basic WEB UI: ok

Jan Hentschel  于2019年11月27日周三 上午2:40写道:

> +1 (binding)
>
> Ran the vote script and had the same problem/solution with the checksum
> described by Wellington below.
>
> * Signature: ok
> * Checksum : failed
> * 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
>
> Best, Jan
>
> From: Wellington Chevreuil 
> Reply-To: "dev@hbase.apache.org" 
> Date: Tuesday, November 26, 2019 at 2:32 PM
> To: "dev@hbase.apache.org" 
> Subject: Re: [VOTE] First release candidate for Apache HBase 1.4.12
>
> +1
> Downloaded source tar, unpacked, then running hbase-vote script all passed,
> apart from checksum failure, but I then had checksum manually and it is
> matching.
> * Signature: ok
> * Checksum : failed
> * Rat check (1.8.0_222): ok
>  - mvn clean apache-rat:check
> * Built from source (1.8.0_222): ok
>  - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_222): ok
>  - mvn package -P runSmallTests
> Built from source on pseudo distributed mode:
> CRUD operations: ok
> ltt 10,000,000: ok
> Web UI: ok
>
> Em dom., 24 de nov. de 2019 às 20:54, Sean Busbey  >
> escreveu:
>
> The first release candidate for HBase 1.4.12 is available for download:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.12RC0/
>
> Maven artifacts are also available in a staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1373/
>
> 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.12RC0, which currently points
> to commit ref
>
> 6ae4a77408ad35d6a7a4e5cebfd401fc4b72b5ec
>
> HBase 1.4.12 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 about a dozen
> fixes and improvements done by the HBase community in the five
> weeks since the prior release.
>
> The detailed source and binary compatibility report vs 1.4.11 has been
> published for your review, at:
>
> https://s.apache.org/hbase-1.4.12-rc0-compat-report
>
> The report shows no issues.
>
> Critical changes include:
>
> * HBASE-23227 - Upgrade jackson-databind to 2.9.10.1 to avoid recent
>  CVEs
> * HBASE-23287 - WALs not aged off of HDFS because LogCleaner is not
>  added to choreService
>
> The full set of fixes in this release can be found here:
>
> https://s.apache.org/hbase-1.4.12-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.12.
>
> The VOTE will remain open for at least 72 hours.
>
> Thanks!
>
> --busbey
>
> as of this email the posted artifacts have the following SHA512:
>
> hbase-1.4.12-src.tar.gz:
> 72A0E4DF BB44C4F3 A07E3FB5 5D6FD3BC DD40C9CC
> BCD311C0 CB61ACB4 2756C735 D465A340 FB05176D
> DDCB29C5 A5D695F6 BC8F8E7E 3AAF6499 8A149DA8
> EC6C4E7A
>
> hbase-1.4.12-bin.tar.gz:
> 58E2873F E4725E0C 6E77437E B09864A5 BD9E50DD
> 9BBE84AD 7461FBCA 8AE51A0C D91DA20B 90E8AD82
> DCF50EB2 C82AC3C8 26CD1C58 8ED69D2A 1E6AD0B4
> 24CD94D5
>
>
>


[jira] [Resolved] (HBASE-23336) [CLI] Incorrect row(s) count "clear_deadservers"

2019-11-26 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23336.
---
Fix Version/s: 2.1.9
   2.2.3
   2.3.0
   3.0.0
   Resolution: Fixed

> [CLI] Incorrect row(s) count  "clear_deadservers"
> -
>
> Key: HBASE-23336
> URL: https://issues.apache.org/jira/browse/HBASE-23336
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 3.0.0, 2.1.0, 2.2.0
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> [HBASE-15849|https://issues.apache.org/jira/browse/HBASE-15849] simplified 
> the format of command total runtime but clear_deadservers caller has not 
> modified so it prints current timestamp instead of no of rows. 
>  
> {code:java}
> hbase(main):015:0>  clear_deadservers 
> 'kpalanisamy-apache302.openstacklocal,16020'
> SERVERNAME
> kpalanisamy-apache302.openstacklocal,16020,16020
> 1574585488 row(s)
> Took 0.0145 seconds
> {code}
>  
>  



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


[jira] [Resolved] (HBASE-23334) The table-lock node of zk is not needed since HBASE-16786

2019-11-25 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23334.
---
Fix Version/s: 2.2.3
   2.3.0
   3.0.0
   Resolution: Fixed

> The table-lock node of zk is not needed since HBASE-16786
> -
>
> Key: HBASE-23334
> URL: https://issues.apache.org/jira/browse/HBASE-23334
> Project: HBase
>  Issue Type: Improvement
>Reporter: Zheng Wang
>Assignee: Zheng Wang
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
>
> The table-lock znode still be created when init,and it may cause confusion.



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


[jira] [Resolved] (HBASE-23237) Negative 'Requests per Second' counts in UI

2019-11-23 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23237.
---
Fix Version/s: 2.1.9
   2.2.3
   1.6.0
   2.3.0
   Resolution: Fixed

> Negative 'Requests per Second' counts in UI
> ---
>
> Key: HBASE-23237
> URL: https://issues.apache.org/jira/browse/HBASE-23237
> Project: HBase
>  Issue Type: Bug
>  Components: UI
>Affects Versions: 2.2.2
>Reporter: Michael Stack
>Assignee: Karthik Palanisamy
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3, 2.1.9
>
> Attachments: Screen Shot 2019-10-30 at 9.45.58 PM.png
>
>
> I see request per second showing with negative sign.
>  !Screen Shot 2019-10-30 at 9.45.58 PM.png! 



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


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

2019-11-23 Thread Guangxu Cheng
+1 (non-binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_201): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_201): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_201): ok
 - mvn package -P runAllTests
* Start in standalone mode: ok
* Basic shell commands (CRUD/flush/compact/split): ok
* LTT 2M rows:  ok
* WEB UI(master/RS/TableDetails): ok

Karthik P  于2019年11月23日周六 下午8:04写道:

> +1 (non-binding)
>
> Setup:
> rhel 7 (3.10.0-123.9.3.el7.x86_64) & jdk1.8.0_211
> Installation 2.1.8RC0 via local build
> Fully distributed secure mode: 1 master and 3 regionservers
> - Signature: ok
> - Checksum : ok
> - Rat check (jdk1.8.0_211): ok
> - Built from source (jdk1.8.0_211): ok
> - Admin cli:  ok
> namespace:  ok
> ddl:  ok
> dml:  ok
> general:  ok
> tools:  ok
> snapshots:  ok
> configuration:  ok
> quotas:  ok  [observation: reset limit is broken for
> throttle_type => write]
> procedures:  ok
> security:  ok
> visibility labels:  ok
> rsgroup:  ok  [observation: 'move_servers_rsgroup'
> return incorrect message]
> replication:  Haven't tested yet.
> - Webui:  ok  [observation: little mess in sorting option. pfa]
> - Regionserver groupping:  ok
> - Security, acl and visibility lables:  ok
> - Secure rest:  ok
> - Secure thrift:  ok
> - Ran ltt for 20m rows(write operation):  ok
> I will check and file a Jira tomorrow for these observations but these are
> minor.
>
>
> - Karthik
>
> On Fri, Nov 22, 2019 at 6:46 AM Wellington Chevreuil <
> wellington.chevre...@gmail.com> wrote:
>
>> +1
>> Signature: ok
>> Checksum : ok
>> Rat check (1.8.0_222): ok
>> Built from source (1.8.0_222): ok
>> Tests: ok
>> Run manual CRUD tests deployed on pseudo distributed mode: ok
>> hbase ltt -tn test-2 -families cf -write 5:100:5 -num_keys 100: ok
>>
>>
>> Em qua., 20 de nov. de 2019 às 06:15, Duo Zhang 
>> escreveu:
>>
>> > Please vote on this Apache hbase release candidate,
>> > hbase-2.1.8RC0
>> >
>> > The VOTE will remain open for at least 72 hours.
>> >
>> > [ ] +1 Release this package as Apache hbase 2.1.8
>> > [ ] -1 Do not release this package because ...
>> >
>> > The tag to be voted on is 2.1.8RC0:
>> >
>> > https://github.com/apache/hbase/tree/2.1.8RC0
>> >
>> > 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.1.8RC0/
>> >
>> > Maven artifacts are available in a staging repository at:
>> >
>> >
>> https://repository.apache.org/content/repositories/orgapachehbase-1372/
>> >
>> > Artifacts were signed with the 9AD2AE49 key which can be found in:
>> >
>> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
>> >
>> > 2.1.8 includes ~59 bug and improvement fixes done since the 2.1.7.
>> > We upgrade jackson to 2.9.10.1 due to CVE-2019-16942 and CVE-2019-16943.
>> >
>> >  To learn more about apache hbase, please see
>> > http://hbase.apache.org/
>> >
>> > Thanks,
>> > Your HBase Release Manager
>> >
>>
>


[jira] [Resolved] (HBASE-23278) Add a table-level compaction progress display on the UI

2019-11-19 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23278.
---
Fix Version/s: 2.2.3
   1.6.0
   2.3.0
   3.0.0
   Resolution: Fixed

>  Add a table-level compaction progress display on the UI
> 
>
> Key: HBASE-23278
> URL: https://issues.apache.org/jira/browse/HBASE-23278
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>Affects Versions: 1.6.0, master
>Reporter: Baiqiang Zhao
>Assignee: Baiqiang Zhao
>Priority: Minor
> Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3
>
> Attachments: HBase-23278-v2.png, HBase-23278.png, 
> image-2019-11-11-20-35-56-103.png, image-2019-11-11-20-37-53-367.png, 
> image-2019-11-11-20-44-04-050.png
>
>
> We have regionserver-level compaction progress in UI. However, we often 
> compact a table, why there is no table-level compaction progress?Use multiple 
> tabs to show  compaction progress.
> !HBase-23278-v2.png!



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


Re: [DISCUSS] Deprecate Review Board in favor of Github reviews

2019-11-14 Thread Guangxu Cheng
+1
It will be more convenient to use Github PR.

张铎(Duo Zhang)  于2019年11月14日周四 下午6:17写道:

> +1,  ReviewBoard is almost dead now as it is only available to
> committers...
>
> Jan Hentschel  于2019年11月14日周四 下午6:11写道:
>
> > +1
> >
> > I also like the GitHub way much more compared to ReviewBoard.
> >
> > From: Peter Somogyi 
> > Reply-To: "dev@hbase.apache.org" 
> > Date: Wednesday, November 13, 2019 at 6:23 PM
> > To: HBase Dev List 
> > Subject: Re: [DISCUSS] Deprecate Review Board in favor of Github reviews
> >
> > +1
> >
> > Another issue with ReviewBoard is that it requires Apache ID so only
> > committers are able to create new reviews or even comment.
> >
> > On Wed, Nov 13, 2019 at 5:21 PM Nick Dimiduk   > ndimi...@apache.org>> wrote:
> >
> > Heya,
> >
> > Seems in the old days we were explicitly non-strict about where code
> review
> > were happening. I remember bouncing between Review Board and a
> Phabricator
> > instance (in addition to in-line patch reviews on JIRA). Now that we have
> > this fancy Gitbox and integration with GitHub, it seems we're making a
> > strong statement toward using Github PRs (in addition to in-line patch
> > reviews on JIRA) for our code review system. Is it worth while supporting
> > those older tools? I think maintaining the developer support tooling
> around
> > just these two mechanisms is plenty to keep up with.
> >
> > I propose we make the move to Github PR's "official". This
> > basically involves updating the tome (here [0], here [1], probably
> others)
> > accordingly and sweeping the `dev-support` dir for old scripts.
> >
> > Thoughts?
> >
> > Thanks,
> > Nick
> >
> > [0]: http://hbase.apache.org/book.html#developing
> > [1]: http://hbase.apache.org/book.html#reviewboard
> >
> >
> >
>


Re: [ANNOUNCE] New HBase committer Ankit Singhal

2019-11-12 Thread Guangxu Cheng
Congratulations and welcome, Ankit!

Toshihiro Suzuki  于2019年11月13日周三 上午6:46写道:

> Congratulations! Ankit
>
> On Wed, Nov 13, 2019 at 6:56 AM Esteban Gutierrez
>  wrote:
>
> > Congrats, Ankit!
> > --
> > Cloudera, Inc.
> >
> >
> >
> > On Tue, Nov 12, 2019 at 2:59 PM Jan Hentschel <
> > jan.hentsc...@ultratendency.com> wrote:
> >
> > > Congratulations and welcome!
> > >
> > > From: Josh Elser 
> > > Reply-To: "dev@hbase.apache.org" 
> > > Date: Tuesday, November 12, 2019 at 5:39 PM
> > > To: dev 
> > > Subject: [ANNOUNCE] New HBase committer Ankit Singhal
> > >
> > > 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!
> > >
> > >
> >
>


[jira] [Resolved] (HBASE-23074) scan#setVersion is invalid.

2019-11-11 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23074.
---
Resolution: Duplicate

> scan#setVersion is invalid.
> ---
>
> Key: HBASE-23074
> URL: https://issues.apache.org/jira/browse/HBASE-23074
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.1.1, master
>Reporter: Bo Cui
>Priority: Critical
> Attachments: image-2019-09-25-16-45-08-870.png, 
> image-2019-09-25-16-45-37-780.png
>
>
> I found a problem, it could be a mistake..
> reproduce steps in hbase shell:
> 1. create 't11', \{NAME => 'f1', VERSIONS => 1}
> 2.put 't11','r1','f1:q1','f1'
> 3.flush 't11'
> 4.put 't11','r1','f1:q1','f2'
> 5.flush 't11'
> 6.scan 't11', \{RAW => true, VERSIONS => 10, FILTER => "(QualifierFilter (>=, 
> 'binary:f1'))"}
>  
> the result:
>  1. 1.3.1 version
>  hbase(main):011:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER => 
> "(QualifierFilter (>=, 'binary:q1'))"}
>  ROW COLUMN+CELL 
>  r1 column=f1:q1, timestamp=1569400085570, value=f2 
>  r1 column=f1:q1, timestamp=1569400068958, value=f1
>  2. in 2.1.1 version
>  hbase(main):023:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER => 
> "(QualifierFilter (>=, 'binary:q1'))"}
>  ROW COLUMN+CELL 
>  r1 column=f1:q1, timestamp=1569400122280, value=f2 
>  1 row(s)
>  Took 0.0800 seconds
>  
>  



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


[jira] [Created] (HBASE-23274) Remove auto generated files by thrift from project

2019-11-09 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-23274:
-

 Summary: Remove auto generated files by thrift from project
 Key: HBASE-23274
 URL: https://issues.apache.org/jira/browse/HBASE-23274
 Project: HBase
  Issue Type: Bug
Reporter: Guangxu Cheng






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


[jira] [Resolved] (HBASE-22980) HRegionPartioner getPartition() method incorrectly partitions the regions of the table.

2019-11-06 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-22980.
---
Fix Version/s: 2.2.3
   2.1.8
   2.3.0
   3.0.0
   Resolution: Fixed

> HRegionPartioner getPartition() method incorrectly partitions the regions of 
> the table.
> ---
>
> Key: HBASE-22980
> URL: https://issues.apache.org/jira/browse/HBASE-22980
> Project: HBase
>  Issue Type: Bug
>  Components: mapreduce
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
>
> *Problem:*
> Partitioner class HRegionPartitioner in a HBase MapReduce job has a method 
> getPartition(). In getPartition(), there is a scenario where we have check 
> for less number of reducers than region. This scenario seems incorrect 
> because for a rowKey present in last region(let us say nth region) , 
> getPartition() should return value (n-1). But it is not returning n-1 for the 
> last region as it is falling in the case where number of reducers < number of 
> regions and returning some random value. 
> So if a client uses this class as a partitioner class in HBase MapReduce 
> jobs, this method incorrectly partitions the regions because rowKeys present 
> in the last regions does not fall to the last region.
> [https://github.com/apache/hbase/blob/fbd5b5e32753104f88600b0f4c803ab5659bce64/hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/HRegionPartitioner.java#L92]
> Consider the following scenario:
> if there are 5 regions for the table, partitions = 5 and number of reducers 
> is also 5.
> So in this case above check for reducers < regions should not return true.
> But for the last region when i=4(last region, 5th region) , getPartition 
> should return 4 but it returns 2 because it falls in the case of when we have 
> less reduces than region and returns true for the above condition even though 
> we have reducers = regions. So the condition is incorrect.
>  
> *Solution:*
> Instead of
>   {code} if (i >= numPartitions-1) {code} 
> It should be
>{code} if (i >= numPartitions){  {code}



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


[jira] [Created] (HBASE-23232) Remove rsgroup profile from pom.xml of hbase-assembly

2019-10-30 Thread Guangxu Cheng (Jira)
Guangxu Cheng created HBASE-23232:
-

 Summary: Remove rsgroup profile from pom.xml of hbase-assembly
 Key: HBASE-23232
 URL: https://issues.apache.org/jira/browse/HBASE-23232
 Project: HBase
  Issue Type: Sub-task
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


branch HBASE-22514 built failed



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


[jira] [Resolved] (HBASE-23200) incorrect description in SortedCompactionPolicy.getNextMajorCompactTime

2019-10-28 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23200.
---
Resolution: Implemented

Implemented by HBASE-23149

> incorrect description in SortedCompactionPolicy.getNextMajorCompactTime
> ---
>
> Key: HBASE-23200
> URL: https://issues.apache.org/jira/browse/HBASE-23200
> Project: HBase
>  Issue Type: Bug
>  Components: Compaction
>Affects Versions: master
>Reporter: jackylau
>Assignee: jackylau
>Priority: Major
> Fix For: 2.2.3
>
>
> // default = 24hrs
> long ret = comConf.getMajorCompactionPeriod();
> but the default value is 7 days in CompactionConfiguration.java



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


[jira] [Resolved] (HBASE-23199) Error populating Table-Attribute fields

2019-10-28 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23199.
---
Fix Version/s: 2.2.3
   2.3.0
   3.0.0
   Resolution: Fixed

Pushed to branch2.2+. 

Thank [~kpalanisamy] for contributing.

> Error populating Table-Attribute fields
> ---
>
> Key: HBASE-23199
> URL: https://issues.apache.org/jira/browse/HBASE-23199
> Project: HBase
>  Issue Type: Bug
>  Components: master, UI
>Affects Versions: 3.0.0
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
> Attachments: Screen Shot 2019-10-21 at 3.25.40 PM.png
>
>
> if quota is enabled, then we fetch table and namespace quota info. It is not 
> necessary both table and namespace will have a quota set.  Sometimes, users 
> only have table level quota or namespace level quota or both un-set.  So we 
> must add Quota "null" check before getting Throttle info(Limit, Type, 
> TimeUnit, Scope). 
>  
> !Screen Shot 2019-10-21 at 3.25.40 PM.png!



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


[jira] [Resolved] (HBASE-23211) Table UI showed exception message when Quota is enabled

2019-10-28 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23211.
---
Resolution: Duplicate

> Table UI showed exception message when Quota is enabled
> ---
>
> Key: HBASE-23211
> URL: https://issues.apache.org/jira/browse/HBASE-23211
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Affects Versions: 2.2.1
>Reporter: xinxin fan
>Priority: Major
> Attachments: image-2019-10-24-10-40-45-152.png
>
>
> org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:361)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748)



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

2019-10-27 Thread Guangxu Cheng
Sorry about that. I don't know this rule yet. Thank you very much for
pointing out this. @palomino219 

张铎(Duo Zhang)  于2019年10月25日周五 上午8:56写道:

> +1 from me.
>
> With 4 +1s, 3 bindings, the vote passes.
>
> Let me push out the release.
>
> BTW, Guangxu, binding means you are a PMC member of HBase, but actually you
> are not till now...
>
> 张铎(Duo Zhang)  于2019年10月25日周五 上午8:53写道:
>
> > For IA.Public there is no IS annotation, all should be IS.Stable.
> >
> > And the exception here is that, we are allowed to add methods to an
> > interface without default implementation if the interface is not expected
> > to be implemented by users. ClusterMetrics is exactly the case here,
> users
> > only get it from the cluster and make use of it, it is not likely that
> > users will implement their own ClusterMetrics.
> >
> > Maybe we can introduce a new IA annotation to indicate this case, like
> > IA.PublicForUse, IA.PublicForExtends, etc.
> >
> > Sakthi  于2019年10月24日周四 下午9:56写道:
> >
> >> +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
> >> > > > >> 

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

2019-10-24 Thread Guangxu Cheng
+1 (binding)

- Signature & Checksum: OK
- Rat check (8u102) : OK
- Built from source (8u102): OK
- Unit tests pass (8u102)(Except TestRSGroupsKillRS): OK
- LTT 2M rows (8u102):  OK
- WEB UI(master/RS/TableDetails): OK
- Basic shell commands (CRUD/flush/compact/split): OK

Sakthi  于2019年10月24日周四 下午9:56写道:

> +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: [ANNOUNCE] Please welcome Sakthi to the Apache HBase PMC

2019-10-24 Thread Guangxu Cheng
Congratulations !

Wellington Chevreuil  于2019年10月24日周四
下午10:48写道:

> Congratulations, Sakthi!
>
> Em qui, 24 de out de 2019 às 12:38, Reid Chan 
> escreveu:
>
> > Welcome Sakthi! Congratulations!
> >
> >
> > --
> >
> > Best regards,
> > R.C
> >
> >
> >
> > 
> > From: Sean Busbey 
> > Sent: 24 October 2019 04:14
> > To: dev; Hbase-User
> > Subject: [ANNOUNCE] Please welcome Sakthi to the Apache HBase PMC
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that
> > Sakthi has accepted our invitation to become a PMC member on the
> > HBase project. We appreciate Sakthi stepping up to take more
> > responsibility in the HBase project.
> >
> > Please join me in welcoming Jan 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: [ANNOUNCE] Please welcome Balazs Meszaros to the Apache HBase PMC

2019-10-24 Thread Guangxu Cheng
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] [Resolved] (HBASE-23149) hbase shouldPerformMajorCompaction logic is not correct

2019-10-24 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23149.
---
Fix Version/s: 1.5.1
   1.3.7
   Resolution: Fixed

Pushed to branch-1, branch-1.3 and branch-1.4. Thanks [~jackylau] for 
contributing.

> hbase shouldPerformMajorCompaction logic is not correct
> ---
>
> Key: HBASE-23149
> URL: https://issues.apache.org/jira/browse/HBASE-23149
> Project: HBase
>  Issue Type: Bug
>  Components: Compaction
>Affects Versions: 1.4.9
>Reporter: jackylau
>Assignee: jackylau
>Priority: Major
> Fix For: 1.4.12, 1.3.7, 1.5.1
>
>
> we can know that the major compaction is skipping  from the below 
> regionserver's log, but it is compacting that region.
> and read the code and find it is not correct  and i add mark  "/*** ***/" 
> below
>  
> public boolean shouldPerformMajorCompaction(final Collection 
> filesToCompact)
>  throws IOException {
>  if (lowTimestamp > 0L && lowTimestamp < (now - mcTime)) {
>  if (filesToCompact.size() == 1) {
>  if (sf.isMajorCompaction() && (cfTTL == Long.MAX_VALUE || oldest < cfTTL)) {
>  float blockLocalityIndex =
>  sf.getHDFSBlockDistribution().getBlockLocalityIndex(
>  RSRpcServices.getHostname(comConf.conf, false));
>  if (blockLocalityIndex < comConf.getMinLocalityToForceCompact())
> { result = true; }
> else
> { LOG.debug("Skipping major compaction of " + regionInfo + " because one 
> (major) compacted file only, oldestTime " + oldest + "ms is < TTL=" + cfTTL + 
> " and blockLocalityIndex is " + blockLocalityIndex + " (min " + 
> comConf.getMinLocalityToForceCompact() + ")"); }
> } else if (cfTTL != HConstants.FOREVER && oldest > cfTTL)
> { LOG.debug("Major compaction triggered on store " + regionInfo + ", because 
> keyvalues outdated; time since last major compaction " + (now - lowTimestamp) 
> + "ms"); result = true; }
> } else
> { LOG.debug("Major compaction triggered on store " + regionInfo + "; time 
> since last major compaction " + (now - lowTimestamp) + "ms"); }
> result = true;{color:#de350b}  */**here it is not right, it should be 
> move to the above */*{color}
>  }
>  return result;
>  }
>  
> 2019-09-27 09:09:35,960 DEBUG [st129,16020,1568236573216_ChoreService_1] 
> compactions.RatioBasedCompactionPolicy: Skipping major compaction of 
> 100E_POINT_point_2ddata_z3_geom_GpsTime_v6,\x17,1568215725799.413a563092544e8df480fd601b2de71b.
>  because one (major) compacted file only, oldestTime 3758085589ms is < 
> TTL=9223372036854775807 and blockLocalityIndex is 1.0 (min 0.0)
>  2019-09-27 09:09:35,961 DEBUG [st129,16020,1568236573216_ChoreService_1] 
> compactions.SortedCompactionPolicy: Selecting compaction from 1 store files, 
> 0 compacting, 1 eligible, 100 blocking
>  2019-09-27 09:09:35,961 DEBUG [st129,16020,1568236573216_ChoreService_1] 
> regionserver.HStore: 413a563092544e8df480fd601b2de71b - d: Initiating major 
> compaction (all files)
>  2019-09-27 09:09:35,961 DEBUG [st129,16020,1568236573216_ChoreService_1] 
> regionserver.CompactSplitThread: Large Compaction requested: 
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine$DefaultCompactionContext@4b5582f1;
>  Because: CompactionChecker requests major compaction; use default priority; 
> compaction_queue=(1:0), split_queue=0, merge_queue=0
>  2019-09-27 09:09:35,961 INFO 
> [regionserver/st129/10.3.72.129:16020-longCompactions-1568236575579] 
> regionserver.HRegion: Starting compaction on d in region 
> 100E_POINT_point_2ddata_z3_geom_GpsTime_v6,\x17,1568215725799.413a563092544e8df480fd601b2de71b.
>  2019-09-27 09:09:35,961 INFO 
> [regionserver/st129/10.3.72.129:16020-longCompactions-1568236575579] 
> regionserver.HStore: Starting compaction of 1 file(s) in d of 
> 100E_POINT_point_2ddata_z3_geom_GpsTime_v6,\x17,1568215725799.413a563092544e8df480fd601b2de71b.
>  into 
> tmpdir=hdfs://st129:8020/hbase/data/default/100E_POINT_point_2ddata_z3_geom_GpsTime_v6/413a563092544e8df480fd601b2de71b/.tmp,
>  totalSize=5.1 G
>  2019-09-27 09:09:35,961 DEBUG 
> [regionserver/st129/10.3.72.129:16020-longCompactions-1568236575579] 
> compactions.Compactor: Compacting 
> hdfs://st129:8020/hbase/data/default/100E_POINT_point_2ddata_z3_geom_GpsTime_v6/413a563092544e8df480fd601b2de71b/d/3b4080f9b6f149e1b0a476058c8564e6,
>  keycount=83914030, bloomtype=NONE, size=5.1 G, encoding=FAST_DIFF, 
> compression=SNAPPY, seqNum=2621061, earliestPutTs=1565788490371



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


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

2019-10-17 Thread Guangxu Cheng
+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
>


[jira] [Resolved] (HBASE-23176) delete_all_snapshot does not work with regex

2019-10-17 Thread Guangxu Cheng (Jira)


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

Guangxu Cheng resolved HBASE-23176.
---
Fix Version/s: 3.0.0
   Resolution: Fixed

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

> delete_all_snapshot does not work with regex
> 
>
> Key: HBASE-23176
> URL: https://issues.apache.org/jira/browse/HBASE-23176
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 3.0.0
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Major
> Fix For: 3.0.0
>
>
> Delete_all_snapshot.rb is using deprecated method 
> SnapshotDescription#getTable but this method is already removed in 3.0.x.
> {code:java}
> hbase(main):022:0>delete_all_snapshot("t10.*")
> SNAPSHOT TABLE + CREATION 
> TIME ERROR: undefined method `getTable' for 
> #
> {code}



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


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

2019-08-05 Thread Guangxu Cheng
Congratulations, Zheng!

Allan Yang  于2019年8月5日周一 下午5:13写道:

> Congratulations, Hu!
> Best Regards
> Allan Yang
>
>
> Peter Somogyi  于2019年8月5日周一 下午4:47写道:
>
> > Congratulations!
> >
> > On Mon, Aug 5, 2019 at 8:57 AM Pankaj kr  wrote:
> >
> > > Congratulations Zheng..!!
> > >
> > > Regards,
> > > Pankaj
> > >
> > > -Original Message-
> > > From: Duo Zhang [mailto:zhang...@apache.org]
> > > Sent: 05 August 2019 07:38
> > > To: HBase Dev List ; hbase-user <
> > > u...@hbase.apache.org>
> > > Subject: [ANNOUNCE] Please welcome Zheng Hu to the HBase PMC
> > >
> > > 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] Please welcome Peter Somogyi to the HBase PMC

2019-01-21 Thread Guangxu Cheng
Congratulations Peter!

-
Best Regards
Guangxu Cheng

Allan Yang  于2019年1月22日周二 上午10:15写道:

> Congratulations Peter!
> Best Regards
> Allan Yang
>
>
> Pankaj kr  于2019年1月22日周二 上午9:49写道:
>
> >
> > Congratulations Peter...!!!
> >
> > Regards,
> > Pankaj
> >
> > --
> > Pankaj Kumar
> > M: +91-9535197664(India Contact Number)
> > E: pankaj...@huawei.com<mailto:pankaj...@huawei.com>
> > 2012实验室-班加罗尔研究所IT BU分部
> > 2012 Laboratories-IT BU Branch Dept.HTIPL
> > From:Duo Zhang 
> > To:HBase Dev List ;hbase-user <
> u...@hbase.apache.org
> > >
> > Date:2019-01-22 07:06:43
> > Subject:[ANNOUNCE] Please welcome Peter Somogyi to the HBase PMC
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that Peter
> > Somogyi
> > has accepted our invitation to become a PMC member on the Apache HBase
> > project.
> > We appreciate Peter stepping up to take more responsibility in the HBase
> > project.
> >
> > Please join me in welcoming Peter to the HBase PMC!
> >
>


Re: [ANNOUNCE] Allan Yang joins the Apache HBase PMC

2018-11-28 Thread Guangxu Cheng
Congratulations, Allan!

Guanghao Zhang  于2018年11月29日周四 上午11:12写道:

> Congratulations!
>
> Reid Chan  于2018年11月29日周四 上午10:17写道:
>
> > Congratulations! Allan
> >
> > --
> >
> > Best regards,
> > R.C
> >
> >
> >
> > 
> > From: Jingyun Tian 
> > Sent: 29 November 2018 09:43
> > To: dev@hbase.apache.org
> > Subject: Re: [ANNOUNCE] Allan Yang joins the Apache HBase PMC
> >
> > Congratulations! Allan!
> >
> > On Thu, Nov 29, 2018 at 9:42 AM OpenInx  wrote:
> >
> > > Congratulations, Allan!
> > >
> > > On Thu, Nov 29, 2018 at 6:58 AM Zach York <
> zyork.contribut...@gmail.com>
> > > wrote:
> > >
> > > > Congratulations and welcome Allan!
> > > >
> > > >
> > > > On Wed, Nov 28, 2018 at 10:21 AM Esteban Gutierrez
> > > >  wrote:
> > > >
> > > > > Congratulations, Allan!
> > > > >
> > > > > --
> > > > > Cloudera, Inc.
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Nov 28, 2018 at 10:11 AM Yu Li  wrote:
> > > > >
> > > > > > On behalf of the Apache HBase PMC I am pleased to announce that
> > Allan
> > > > > Yang
> > > > > > has accepted our invitation to become a PMC member on the Apache
> > > HBase
> > > > > > project. We appreciate Allan stepping up to take more
> > responsibility
> > > in
> > > > > the
> > > > > > HBase project.
> > > > > >
> > > > > > Please join me in welcoming Allan to the HBase PMC!
> > > > > >
> > > > > > Best Regards,
> > > > > > Yu
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: Re: [ANNOUNCE] New HBase committer Jingyun Tian

2018-11-13 Thread Guangxu Cheng
Congratulations and welcome, Jingyun!

Best Regards,
Guangxu



Tencent/Guangxu Cheng
 
From: Nihal Jain
Date: 2018-11-13 17:30
To: dev
Subject: Re: [ANNOUNCE] New HBase committer Jingyun Tian
Congratulations Jingyun :)
 
Regards,
Nihal
 
On Tue 13 Nov, 2018, 2:19 PM Yu Li  Congratulations and welcome, Jingyun!
>
> Best Regards,
> Yu
>
>
> On Tue, 13 Nov 2018 at 16:46, Srinivas Reddy 
> wrote:
>
> > Congratulations Jingyun
> >
> > -
> > Srinivas
> >
> > - Typed on tiny keys. pls ignore typos.{mobile app}
> >
> > On Tue 13 Nov, 2018, 15:54 张铎(Duo Zhang)  >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Jingyun
> > > Tian has accepted the PMC's invitation to become a committer on the
> > > project. We appreciate all of Jingyun's generous contributions thus far
> > and
> > > look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Jingyun!
> > >
> >
>


Re: [ANNOUNCE] Please welcome Zach York to the HBase PMC

2018-10-11 Thread Guangxu Cheng
Congratulations, Zach !

Srinivas Reddy  于2018年10月12日周五 下午12:15写道:

> Congratulations Zach.
>
> -
> Srinivas
>
> - Typed on tiny keys. pls ignore typos.{mobile app}
>
> On Fri 12 Oct, 2018, 04:01 Sean Busbey,  wrote:
>
> > On behalf of the Apache HBase PMC I am pleased to announce that Zach
> > York has accepted our invitation to become a PMC member on the Apache
> > HBase project. We appreciate Zach stepping up to take more
> > responsibility in the HBase project.
> >
> > Please join me in welcoming Zach 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: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Guangxu Cheng
Congratulations and welcome Balazs.

Srinivas Reddy  于2018年10月12日周五 下午12:14写道:

> Congratulations Balazs.
>
> -
> Srinivas
>
> - Typed on tiny keys. pls ignore typos.{mobile app}
>
> On Fri 12 Oct, 2018, 03:49 Sean Busbey,  wrote:
>
> > On behalf of the HBase PMC, I'm pleased to announce that Balazs
> > Meszaros has accepted our invitation to become an HBase committer.
> >
> > Thanks for all your hard work Balazs; we look forward to more
> > contributions!
> >
> > Please join me in extending congratulations to Balazs!
> >
>


[jira] [Created] (HBASE-21218) TableStateNotFoundException thrown from RSGroupAdminEndpoint#postCreateTable when creating table

2018-09-21 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21218:
-

 Summary: TableStateNotFoundException thrown from 
RSGroupAdminEndpoint#postCreateTable when creating table
 Key: HBASE-21218
 URL: https://issues.apache.org/jira/browse/HBASE-21218
 Project: HBase
  Issue Type: Bug
  Components: rsgroup
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


Similar to HBASE-19509, I found the following logs in master log when creating 
table
{code}
2018-09-21 15:14:47,476 ERROR 
[RpcServer.default.FPBQ.Fifo.handler=296,queue=26,port=16000] 
master.TableStateManager: Unable to get table t3 state
org.apache.hadoop.hbase.master.TableStateManager$TableStateNotFoundException: t3
at 
org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:215)
at 
org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:147)
at 
org.apache.hadoop.hbase.master.assignment.AssignmentManager.isTableDisabled(AssignmentManager.java:344)
at 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminServer.moveTables(RSGroupAdminServer.java:412)
at 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.assignTableToGroup(RSGroupAdminEndpoint.java:471)
at 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint.postCreateTable(RSGroupAdminEndpoint.java:494)
at 
org.apache.hadoop.hbase.master.MasterCoprocessorHost$12.call(MasterCoprocessorHost.java:335)
at 
org.apache.hadoop.hbase.master.MasterCoprocessorHost$12.call(MasterCoprocessorHost.java:332)
at 
org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:540)
at 
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:614)
at 
org.apache.hadoop.hbase.master.MasterCoprocessorHost.postCreateTable(MasterCoprocessorHost.java:332)
at org.apache.hadoop.hbase.master.HMaster$3.run(HMaster.java:1929)
at 
org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:131)
at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1911)
at 
org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:628)
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)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
{code}  

In fact, we only need to change the information of rsgroup without moving 
region.



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


[jira] [Created] (HBASE-21179) Fix the number of actions in responseTooSlow log

2018-09-10 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21179:
-

 Summary: Fix the number of actions in responseTooSlow log
 Key: HBASE-21179
 URL: https://issues.apache.org/jira/browse/HBASE-21179
 Project: HBase
  Issue Type: Bug
  Components: rpc
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{panel:title=responseTooSlow|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
2018-09-10 16:13:53,022 WARN  
[B.DefaultRpcServer.handler=209,queue=29,port=60020] ipc.RpcServer: 
(responseTooSlow): 
{"processingtimems":321262,"call":"Multi(org.apache.hadoop.hbase.protobuf.generated.ClientProtos$MultiRequest)","client":"127.0.0.1:56149","param":"region=
 
tsdb,\\x00\\x00.[\\x89\\x1F\\xB0\\x00\\x00\\x01\\x00\\x01Y\\x00\\x00\\x02\\x00\\x00\\x04,1536133210446.7c752de470bd5558a001117b123a5db5.,
 {color:red}for 1 actions and 1st row{color} 
key=\\x00\\x00.[\\x96\\x16p","starttimems":1536566911759,"queuetimems":0,"class":"HRegionServer","responsesize":2,"method":"Multi"}
{panel}

The responseTooSlow log is printed when the processing time of a request 
exceeds the specified threshold. The number of actions and the contents of the 
first rowkey in the request will be included in the log.
However, the number of actions is inaccurate, and it is actually the number of 
regions that the request needs to visit.
Just like the logs above, users may be mistaken for using 321262ms to process 
an action, which is incredible, so we need to fix it.



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


[jira] [Created] (HBASE-21174) [REST] Failed to parse empty qualifier in TableResource#getScanResource

2018-09-09 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21174:
-

 Summary: [REST] Failed to parse empty qualifier in 
TableResource#getScanResource
 Key: HBASE-21174
 URL: https://issues.apache.org/jira/browse/HBASE-21174
 Project: HBase
  Issue Type: Bug
  Components: REST
Affects Versions: 3.0.0, 2.2.0
 Environment: {code:xml}
GET /t1/*?column=f:c1=f:
{code}
If I want to get the values of 'f:'(empty qualifier) for all rows in the table 
by rest server, I will send the above request. However, this request will 
return all column values.
{code:java|title=TableResource#getScanResource|borderStyle=solid}
  for (String csplit : column) {
String[] familysplit = csplit.trim().split(":");
if (familysplit.length == 2) {
  if (familysplit[1].length() > 0) {
if (LOG.isTraceEnabled()) {
  LOG.trace("Scan family and column : " + familysplit[0] + "  " + 
familysplit[1]);
}
tableScan.addColumn(Bytes.toBytes(familysplit[0]), 
Bytes.toBytes(familysplit[1]));
  } else {
tableScan.addFamily(Bytes.toBytes(familysplit[0]));
if (LOG.isTraceEnabled()) {
  LOG.trace("Scan family : " + familysplit[0] + " and empty 
qualifier.");
}
tableScan.addColumn(Bytes.toBytes(familysplit[0]), null);
  }
} else if (StringUtils.isNotEmpty(familysplit[0])) {
  if (LOG.isTraceEnabled()) {
LOG.trace("Scan family : " + familysplit[0]);
  }
  tableScan.addFamily(Bytes.toBytes(familysplit[0]));
}
  }
{code}
Through the above code, when the column has an empty qualifier, the empty 
qualifier cannot be parsed correctly.In other words, 'f:'(empty qualifier) and 
'f' (column family) are considered to have the same meaning, which is wrong.
    Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code:title=TableResource#getScanResource|borderStyle=solid}
  for (String csplit : column) {
String[] familysplit = csplit.trim().split(":");
if (familysplit.length == 2) {
  if (familysplit[1].length() > 0) {
if (LOG.isTraceEnabled()) {
  LOG.trace("Scan family and column : " + familysplit[0] + "  " + 
familysplit[1]);
}
tableScan.addColumn(Bytes.toBytes(familysplit[0]), 
Bytes.toBytes(familysplit[1]));
  } else {
tableScan.addFamily(Bytes.toBytes(familysplit[0]));
if (LOG.isTraceEnabled()) {
  LOG.trace("Scan family : " + familysplit[0] + " and empty 
qualifier.");
}
tableScan.addColumn(Bytes.toBytes(familysplit[0]), null);
  }
} else if (StringUtils.isNotEmpty(familysplit[0])) {
  if (LOG.isTraceEnabled()) {
LOG.trace("Scan family : " + familysplit[0]);
  }
  tableScan.addFamily(Bytes.toBytes(familysplit[0]));
}
  }
{code}
{code:xml}
GET /t1/*?column=f:c1=f:
{code}



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


[jira] [Created] (HBASE-21173) Remove the duplicate HRegion#close in TestHRegion

2018-09-08 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21173:
-

 Summary: Remove the duplicate HRegion#close in TestHRegion
 Key: HBASE-21173
 URL: https://issues.apache.org/jira/browse/HBASE-21173
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 3.0.0, 2.2.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


 After HBASE-21138, some test methods still have the duplicate HRegion#close.So 
open this issue to remove the duplicate close



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


[jira] [Created] (HBASE-21158) Empty qualifier cell is always returned when using QualifierFilter

2018-09-06 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21158:
-

 Summary: Empty qualifier cell is always returned when using 
QualifierFilter
 Key: HBASE-21158
 URL: https://issues.apache.org/jira/browse/HBASE-21158
 Project: HBase
  Issue Type: Bug
  Components: Filters
Affects Versions: 3.0.0, 2.2.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code:xml}
hbase(main):002:0> put 'testTable','testrow','f:testcol1','testvalue1'
0 row(s) in 0.0040 seconds

hbase(main):003:0> put 'testTable','testrow','f:','testvalue2'
0 row(s) in 0.0070 seconds

# get row with empty column f:, result is correct.
hbase(main):004:0> scan 'testTable',{FILTER => "QualifierFilter (=, 'binary:')"}
ROW COLUMN+CELL 

   
 testrowcolumn=f:, timestamp=1536218563581, 
value=testvalue2
   
1 row(s) in 0.0460 seconds

# get row with column f:testcol1, result is incorrect.
hbase(main):005:0> scan 'testTable',{FILTER => "QualifierFilter (=, 
'binary:testcol1')"}
ROW COLUMN+CELL 

   
 testrowcolumn=f:, timestamp=1536218563581, 
value=testvalue2
   
 testrowcolumn=f:testcol1, 
timestamp=1536218550827, value=testvalue1   

1 row(s) in 0.0070 seconds
{code}

As the above operation, when the row contains empty qualifier column, empty 
qualifier cell is always returned when using QualifierFilter.



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


[jira] [Created] (HBASE-21143) Update findbugs-maven-plugin to 3.0.4

2018-09-03 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21143:
-

 Summary: Update findbugs-maven-plugin to 3.0.4
 Key: HBASE-21143
 URL: https://issues.apache.org/jira/browse/HBASE-21143
 Project: HBase
  Issue Type: Bug
  Components: pom
Affects Versions: 2.0.2, 2.1.0, 3.0.0, 2.2.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code}
Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.0:findbugs 
(default) on project hbase: Execution default of goal 
org.codehaus.mojo:findbugs-maven-plugin:3.0.0:findbugs failed: Plugin 
org.codehaus.mojo:findbugs-maven-plugin:3.0.0 or one of its dependencies could 
not be resolved: Failed to collect dependencies at 
org.codehaus.mojo:findbugs-maven-plugin:jar:3.0.0 -> 
org.codehaus.groovy:groovy-all:jar:1.7.4: Failed to read artifact descriptor 
for org.codehaus.groovy:groovy-all:jar:1.7.4: Could not transfer artifact 
org.codehaus.groovy:groovy-all:pom:1.7.4 from/to mirror 
(http://xxx..xxx/nexus/content/groups/public): Failed to transfer file: 
http://xxx..xxx/nexus/content/groups/public/org/codehaus/groovy/groovy-all/1.7.4/groovy-all-1.7.4.pom.
 Return code is: 418 , ReasonPhrase:Artifact is in Tencent Blacklist! Please 
update to the safe version, more information: 
http://xxx..xxx/?tab=blackList.
{code}
Recently, when I compile HBase with a new machine, I got the above error. Since 
the machine could not connect to the external network, we visited our internal 
Maven repository, but org.codehaus.groovy:groovy-all:jar:1.7.4 was added to the 
blacklist and could not be downloaded. See details, 
org.codehaus.groovy:groovy-all:jar:1.7.4 is marked as vulnerable by 
[CVE-2015-3253|https://www.cvedetails.com/cve/CVE-2015-3253], so we should 
upgrade the version.
{code:xml}
  org.codehaus.mojo
  findbugs-maven-plugin
  3.0.0
  
  

${project.basedir}/../dev-support/findbugs-exclude.xml
{code}
Look at the history commit record, findbugs-maven-plugin has been upgraded to 
3.0.4 in HBASE-18264, but one place is missing which still using the version of 
3.0.0.



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


[jira] [Resolved] (HBASE-18910) Backport HBASE-17292 "Add observer notification before bulk loaded hfile is moved to region directory" to 1.3

2018-09-02 Thread Guangxu Cheng (JIRA)


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

Guangxu Cheng resolved HBASE-18910.
---
   Resolution: Won't Fix
Fix Version/s: (was: 1.3.3)

> Backport HBASE-17292 "Add observer notification before bulk loaded hfile is 
> moved to region directory" to 1.3
> -
>
> Key: HBASE-18910
> URL: https://issues.apache.org/jira/browse/HBASE-18910
> Project: HBase
>  Issue Type: Bug
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Attachments: HBASE-18910.branch-1.3.v1.patch
>
>
> HBASE-18900 will backport HBASE-17290 to branch-1.3.But  HBASE-17290 is 
> dependent on HBASE-17292.so this issue will backport HBASE-17292 to 
> branch-1.3.



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


[jira] [Created] (HBASE-21133) '/version' in rest should return hbase rest client version

2018-08-30 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21133:
-

 Summary: '/version' in rest should return hbase rest client version
 Key: HBASE-21133
 URL: https://issues.apache.org/jira/browse/HBASE-21133
 Project: HBase
  Issue Type: Bug
  Components: REST
Affects Versions: 2.0.1, 3.0.0, 2.2.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


restVersion is a constant, which is meaningless.
{code:java}
  public VersionModel(ServletContext context) {
restVersion = RESTServlet.VERSION_STRING;
{code}
{code:java}
String VERSION_STRING = "0.0.3";
{code}

the result of '/version'
{code:json}
{"Server":"jetty/6.1.26","Jersey":"1.9","REST":"0.0.3","JVM":"Oracle 
Corporation 1.8.0_102-25.102-b14","OS":"Linux 2.6.32.57-tlinux-1.1.2-container 
amd64"}
{code}



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


[jira] [Created] (HBASE-21132) return wrong result in rest multiget

2018-08-30 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-21132:
-

 Summary: return wrong result in rest multiget
 Key: HBASE-21132
 URL: https://issues.apache.org/jira/browse/HBASE-21132
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.0.0, 3.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


There are two ways to specify columns in multi-gets feature。

1、Specify columns in PathParam as described in HBASE-15870. Examples: 
{code:sh}GET /t1/multiget/cf1:c1,cf2?row=r1{code}
2、Specify columns in QueryParam. Examples:
{code:sh} GET /t1/multiget?row=r1/cf1:c1,cf2=r2/cf2 {code}

However, when we specify columns in QueryParam, the result is wrong , the 
rowkey contains the columns.





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


Re: Re: [ANNOUNCE] New Committer: Toshihiro Suzuki

2018-08-01 Thread Guangxu Cheng
Congratulations!



Tencent/Guangxu Cheng
 
From: Guanghao Zhang
Date: 2018-08-02 10:27
To: dev
Subject: Re: [ANNOUNCE] New Committer: Toshihiro Suzuki
Congratulations!
 
2018-08-02 6:10 GMT+08:00 张铎(Duo Zhang) :
 
>  Congratulations!
>
> 2018-08-02 2:40 GMT+08:00 Esteban Gutierrez 
> :
>
> > Congrats, Toshi! and welcome!
> >
> > --
> > Cloudera, Inc.
> >
> >
> > On Wed, Aug 1, 2018 at 12:38 PM, Andrew Purtell 
> > wrote:
> >
> > > Congratulations! And welcome.
> > >
> > > On Wed, Aug 1, 2018 at 7:47 AM Josh Elser  wrote:
> > >
> > > > On behalf of the HBase PMC, I'm pleased to announce that Toshihiro
> > > > Suzuki (aka Toshi, brfn169) has accepted our invitation to become an
> > > > HBase committer. This was extended to Toshi as a result of his
> > > > consistent, high-quality contributions to HBase. Thanks for all of
> your
> > > > hard work, and we look forward to working with you even more!
> > > >
> > > > Please join me in extending a hearty "congrats" to Toshi!
> > > >
> > > > - Josh
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>


[jira] [Created] (HBASE-20845) Support set the consistency for Gets and Scans in thrift2

2018-07-04 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20845:
-

 Summary: Support set the consistency for Gets and Scans in thrift2
 Key: HBASE-20845
 URL: https://issues.apache.org/jira/browse/HBASE-20845
 Project: HBase
  Issue Type: Improvement
  Components: Thrift
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng
 Fix For: 3.0.0, 2.1.0, 2.2.0


Support set the consistency for Gets and Scans in thrift2



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


[jira] [Reopened] (HBASE-20474) Show non-RPC tasks on master/regionserver Web UI by default

2018-07-03 Thread Guangxu Cheng (JIRA)


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

Guangxu Cheng reopened HBASE-20474:
---

> Show non-RPC tasks on master/regionserver Web UI  by default
> 
>
> Key: HBASE-20474
> URL: https://issues.apache.org/jira/browse/HBASE-20474
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
> Attachments: HBASE-20474.master.001.patch, tasks-UI.png
>
>
> Now, when opening master or regionserver pages, all tasks will be displayed 
> on the page, however, but in most cases we will pay more attention to non-RPC 
> tasks.
> In addition, if all tasks are displayed by default, a large number of pages 
> will be occupied.



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


[jira] [Resolved] (HBASE-20474) Show non-RPC tasks on master/regionserver Web UI by default

2018-07-03 Thread Guangxu Cheng (JIRA)


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

Guangxu Cheng resolved HBASE-20474.
---
Resolution: Fixed

> Show non-RPC tasks on master/regionserver Web UI  by default
> 
>
> Key: HBASE-20474
> URL: https://issues.apache.org/jira/browse/HBASE-20474
> Project: HBase
>  Issue Type: Improvement
>  Components: UI
>    Reporter: Guangxu Cheng
>    Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
> Attachments: HBASE-20474.master.001.patch, tasks-UI.png
>
>
> Now, when opening master or regionserver pages, all tasks will be displayed 
> on the page, however, but in most cases we will pay more attention to non-RPC 
> tasks.
> In addition, if all tasks are displayed by default, a large number of pages 
> will be occupied.



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


[jira] [Created] (HBASE-20636) Introduce two bloom filter type : ROWPREFIX and ROWPREFIX_DELIMITED

2018-05-24 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20636:
-

 Summary: Introduce two bloom filter type : ROWPREFIX and 
ROWPREFIX_DELIMITED
 Key: HBASE-20636
 URL: https://issues.apache.org/jira/browse/HBASE-20636
 Project: HBase
  Issue Type: New Feature
  Components: regionserver
 Environment: As we all know, HBase uses BloomFilter(ROW and ROWCOL) to 
filter unnecessary files to improve read performance. But they only support Get 
and do not support Scan.

In our company(Tencent), many users need to scan all rows with the same prefix, 
such as Tencent Game. Game user's some operational record will be written into 
HBase, each game user will have a lot of records, the rowkey is constructed as 
userid+'#'+timestamps. So we can scan all records for a given user for a 
specified period.

For this scenario, we designed the prefix Bloom filter. If the startRow and 
stopRow of the Scan has a valid common prefix, the scan will be allowed to use 
BloomFilter to filter files which will enhance the performance of the scan.

Now, this feature has been running on our cluster over a year, and scan 
performance for this scenario has been improved by more than one times than 
before.
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng






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


[jira] [Created] (HBASE-20626) Change the value of "Requests Per Second" on WEBUI

2018-05-23 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20626:
-

 Summary: Change the value of "Requests Per Second" on WEBUI
 Key: HBASE-20626
 URL: https://issues.apache.org/jira/browse/HBASE-20626
 Project: HBase
  Issue Type: Improvement
  Components: metrics, UI
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


Now we use "totalRequestCount"(RSRpcServices#requestCount) to calculate 
requests per second.
 After HBASE-18469, "totalRequestCount" count only once for multi 
request.(Includes requests that are not serviced by regions.)
 When we have a large number of read and write requests, the value of "Requests 
Per Second" is very small which does not reflect the load of the cluster.

Maybe it is more reasonable to use "totalRowActionRequestCount" to calculate 
RPS?



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


[jira] [Created] (HBASE-20474) Show non-RPC tasks on master/regionserver Web UI by default

2018-04-22 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20474:
-

 Summary: Show non-RPC tasks on master/regionserver Web UI  by 
default
 Key: HBASE-20474
 URL: https://issues.apache.org/jira/browse/HBASE-20474
 Project: HBase
  Issue Type: Improvement
  Components: UI
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


Now, when opening master or regionserver pages, all tasks will be displayed on 
the page, however, but in most cases we will pay more attention to non-RPC 
tasks.
In addition, if all tasks are displayed by default, a large number of pages 
will be occupied.



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


[jira] [Created] (HBASE-20396) Remove redundant MBean from thrift JMX

2018-04-12 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20396:
-

 Summary: Remove redundant MBean from thrift JMX
 Key: HBASE-20396
 URL: https://issues.apache.org/jira/browse/HBASE-20396
 Project: HBase
  Issue Type: Improvement
  Components: Thrift
 Environment: HBase has two types of thrift server. When any type of 
thrift server is started, the MBean of the two thrift servers will be 
registered which is redundant.
For example, when starting thrift2, we only need to register MBean 
"Hadoop:service=HBase,name=Thrift,sub=ThriftTwo" of thrift2 in JMX, there's no 
need to register MBean "Hadoop:service=HBase,name=Thrift,sub=ThriftOne" of 
thrift. vice versa
        Reporter: Guangxu Cheng
        Assignee: Guangxu Cheng






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


[jira] [Created] (HBASE-20395) Displaying thrift server type on the thrift page

2018-04-12 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20395:
-

 Summary: Displaying thrift server type on the thrift page
 Key: HBASE-20395
 URL: https://issues.apache.org/jira/browse/HBASE-20395
 Project: HBase
  Issue Type: Improvement
  Components: Thrift
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


HBase supports two types of thrift server: thrift and thrift2.

But after start the thrift server successfully, we can not get the thrift 
server type conveniently. 

So, displaying thrift server type on the thrift page may provide some 
convenience for the users.



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


[jira] [Created] (HBASE-20243) [Shell] Add shell command to create a new table by cloning the existent table

2018-03-21 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20243:
-

 Summary: [Shell] Add shell command to create a new table by 
cloning the existent table
 Key: HBASE-20243
 URL: https://issues.apache.org/jira/browse/HBASE-20243
 Project: HBase
  Issue Type: Improvement
  Components: shell
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


In the production environment, we need to create a new table every day. The 
schema and the split keys of the table are the same as that of yesterday's 
table, only the name of the table is different. For example, 
x_20180321,x_20180322 etc.But now there is no convenient command to do 
this. So we may need such a command(clone_table) to create a new table by 
cloning the existent table.



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


[jira] [Created] (HBASE-20220) [RSGroup] Check if table exists in the cluster before moving it to the specified regionserver group

2018-03-19 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-20220:
-

 Summary: [RSGroup] Check if table exists in the cluster before 
moving it to the specified regionserver group
 Key: HBASE-20220
 URL: https://issues.apache.org/jira/browse/HBASE-20220
 Project: HBase
  Issue Type: Improvement
  Components: rsgroup
Affects Versions: 3.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


move_tables_rsgroup/move_servers_tables_rsgroup can move non-existent tables in 
the cluster to the specified regionserver group successfully.It's not 
reasonable.We should check whether the table has already existed in the cluster 
before moving the table.



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


[jira] [Created] (HBASE-19799) Add web UI to rsgroup

2018-01-15 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19799:
-

 Summary: Add web UI to rsgroup
 Key: HBASE-19799
 URL: https://issues.apache.org/jira/browse/HBASE-19799
 Project: HBase
  Issue Type: New Feature
  Components: rsgroup, UI
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


When the RSGroup feature is enabled, there is’t a webui to show the details of 
rsgroup. we can only view the details of the rsgroup via shell commands, which 
is inconvenient.

This issue will add a webui to rsgroup. To show the statistics and details of 
each rsgroup



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


[jira] [Created] (HBASE-19561) maxCacheSize in CacheEvictionStats can't be accumulated repeatedly When dealing with each region

2017-12-19 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19561:
-

 Summary: maxCacheSize in CacheEvictionStats can't be accumulated 
repeatedly When dealing with each region
 Key: HBASE-19561
 URL: https://issues.apache.org/jira/browse/HBASE-19561
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code:title=HRegionServer.java|borderStyle=solid}
  public CacheEvictionStats clearRegionBlockCache(Region region) {
BlockCache blockCache = this.getCacheConfig().getBlockCache();
long evictedBlocks = 0;

for(Store store : region.getStores()) {
  for(StoreFile hFile : store.getStorefiles()) {
evictedBlocks += 
blockCache.evictBlocksByHfileName(hFile.getPath().getName());
  }
}

return CacheEvictionStats.builder()
.withEvictedBlocks(evictedBlocks)
.withMaxCacheSize(blockCache.getMaxSize())
.build();
  }
{code}

BlockCache is the regionserver level object.If we accumulate this value for 
each region, we will get a wrong result.
The value of maxCacheSize should be set to BlockCache.getMaxSize() after 
processing all the regions on this regionserver.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19518) Moving the bulk load hooks to SecureBulkLoadEndpoint

2017-12-14 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19518:
-

 Summary: Moving the bulk load hooks to SecureBulkLoadEndpoint
 Key: HBASE-19518
 URL: https://issues.apache.org/jira/browse/HBASE-19518
 Project: HBase
  Issue Type: Bug
Reporter: Guangxu Cheng


Based on the discussion in HBASE-19483, we should move the bulk load hooks from 
AccessController to SecureBulkLoadEndpoint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19432) Roll the specified writer in HFileOutputFormat2

2017-12-05 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19432:
-

 Summary: Roll the specified writer in HFileOutputFormat2
 Key: HBASE-19432
 URL: https://issues.apache.org/jira/browse/HBASE-19432
 Project: HBase
  Issue Type: Improvement
Affects Versions: 3.0.0, 2.0.0-beta-1
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code}
// If any of the HFiles for the column families has reached
// maxsize, we need to roll all the writers
if (wl != null && wl.written + length >= maxsize) {
  this.rollRequested = true;
}
{code}
If we always roll all the writers, a large number of small files will be 
generated in the multi family or multi table scene.
So we should only roll the specified writer which HFile has reached maxsize.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19325) Pass a list of server name to postClearDeadServers

2017-11-22 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19325:
-

 Summary: Pass a list of server name to postClearDeadServers
 Key: HBASE-19325
 URL: https://issues.apache.org/jira/browse/HBASE-19325
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


Over on the tail of HBASE-18131. [~chia7712] said 
{quote}
(Revisiting the AccessController remind me of this issue) 
Could we remove the duplicate code on the server side? Why not pass a list of 
server name to postClearDeadServers and postListDeadServers?
{quote}
The duplicate code has been removed in HBASE-19131.Now Pass a list of server 
name to postClearDeadServers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19199) RatioBasedCompactionPolicy#shouldPerformMajorCompaction() always return true when only one file needs to compact

2017-11-07 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19199:
-

 Summary: RatioBasedCompactionPolicy#shouldPerformMajorCompaction() 
always return true when only one file needs to compact
 Key: HBASE-19199
 URL: https://issues.apache.org/jira/browse/HBASE-19199
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.3.1, 3.0.0, 1.4.1, 1.5.0, 2.0.0-beta-1
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


{code:title=RatioBasedCompactionPolicy.java|borderStyle=solid}
  public boolean shouldPerformMajorCompaction(Collection 
filesToCompact)
throws IOException {
boolean result = false;
long mcTime = getNextMajorCompactTime(filesToCompact);
if (filesToCompact == null || filesToCompact.isEmpty() || mcTime == 0) {
  return result;
}
// TODO: Use better method for determining stamp of last major (HBASE-2990)
long lowTimestamp = StoreUtils.getLowestTimestamp(filesToCompact);
long now = EnvironmentEdgeManager.currentTime();
if (lowTimestamp > 0L && lowTimestamp < (now - mcTime)) {
  String regionInfo;
  if (this.storeConfigInfo != null && this.storeConfigInfo instanceof 
HStore) {
regionInfo = 
((HStore)this.storeConfigInfo).getRegionInfo().getRegionNameAsString();
  } else {
regionInfo = this.toString();
  }
  // Major compaction time has elapsed.
  long cfTTL = HConstants.FOREVER;
  if (this.storeConfigInfo != null) {
 cfTTL = this.storeConfigInfo.getStoreFileTtl();
  }
  if (filesToCompact.size() == 1) {
// Single file
HStoreFile sf = filesToCompact.iterator().next();
OptionalLong minTimestamp = sf.getMinimumTimestamp();
long oldest = minTimestamp.isPresent() ? now - minTimestamp.getAsLong() 
: Long.MIN_VALUE;
if (sf.isMajorCompactionResult() && (cfTTL == Long.MAX_VALUE || oldest 
< cfTTL)) {
  float blockLocalityIndex =
sf.getHDFSBlockDistribution().getBlockLocalityIndex(
RSRpcServices.getHostname(comConf.conf, false));
  if (blockLocalityIndex < comConf.getMinLocalityToForceCompact()) {
LOG.debug("Major compaction triggered on only store " + regionInfo
  + "; to make hdfs blocks local, current blockLocalityIndex is "
  + blockLocalityIndex + " (min " + 
comConf.getMinLocalityToForceCompact() + ")");
result = true;
  } else {
LOG.debug("Skipping major compaction of " + regionInfo
  + " because one (major) compacted file only, oldestTime " + oldest
  + "ms is < TTL=" + cfTTL + " and blockLocalityIndex is " + 
blockLocalityIndex
  + " (min " + comConf.getMinLocalityToForceCompact() + ")");
  }
} else if (cfTTL != HConstants.FOREVER && oldest > cfTTL) {
  LOG.debug("Major compaction triggered on store " + regionInfo
+ ", because keyvalues outdated; time since last major compaction "
+ (now - lowTimestamp) + "ms");
  result = true;
}
  } else {
LOG.debug("Major compaction triggered on store " + regionInfo
  + "; time since last major compaction " + (now - lowTimestamp) + 
"ms");
  }
  result = true;
}
return result;
  }
{code}

{code}  
   } else {
LOG.debug("Major compaction triggered on store " + regionInfo
  + "; time since last major compaction " + (now - lowTimestamp) + 
"ms");
  }
  result = true;
{code}
if (lowTimestamp > 0L && lowTimestamp < (now - mcTime)), the result always 
equal true.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19088) move_tables_rsgroup will throw an exception when the table is disabled

2017-10-25 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19088:
-

 Summary: move_tables_rsgroup will throw an exception when the 
table is disabled
 Key: HBASE-19088
 URL: https://issues.apache.org/jira/browse/HBASE-19088
 Project: HBase
  Issue Type: Bug
  Components: rsgroup
Affects Versions: 3.0.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng



When the table is disabled, *move_tables_rsgroup* will throw an exception, but 
the table has been moved to the new group successfully.

{code:java}
hbase(main):009:0> move_tables_rsgroup 'default',['t1']
ERROR: java.io.IOException
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:465)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:134)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:325)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:305)
Caused by: java.lang.NullPointerException
at 
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProcedureProtos$MoveRegionStateData$Builder.setSourceServer(MasterProcedureProtos.java:26022)
at 
org.apache.hadoop.hbase.master.assignment.MoveRegionProcedure.serializeStateData(MoveRegionProcedure.java:133)
at 
org.apache.hadoop.hbase.procedure2.ProcedureUtil.convertToProtoProcedure(ProcedureUtil.java:198)
at 
org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.writeEntry(ProcedureWALFormat.java:211)
at 
org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.writeInsert(ProcedureWALFormat.java:222)
at 
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.insert(WALProcedureStore.java:470)
at 
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.submitProcedure(ProcedureExecutor.java:866)
at 
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.submitProcedure(ProcedureExecutor.java:835)
at 
org.apache.hadoop.hbase.master.procedure.ProcedureSyncWait.submitAndWaitProcedure(ProcedureSyncWait.java:120)
at 
org.apache.hadoop.hbase.master.assignment.AssignmentManager.move(AssignmentManager.java:557)
at 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminServer.moveTables(RSGroupAdminServer.java:413)
at 
org.apache.hadoop.hbase.rsgroup.RSGroupAdminEndpoint$RSGroupAdminServiceImpl.moveTables(RSGroupAdminEndpoint.java:190)
at 
org.apache.hadoop.hbase.protobuf.generated.RSGroupAdminProtos$RSGroupAdminService.callMethod(RSGroupAdminProtos.java:12786)
at 
org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:786)
at 
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
... 3 more

Reassign tables from one RegionServer group to another.

Example:

  hbase> move_tables_rsgroup 'dest',['table1','table2']


Took 0.0297 seconds
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19087) Remove redundant characters from the audit log

2017-10-25 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-19087:
-

 Summary: Remove redundant characters from the audit log
 Key: HBASE-19087
 URL: https://issues.apache.org/jira/browse/HBASE-19087
 Project: HBase
  Issue Type: Bug
Affects Versions: 3.0.0, 2.0.0-alpha-4
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


After HBASE-18878, the audit log contains redundant characters "Optional" which 
leading to unreadable
{code:java}
2017-10-19 19:51:08,054 INFO  
[RpcServer.default.FPBQ.Fifo.handler=49,queue=4,port=8081] master.HMaster: 
Client=Optional[username]/Optional[/locahost] disable tablename 
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18910) Backport HBASE-17292 "Add observer notification before bulk loaded hfile is moved to region directory" to 1.3

2017-09-29 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-18910:
-

 Summary: Backport HBASE-17292 "Add observer notification before 
bulk loaded hfile is moved to region directory" to 1.3
 Key: HBASE-18910
 URL: https://issues.apache.org/jira/browse/HBASE-18910
 Project: HBase
  Issue Type: Bug
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng
 Fix For: 1.3.2


HBASE-18900 will backport HBASE-17290 to branch-1.3.But  HBASE-17290 is 
dependent on HBASE-17292.so this issue will backport HBASE-17292 to branch-1.3.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18899) Make Fileinfo more readable in HFilePrettyPrinter

2017-09-28 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-18899:
-

 Summary: Make Fileinfo more readable in HFilePrettyPrinter
 Key: HBASE-18899
 URL: https://issues.apache.org/jira/browse/HBASE-18899
 Project: HBase
  Issue Type: Bug
Reporter: Guangxu Cheng


Fileinfo as follows. some fields can print  readable values.
{code}
Fileinfo:
BLOOM_FILTER_TYPE = ROW
DELETE_FAMILY_COUNT = \x00\x00\x00\x00\x00\x00\x00\x00
EARLIEST_PUT_TS = \x00\x00\x01^Q\xF6\x0E\xCF
KEY_VALUE_VERSION = \x00\x00\x00\x01
LAST_BLOOM_KEY = f
MAJOR_COMPACTION_KEY = \xFF
MAX_MEMSTORE_TS_KEY = \x00\x00\x00\x00\x00\x00\x00\x18
MAX_SEQ_ID_KEY = 27
TIMERANGE = 15046136337431506570582061
hfile.AVG_KEY_LEN = 14
hfile.AVG_VALUE_LEN = 3
hfile.CREATE_TIME_TS = \x00\x00\x01^\xC6\xB4J\xF9
hfile.LASTKEY = \x00\x01f\x01i\x00\x00\x01^\xC6\x9A\xB8-\x04
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18880) Failed to start rest server if the value of hbase.rest.threads.max is too small.

2017-09-26 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-18880:
-

 Summary: Failed to start rest server if the value of 
hbase.rest.threads.max is too small.
 Key: HBASE-18880
 URL: https://issues.apache.org/jira/browse/HBASE-18880
 Project: HBase
  Issue Type: Bug
  Components: REST
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng
 Fix For: 3.0.0, 2.0.0-alpha-4


After HBASE-18224, Jetty has be updated to 9.4.6, and it requires more threads 
to start up.

If the value of hbase.rest.threads.max is too small, the rest server will fail 
to start.

What I observed was as follows:
1. The process did not exit. (At the beginning, I thought the rest server has 
been start normally because of the process exists.)
2. Can't connect to the rest server and I didn't found any exception log in 
***.log.
3. the main thread has exited (jstack log).
4. Found the exception information from ***.out.
{code}
java.lang.IllegalStateException: Insufficient threads: max=5 < 
needed(acceptors=1 + selectors=8 + request=1)
at org.eclipse.jetty.server.Server.doStart(Server.java:414)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.apache.hadoop.hbase.rest.RESTServer.main(RESTServer.java:360)
{code}

I think the process should exit and log the information in ***.log when it 
happens.
So that the user can directly discover that the rest server is abnormal.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18875) Thrift server support read-only mode

2017-09-25 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-18875:
-

 Summary: Thrift server support read-only mode
 Key: HBASE-18875
 URL: https://issues.apache.org/jira/browse/HBASE-18875
 Project: HBase
  Issue Type: New Feature
  Components: Thrift
Affects Versions: 2.0.0, 3.0.0, 1.5.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


Provide option for thrift server to support read-only mode.

To start the thrift server, use the -ro option or set hbase.thrift.readonly to 
true.

false: Both read and write request are permitted.(all methods)
true : Only the read request is permitted.  (only get/scan method)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18804) Sanity check the number of regions when creating a table

2017-09-13 Thread Guangxu Cheng (JIRA)
Guangxu Cheng created HBASE-18804:
-

 Summary: Sanity check the number of regions when creating a table
 Key: HBASE-18804
 URL: https://issues.apache.org/jira/browse/HBASE-18804
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 2.0.0, 1.5.0
Reporter: Guangxu Cheng
Assignee: Guangxu Cheng


A few days ago, a table was erroneously created with NUMREGIONS set to 200k 
which resulted in the master down. 
I got exceptions like:
{code:java}
2017-08-17 11:10:17,970 WARN  [main-SendThread(localhost:2181)] 
zookeeper.ClientCnxn: Session 0x45c9d4132c547f1 for server 
localhost/localhost:2181, unexpected error, closing socket connection and 
attempting reconnect
java.io.IOException: Packet len6842180 is out of range!
at 
org.apache.zookeeper.ClientCnxnSocket.readLength(ClientCnxnSocket.java:112)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:79)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:366)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
{code}
That's because a lot of regions need to assign in a short interval, and the 
size of the node /hbase/region-in-transition exceeds the default value.
We solved this problem by setting "jute.maxbuffer".

But we can sanity check the number of regions when creating a table and reject 
the requests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


  1   2   >