[RESULT] Re: [VOTE] First release candidate for HBase 1.2.10 is available

2019-01-16 Thread Sean Busbey 
with 3 binding +1s and 2 non-binding +1s this vote passes.

thanks everyone!

On Mon, Jan 7, 2019 at 6:51 PM Sean Busbey  wrote:
>
> The first release candidate for HBase 1.2.10 is available for download:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.10RC0/
>
> Maven artifacts are also available in a staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1249/
>
> 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.2.10RC0, which currently points
> to commit ref
>
> 18f428abb64b405de24d164425e470512e82f287
>
> HBase 1.2.10 is the tenth maintenance release in the HBase 1.2 line,
> continuing on the theme of bringing a stable, reliable database to
> the Hadoop and NoSQL communities. This release includes about a half
> dozen bug fixes done in the month since 1.2.9.
>
> The detailed source and binary compatibility report vs 1.2.9 has been
> published for your review, at:
>
> https://s.apache.org/hbase-1.2.10-rc0-compat-report
>
> The report shows some issues with two IA.LimitedPrivate classes annotated
> for use in TOOLS and CONFIG, as well as a false positive incompatibility for
> the WALCellCodec class.
>
> Critical fixes include:
>
> * HBASE-21387 - Race condition surrounding in progress snapshot handling in
> snapshot cache leads to loss of snapshot files
> * HBASE-21492 - CellCodec Written To WAL Before It's Verified
> * HBASE-21504 - If enable FIFOCompactionPolicy, a compaction may write a
> "empty" hfile whose maxTimeStamp is long max. This kind of
> hfile will never be archived.
> * HBASE-21582 - If call HBaseAdmin#snapshotAsync but forget call
> isSnapshotFinished, then SnapshotHFileCleaner will skip to
> run every time
>
> The full list of fixes included in this release is available at:
>
> https://s.apache.org/hbase-1.2.10-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 HBase 1.2.10.
>
> The VOTE will remain open for at least 72 hours. Given sufficient votes
> I would like to close it on January 11th, 2019.
>
> thanks!
>
> -busbey
>
> as of this email the posted artifacts have the following SHA512:
>
> hbase-1.2.10-src.tar.gz:
> D800AEEC 1F6B448D 33C15C5A EA5ECE2E 965C82F1 C68DA586
> BA6DB8A7 471573A7 09434016 2E5A14C0 87EF188A 365A4009
> 3F726587 21F85D4A 57DA50F1 E940EEE6
>
> hbase-1.2.10-bin.tar.gz:
> BA085D9E 0EBC67FC E37A4F47 02C98EB0 2EFEF8BE 81AE4388
> 16A0CC4A 6614788A 4CBF0ABE 47F02C85 ECF4C20E 89343417
> F2A80FD8 B80481D0 DD2B844B 580D143F
>

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

2019-01-16 Thread Sean Busbey 
+1 (binding)

On Mon, Jan 7, 2019 at 6:51 PM Sean Busbey  wrote:
>
> The first release candidate for HBase 1.2.10 is available for download:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.10RC0/
>
> Maven artifacts are also available in a staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1249/
>
> 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.2.10RC0, which currently points
> to commit ref
>
> 18f428abb64b405de24d164425e470512e82f287
>
> HBase 1.2.10 is the tenth maintenance release in the HBase 1.2 line,
> continuing on the theme of bringing a stable, reliable database to
> the Hadoop and NoSQL communities. This release includes about a half
> dozen bug fixes done in the month since 1.2.9.
>
> The detailed source and binary compatibility report vs 1.2.9 has been
> published for your review, at:
>
> https://s.apache.org/hbase-1.2.10-rc0-compat-report
>
> The report shows some issues with two IA.LimitedPrivate classes annotated
> for use in TOOLS and CONFIG, as well as a false positive incompatibility for
> the WALCellCodec class.
>
> Critical fixes include:
>
> * HBASE-21387 - Race condition surrounding in progress snapshot handling in
> snapshot cache leads to loss of snapshot files
> * HBASE-21492 - CellCodec Written To WAL Before It's Verified
> * HBASE-21504 - If enable FIFOCompactionPolicy, a compaction may write a
> "empty" hfile whose maxTimeStamp is long max. This kind of
> hfile will never be archived.
> * HBASE-21582 - If call HBaseAdmin#snapshotAsync but forget call
> isSnapshotFinished, then SnapshotHFileCleaner will skip to
> run every time
>
> The full list of fixes included in this release is available at:
>
> https://s.apache.org/hbase-1.2.10-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 HBase 1.2.10.
>
> The VOTE will remain open for at least 72 hours. Given sufficient votes
> I would like to close it on January 11th, 2019.
>
> thanks!
>
> -busbey
>
> as of this email the posted artifacts have the following SHA512:
>
> hbase-1.2.10-src.tar.gz:
> D800AEEC 1F6B448D 33C15C5A EA5ECE2E 965C82F1 C68DA586
> BA6DB8A7 471573A7 09434016 2E5A14C0 87EF188A 365A4009
> 3F726587 21F85D4A 57DA50F1 E940EEE6
>
> hbase-1.2.10-bin.tar.gz:
> BA085D9E 0EBC67FC E37A4F47 02C98EB0 2EFEF8BE 81AE4388
> 16A0CC4A 6614788A 4CBF0ABE 47F02C85 ECF4C20E 89343417
> F2A80FD8 B80481D0 DD2B844B 580D143F
>

[jira] [Reopened] (HBASE-21626) log the regions blocking WAL from being archived

2019-01-16 Thread Sergey Shelukhin (JIRA) 


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

Sergey Shelukhin reopened HBASE-21626:
--

There's an issue in this patch that causes the message to never be logged.

> log the regions blocking WAL from being archived
> 
>
> Key: HBASE-21626
> URL: https://issues.apache.org/jira/browse/HBASE-21626
> Project: HBase
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-21626.01.patch, HBASE-21626.02.patch, 
> HBASE-21626.patch
>
>
> The WALs not being archived for a long time can result in a long recovery 
> later. It's useful to know what regions are blocking the WALs from being 
> archived, to be able to debug flush logic and tune configuration.



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

Re: Seek for help to create an account on review.apache

2019-01-16 Thread Zach York 
It looks like it is now much easier to close PRs so I think it makes sense
to use a PR as a substitute for ReviewBoard in the short term. Note that it
would be the committer's responsibility to close the PR.

I think this is a good intermediate step before we figure out the process
to commit using PR.

On Wed, Jan 16, 2019 at 8:15 AM Sean Busbey  wrote:

> Unfortunately it looks like review board posting is now only available
> to ASF committers. We'll have to update our community docs to
> de-emphasize using it. :/
>
> Wang Huan it looks like you have a patch file attached to the JIRA for
> HBASE-21699. Until a reviewer asks for it in a different format that
> ought to be fine. If the change is big enough that review board is
> needed then we'll have to get a committer to upload it.
>
> Misty is correct that you could put up a GitHub PR, but keep in mind
> we (the project) haven't gotten much process expectations in place for
> those so how well it goes will depend on the specific reviewers
> looking at your contribution.
>
> On Tue, Jan 15, 2019 at 10:31 PM Misty Linville  wrote:
> >
> > I think you may need to contact infra directly. I'm sorry you're facing
> > this trouble and I appreciate the extra effort you're going through to
> > contribute. I wonder if you can try creating a pull request on GitHub
> > instead of using Reviewboard until you get a resolution. I confess I am
> not
> > as familiar with the Gitbox functionality as I should be. Can anyone else
> > help out here? I've added the PMC list just in case it helps speed things
> > along.
> >
> > On Tue, Jan 15, 2019, 6:59 PM wang huan  >
> > > Hi, Zhang: https://reviews.apache.org have enabled LDAP,  can not log
> in
> > > with account on jira.
> > >
> > > On 16/1/19, 10:17 AM, "张铎(Duo Zhang)"  wrote:
> > >
> > > I think it uses the same account with jira? i.e, issues.apache.org
> .
> > >
> > > wang huan  于2019年1月16日周三 上午10:13写道：
> > >
> > > > Hi, All:
> > > > I want to login https://reviews.apache.org to upload my
> patch
> > > > onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache
> > > projects
> > > > told me go to https://reviews.apache.org and create an account,
> but
> > > no
> > > > register page on there !
> > > >  My colleague told me he got his account from dev@mesos, so
> I
> > > want to
> > > > know if someone can
> > > > help me create an account
> > > >
> > > > Best Regards,
> > > > huan
> > > >
> > > >
> > >
> > >
>

Re: Seek for help to create an account on review.apache

2019-01-16 Thread huan wang 

Noted it, thank you for patient answer!
On Jan 17 2019, at 12:15 am, Sean Busbey  wrote:
> Unfortunately it looks like review board posting is now only available
> to ASF committers. We'll have to update our community docs to
> de-emphasize using it. :/
>
> Wang Huan it looks like you have a patch file attached to the JIRA for
> HBASE-21699. Until a reviewer asks for it in a different format that
> ought to be fine. If the change is big enough that review board is
> needed then we'll have to get a committer to upload it.
>
> Misty is correct that you could put up a GitHub PR, but keep in mind
> we (the project) haven't gotten much process expectations in place for
> those so how well it goes will depend on the specific reviewers
> looking at your contribution.
>
> On Tue, Jan 15, 2019 at 10:31 PM Misty Linville  wrote:
> >
> > I think you may need to contact infra directly. I'm sorry you're facing
> > this trouble and I appreciate the extra effort you're going through to
> > contribute. I wonder if you can try creating a pull request on GitHub
> > instead of using Reviewboard until you get a resolution. I confess I am not
> > as familiar with the Gitbox functionality as I should be. Can anyone else
> > help out here? I've added the PMC list just in case it helps speed things
> > along.
> >
> > On Tue, Jan 15, 2019, 6:59 PM wang huan  > > Hi, Zhang: https://reviews.apache.org have enabled LDAP, can not log in
> > > with account on jira.
> > >
> > > On 16/1/19, 10:17 AM, "张铎(Duo Zhang)"  wrote:
> > > I think it uses the same account with jira? i.e, issues.apache.org.
> > > wang huan  于2019年1月16日周三 上午10:13写道：
> > > > Hi, All:
> > > > I want to login https://reviews.apache.org to upload my patch
> > > > onhttps://jira.apache.org/jira/browse/HBASE-21699, all apache
> > >
> > > projects
> > > > told me go to https://reviews.apache.org and create an account, but
> > >
> > > no
> > > > register page on there !
> > > > My colleague told me he got his account from dev@mesos, so I
> > >
> > > want to
> > > > know if someone can
> > > > help me create an account
> > > >
> > > > Best Regards,
> > > > huan
> > >
> >
>
>

Re: Seek for help to create an account on review.apache

2019-01-16 Thread Sean Busbey 
Unfortunately it looks like review board posting is now only available
to ASF committers. We'll have to update our community docs to
de-emphasize using it. :/

Wang Huan it looks like you have a patch file attached to the JIRA for
HBASE-21699. Until a reviewer asks for it in a different format that
ought to be fine. If the change is big enough that review board is
needed then we'll have to get a committer to upload it.

Misty is correct that you could put up a GitHub PR, but keep in mind
we (the project) haven't gotten much process expectations in place for
those so how well it goes will depend on the specific reviewers
looking at your contribution.

On Tue, Jan 15, 2019 at 10:31 PM Misty Linville  wrote:
>
> I think you may need to contact infra directly. I'm sorry you're facing
> this trouble and I appreciate the extra effort you're going through to
> contribute. I wonder if you can try creating a pull request on GitHub
> instead of using Reviewboard until you get a resolution. I confess I am not
> as familiar with the Gitbox functionality as I should be. Can anyone else
> help out here? I've added the PMC list just in case it helps speed things
> along.
>
> On Tue, Jan 15, 2019, 6:59 PM wang huan 
> > Hi, Zhang: https://reviews.apache.org have enabled LDAP,  can not log in
> > with account on jira.
> >
> > On 16/1/19, 10:17 AM, "张铎(Duo Zhang)"  wrote:
> >
> > I think it uses the same account with jira? i.e, issues.apache.org.
> >
> > wang huan  于2019年1月16日周三 上午10:13写道：
> >
> > > Hi, All:
> > > I want to login https://reviews.apache.org to upload my patch
> > > onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache
> > projects
> > > told me go to https://reviews.apache.org and create an account, but
> > no
> > > register page on there !
> > >  My colleague told me he got his account from dev@mesos, so I
> > want to
> > > know if someone can
> > > help me create an account
> > >
> > > Best Regards,
> > > huan
> > >
> > >
> >
> >

[jira] [Reopened] (HBASE-21034) Add new throttle type: read/write capacity unit

2019-01-16 Thread Guanghao Zhang (JIRA) 


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

Guanghao Zhang reopened HBASE-21034:


Reopen for branch-2.0 and branch-2.1.

> Add new throttle type: read/write capacity unit
> ---
>
> Key: HBASE-21034
> URL: https://issues.apache.org/jira/browse/HBASE-21034
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Yi Mei
>Assignee: Yi Mei
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21034.branch-2.0.001.patch, 
> HBASE-21034.branch-2.1.001.patch, HBASE-21034.master.001.patch, 
> HBASE-21034.master.002.patch, HBASE-21034.master.003.patch, 
> HBASE-21034.master.004.patch, HBASE-21034.master.005.patch, 
> HBASE-21034.master.006.patch, HBASE-21034.master.006.patch, 
> HBASE-21034.master.007.patch, HBASE-21034.master.007.patch
>
>
> Add new throttle type: read/write capacity unit like DynamoDB.
> One read capacity unit represents that read up to 1K data per time unit. If 
> data size is more than 1K, then consume additional read capacity units.
> One write capacity unit represents that one write for an item up to 1 KB in 
> size per time unit. If data size is more than 1K, then consume additional 
> write capacity units.
> For example, 100 read capacity units per second means that, HBase user can 
> read 100 times for 1K data in every second, or 50 times for 2K data in every 
> second and so on.



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

Re: Requesting access to hbase slack channel

2019-01-16 Thread Peter Somogyi 
Invite sent.

On Wed, Jan 16, 2019 at 1:03 PM Nihal Jain  wrote:

> Hi
>
> Could you please invite me: nihaljain...@gmail.com  >?
>
> Regards,
> Nihal
>
> On Wed, 16 Jan, 2019, 2:54 PM Peter Somogyi 
> > Sent invitation to madhurpan...@gmail.com.
> >
> > On Wed, Jan 16, 2019 at 7:27 AM Madhur Pant 
> > wrote:
> >
> > > Hi Team,
> > >
> > > I was wondering if I could get access to the HBase user slack channel
> > >
> > > https://apache-hbase.slack.com
> > >
> > > It says here 
> that I
> > > should email you guys  :)
> > >
> > > Thanks,
> > > Madhur Pant
> > >
> >
>

Re: Requesting access to hbase slack channel

2019-01-16 Thread Nihal Jain 
Hi

Could you please invite me: nihaljain...@gmail.com ?

Regards,
Nihal

On Wed, 16 Jan, 2019, 2:54 PM Peter Somogyi  Sent invitation to madhurpan...@gmail.com.
>
> On Wed, Jan 16, 2019 at 7:27 AM Madhur Pant 
> wrote:
>
> > Hi Team,
> >
> > I was wondering if I could get access to the HBase user slack channel
> >
> > https://apache-hbase.slack.com
> >
> > It says here   that I
> > should email you guys  :)
> >
> > Thanks,
> > Madhur Pant
> >
>

[jira] [Resolved] (HBASE-20854) Wrong retries number in RpcRetryingCaller's log message

2019-01-16 Thread Peter Somogyi (JIRA) 


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

Peter Somogyi resolved HBASE-20854.
---
   Resolution: Fixed
Fix Version/s: 2.2.0

> Wrong retries number in RpcRetryingCaller's log message
> ---
>
> Key: HBASE-20854
> URL: https://issues.apache.org/jira/browse/HBASE-20854
> Project: HBase
>  Issue Type: Bug
>  Components: Client, logging
>Affects Versions: 2.0.0
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Minor
> Fix For: 3.0.0, 2.2.0, 2.0.2, 2.1.0
>
> Attachments: HBASE-20854.branch-2.0.patch
>
>
> Just a small bug fix. In the error log message of RpcRetryingCallerImpl. 
> Tries number is passed to both tries and retries. Causing a bit of confusing.
> {code:java}
> 2018-07-05 21:04:46,343 INFO [Thread-20] 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl: Call exception, 
> tries=6, retries=6, started=4174 ms ago, cancelled=false, 
> msg=org.apache.hadoop.hbase.exce
> ptions.RegionOpeningException: Region 
> IntegrationTestBigLinkedList,\x7F\xFF\xFF\xFF\xFF\xFF\xFF\xFE,1530795739116.0cfd339596648348ac13d979150eb2bf.
>  is opening on e010125049164.bja,60020,1530795698451
> {code}



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

[jira] [Reopened] (HBASE-20854) Wrong retries number in RpcRetryingCaller's log message

2019-01-16 Thread Peter Somogyi (JIRA) 


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

Peter Somogyi reopened HBASE-20854:
---

This change did not land on branch-2. Reopen for backporting.

> Wrong retries number in RpcRetryingCaller's log message
> ---
>
> Key: HBASE-20854
> URL: https://issues.apache.org/jira/browse/HBASE-20854
> Project: HBase
>  Issue Type: Bug
>  Components: Client, logging
>Affects Versions: 2.0.0
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Minor
> Fix For: 3.0.0, 2.1.0, 2.0.2
>
> Attachments: HBASE-20854.branch-2.0.patch
>
>
> Just a small bug fix. In the error log message of RpcRetryingCallerImpl. 
> Tries number is passed to both tries and retries. Causing a bit of confusing.
> {code:java}
> 2018-07-05 21:04:46,343 INFO [Thread-20] 
> org.apache.hadoop.hbase.client.RpcRetryingCallerImpl: Call exception, 
> tries=6, retries=6, started=4174 ms ago, cancelled=false, 
> msg=org.apache.hadoop.hbase.exce
> ptions.RegionOpeningException: Region 
> IntegrationTestBigLinkedList,\x7F\xFF\xFF\xFF\xFF\xFF\xFF\xFE,1530795739116.0cfd339596648348ac13d979150eb2bf.
>  is opening on e010125049164.bja,60020,1530795698451
> {code}



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

[jira] [Created] (HBASE-21732) Should call toUpperCase before using Enum.valueOf in some methods for ColumnFamilyDescriptor

2019-01-16 Thread Duo Zhang (JIRA) 
Duo Zhang created HBASE-21732:
-

 Summary: Should call toUpperCase before using Enum.valueOf in some 
methods for ColumnFamilyDescriptor
 Key: HBASE-21732
 URL: https://issues.apache.org/jira/browse/HBASE-21732
 Project: HBase
  Issue Type: Bug
  Components: Client
Reporter: Duo Zhang


When upgrading we faced a problem that the some regions can not be opened due 
to the region server can not recognize the lower case 'snappy' config. In code 
for branch-1, we have done this
{code}
  public Compression.Algorithm getCompression() {
String n = getValue(COMPRESSION);
if (n == null) {
  return Compression.Algorithm.NONE;
}
return Compression.Algorithm.valueOf(n.toUpperCase(Locale.ROOT));
  }
{code} 

But in the code of 2.0+, we just call valueOf.



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

Re: Requesting access to hbase slack channel

2019-01-16 Thread Peter Somogyi 
Sent invitation to madhurpan...@gmail.com.

On Wed, Jan 16, 2019 at 7:27 AM Madhur Pant  wrote:

> Hi Team,
>
> I was wondering if I could get access to the HBase user slack channel
>
> https://apache-hbase.slack.com
>
> It says here   that I
> should email you guys  :)
>
> Thanks,
> Madhur Pant
>