Re: [VOTE] First hbase-2.0.0-alpha-2 Release Candidate is available

2017-08-19 Thread Ashish Singhi 
+1(non-binding)

Built tar from source code
Verified few commands on shell and other few from Java API, all looks ok
Verified audit logs
Verified HBase replication on a single node cluster, checked metrics
Checked zk_dump and web UI, looks ok

Regards,
Ashish

On Thu, Aug 17, 2017 at 2:13 AM, Stack  wrote:

> The first release candidate for HBase 2.0.0-alpha-2 is up at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-2RC0/
>
> Maven artifacts are available from a staging directory here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1173
>
> All was signed with my key at y 8ACC93D2
> 
>
> I tagged the RC as 2.0.0-alpha-2RC0
> (7149f999786b6fd5a3fc1f7aec1214afb738925e)
>
> hbase-2.0.0-alpha-2 includes all that was in alpha-1 (new assignment
> manager, offheap read/write path, in-memory compactions, etc.) plus a
> return to branch-1 deploy mode where master carries no regions (branch-2
> and master up to this had master carrying system tables), a purge of all
> checked-in generated content, updates to all dependencies including a move
> to rely on new hbase-thirdparty lib for relocated versions of guava, netty,
> and protobuf, etc.
>
> This is a rough cut ('alpha'), not-for-production preview of what
> hbase-2.0.0 will look like meant for devs and downstreamers to test drive
> and flag us early if we messed up anything ahead of our rolling GAs.
>
> The list of features addressed in 2.0.0 so far can be found here [4]. There
> are about 2700+. The list of ~500 fixes in 2.0.0 exclusively can be found
> here [3].
>
> I've updated our overview doc. on the state of 2.0.0 [1] but JIRA 2.0.0
> label [2] has undergone extensive weeding and presents a fairly good
> picture on what is yet to do before we 2.0.0. Check it out.
>
> Please take it for a spin and vote on whether it ok to put out as our first
> alpha (bar is low for an 'alpha'). Let the VOTE be open for 72 hours
> (Saturday)
>
> Thanks,
> St.Ack
>
> 1.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#
> 2. https://issues.apache.org/jira/projects/HBASE/versions/12327188
> 3.
> https://issues.apache.org/jira/browse/HBASE-18611?jql=
> project%20%3D%20HBASE%20%20and%20(fixVersion%20%3D%202.
> 0.0%20%7C%7C%20fixVersion%20%3D%202.0.0.alpha1%20%7C%7C%
> 20fixVersion%20%3D%202.0.0-alpha-2)%20and%20fixVersion%
> 20not%20in%20(1.0.0%2C%201.0.1%2C%201.0.2%2C%201.0.3%2C%
> 201.0.4%2C%201.0.5%2C%201.0.6%2C%201.1.0%2C%201.1.1%2C%201.
> 1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%2C%201.1.6%2C%201.1.7%
> 2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%201.2.0%2C%201.2.1%2C%
> 201.2.2%2C%201.2.3%2C%201.2.4%2C%201.2.5%2C%201.2.6%2C%201.
> 3.0%2C%201.3.1%2C%201.4.0)%20and%20%20(status%20%3D%
> 20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> 4.
> https://issues.apache.org/jira/browse/HBASE-18599?jql=
> project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> 202.0.0%20%7C%7C%20fixVersion%20%3D%202.0.0-alpha-1%20%7C%
> 7C%20fixVersion%20%3D%202.0.0-alpha-2)%20and%20(status%20%3D%20Resolved)
>

Re: [VOTE] First hbase-2.0.0-alpha-2 Release Candidate is available

2017-08-19 Thread Guanghao Zhang 
+1(non-binding)

Verified md5sum: ok
Build from source: ok
Start HBase in standalone mode: ok
Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
Checked master/regionserver/table/region Web UI: ok
Stop HBase: ok

2017-08-19 11:31 GMT+08:00 ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com>:

> +1
> Untared the tar ball.
>
> Loaded some 100G data with PE .Did full table scan. Then ran randomReads
> with 500 threads with and without block cache.
> All seems to be fine.
>
> Regards
> Ram
>
> On Sat, Aug 19, 2017 at 2:33 AM, Stack  wrote:
>
> > On Fri, Aug 18, 2017 at 1:45 PM, Josh Elser  wrote:
> >
> > > +1 (binding)
> > >
> > > * Saw the same unit test failures as Andrew did (obviously)
> > > * Ran a brief randomWrite PE locally and didn't have any obvious issues
> > >
> > > I took a glance at the contents of the lib/ dir for the bin tarball,
> and
> > > noticed that we seem to be duplicating a few dependencies (e.g.
> > jetty-util,
> > > javax.servlet*, jersey*, aopalliance*). It probably wouldn't be a bad
> > idea
> > > to proactively look at these and compare to a 1.x release (for
> licensing
> > > purposes)
> > >
> > >
> > Thanks for testing. The REST one is a little involved but will be fixed
> by
> > alpha3 (with some sweet help from Samir).
> >
> > Good idea on review of lib-dir: HBASE-18630
> >
> > Thanks Josh,
> > St.Ack
> >
> >
> >
> > > On 8/16/17 4:43 PM, Stack wrote:
> > >
> > >> The first release candidate for HBase 2.0.0-alpha-2 is up at:
> > >>
> > >>https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> alpha-2RC0/
> > >>
> > >> Maven artifacts are available from a staging directory here:
> > >>
> > >>https://repository.apache.org/content/repositories/
> > orgapachehbase-1173
> > >>
> > >> All was signed with my key at y 8ACC93D2
> > >> 
> > >>
> > >>
> > >> I tagged the RC as 2.0.0-alpha-2RC0
> > >> (7149f999786b6fd5a3fc1f7aec1214afb738925e)
> > >>
> > >> hbase-2.0.0-alpha-2 includes all that was in alpha-1 (new assignment
> > >> manager, offheap read/write path, in-memory compactions, etc.) plus a
> > >> return to branch-1 deploy mode where master carries no regions
> (branch-2
> > >> and master up to this had master carrying system tables), a purge of
> all
> > >> checked-in generated content, updates to all dependencies including a
> > move
> > >> to rely on new hbase-thirdparty lib for relocated versions of guava,
> > >> netty,
> > >> and protobuf, etc.
> > >>
> > >> This is a rough cut ('alpha'), not-for-production preview of what
> > >> hbase-2.0.0 will look like meant for devs and downstreamers to test
> > drive
> > >> and flag us early if we messed up anything ahead of our rolling GAs.
> > >>
> > >> The list of features addressed in 2.0.0 so far can be found here [4].
> > >> There
> > >> are about 2700+. The list of ~500 fixes in 2.0.0 exclusively can be
> > found
> > >> here [3].
> > >>
> > >> I've updated our overview doc. on the state of 2.0.0 [1] but JIRA
> 2.0.0
> > >> label [2] has undergone extensive weeding and presents a fairly good
> > >> picture on what is yet to do before we 2.0.0. Check it out.
> > >>
> > >> Please take it for a spin and vote on whether it ok to put out as our
> > >> first
> > >> alpha (bar is low for an 'alpha'). Let the VOTE be open for 72 hours
> > >> (Saturday)
> > >>
> > >> Thanks,
> > >> St.Ack
> > >>
> > >> 1.
> > >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> > >> Eu_ktczrlKHK8N4SZzs/edit#
> > >> 2. https://issues.apache.org/jira/projects/HBASE/versions/12327188
> > >> 3.
> > >> https://issues.apache.org/jira/browse/HBASE-18611?jql=projec
> > >> t%20%3D%20HBASE%20%20and%20(fixVersion%20%3D%202.0.0%20%7C%
> > >> 7C%20fixVersion%20%3D%202.0.0.alpha1%20%7C%7C%20fixVersion%
> > >> 20%3D%202.0.0-alpha-2)%20and%20fixVersion%20not%20in%20(1.
> > >> 0.0%2C%201.0.1%2C%201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%
> > >> 2C%201.0.6%2C%201.1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%
> > >> 201.1.4%2C%201.1.5%2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.
> > >> 1.9%2C%201.1.10%2C%201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%
> > >> 2C%201.2.4%2C%201.2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%
> > >> 201.4.0)%20and%20%20(status%20%3D%20Open%20or%20status%20%
> > >> 3D%20%22Patch%20Available%22)
> > >> 4.
> > >> https://issues.apache.org/jira/browse/HBASE-18599?jql=projec
> > >> t%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0%20%7
> > >> C%7C%20fixVersion%20%3D%202.0.0-alpha-1%20%7C%7C%20fixVersio
> > >> n%20%3D%202.0.0-alpha-2)%20and%20(status%20%3D%20Resolved)
> > >>
> > >>
> >
>

[jira] [Created] (HBASE-18636) Cannot run REST server out of a built checkout; fails with NoSuchMethodError: javax.ws.rs.core.Application.getProperties

2017-08-19 Thread stack (JIRA) 
stack created HBASE-18636:
-

 Summary: Cannot run REST server out of a built checkout; fails 
with NoSuchMethodError: javax.ws.rs.core.Application.getProperties
 Key: HBASE-18636
 URL: https://issues.apache.org/jira/browse/HBASE-18636
 Project: HBase
  Issue Type: Sub-task
  Components: REST
Reporter: stack
Priority: Minor


I think this a symptom of our move to jersey2 but haven't done the work to 
verify. Besides, it is a minor inconvenience as we make the migration from 
jersey1 to jersey2 but here I make note  of it.

While the REST unit tests pass and if you run hbase and then the rest server 
out of a built tarball, this works too, what does not work is running a REST 
server in-situ out of a built checkout; i.e. checkout, mvn install, and then do 
start-hbase.sh followed by hbase-daemon.sh rest start. HBase starts but the 
rest server does not. In its .out you will find the below exception which 
occurs because we have jersey1 and jersey2 on our CLASSPATH and REST on startup 
is finding jersey1 first in which the cited method does not exist.

See the parent issue for struggles trying to take hbase pure jersey2. It 
involves lots of filtering out of transitive includes that are coming in from 
hadoop. It also means we undo our use of the Jackson1Feature trick since it 
depends on jersey1. While we get to a place where we can launch REST in-situ 
out of the build dir, we break the world of unit tests that want to run yarn et 
al.

Filing this for now. It is low-priority I think and hopefully the learnings 
from the parent issue help move us to jersey2 and then this issue will 
evaporate.

{code}
Exception in thread "main" java.lang.NoSuchMethodError: 
javax.ws.rs.core.Application.getProperties()Ljava/util/Map;
  at 
org.glassfish.jersey.server.ApplicationHandler.(ApplicationHandler.java:331)
  at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:392)
  at 
org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:177)
  at 
org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:369)
  at javax.servlet.GenericServlet.init(GenericServlet.java:244)
  at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640)
  at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419)
  at 
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:875)
  at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:348)
  at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:772)
  at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:261)
  at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
  at org.eclipse.jetty.server.Server.start(Server.java:405)
  at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
  at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
  at org.eclipse.jetty.server.Server.doStart(Server.java:372)
  at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.apache.hadoop.hbase.rest.RESTServer.main(RESTServer.java:356)
{code}



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

[jira] [Created] (HBASE-18635) Fix asciidoc warnings

2017-08-19 Thread Misty Stanley-Jones (JIRA) 
Misty Stanley-Jones created HBASE-18635:
---

 Summary: Fix asciidoc warnings
 Key: HBASE-18635
 URL: https://issues.apache.org/jira/browse/HBASE-18635
 Project: HBase
  Issue Type: Bug
Reporter: Misty Stanley-Jones


When building docs, I noticed:

{code}
Failed to parse formatted text: To supply filters to the Scanner object or 
configure the Scanner in any other way, you can create a text file and add your 
filter to the file. For example, to return only rows for which keys start with 
codephu123/codeph and use a batch size of 100, the filter file 
would look like this:

  Scanner batch="100" filter { "type": "PrefixFilter", 
"value": "u123" } /filter /Scanner 

{code}

Working hypthesis is that we should either be using proper codeblocks rather 
than pre tags. Otherwise we may need to do something to escape curly braces. 
Asciidoctor is probably trying to interpret them as Liquid tags.



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

[jira] [Created] (HBASE-18634) Fix client.TestClientClusterStatus

2017-08-19 Thread Chia-Ping Tsai (JIRA) 
Chia-Ping Tsai created HBASE-18634:
--

 Summary: Fix client.TestClientClusterStatus
 Key: HBASE-18634
 URL: https://issues.apache.org/jira/browse/HBASE-18634
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
 Fix For: 2.0.0


After HBASE-18511, the master doesn't carry any regions by default. Hence, The 
active master doesn't report its load because the report thread is sleeping in 
waitForMasterActive().
{code}
  protected void waitForMasterActive(){
boolean tablesOnMaster = LoadBalancer.isTablesOnMaster(conf);
while (!(tablesOnMaster && activeMaster) && !isStopped() && !isAborted()) {
  sleeper.sleep();
}
  }
{code}
In conclusion, the ClusterStatue#getServers won't contain the master name.



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

[jira] [Resolved] (HBASE-18506) java.lang.AbstractMethodError in hbase REST server

2017-08-19 Thread Samir Ahmic (JIRA) 

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

Samir Ahmic resolved HBASE-18506.
-
   Resolution: Fixed
Fix Version/s: 3.0.0

This is fixed for for master branch. For branch-2 there will be different 
solution under HBASE-18615

> java.lang.AbstractMethodError in hbase REST server
> --
>
> Key: HBASE-18506
> URL: https://issues.apache.org/jira/browse/HBASE-18506
> Project: HBase
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Samir Ahmic
>Assignee: Samir Ahmic
>Priority: Blocker
> Fix For: 3.0.0
>
>
> Just run it this one while testing some scripts. Basically any call to 
> service will end up with 500 error. After some checking it looks like we have 
> some issues with dependencies incompatibility. 
> Here is more details:
> {code}
> Stack trace:
> 2017-08-02 20:46:25,407 WARN  [qtp422330142-30] servlet.ServletHandler: Error 
> for /status/cluster
> java.lang.AbstractMethodError: 
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
>   at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:119)
>   at 
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:298)
>   at 
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
>   at 
> org.apache.hadoop.hbase.rest.filter.GzipFilter.doFilter(GzipFilter.java:77)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>   at org.eclipse.jetty.server.Server.handle(Server.java:518)
>   at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
>   at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
>   at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
>   at 
> org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
>   at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
>   at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
>   at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> and here are suspects from lib dir
> {code}
> $ grep -r "UriBuilder" .
> Binary file ./javax.ws.rs-api-2.0.1.jar matches
> Binary file ./jersey-common-2.25.1.jar matches
> Binary file ./jersey-core-1.9.jar matches
> {code}
> I have also checked hbase-1.2.6 we have only jersey-core-1.9.jar there



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