[jira] [Reopened] (HBASE-21242) [amv2] Miscellaneous minor log and assign procedure create improvements

2018-10-11 Thread stack (JIRA)


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

stack reopened HBASE-21242:
---

Reopen. Only branch-2.0 and branch-2.1 done so far.

> [amv2] Miscellaneous minor log and assign procedure create improvements
> ---
>
> Key: HBASE-21242
> URL: https://issues.apache.org/jira/browse/HBASE-21242
> Project: HBase
>  Issue Type: Bug
>  Components: amv2, Operability
>Reporter: stack
>Assignee: stack
>Priority: Minor
> Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21242.branch-2.0.001.patch, 
> HBASE-21242.branch-2.0.001.patch, HBASE-21242.branch-2.0.002.patch, 
> HBASE-21242.branch-2.001.patch, HBASE-21242.branch-2.1.001.patch, 
> HBASE-21242.branch-2.1.001.patch, HBASE-21242.branch-2.1.001.patch, 
> HBASE-21242.branch-2.1.002.patch
>
>
> Some minor fixups:
> {code}
> For RIT Duration, do better than print ms/seconds. Remove redundant UI
> column dedicated to duration when we log it in the status field too.
> Make bypass log at INFO level -- when DEBUG we can miss important
> fixup detail like why we failed.
> Make it so on complete of subprocedure, we note count of outstanding
> siblings so we have a clue how much further the parent has to go before
> it is done (Helpful when hundreds of servers doing SCP).
> Have the SCP run the AP preflight check before creating an AP; saves
> creation of hundreds of thousands of APs during fixup of this big cluster
> of mine.
> Don't log tablename three times when reporting remote call failed.
> If lock is held already, note who has it. Also log after we get lock
> or if we have to wait rather than log on entrance though we may
> later have to wait (or we may have just picked up the lock).
> {code}
> Posting patch in a sec but let me try it on cluster too.



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


[jira] [Created] (HBASE-21299) List counts of actual region states in master UI tables section

2018-10-11 Thread stack (JIRA)
stack created HBASE-21299:
-

 Summary: List counts of actual region states in master UI tables 
section
 Key: HBASE-21299
 URL: https://issues.apache.org/jira/browse/HBASE-21299
 Project: HBase
  Issue Type: Improvement
  Components: UI
Reporter: stack
 Attachments: Screen Shot 2018-10-11 at 9.44.39 PM.png, Screen Shot 
2018-10-11 at 9.44.56 PM.png

It the tables panel, we list Open Regions, Offline Regions, Failed Regions, 
Split Region, and Other. This is not very useful. It is from a time before 
region states were edited down. Better to list OPEN, CLOSED, OPENING, 
CLOSING... 



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


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


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

2018-10-11 Thread Srinivas Reddy
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 Srinivas Reddy
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!
>


Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Allan Yang
Congratulations!, Balazs.
Best Regards
Allan Yang


Reid Chan  于2018年10月12日周五 上午10:26写道:

> Congratulations and welcome, Balazs.
>
> --
>
> Best regards,
> R.C
>
>
>
> 
> From: Umesh Agashe 
> Sent: 12 October 2018 06:43
> To: dev@hbase.apache.org
> Cc: Hbase-User; meszib...@apache.org
> Subject: Re: [ANNOUNCE] New Committer: Balazs Meszaros
>
> Congrats Balazs!
>
> On Thu, Oct 11, 2018 at 3:34 PM Andrew Purtell 
> wrote:
>
> > Congratulations and welcome Balazs.
> >
> > On Thu, Oct 11, 2018 at 12:49 PM 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!
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>


Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Reid Chan
Congratulations and welcome, Balazs.

--

Best regards,
R.C




From: Umesh Agashe 
Sent: 12 October 2018 06:43
To: dev@hbase.apache.org
Cc: Hbase-User; meszib...@apache.org
Subject: Re: [ANNOUNCE] New Committer: Balazs Meszaros

Congrats Balazs!

On Thu, Oct 11, 2018 at 3:34 PM Andrew Purtell  wrote:

> Congratulations and welcome Balazs.
>
> On Thu, Oct 11, 2018 at 12:49 PM 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!
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


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

2018-10-11 Thread Reid Chan
Congratulations, Zach!

--

Best regards,
R.C




From: Andrew Purtell 
Sent: 12 October 2018 06:34
To: dev
Subject: Re: [ANNOUNCE] Please welcome Zach York to the HBase PMC

Welcome, Zach.

On Thu, Oct 11, 2018 at 1:01 PM 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.
>


--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk


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

2018-10-11 Thread Allan Yang
Congratulations, Zach !
Best Regards
Allan Yang


Andrew Purtell  于2018年10月12日周五 上午6:34写道:

> Welcome, Zach.
>
> On Thu, Oct 11, 2018 at 1:01 PM 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.
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Umesh Agashe
Congrats Balazs!

On Thu, Oct 11, 2018 at 3:34 PM Andrew Purtell  wrote:

> Congratulations and welcome Balazs.
>
> On Thu, Oct 11, 2018 at 12:49 PM 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!
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Andrew Purtell
Congratulations and welcome Balazs.

On Thu, Oct 11, 2018 at 12:49 PM 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!
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk


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

2018-10-11 Thread Andrew Purtell
Welcome, Zach.

On Thu, Oct 11, 2018 at 1:01 PM 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.
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk


[jira] [Created] (HBASE-21298) Improved scheduling ("Muzzled HBase")

2018-10-11 Thread stack (JIRA)
stack created HBASE-21298:
-

 Summary: Improved scheduling ("Muzzled HBase")
 Key: HBASE-21298
 URL: https://issues.apache.org/jira/browse/HBASE-21298
 Project: HBase
  Issue Type: Improvement
Reporter: stack


Interesting paper on Thread scheduling with hbase for illustration. After study 
using interesting Thread analysis tooling, authors were able to improve HBase 
throughputs ("Muzzled-HBase").

https://www.usenix.org/system/files/osdi18-yang.pdf

(Via [~ebort...@oath.com])



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


[jira] [Created] (HBASE-21297) ModifyTableProcedure can throw TNDE instead of IOE in case of REGION_REPLICATION change

2018-10-11 Thread Nihal Jain (JIRA)
Nihal Jain created HBASE-21297:
--

 Summary: ModifyTableProcedure can throw TNDE instead of IOE in 
case of REGION_REPLICATION change
 Key: HBASE-21297
 URL: https://issues.apache.org/jira/browse/HBASE-21297
 Project: HBase
  Issue Type: Improvement
Reporter: Nihal Jain
Assignee: Nihal Jain


Currently {{ModifyTableProcedure}} throws an {{IOException}} (See 
[ModifyTableProcedure.java#L252|https://github.com/apache/hbase/blob/924d183ba0e67b975e998f6006c993f457e03c20/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ModifyTableProcedure.java#L252])
 when a user tries to modify REGION_REPLICATION for an enabled table. Instead, 
it can throw a more specific {{TableNotDisabledException}}.



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


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

2018-10-11 Thread Mike Drob
Welcome, Zach!

On Thu, Oct 11, 2018 at 3:21 PM Tak-Lon (Stephen) Wu 
wrote:

> Congratulations Zach !
>
> -Stephen
>
> On Thu, Oct 11, 2018 at 1:10 PM Nihal Jain  wrote:
>
> > Congrats Zach :)
> >
> > On Fri 12 Oct, 2018, 1:38 AM Esteban Gutierrez,
> >  wrote:
> >
> > > Congrats, Zach!
> > >
> > > --
> > > Cloudera, Inc.
> > >
> > >
> > >
> > > On Thu, Oct 11, 2018 at 3:06 PM Ted Yu  wrote:
> > >
> > > > Congratulations, Zach !
> > > >
> > > > On Thu, Oct 11, 2018 at 1:01 PM 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.
> > > > >
> > > >
> > >
> >
>
>
> --
> Stephen Wu | Indiana University, Bloomington
>


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

2018-10-11 Thread Tak-Lon (Stephen) Wu
Congratulations Zach !

-Stephen

On Thu, Oct 11, 2018 at 1:10 PM Nihal Jain  wrote:

> Congrats Zach :)
>
> On Fri 12 Oct, 2018, 1:38 AM Esteban Gutierrez,
>  wrote:
>
> > Congrats, Zach!
> >
> > --
> > Cloudera, Inc.
> >
> >
> >
> > On Thu, Oct 11, 2018 at 3:06 PM Ted Yu  wrote:
> >
> > > Congratulations, Zach !
> > >
> > > On Thu, Oct 11, 2018 at 1:01 PM 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.
> > > >
> > >
> >
>


-- 
Stephen Wu | Indiana University, Bloomington


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

2018-10-11 Thread Nihal Jain
Congrats Zach :)

On Fri 12 Oct, 2018, 1:38 AM Esteban Gutierrez,
 wrote:

> Congrats, Zach!
>
> --
> Cloudera, Inc.
>
>
>
> On Thu, Oct 11, 2018 at 3:06 PM Ted Yu  wrote:
>
> > Congratulations, Zach !
> >
> > On Thu, Oct 11, 2018 at 1:01 PM 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] Please welcome Zach York to the HBase PMC

2018-10-11 Thread Esteban Gutierrez
Congrats, Zach!

--
Cloudera, Inc.



On Thu, Oct 11, 2018 at 3:06 PM Ted Yu  wrote:

> Congratulations, Zach !
>
> On Thu, Oct 11, 2018 at 1:01 PM 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 Esteban Gutierrez
Congratulations and welcome, Balazs!

esteban.

--
Cloudera, Inc.



On Thu, Oct 11, 2018 at 2:57 PM Nihal Jain  wrote:

> Congrats Balazs :)
>
> On Fri 12 Oct, 2018, 1:20 AM Mike Drob,  wrote:
>
> > Welcome, Balazs!
> >
> > On Thu, Oct 11, 2018 at 2:49 PM 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!
> > >
> >
>


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

2018-10-11 Thread Ted Yu
Congratulations, Zach !

On Thu, Oct 11, 2018 at 1:01 PM 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.
>


[ANNOUNCE] Please welcome Zach York to the HBase PMC

2018-10-11 Thread Sean Busbey
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 Nihal Jain
Congrats Balazs :)

On Fri 12 Oct, 2018, 1:20 AM Mike Drob,  wrote:

> Welcome, Balazs!
>
> On Thu, Oct 11, 2018 at 2:49 PM 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!
> >
>


Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Mike Drob
Welcome, Balazs!

On Thu, Oct 11, 2018 at 2:49 PM 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!
>


[ANNOUNCE] New Committer: Balazs Meszaros

2018-10-11 Thread Sean Busbey
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-21296) [2.1] Upgrade Jetty dependencies to latest in major-line

2018-10-11 Thread Josh Elser (JIRA)
Josh Elser created HBASE-21296:
--

 Summary: [2.1] Upgrade Jetty dependencies to latest in major-line
 Key: HBASE-21296
 URL: https://issues.apache.org/jira/browse/HBASE-21296
 Project: HBase
  Issue Type: Task
  Components: dependencies
Reporter: Josh Elser
Assignee: Josh Elser
 Fix For: 3.0.0, 2.2.0, 2.1.2
 Attachments: HBASE-21282.001.branch-2.0.patch

Looks like we have dependencies on both jetty 9.2 and 9.3, but we're lagging 
pretty far behind in both. We can upgrade both of these to the latest (august 
2018).

 

I'll also have to take a look at why we're using two separate versions (maybe 
we didn't want to switch from jetty-jsp to apache-jsp on 9.2->9.3?). Not sure 
if there's a good reason for this.



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


[jira] [Resolved] (HBASE-21293) [2.0] Update bouncycastle dependency.

2018-10-11 Thread Josh Elser (JIRA)


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

Josh Elser resolved HBASE-21293.

  Resolution: Fixed
Hadoop Flags: Reviewed

> [2.0] Update bouncycastle dependency.
> -
>
> Key: HBASE-21293
> URL: https://issues.apache.org/jira/browse/HBASE-21293
> Project: HBase
>  Issue Type: Task
>  Components: dependencies, test
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Major
> Fix For: 2.0.3
>
> Attachments: HBASE-21281.001.branch-2.0.patch
>
>
> Looks like we still depend on bcprov-jdk16 for some x509 certificate 
> generation in our tests. Bouncycastle has moved beyond this in 1.47, changing 
> the artifact names.
> [http://www.bouncycastle.org/wiki/display/JA1/Porting+from+earlier+BC+releases+to+1.47+and+later]
> There are some API changes too, but it looks like we don't use any of these.
> It seems like we also have vestiges in the POMs from when we were depending 
> on a specific BC version that came in from Hadoop. We now have a 
> KeyStoreTestUtil class in HBase, which makes me think we can also clean up 
> some dependencies.



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


[jira] [Created] (HBASE-21295) Update compatibility matrices

2018-10-11 Thread Peter Somogyi (JIRA)
Peter Somogyi created HBASE-21295:
-

 Summary: Update compatibility matrices
 Key: HBASE-21295
 URL: https://issues.apache.org/jira/browse/HBASE-21295
 Project: HBase
  Issue Type: Improvement
  Components: documentation
Affects Versions: 3.0.0
Reporter: Peter Somogyi
Assignee: Peter Somogyi


JDK and Hadoop compatibility matrices does not cover all of the current 
releases and available JDKs. These should be added to both tables.

[https://hbase.apache.org/book.html#hadoop]



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


[jira] [Created] (HBASE-21294) [2.1] Update bouncycastle dependency.

2018-10-11 Thread Josh Elser (JIRA)
Josh Elser created HBASE-21294:
--

 Summary: [2.1] Update bouncycastle dependency.
 Key: HBASE-21294
 URL: https://issues.apache.org/jira/browse/HBASE-21294
 Project: HBase
  Issue Type: Task
  Components: dependencies, test
Reporter: Josh Elser
Assignee: Josh Elser
 Fix For: 3.0.0, 2.2.0, 2.0.3, 2.1.2
 Attachments: HBASE-21281.001.branch-2.0.patch

Looks like we still depend on bcprov-jdk16 for some x509 certificate generation 
in our tests. Bouncycastle has moved beyond this in 1.47, changing the artifact 
names.

[http://www.bouncycastle.org/wiki/display/JA1/Porting+from+earlier+BC+releases+to+1.47+and+later]

There are some API changes too, but it looks like we don't use any of these.

It seems like we also have vestiges in the POMs from when we were depending on 
a specific BC version that came in from Hadoop. We now have a KeyStoreTestUtil 
class in HBase, which makes me think we can also clean up some dependencies.



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


[jira] [Created] (HBASE-21293) [2.0] Update bouncycastle dependency.

2018-10-11 Thread Josh Elser (JIRA)
Josh Elser created HBASE-21293:
--

 Summary: [2.0] Update bouncycastle dependency.
 Key: HBASE-21293
 URL: https://issues.apache.org/jira/browse/HBASE-21293
 Project: HBase
  Issue Type: Task
  Components: dependencies, test
Reporter: Josh Elser
Assignee: Josh Elser
 Fix For: 3.0.0, 2.2.0, 2.0.3, 2.1.2
 Attachments: HBASE-21281.001.branch-2.0.patch

Looks like we still depend on bcprov-jdk16 for some x509 certificate generation 
in our tests. Bouncycastle has moved beyond this in 1.47, changing the artifact 
names.

[http://www.bouncycastle.org/wiki/display/JA1/Porting+from+earlier+BC+releases+to+1.47+and+later]

There are some API changes too, but it looks like we don't use any of these.

It seems like we also have vestiges in the POMs from when we were depending on 
a specific BC version that came in from Hadoop. We now have a KeyStoreTestUtil 
class in HBase, which makes me think we can also clean up some dependencies.



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


[jira] [Reopened] (HBASE-21247) Allow WAL Provider to be specified by configuration without explicit enum in Providers

2018-10-11 Thread Sean Busbey (JIRA)


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

Sean Busbey reopened HBASE-21247:
-

please revert this.

You can already provide a class name for something that implements WALProvider 
for the config "hbase.wal.provider". It's in the code and also documented in 
the javadoc for WALFactory.

{code}

 * Configure which provider gets used with the configuration setting 
"hbase.wal.provider". Available
 * implementations:
 * 
 *   defaultProvider : whatever provider is standard for the hbase 
version. Currently
 *  "asyncfs"
 *   asyncfs : a provider that will run on top of an 
implementation of the Hadoop
 * FileSystem interface via an asynchronous 
client.
 *   filesystem : a provider that will run on top of an 
implementation of the Hadoop
 * FileSystem interface via HDFS's synchronous 
DFSClient.
 *   multiwal : a provider that will use multiple "filesystem" wal 
instances per region
 *   server.
 * 
 *
 * Alternatively, you may provide a custom implementation of {@link 
WALProvider} by class name.
{code}

> Allow WAL Provider to be specified by configuration without explicit enum in 
> Providers
> --
>
> Key: HBASE-21247
> URL: https://issues.apache.org/jira/browse/HBASE-21247
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 21247.v1.txt, 21247.v2.txt, 21247.v3.txt, 21247.v4.txt
>
>
> Currently all the WAL Providers acceptable to hbase are specified in 
> Providers enum of WALFactory.
> This restricts the ability for additional WAL Providers to be supplied - by 
> class name.
> This issue introduces additional config which allows the specification of new 
> WAL Provider through class name.



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


[jira] [Created] (HBASE-21292) IdLock.getLockEntry() may hang if interrupted

2018-10-11 Thread Allan Yang (JIRA)
Allan Yang created HBASE-21292:
--

 Summary: IdLock.getLockEntry() may hang if interrupted
 Key: HBASE-21292
 URL: https://issues.apache.org/jira/browse/HBASE-21292
 Project: HBase
  Issue Type: Bug
Reporter: Allan Yang
Assignee: Allan Yang
 Fix For: 1.4.9, 2.0.2, 2.1.0


This is a rare case found by my colleague which really happened on our 
production env. 
Thread may hang(or enter a infinite loop ) when try to call 
IdLock.getLockEntry(). Here is the case:
1. Thread1 owned the IdLock, while Thread2(the only one waiting) was waiting 
for it.
2. Thread1 called releaseLockEntry, it will set IdLock.locked = false, but 
since Thread2 was waiting, it won't call map.remove(entry.id)
3. While Thread1 was calling releaseLockEntry, Thread2 was interrupted. So no 
one will remove this IdLock from the map.
4. If another thread try to call getLockEntry on this IdLock, it will end up in 
a infinite loop. Since existing = map.putIfAbsent(entry.id, entry)) != null and 
existing.locked=false

It is hard to write a UT since it is a very rare race condition.




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


[jira] [Created] (HBASE-21291) Bypass doesn't work for state-machine procedures

2018-10-11 Thread Jingyun Tian (JIRA)
Jingyun Tian created HBASE-21291:


 Summary: Bypass doesn't work for state-machine procedures
 Key: HBASE-21291
 URL: https://issues.apache.org/jira/browse/HBASE-21291
 Project: HBase
  Issue Type: Improvement
Affects Versions: 2.2.0
Reporter: Jingyun Tian


{code}
  if (!procedure.isFailed()) {
if (subprocs != null) {
  if (subprocs.length == 1 && subprocs[0] == procedure) {
// Procedure returned itself. Quick-shortcut for a state 
machine-like procedure;
// i.e. we go around this loop again rather than go back out on the 
scheduler queue.
subprocs = null;
reExecute = true;
LOG.trace("Short-circuit to next step on pid={}", 
procedure.getProcId());
  } else {
// Yield the current procedure, and make the subprocedure runnable
// subprocs may come back 'null'.
subprocs = initializeChildren(procStack, procedure, subprocs);
LOG.info("Initialized subprocedures=" +
  (subprocs == null? null:
Stream.of(subprocs).map(e -> "{" + e.toString() + "}").
collect(Collectors.toList()).toString()));
  }
} else if (procedure.getState() == ProcedureState.WAITING_TIMEOUT) {
  LOG.debug("Added to timeoutExecutor {}", procedure);
  timeoutExecutor.add(procedure);
} else if (!suspended) {
  // No subtask, so we are done
  procedure.setState(ProcedureState.SUCCESS);
}
  }
{code}
Currently implementation of ProcedureExecutor will set the reExcecute to true 
for state machine like procedure. Then if this procedure is stuck at one 
certain state, it will loop forever.
{code}
  IdLock.Entry lockEntry = 
procExecutionLock.getLockEntry(proc.getProcId());
  try {
executeProcedure(proc);
  } catch (AssertionError e) {
LOG.info("ASSERT pid=" + proc.getProcId(), e);
throw e;
  } finally {
procExecutionLock.releaseLockEntry(lockEntry);
{code}
Since procedure will get the IdLock and release it after execution done, state 
machine procedure will never release IdLock until it is finished.
Then bypassProcedure doesn't work because is will try to grab the IdLock at 
first.
{code}
IdLock.Entry lockEntry = 
procExecutionLock.tryLockEntry(procedure.getProcId(), lockWait);
{code}



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


[jira] [Created] (HBASE-21290) No need to instantiate BlockCache for master which not carry table

2018-10-11 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21290:
--

 Summary: No need to instantiate BlockCache for master which not 
carry table
 Key: HBASE-21290
 URL: https://issues.apache.org/jira/browse/HBASE-21290
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang
Assignee: Guanghao Zhang


In our production clusters, we use different jvm config for master/regionserver 
but use same hbase-site.xml for master/regionserver. And master has a small 
heap/offheap config. So the regionserver's hbase.bucketcache.size is not 
suitable for master. I thought we don't need to instantiate BlockCache for 
master which not carry table.




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


[jira] [Created] (HBASE-21289) Remove the log "'hbase.regionserver.maxlogs' was deprecated." in AbstractFSWAL

2018-10-11 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-21289:
--

 Summary: Remove the log "'hbase.regionserver.maxlogs' was 
deprecated." in AbstractFSWAL
 Key: HBASE-21289
 URL: https://issues.apache.org/jira/browse/HBASE-21289
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang


This log was added by HBASE-14951. And the description and release note never 
said this config was deprecated. I thought HBASE-14951 only changed the default 
value of maxlogs (Please correct me if I am wrong). And we still use this 
config in our hbase book. So the log "'hbase.regionserver.maxlogs' was 
deprecated." in AbstractFSWAL is confused. Let's remove it. FYI [~vrodionov]



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