[jira] [Updated] (HBASE-18477) Umbrella JIRA for HBase Read Replica clusters
[ https://issues.apache.org/jira/browse/HBASE-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18477: Attachment: HBase Read-Replica Clusters Scope doc.pdf > Umbrella JIRA for HBase Read Replica clusters > - > > Key: HBASE-18477 > URL: https://issues.apache.org/jira/browse/HBASE-18477 > Project: HBase > Issue Type: New Feature >Reporter: Zach York >Assignee: Zach York > Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase > Read-Replica Clusters Scope doc.pdf > > > Recently, changes (such as HBASE-17437) have unblocked HBase to run with a > root directory external to the cluster (such as in Amazon S3). This means > that the data is stored outside of the cluster and can be accessible after > the cluster has been terminated. One use case that is often asked about is > pointing multiple clusters to one root directory (sharing the data) to have > read resiliency in the case of a cluster failure. > > This JIRA is an umbrella JIRA to contain all the tasks necessary to create a > read-replica HBase cluster that is pointed at the same root directory. > > This requires making the Read-Replica cluster Read-Only (no metadata > operation or data operations). > Separating the hbase:meta table for each cluster (Otherwise HBase gets > confused with multiple clusters trying to update the meta table with their ip > addresses) > Adding refresh functionality for the meta table to ensure new metadata is > picked up on the read replica cluster. > Adding refresh functionality for HFiles for a given table to ensure new data > is picked up on the read replica cluster. > > This can be used with any existing cluster that is backed by an external > filesystem. > > Please note that this feature is still quite manual (with the potential for > automation later). > > More information on this particular feature can be found here: > https://aws.amazon.com/blogs/big-data/setting-up-read-replica-clusters-with-hbase-on-amazon-s3/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17442) Move most of the replication related classes to hbase-server package
[ https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-17442: --- Attachment: HBASE-17442.branch-2.001.patch Retry. > Move most of the replication related classes to hbase-server package > > > Key: HBASE-17442 > URL: https://issues.apache.org/jira/browse/HBASE-17442 > Project: HBase > Issue Type: Sub-task > Components: build, Replication >Affects Versions: 2.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Critical > Fix For: 2.0.0-alpha-3 > > Attachments: 0001-hbase-replication-module.patch, > HBASE-17442.branch-2.001.patch, HBASE-17442.branch-2.001.patch, > HBASE-17442.master.001.patch, HBASE-17442.master.001.patch, > HBASE-17442.v1.patch, HBASE-17442.v2.patch, HBASE-17442.v2.patch, > HBASE-17442.v3.patch > > > After the replication requests are routed through master, replication > implementation details didn't need be exposed to client. We should move most > of the replication related classes to hbase-server package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17442) Move most of the replication related classes to hbase-server package
[ https://issues.apache.org/jira/browse/HBASE-17442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-17442: --- Attachment: HBASE-17442.master.001.patch Retry. > Move most of the replication related classes to hbase-server package > > > Key: HBASE-17442 > URL: https://issues.apache.org/jira/browse/HBASE-17442 > Project: HBase > Issue Type: Sub-task > Components: build, Replication >Affects Versions: 2.0.0 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Critical > Fix For: 2.0.0-alpha-3 > > Attachments: 0001-hbase-replication-module.patch, > HBASE-17442.branch-2.001.patch, HBASE-17442.master.001.patch, > HBASE-17442.master.001.patch, HBASE-17442.v1.patch, HBASE-17442.v2.patch, > HBASE-17442.v2.patch, HBASE-17442.v3.patch > > > After the replication requests are routed through master, replication > implementation details didn't need be exposed to client. We should move most > of the replication related classes to hbase-server package. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0
[
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134275#comment-16134275
]
Hadoop QA commented on HBASE-16179:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
2s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 9 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 0m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
30m 22s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
13s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} scaladoc {color} | {color:red} 0m
26s{color} | {color:red} hbase-spark in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
49s{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
7s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 43m 7s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-16179 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12882753/16179.v28.txt |
| Optional Tests | asflicense javac javadoc unit xml compile scalac
scaladoc |
| uname | Linux 4019a466b1c3 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b932d38 |
| Default Java | 1.8.0_144 |
| scaladoc |
https://builds.apache.org/job/PreCommit-HBASE-Build/8179/artifact/patchprocess/patch-scaladoc-hbase-spark.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/8179/testReport/ |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8179/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Fix compilation errors when building hbase-spark against Spark 2.0
> --
>
> Key: HBASE-16179
> URL: https://issues.apache.org/jira/browse/HBASE-16179
> Project: HBase
>
[jira] [Updated] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0
[ https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-16179: --- Attachment: 16179.v28.txt > Fix compilation errors when building hbase-spark against Spark 2.0 > -- > > Key: HBASE-16179 > URL: https://issues.apache.org/jira/browse/HBASE-16179 > Project: HBase > Issue Type: Bug > Components: spark >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Critical > Labels: build > Fix For: 2.0.0 > > Attachments: 16179.v0.txt, 16179.v10.txt, 16179.v11.txt, > 16179.v12.txt, 16179.v12.txt, 16179.v12.txt, 16179.v13.txt, 16179.v15.txt, > 16179.v16.txt, 16179.v18.txt, 16179.v19.txt, 16179.v19.txt, 16179.v1.txt, > 16179.v1.txt, 16179.v20.txt, 16179.v22.txt, 16179.v23.txt, 16179.v24.txt, > 16179.v25.txt, 16179.v26.txt, 16179.v27.txt, 16179.v28.txt, 16179.v28.txt, > 16179.v4.txt, 16179.v5.txt, 16179.v7.txt, 16179.v8.txt, 16179.v9.txt > > > I tried building hbase-spark module against Spark-2.0 snapshot and got the > following compilation errors: > http://pastebin.com/bg3w247a > Some Spark classes such as DataTypeParser and Logging are no longer > accessible to downstream projects. > hbase-spark module should not depend on such classes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18636) Cannot run REST server out of a built checkout; fails with NoSuchMethodError: javax.ws.rs.core.Application.getProperties
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] [Updated] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[ https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18615: -- Release Note: (was: Fix incomplete migration to jersey 2 that has a mix of clashing jersey1 and jersey2 invocations.) > hbase-rest tests fail in hbase-2.0.0-alpha2 > --- > > Key: HBASE-18615 > URL: https://issues.apache.org/jira/browse/HBASE-18615 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt, > HBASE-18615.branch-2.001.patch, HBASE-18615.branch-2.002.patch > > > Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[
https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134239#comment-16134239
]
stack commented on HBASE-18615:
---
Reset. Reel back my attempt at moving us up on to jersey2 exclusively.
Master hbase-rest test suite passes. If I run REST from tarball, it works too
doing curl get text/xml or application/json (see below). If I try to run
in-situ out of built dir, it fails w/ the below NoSuchMethodError which happens
because it is finding a jersey1 before jersey2 on the CLASSPATH (from Hadoop).
REST actually makes use of jersey1 doing JSON, the Jackson1Feature that we ask
for on creation of the ResourceConfig setting up the REST server.
branch-2 works out of tarball but hbase-rest suite fails. Ditto on the run from
in-situ out of a build dir.
The difference between the two branches is what @samir ahmic, above, the use of
Jackson1Feature in the REST test utility (in master but not in branch-2). When
I put that into branch-2, it works like master branch.
For this issue, lets push the branch-2 patch that makes master and branch-2 the
same. Tests will pass then. The work to come up purely on jersey2 and that REST
does not run in-situ, we can do elsewhere; they are of less import.
{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}
{code}
kalashnikov:hbase-3.0.0-SNAPSHOT stack$ curl -vi -X GET -H "Accept: text/xml"
http://localhost:8080/version/cluster
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8080 (#0)
> GET /version/cluster HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.51.0
> Accept: text/xml
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Cache-Control: no-cache
Cache-Control: no-cache
< Content-Type: text/xml
Content-Type: text/xml
< Content-Length: 102
Content-Length: 102
<
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
3.0.0-SNAPSHOT
kalashnikov:hbase-3.0.0-SNAPSHOT stack$ curl -vi -X GET -H "Accept:
application/json" http://localhost:8080/version/cluster
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8080 (#0)
> GET /version/cluster HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.51.0
> Accept: application/json
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Cache-Control: no-cache
Cache-Control: no-cache
< Content-Type: application/json
Content-Type: application/json
< Content-Length: 16
Content-Length: 16
<
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
"3.0.0-SNAPSHOT"
{code}
> hbase-rest tests fail in hbase-2.0.0-alpha2
> ---
>
> Key: HBASE-18615
> URL: https://issues.apache.org/jira/browse/HBASE-18615
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt,
> HBASE-18615.branch-2.001.patch, HBASE-18615.branch-2.002.patch
>
>
> Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[ https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18615: -- Attachment: HBASE-18615.branch-2.002.patch > hbase-rest tests fail in hbase-2.0.0-alpha2 > --- > > Key: HBASE-18615 > URL: https://issues.apache.org/jira/browse/HBASE-18615 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt, > HBASE-18615.branch-2.001.patch, HBASE-18615.branch-2.002.patch > > > Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17949) Shorten the execution time of TestBackupMultipleDeletes
[ https://issues.apache.org/jira/browse/HBASE-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-17949: --- Attachment: testBackupMultipleDeletes-output.tar.gz When I ran the test on MacBook, it took >5 minutes. Here is test output. > Shorten the execution time of TestBackupMultipleDeletes > --- > > Key: HBASE-17949 > URL: https://issues.apache.org/jira/browse/HBASE-17949 > Project: HBase > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Labels: backup > Attachments: testBackupMultipleDeletes-output.tar.gz > > > On my Mac, TestBackupMultipleDeletes took 10 minutes to run. > The test performs 5 incremental backups in total for 3 tables. > We can reduce the number of incremental backups so that runtime comes down by > a few minutes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14785) Hamburger menu for mobile site
[ https://issues.apache.org/jira/browse/HBASE-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134213#comment-16134213 ] Mike Drob commented on HBASE-14785: --- sometimes probably means that it happens with some commands and not others, but i haven't been paying enough attention to figure out which ones. e.g. maybe site triggers it, but package doesn't. > Hamburger menu for mobile site > -- > > Key: HBASE-14785 > URL: https://issues.apache.org/jira/browse/HBASE-14785 > Project: HBase > Issue Type: Sub-task > Components: website >Affects Versions: 2.0.0 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: > 0001-HBASE-14774-Addendum-Exclude-src-main-site-resources.patch, > HBASE-14774-addendum2_tweak_css.patch, HBASE-14785-addendum.patch, > HBASE-14785-addendum-v1.patch, HBASE-14785.patch, HBASE-14785-v1.patch, > HBASE-14785-v2.patch, maven-fluido-skin-1.5-HBASE.jar > > > Figure out how to do a hamburger menu on mobile. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134207#comment-16134207 ] Sean Busbey commented on HBASE-17823: - want me to do that as a follow-on so that the change set in the github PR is smaller? > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-12349) Add Maven build support module for a custom version of error-prone
[ https://issues.apache.org/jira/browse/HBASE-12349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134206#comment-16134206 ] Sean Busbey commented on HBASE-12349: - just a heads up, since I don't want to make this a blocker for the next alpha I may pull the addition of the hbase-build-configuration module into HBASE-17823 if it looks like that's going to land first. > Add Maven build support module for a custom version of error-prone > -- > > Key: HBASE-12349 > URL: https://issues.apache.org/jira/browse/HBASE-12349 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Mike Drob >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-12349.patch, HBASE-12349.v2.patch, > HBASE-12349.v3.patch, HBASE-12349.v4.patch, HBASE-12349.v5.patch > > > Add a new Maven build support module that builds and publishes a custom > error-prone artifact for use by the rest of the build. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134205#comment-16134205 ] Misty Stanley-Jones commented on HBASE-17823: - It builds and I don't see any problems. If you'd like to work together on the doc changes, can you just open a Github PR and tag me there so I can commit into it? > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134200#comment-16134200
]
Hadoop QA commented on HBASE-18634:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 57s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 64m 40s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
32s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}116m 15s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | org.apache.hadoop.hbase.mapreduce.TestWALPlayer |
| | org.apache.hadoop.hbase.master.procedure.TestCreateTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | org.apache.hadoop.hbase.client.TestSnapshotCloneIndependence |
| | org.apache.hadoop.hbase.mapreduce.TestTableInputFormat |
| | org.apache.hadoop.hbase.client.TestAsyncTableScanAll |
| | org.apache.hadoop.hbase.client.TestFromClientSide |
| | org.apache.hadoop.hbase.client.TestMultipleTimestamps |
| | org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
| | org.apache.hadoop.hbase.backup.TestRemoteBackup |
| | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
| | org.apache.hadoop.hbase.client.TestAsyncTableBatch |
| | org.apache.hadoop.hbase.client.TestAsyncNamespaceAdminApi |
| | org.apache.hadoop.hbase.client.TestAsyncProcedureAdminApi |
| | org.apache.hadoop.hbase.TestFullLogReconstruction |
| | org.apache.hadoop.hbase.mapred.TestTableInputFormat |
| | org.apache.hadoop.hbase.namespace.TestNamespaceAuditor |
| | org.apache.hadoop.hbase.coprocessor.TestCoprocessorMetrics |
| | org.apache.hadoop.hbase.TestMultiVersions |
| | org.apache.hadoop.hbase.client.TestAsyncSnapshotAdminApi |
| | org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator |
| | org.apache.hadoop.hbase.quotas.TestQuotaStatusRPCs |
| |
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
[jira] [Commented] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134198#comment-16134198
]
Misty Stanley-Jones commented on HBASE-18635:
-
It's in src/main/asciidoc/_chapters/external_apis.adoc
> 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] [Updated] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-15753:
Component/s: website
documentation
community
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18635) Fix asciidoc warnings
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] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134195#comment-16134195 ] Sean Busbey commented on HBASE-17823: - excellent catch. I'll post a new patch with that section updated later tonight. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134190#comment-16134190 ] Misty Stanley-Jones commented on HBASE-17823: - Please have a look at http://hbase.apache.org/book.html#hbase.client.api.surface and make sure nothing needs changing due to this. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14785) Hamburger menu for mobile site
[
https://issues.apache.org/jira/browse/HBASE-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134179#comment-16134179
]
Misty Stanley-Jones commented on HBASE-14785:
-
I'm a little concerned about "sometimes" -- it's not happening every time?
As a working hypothesis, there is probably some time where {{project.basedir}}
is referred to in the POM with slightly off syntax and isn't getting expanded.
> Hamburger menu for mobile site
> --
>
> Key: HBASE-14785
> URL: https://issues.apache.org/jira/browse/HBASE-14785
> Project: HBase
> Issue Type: Sub-task
> Components: website
>Affects Versions: 2.0.0
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments:
> 0001-HBASE-14774-Addendum-Exclude-src-main-site-resources.patch,
> HBASE-14774-addendum2_tweak_css.patch, HBASE-14785-addendum.patch,
> HBASE-14785-addendum-v1.patch, HBASE-14785.patch, HBASE-14785-v1.patch,
> HBASE-14785-v2.patch, maven-fluido-skin-1.5-HBASE.jar
>
>
> Figure out how to do a hamburger menu on mobile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17949) Shorten the execution time of TestBackupMultipleDeletes
[
https://issues.apache.org/jira/browse/HBASE-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134172#comment-16134172
]
Reid Chan commented on HBASE-17949:
---
here is mine (one of):
{code}
Running org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 178.117 sec -
in org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{code} But sometimes, it couldn't finish itself.
My mac: 2.7 GHz Intel Core i5, 8 GB 1867 MHz DDR3.
Maybe there are unstable factors? i'm going to run more few times and look
deeply in codes
> Shorten the execution time of TestBackupMultipleDeletes
> ---
>
> Key: HBASE-17949
> URL: https://issues.apache.org/jira/browse/HBASE-17949
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Priority: Minor
> Labels: backup
>
> On my Mac, TestBackupMultipleDeletes took 10 minutes to run.
> The test performs 5 incremental backups in total for 3 tables.
> We can reduce the number of incremental backups so that runtime comes down by
> a few minutes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18511) Default no regions on master
[ https://issues.apache.org/jira/browse/HBASE-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134165#comment-16134165 ] stack commented on HBASE-18511: --- Thanks. Let take a look > Default no regions on master > > > Key: HBASE-18511 > URL: https://issues.apache.org/jira/browse/HBASE-18511 > Project: HBase > Issue Type: Task > Components: master >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18511.master.001.patch, > HBASE-18511.master.002.patch, HBASE-18511.master.003.patch, > HBASE-18511.master.004.patch, HBASE-18511.master.005.patch, > HBASE-18511.master.006.patch, HBASE-18511.master.007.patch, > HBASE-18511.master.008.patch, HBASE-18511.master.009.patch, > HBASE-18511.master.010.patch, HBASE-18511.master.011.patch, > HBASE-18511.master.012.patch, HBASE-18511.master.013.patch, > HBASE-18511.master.014.patch, HBASE-18511.master.015.patch > > > Let this be umbrella issue for no-regions-on-master as default deploy (as it > was in branch-1). > Also need to make sure we can run WITH regions on master; in particular > system tables with RPC short-circuit as it is now in hbase master. > Background is that master branch carried a change that allowed Master carry > regions. On top of this improvement on branch-1, Master defaulted to carry > system tables only. No release was made with this configuration. Now we are > going to cut the 2.0.0 release, the decision is that hbase-2 should have the > same layout as hbase-1 so this issue implements the undoing of Master > carrying system tables by default (though the capability remains). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[ https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134163#comment-16134163 ] stack commented on HBASE-18615: --- [~asamir] thanks for tip but I was trying to remove all instances of jackson1feature since it pulls in jersey1. I was going to start over this morning. Back out of the current rate hole. > hbase-rest tests fail in hbase-2.0.0-alpha2 > --- > > Key: HBASE-18615 > URL: https://issues.apache.org/jira/browse/HBASE-18615 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt, > HBASE-18615.branch-2.001.patch > > > Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18621) Refactor ClusterOptions before applying to code base
[ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134158#comment-16134158 ] Reid Chan commented on HBASE-18621: --- There is conflict with [HBASE-18634|https://issues.apache.org/jira/browse/HBASE-18634], waiting until it is committed. > Refactor ClusterOptions before applying to code base > > > Key: HBASE-18621 > URL: https://issues.apache.org/jira/browse/HBASE-18621 > Project: HBase > Issue Type: Improvement >Reporter: Reid Chan >Assignee: Reid Chan > Attachments: HBASE-18621.master.001.patch, > HBASE-18621.master.002.patch > > > So far, ClusterStatus.Options is not so clean that can be applied to code > base. > Refactoring it before next move. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18621) Refactor ClusterOptions before applying to code base
[ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan updated HBASE-18621: -- Status: Open (was: Patch Available) > Refactor ClusterOptions before applying to code base > > > Key: HBASE-18621 > URL: https://issues.apache.org/jira/browse/HBASE-18621 > Project: HBase > Issue Type: Improvement >Reporter: Reid Chan >Assignee: Reid Chan > Attachments: HBASE-18621.master.001.patch, > HBASE-18621.master.002.patch > > > So far, ClusterStatus.Options is not so clean that can be applied to code > base. > Refactoring it before next move. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134154#comment-16134154
]
Chia-Ping Tsai commented on HBASE-18634:
Thanks for the reviews. [~reidchan]
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Commented] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134153#comment-16134153
]
Reid Chan commented on HBASE-18634:
---
Yea, after patch
[HBASE-18511|https://issues.apache.org/jira/browse/HBASE-18511] i think
{code}
+// By default, HMaster don't carry any regions so it won't report its load.
+// Hence, it won't be in the server list.
+Assert.assertEquals(status.getServers().size(), numRs);
{code}
is right, besides that, these codes
{code}
-while (!DEAD.isStopped()) {
+while (rst.isAlive()) {
Thread.sleep(500);
}
{code} make this test stable, not like previous version...
lgtm.
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Commented] (HBASE-12349) Add Maven build support module for a custom version of error-prone
[
https://issues.apache.org/jira/browse/HBASE-12349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134149#comment-16134149
]
Sean Busbey commented on HBASE-12349:
-
generated source tarball with:
{code}
$ git clean -xdfff
$ mvn clean install -DskipTests assembly:single
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{code}
Looks like it's got some extra cruft:
{code}
$ mkdir /tmp/hbase_cc0b245_src
$ tar -C /tmp/hbase_cc0b245_src -xzf
hbase-assembly/target/hbase-3.0.0-SNAPSHOT-src.tar.gz
$ diff -r . /tmp/hbase_cc0b245_src/hbase-3.0.0-SNAPSHOT/
Only in .: .git
Only in .: .gitattributes
Only in .: .gitignore
Only in .: .pylintrc
Only in
/tmp/hbase_cc0b245_src/hbase-3.0.0-SNAPSHOT/hbase-build-support/hbase-error-prone:
target
Only in .: hbase-native-client
Only in /tmp/hbase_cc0b245_src/hbase-3.0.0-SNAPSHOT/hbase-protocol-shaded:
dependency-reduced-pom.xml
{code}
Some of those have been around awhile, some are new-to-me. I think only the
target directory in the hbase-error-prone module is from this patch.
> Add Maven build support module for a custom version of error-prone
> --
>
> Key: HBASE-12349
> URL: https://issues.apache.org/jira/browse/HBASE-12349
> Project: HBase
> Issue Type: Sub-task
>Reporter: Andrew Purtell
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-12349.patch, HBASE-12349.v2.patch,
> HBASE-12349.v3.patch, HBASE-12349.v4.patch, HBASE-12349.v5.patch
>
>
> Add a new Maven build support module that builds and publishes a custom
> error-prone artifact for use by the rest of the build.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134143#comment-16134143
]
Chia-Ping Tsai commented on HBASE-18634:
[~reidchan] Any suggestions?
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Commented] (HBASE-18511) Default no regions on master
[ https://issues.apache.org/jira/browse/HBASE-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134135#comment-16134135 ] Chia-Ping Tsai commented on HBASE-18511: This issue breaks some tests. I opened HBASE-18627 and HBASE-18634 to fix. FYI [~stack] > Default no regions on master > > > Key: HBASE-18511 > URL: https://issues.apache.org/jira/browse/HBASE-18511 > Project: HBase > Issue Type: Task > Components: master >Reporter: stack >Assignee: stack >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-18511.master.001.patch, > HBASE-18511.master.002.patch, HBASE-18511.master.003.patch, > HBASE-18511.master.004.patch, HBASE-18511.master.005.patch, > HBASE-18511.master.006.patch, HBASE-18511.master.007.patch, > HBASE-18511.master.008.patch, HBASE-18511.master.009.patch, > HBASE-18511.master.010.patch, HBASE-18511.master.011.patch, > HBASE-18511.master.012.patch, HBASE-18511.master.013.patch, > HBASE-18511.master.014.patch, HBASE-18511.master.015.patch > > > Let this be umbrella issue for no-regions-on-master as default deploy (as it > was in branch-1). > Also need to make sure we can run WITH regions on master; in particular > system tables with RPC short-circuit as it is now in hbase master. > Background is that master branch carried a change that allowed Master carry > regions. On top of this improvement on branch-1, Master defaulted to carry > system tables only. No release was made with this configuration. Now we are > going to cut the 2.0.0 release, the decision is that hbase-2 should have the > same layout as hbase-1 so this issue implements the undoing of Master > carrying system tables by default (though the capability remains). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134136#comment-16134136
]
Chia-Ping Tsai commented on HBASE-18634:
I have run the test 50 times. All pass
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Updated] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18634:
---
Attachment: HBASE-18634.v0.patch
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Updated] (HBASE-18634) Fix client.TestClientClusterStatus
[
https://issues.apache.org/jira/browse/HBASE-18634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18634:
---
Status: Patch Available (was: Open)
> 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
>
> Attachments: HBASE-18634.v0.patch
>
>
> 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] [Created] (HBASE-18634) Fix client.TestClientClusterStatus
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] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134125#comment-16134125 ] Sean Busbey commented on HBASE-17823: - ran through TestInterfaceAudienceAnnotations, which worked. Also ran through maven site and checked that generated javadocs still properly handle split between public and non-public classes. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[
https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134062#comment-16134062
]
Samir Ahmic commented on HBASE-18615:
-
[~stack] small tip for test failures we probably need this line in
HBaseRESTTestingUtility.java also:
{code}
@@ -62,6 +62,7 @@ public class HBaseRESTTestingUtility {
// set up the Jersey servlet container for Jetty
ResourceConfig app = new ResourceConfig();
+
app.packages("org.apache.hadoop.hbase.rest").register(Jackson1Feature.class);
ServletHolder sh = new ServletHolder(new ServletContainer(app));
{code}
> hbase-rest tests fail in hbase-2.0.0-alpha2
> ---
>
> Key: HBASE-18615
> URL: https://issues.apache.org/jira/browse/HBASE-18615
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt,
> HBASE-18615.branch-2.001.patch
>
>
> Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-17823: Attachment: HBASE-17823.0.patch -0 - presumes HBASE-12349 is in place; needs it to avoid a dependency loop between annotations for tests and checkstyle - move everything to yetus annotations (includes hbase audience annotations and a ton of erroneous use of hadoop audience annotations) - delete our own annotations > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18506) java.lang.AbstractMethodError in hbase REST server
[
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)
[jira] [Updated] (HBASE-18518) Remove jersey1* dependencies from project and jersey1* jars from lib dir
[ https://issues.apache.org/jira/browse/HBASE-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samir Ahmic updated HBASE-18518: Fix Version/s: (was: 2.0.0-alpha-3) 3.0.0 > Remove jersey1* dependencies from project and jersey1* jars from lib dir > > > Key: HBASE-18518 > URL: https://issues.apache.org/jira/browse/HBASE-18518 > Project: HBase > Issue Type: Task > Components: dependencies, pom, REST >Affects Versions: 3.0.0, 2.0.0-alpha-1 >Reporter: Samir Ahmic >Assignee: Samir Ahmic > Labels: cleanup > Fix For: 3.0.0 > > Attachments: HBASE-18518-master-01.patch, HBASE-18518-master-02.patch > > > Recently i have opened https://issues.apache.org/jira/browse/HBASE-18506 and > it is clear that is caused by mixing jersey1 and jersey2 jars in classpath. > With https://issues.apache.org/jira/browse/HBASE-12894 we have introduced > jersey2 to project, and we also have bunch of transitive dependencies > (mainly from hadoop) on jersey1 which is not happiest situation since jersey1 > and jersey2 under same classpath can case runtime issues as it was case with > rest. > This task will have following steps > * Clean code and replace jersey1 constructs with jersey2 versions(there > should not be much of this) > * Add exclusions for transitive jersey1 dependencies in pom.xml > * Add exclusions in hadoop-two-compat.xml to prevent jersey1 jars in lib dir -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14498) Master stuck in infinite loop when all Zookeeper servers are unreachable
[
https://issues.apache.org/jira/browse/HBASE-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134032#comment-16134032
]
Pankaj Kumar commented on HBASE-14498:
--
Oh, I will check this for branch 1.3..
> Master stuck in infinite loop when all Zookeeper servers are unreachable
>
>
> Key: HBASE-14498
> URL: https://issues.apache.org/jira/browse/HBASE-14498
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Y. SREENIVASULU REDDY
>Assignee: Pankaj Kumar
>Priority: Critical
> Fix For: 2.0.0, 1.3.2, 1.4.1, 1.5.0
>
> Attachments: HBASE-14498-addendum.patch,
> HBASE-14498-branch-1.3.patch, HBASE-14498-branch-1.4.patch,
> HBASE-14498-branch-1.patch, HBASE-14498.master.001.patch,
> HBASE-14498.master.002.patch, HBASE-14498.patch, HBASE-14498-V2.patch,
> HBASE-14498-V3.patch, HBASE-14498-V4.patch, HBASE-14498-V5.patch,
> HBASE-14498-V6.patch, HBASE-14498-V6.patch
>
>
> We met a weird scenario in our production environment.
> In a HA cluster,
> > Active Master (HM1) is not able to connect to any Zookeeper server (due to
> > N/w breakdown on master machine network with Zookeeper servers).
> {code}
> 2015-09-26 15:24:47,508 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Client session timed out, have not heard from server in
> 33463ms for sessionid 0x104576b8dda0002, closing socket connection and
> attempting reconnect
> 2015-09-26 15:24:47,877 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> client.FourLetterWordMain: connecting to ZK-Host1 2181
> 2015-09-26 15:24:48,236 INFO [main-SendThread(ZK-Host1:2181)]
> client.FourLetterWordMain: connecting to ZK-Host1 2181
> 2015-09-26 15:24:49,879 WARN
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host1
> 2015-09-26 15:24:49,879 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ZK-Host1/ZK-IP1:2181. Will not attempt to authenticate using SASL (unknown
> error)
> 2015-09-26 15:24:50,238 WARN [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host1
> 2015-09-26 15:24:50,238 INFO [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ZK-Host1/ZK-Host1:2181. Will not attempt to authenticate using SASL (unknown
> error)
> 2015-09-26 15:25:17,470 INFO [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Client session timed out, have not heard from server in
> 30023ms for sessionid 0x2045762cc710006, closing socket connection and
> attempting reconnect
> 2015-09-26 15:25:17,571 WARN [master/HM1-Host/HM1-IP:16000]
> zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper,
> quorum=ZK-Host:2181,ZK-Host1:2181,ZK-Host2:2181,
> exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /hbase/master
> 2015-09-26 15:25:17,872 INFO [main-SendThread(ZK-Host:2181)]
> client.FourLetterWordMain: connecting to ZK-Host 2181
> 2015-09-26 15:25:19,874 WARN [main-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host
> 2015-09-26 15:25:19,874 INFO [main-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server ZK-Host/ZK-IP:2181.
> Will not attempt to authenticate using SASL (unknown error)
> {code}
> > Since HM1 was not able to connect to any ZK, so session timeout didnt
> > happen at Zookeeper server side and HM1 didnt abort.
> > On Zookeeper session timeout standby master (HM2) registered himself as an
> > active master.
> > HM2 is keep on waiting for region server to report him as part of active
> > master intialization.
> {noformat}
> 2015-09-26 15:24:44,928 | INFO | HM2-Host:21300.activeMasterManager | Waiting
> for region servers count to settle; currently checked in 0, slept for 0 ms,
> expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval
> of 1500 ms. |
> org.apache.hadoop.hbase.master.ServerManager.waitForRegionServers(ServerManager.java:1011)
> ---
> ---
> 2015-09-26 15:32:50,841 | INFO | HM2-Host:21300.activeMasterManager | Waiting
> for region servers count to settle; currently checked in 0, slept for 483913
> ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms,
> interval of 1500 ms. |
> org.apache.hadoop.hbase.master.ServerManager.waitForRegionServers(ServerManager.java:1011)
> {noformat}
> > At other end, region servers are reporting to HM1 on 3 sec interval. Here
> > region server retrieve master location from zookeeper only when they
> > couldn't connect
[jira] [Updated] (HBASE-18621) Refactor ClusterOptions before applying to code base
[ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan updated HBASE-18621: -- Status: Patch Available (was: Open) > Refactor ClusterOptions before applying to code base > > > Key: HBASE-18621 > URL: https://issues.apache.org/jira/browse/HBASE-18621 > Project: HBase > Issue Type: Improvement >Reporter: Reid Chan >Assignee: Reid Chan > Attachments: HBASE-18621.master.001.patch, > HBASE-18621.master.002.patch > > > So far, ClusterStatus.Options is not so clean that can be applied to code > base. > Refactoring it before next move. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18621) Refactor ClusterOptions before applying to code base
[ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan updated HBASE-18621: -- Status: Open (was: Patch Available) > Refactor ClusterOptions before applying to code base > > > Key: HBASE-18621 > URL: https://issues.apache.org/jira/browse/HBASE-18621 > Project: HBase > Issue Type: Improvement >Reporter: Reid Chan >Assignee: Reid Chan > Attachments: HBASE-18621.master.001.patch, > HBASE-18621.master.002.patch > > > So far, ClusterStatus.Options is not so clean that can be applied to code > base. > Refactoring it before next move. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18621) Refactor ClusterOptions before applying to code base
[ https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134028#comment-16134028 ] Reid Chan commented on HBASE-18621: --- It's abnormal, trigger QA again. > Refactor ClusterOptions before applying to code base > > > Key: HBASE-18621 > URL: https://issues.apache.org/jira/browse/HBASE-18621 > Project: HBase > Issue Type: Improvement >Reporter: Reid Chan >Assignee: Reid Chan > Attachments: HBASE-18621.master.001.patch, > HBASE-18621.master.002.patch > > > So far, ClusterStatus.Options is not so clean that can be applied to code > base. > Refactoring it before next move. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18375) The pool chunks from ChunkCreator are deallocated while in pool because there is no reference to them
[ https://issues.apache.org/jira/browse/HBASE-18375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134016#comment-16134016 ] Anastasia Braginsky commented on HBASE-18375: - [~anoop.hbase] and [~ram_krish] thank you for your help and reviews! Anoop, Ram and [~stack], what about committing to Release 2.0 as well? If it is needed, what branch should be used? In Release 2.0 the MSLAB chunks may not return to the pool, but with low probability of this to happen. > The pool chunks from ChunkCreator are deallocated while in pool because there > is no reference to them > - > > Key: HBASE-18375 > URL: https://issues.apache.org/jira/browse/HBASE-18375 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.0.0-alpha-1 >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18375-V01.patch, HBASE-18375-V02.patch, > HBASE-18375-V03.patch, HBASE-18375-V04.patch, HBASE-18375-V05.patch, > HBASE-18375-V06.patch, HBASE-18375-V07.patch, HBASE-18375-V08.patch, > HBASE-18375-V09.patch, HBASE-18375-V10.patch, HBASE-18375-V11.patch > > > Because MSLAB list of chunks was changed to list of chunk IDs, the chunks > returned back to pool can be deallocated by JVM because there is no reference > to them. The solution is to protect pool chunks from GC by the strong map of > ChunkCreator introduced by HBASE-18010. Will prepare the patch today. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18621) Refactor ClusterOptions before applying to code base
[
https://issues.apache.org/jira/browse/HBASE-18621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134011#comment-16134011
]
Hadoop QA commented on HBASE-18621:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
39s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
38m 4s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
55s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 80m 56s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
57s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}148m 37s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestEnableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestDeleteTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestModifyTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestCreateTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | org.apache.hadoop.hbase.regionserver.TestRowTooBig |
| | org.apache.hadoop.hbase.mapreduce.TestWALPlayer |
| | org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy
|
| | org.apache.hadoop.hbase.mapreduce.TestTableInputFormat |
| | org.apache.hadoop.hbase.mapreduce.TestHRegionPartitioner |
| | org.apache.hadoop.hbase.master.TestGetLastFlushedSequenceId |
| | org.apache.hadoop.hbase.regionserver.wal.TestFSHLog |
| | org.apache.hadoop.hbase.regionserver.TestCompaction |
| | org.apache.hadoop.hbase.trace.TestHTraceHooks |
| |
[jira] [Commented] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[
https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134004#comment-16134004
]
stack commented on HBASE-18615:
---
Having trouble getting jersey2 reading/writing json. The Jackson1Feature trick
that was used in past pulls in jersey1. Trying to change it to go the kosher
route makes for new issues. Here are some items that get more of the tests to
pass and json to render in certain contexts.
Add registering of the jaxrs and a provider when setting up the Rest
Application:
+ static class RESTApplication extends ResourceConfig {
+public RESTApplication() {
+ packages( "org.apache.hadoop.hbase.rest",
"com.fasterxml.jackson.jaxrs.base");
+ register(JacksonJsonProvider.class);
+}
+ }
Fixed TestTableResource at least.
Next up is using alternate JacksonJaxbJsonProvider from fasterxml but it
doesn't know what to do w/ iterator type.
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized
field "iterator" (class org.apache.hadoop.hbase.rest.model.CellSetModel), not
marked as ignorable (one known property: "Row"])
The filtering out of jersey1 from hadoop is causing other test failures.
Didn't expect this to get so ugly. It comes of our upgrade of jetty/jersey so
would be worth getting to the end
> hbase-rest tests fail in hbase-2.0.0-alpha2
> ---
>
> Key: HBASE-18615
> URL: https://issues.apache.org/jira/browse/HBASE-18615
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt,
> HBASE-18615.branch-2.001.patch
>
>
> Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18632) TestMultiParallel#testFlushCommitsWithAbort fails in master branch
[
https://issues.apache.org/jira/browse/HBASE-18632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133997#comment-16133997
]
Ted Yu edited comment on HBASE-18632 at 8/19/17 7:37 AM:
-
The failed tests were not related to the patch.
was (Author: yuzhih...@gmail.com):
TestMultiParallel passed.
The failed tests were not related to the patch.
> TestMultiParallel#testFlushCommitsWithAbort fails in master branch
> --
>
> Key: HBASE-18632
> URL: https://issues.apache.org/jira/browse/HBASE-18632
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 18632.v1.txt
>
>
> This can be reproduced:
> {code}
> java.lang.AssertionError: Waiting timed out after [15,000] msec
> at
> org.apache.hadoop.hbase.client.TestMultiParallel.doTestFlushCommits(TestMultiParallel.java:310)
> at
> org.apache.hadoop.hbase.client.TestMultiParallel.testFlushCommitsWithAbort(TestMultiParallel.java:257)
> {code}
> The server count is affected by no-regions-on-master being the default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-14498) Master stuck in infinite loop when all Zookeeper servers are unreachable
[
https://issues.apache.org/jira/browse/HBASE-14498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134001#comment-16134001
]
Hudson commented on HBASE-14498:
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #256 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/256/])
Revert "HBASE-14498 Master stuck in infinite loop when all Zookeeper (stack:
rev 92a2dfcd6cef87b1b2ec62a5e8912d3c26f9b30d)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/zookeeper/TestZooKeeperWatcher.java
> Master stuck in infinite loop when all Zookeeper servers are unreachable
>
>
> Key: HBASE-14498
> URL: https://issues.apache.org/jira/browse/HBASE-14498
> Project: HBase
> Issue Type: Bug
> Components: master
>Reporter: Y. SREENIVASULU REDDY
>Assignee: Pankaj Kumar
>Priority: Critical
> Fix For: 2.0.0, 1.3.2, 1.4.1, 1.5.0
>
> Attachments: HBASE-14498-addendum.patch,
> HBASE-14498-branch-1.3.patch, HBASE-14498-branch-1.4.patch,
> HBASE-14498-branch-1.patch, HBASE-14498.master.001.patch,
> HBASE-14498.master.002.patch, HBASE-14498.patch, HBASE-14498-V2.patch,
> HBASE-14498-V3.patch, HBASE-14498-V4.patch, HBASE-14498-V5.patch,
> HBASE-14498-V6.patch, HBASE-14498-V6.patch
>
>
> We met a weird scenario in our production environment.
> In a HA cluster,
> > Active Master (HM1) is not able to connect to any Zookeeper server (due to
> > N/w breakdown on master machine network with Zookeeper servers).
> {code}
> 2015-09-26 15:24:47,508 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Client session timed out, have not heard from server in
> 33463ms for sessionid 0x104576b8dda0002, closing socket connection and
> attempting reconnect
> 2015-09-26 15:24:47,877 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> client.FourLetterWordMain: connecting to ZK-Host1 2181
> 2015-09-26 15:24:48,236 INFO [main-SendThread(ZK-Host1:2181)]
> client.FourLetterWordMain: connecting to ZK-Host1 2181
> 2015-09-26 15:24:49,879 WARN
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host1
> 2015-09-26 15:24:49,879 INFO
> [HM1-Host:16000.activeMasterManager-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ZK-Host1/ZK-IP1:2181. Will not attempt to authenticate using SASL (unknown
> error)
> 2015-09-26 15:24:50,238 WARN [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host1
> 2015-09-26 15:24:50,238 INFO [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server
> ZK-Host1/ZK-Host1:2181. Will not attempt to authenticate using SASL (unknown
> error)
> 2015-09-26 15:25:17,470 INFO [main-SendThread(ZK-Host1:2181)]
> zookeeper.ClientCnxn: Client session timed out, have not heard from server in
> 30023ms for sessionid 0x2045762cc710006, closing socket connection and
> attempting reconnect
> 2015-09-26 15:25:17,571 WARN [master/HM1-Host/HM1-IP:16000]
> zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper,
> quorum=ZK-Host:2181,ZK-Host1:2181,ZK-Host2:2181,
> exception=org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /hbase/master
> 2015-09-26 15:25:17,872 INFO [main-SendThread(ZK-Host:2181)]
> client.FourLetterWordMain: connecting to ZK-Host 2181
> 2015-09-26 15:25:19,874 WARN [main-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Can not get the principle name from server ZK-Host
> 2015-09-26 15:25:19,874 INFO [main-SendThread(ZK-Host:2181)]
> zookeeper.ClientCnxn: Opening socket connection to server ZK-Host/ZK-IP:2181.
> Will not attempt to authenticate using SASL (unknown error)
> {code}
> > Since HM1 was not able to connect to any ZK, so session timeout didnt
> > happen at Zookeeper server side and HM1 didnt abort.
> > On Zookeeper session timeout standby master (HM2) registered himself as an
> > active master.
> > HM2 is keep on waiting for region server to report him as part of active
> > master intialization.
> {noformat}
> 2015-09-26 15:24:44,928 | INFO | HM2-Host:21300.activeMasterManager | Waiting
> for region servers count to settle; currently checked in 0, slept for 0 ms,
> expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval
> of 1500 ms. |
> org.apache.hadoop.hbase.master.ServerManager.waitForRegionServers(ServerManager.java:1011)
> ---
> ---
> 2015-09-26 15:32:50,841 | INFO | HM2-Host:21300.activeMasterManager
[jira] [Commented] (HBASE-18632) TestMultiParallel#testFlushCommitsWithAbort fails in master branch
[
https://issues.apache.org/jira/browse/HBASE-18632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133997#comment-16133997
]
Ted Yu commented on HBASE-18632:
TestMultiParallel passed.
The failed tests were not related to the patch.
> TestMultiParallel#testFlushCommitsWithAbort fails in master branch
> --
>
> Key: HBASE-18632
> URL: https://issues.apache.org/jira/browse/HBASE-18632
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 18632.v1.txt
>
>
> This can be reproduced:
> {code}
> java.lang.AssertionError: Waiting timed out after [15,000] msec
> at
> org.apache.hadoop.hbase.client.TestMultiParallel.doTestFlushCommits(TestMultiParallel.java:310)
> at
> org.apache.hadoop.hbase.client.TestMultiParallel.testFlushCommitsWithAbort(TestMultiParallel.java:257)
> {code}
> The server count is affected by no-regions-on-master being the default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18577) shaded client includes several non-relocated third party dependencies
[
https://issues.apache.org/jira/browse/HBASE-18577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-18577:
Attachment: HBASE-18577.WIP.3.patch
-03 still WIP, but (untested) client artifact now has reasonable looking deps
- removed some transitives from hbase-client that I don't think are used
- moved junit to test scope in hbase-client and shaded-client
- moved all the logging backends to be optional
{code}
Busbey-MBA:hbase busbey$ mvn -Dtest=NoUnitTestsPlease -pl
hbase-shaded/hbase-shaded-check-invariants -am -Prelease verify install
Busbey-MBA:hbase busbey$ mvn -f
~/.m2/repository/org/apache/hbase/hbase-shaded-client/3.0.0-SNAPSHOT/hbase-shaded-client-3.0.0-SNAPSHOT.pom
dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO] Detecting the operating system and CPU architecture
[INFO]
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.11
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 11
[INFO] os.detected.classifier: osx-x86_64
[INFO]
[INFO]
[INFO] Building Apache HBase - Shaded - Client 3.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:tree (default-cli) @
hbase-shaded-client ---
[INFO] org.apache.hbase:hbase-shaded-client:jar:3.0.0-SNAPSHOT
[INFO] +- commons-logging:commons-logging:jar:1.2:compile
[INFO] +- org.apache.htrace:htrace-core:jar:3.2.0-incubating:compile
[INFO] +- org.apache.hbase:hbase-resource-bundle:jar:3.0.0-SNAPSHOT:compile
(optional)
[INFO] +- log4j:log4j:jar:1.2.17:compile (optional)
[INFO] +- org.slf4j:slf4j-log4j12:jar:1.7.24:compile (optional)
[INFO] +- org.slf4j:slf4j-api:jar:1.7.24:compile
[INFO] +- com.github.stephenc.findbugs:findbugs-annotations:jar:1.3.9-1:compile
[INFO] +- junit:junit:jar:4.12:test
[INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO] \- org.mockito:mockito-all:jar:1.10.19:test
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 4.185 s
[INFO] Finished at: 2017-08-19T02:22:32-05:00
[INFO] Final Memory: 21M/228M
[INFO]
Busbey-MBA:hbase busbey$
{code}
hbase-shaded-server still is a mess:
{code}
Busbey-MBA:hbase busbey$ mvn -f
~/.m2/repository/org/apache/hbase/hbase-shaded-server/3.0.0-SNAPSHOT/hbase-shaded-server-3.0.0-SNAPSHOT.pom
dependency:tree
[INFO] Scanning for projects...
[INFO]
[INFO] Detecting the operating system and CPU architecture
[INFO]
[INFO] os.detected.name: osx
[INFO] os.detected.arch: x86_64
[INFO] os.detected.version: 10.11
[INFO] os.detected.version.major: 10
[INFO] os.detected.version.minor: 11
[INFO] os.detected.classifier: osx-x86_64
[INFO]
[INFO]
[INFO] Building Apache HBase - Shaded - Server 3.0.0-SNAPSHOT
[INFO]
Downloading:
file:/Users/busbey/.m2/repository/org/apache/hbase/hbase-shaded-server/3.0.0-SNAPSHOT/src/site/resources/repo/org/glassfish/javax.el/3.0.1-b06-SNAPSHOT/javax.el-3.0.1-b06-SNAPSHOT.pom
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT is missing,
no dependency information available
Downloading:
file:/Users/busbey/.m2/repository/org/apache/hbase/hbase-shaded-server/3.0.0-SNAPSHOT/src/site/resources/repo/org/glassfish/javax.el/3.0.1-b07-SNAPSHOT/javax.el-3.0.1-b07-SNAPSHOT.pom
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b07-SNAPSHOT is missing,
no dependency information available
Downloading:
file:/Users/busbey/.m2/repository/org/apache/hbase/hbase-shaded-server/3.0.0-SNAPSHOT/src/site/resources/repo/org/glassfish/javax.el/3.0.1-b08-SNAPSHOT/javax.el-3.0.1-b08-SNAPSHOT.pom
[WARNING] The POM for org.glassfish:javax.el:jar:3.0.1-b08-SNAPSHOT is missing,
no dependency information available
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:tree (default-cli) @
hbase-shaded-server ---
[INFO] org.apache.hbase:hbase-shaded-server:jar:3.0.0-SNAPSHOT
[INFO] +- org.eclipse.jetty:jetty-server:jar:9.3.8.v20160314:compile
[INFO] +- javax.servlet:javax.servlet-api:jar:3.1.0:compile
[INFO] +- org.eclipse.jetty:jetty-http:jar:9.3.8.v20160314:compile
[jira] [Commented] (HBASE-18508) [HLC] Fix timing out tests in HBASE-14070.HLC branch
[
https://issues.apache.org/jira/browse/HBASE-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133995#comment-16133995
]
Hadoop QA commented on HBASE-18508:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
26s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
55s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
5s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} HBASE-14070.HLC passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 18s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}101m 50s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}155m 53s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestHRegionOnCluster |
| | hadoop.hbase.regionserver.TestStoreScanner |
| Timed out junit tests |
org.apache.hadoop.hbase.client.TestSnapshotCloneIndependence |
| | org.apache.hadoop.hbase.client.TestAsyncTableScanAll |
| | org.apache.hadoop.hbase.client.TestFromClientSide |
| | org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
| | org.apache.hadoop.hbase.client.TestAsyncTableBatch |
| | org.apache.hadoop.hbase.coprocessor.TestCoprocessorMetrics |
| | org.apache.hadoop.hbase.TestMultiVersions |
| | org.apache.hadoop.hbase.client.TestAsyncSnapshotAdminApi |
| | org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator |
| | org.apache.hadoop.hbase.client.TestAsyncRegionAdminApi |
| | org.apache.hadoop.hbase.client.TestAsyncTableScanMetrics |
| | org.apache.hadoop.hbase.TestZooKeeper |
| | org.apache.hadoop.hbase.constraint.TestConstraint |
| | org.apache.hadoop.hbase.client.TestScannersFromClientSide2 |
| | org.apache.hadoop.hbase.coprocessor.TestMasterObserver |
| | org.apache.hadoop.hbase.client.TestServerBusyException |
| | org.apache.hadoop.hbase.client.TestMetaWithReplicas |
| | org.apache.hadoop.hbase.coprocessor.TestWALObserver |
| | org.apache.hadoop.hbase.client.TestFromClientSide3 |
| | org.apache.hadoop.hbase.TestClusterBootOrder |
| | org.apache.hadoop.hbase.client.TestScannerTimeout |
| |
[jira] [Assigned] (HBASE-18615) hbase-rest tests fail in hbase-2.0.0-alpha2
[ https://issues.apache.org/jira/browse/HBASE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-18615: - Assignee: stack Release Note: Fix incomplete migration to jersey 2 that has a mix of clashing jersey1 and jersey2 invocations. Looking. It is a bit of a mess. Most tests pass. The JSON bindings are not working (the backup stuff is because the tests are launching yarn clusters to do work and they don't like not being able to find their jersey1 jars) > hbase-rest tests fail in hbase-2.0.0-alpha2 > --- > > Key: HBASE-18615 > URL: https://issues.apache.org/jira/browse/HBASE-18615 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Attachments: 18615.2.txt, 18615.txt, 18615.v3.txt, > HBASE-18615.branch-2.001.patch > > > Pointed out by Andrew on VOTE mail for hbase-2.0.0-alpha2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18632) TestMultiParallel#testFlushCommitsWithAbort fails in master branch
[
https://issues.apache.org/jira/browse/HBASE-18632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133990#comment-16133990
]
Hadoop QA commented on HBASE-18632:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
2s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 22s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 96m 25s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}145m 37s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestModifyTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestCreateTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestEnableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestDeleteTableProcedure |
| | org.apache.hadoop.hbase.master.TestGetLastFlushedSequenceId |
| | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
| | org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics |
| | org.apache.hadoop.hbase.namespace.TestNamespaceAuditor |
| | org.apache.hadoop.hbase.TestHBaseTestingUtility |
| | org.apache.hadoop.hbase.mapred.TestTableInputFormat |
| | org.apache.hadoop.hbase.TestMultiVersions |
| | org.apache.hadoop.hbase.quotas.TestQuotaStatusRPCs |
| | org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator |
| | org.apache.hadoop.hbase.security.access.TestAccessController2 |
| | org.apache.hadoop.hbase.mapred.TestTableMapReduceUtil |
| | org.apache.hadoop.hbase.client.TestAsyncRegionLocatorTimeout
