date:20180303

[jira] [Commented] (HBASE-19973) Implement a procedure to replay sync replication wal for standby cluster

2018-03-03 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385006#comment-16385006
 ] 

Hadoop QA commented on HBASE-19973:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
17s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
1s{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:brown} HBASE-19064 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
25s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
35s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
12s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
21s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
 8s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m  
2s{color} | {color:green} HBASE-19064 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
40s{color} | {color:green} HBASE-19064 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m 
11s{color} | {color:red} hbase-server: The patch generated 3 new + 359 
unchanged - 3 fixed = 362 total (was 362) {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} shadedjars {color} | {color:green}  4m 
45s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
18m 35s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}  
0m 59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  0m 
30s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}117m  0s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
42s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}167m 52s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAsyncTableBatch |
|   | hadoop.hbase.master.TestDLSFSHLog |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19973 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912905/HBASE-19973.HBASE-19064.004.patch
 |
| Optional Tests |  asflicense  cc  unit  hbaseprotoc  javac  javadoc

[jira] [Updated] (HBASE-20115) Reimplement serial replication based on the new replication storage layer

2018-03-03 Thread Duo Zhang (JIRA)


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

Duo Zhang updated HBASE-20115:
--
Attachment: HBASE-20115-v1.patch

> Reimplement serial replication based on the new replication storage layer
> -
>
> Key: HBASE-20115
> URL: https://issues.apache.org/jira/browse/HBASE-20115
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-20115-v1.patch, HBASE-20115.patch
>
>




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

[jira] [Resolved] (HBASE-13887) Document 0.98 release build differences

2018-03-03 Thread Sean Busbey (JIRA)


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

Sean Busbey resolved HBASE-13887.
-
Resolution: Won't Fix

0.98 is EOM

> Document 0.98 release build differences
> ---
>
> Key: HBASE-13887
> URL: https://issues.apache.org/jira/browse/HBASE-13887
> Project: HBase
>  Issue Type: Bug
>  Components: documentation, site
>Reporter: Andrew Purtell
>Priority: Major
>
> The build instructions in the online manual do not describe the extra steps 
> we need to take to build 0.98. Add a section on this.
> A quick enumeration of the differences:
> 1. Source assemblies will be missing the hbase-hadoop1-compat module. This 
> should be fixed in the POM somehow. What I do now is untar the src tarball, 
> cp -a the module over, then tar up the result. (It's a hack in a release 
> script.)
> 2. We must munge POMs for building hadoop1 and hadoop2 variants and then 
> execute two builds pointing Maven at each munged POM. The 
> generate-hadoop-X-poms script requires bash
> {noformat}
> $ bash dev-support/generate-hadoopX-poms.sh $version $version-hadoop1
> $ bash dev-support/generate-hadoopX-poms.sh $version $version-hadoop2
> {noformat}
> Build Hadoop 1
> {noformat}
>   $ mvn -f pom.xml.hadoop1 clean install -DskipTests -Prelease && \
>   mvn -f pom.xml.hadoop1 install -DskipTests site assembly:single \
> -Prelease && \
>   mvn -f pom.xml.hadoop1 deploy -DskipTests -Papache-release
>   $ cp hbase-assembly/target/hbase*-bin.tar.gz $release_dir
> {noformat}
> Build Hadoop 2
> {noformat}
>   $ mvn -f pom.xml.hadoop2 clean install -DskipTests -Prelease && \
>   mvn -f pom.xml.hadoop2 install -DskipTests site assembly:single \
> -Prelease && \
>   mvn -f pom.xml.hadoop2 deploy -DskipTests -Papache-release
>   $ cp hbase-assembly/target/hbase*-bin.tar.gz $release_dir
> {noformat}
> 3. Current HEAD of 0.98 branch enforces a requirement that the release be 
> built with a JDK no more recent than the compile language level. For 0.98, 
> that is 1.6, therefore the ancient 6u45 JDK. This JDK suffers from 
> [JDK-6521495|http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6521495] so 
> the following workaround is required in order to deploy artifacts to Apache's 
> Nexus:
> 3.a. Download https://www.bouncycastle.org/download/bcprov-jdk15on-152.jar 
> and https://www.bouncycastle.org/download/bcprov-ext-jdk15on-152.jar into 
> $JAVA_HOME/lib/ext.
> 3.b. Edit $JAVA_HOME/lib/security/java.security and add the BouncyCastle 
> provider as the first provider: 
> {noformat}
> security.provider.1=org.bouncycastle.jce.provider.BouncyCastleProvider
> {noformat}



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

[jira] [Resolved] (HBASE-15553) "publish hbase website" section is out of date

2018-03-03 Thread Sean Busbey (JIRA)


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

Sean Busbey resolved HBASE-15553.
-
Resolution: Duplicate

> "publish hbase website" section is out of date
> --
>
> Key: HBASE-15553
> URL: https://issues.apache.org/jira/browse/HBASE-15553
> Project: HBase
>  Issue Type: Bug
>  Components: documentation, website
>Reporter: Sean Busbey
>Priority: Major
>
> the current [ref guide section on publishing the 
> webste|http://hbase.apache.org/book.html#website_publish] refers to using hte 
> asf-site branch.
> it should reference the [hbase-site 
> repo|git-wip-us.apache.org/repos/asf/hbase-site.git] and the [jenkins 
> job|https://builds.apache.org/view/H-L/view/HBase/job/hbase_generate_website/]



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

[jira] [Commented] (HBASE-18827) Site build takes 1.5 hours; it looks like it is stuck...

2018-03-03 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-18827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384993#comment-16384993
 ] 

Sean Busbey commented on HBASE-18827:
-

I think maybe this has been fixed via HBASE-20070. I can consistently build the 
site in ~18 minutes following the invocations used in the website maintenance 
script (5-7 for an install and then 10-11 for running the site goal without 
compilation)

> Site build takes 1.5 hours; it looks like it is stuck...
> 
>
> Key: HBASE-18827
> URL: https://issues.apache.org/jira/browse/HBASE-18827
> Project: HBase
>  Issue Type: Bug
>  Components: site
>Reporter: stack
>Priority: Minor
>
> I'm trying to make a release. I'm in a tizzy as is usual around these times*. 
> 1.5 hours seems totally over-the-top. I think [~misty]'s lovely automation 
> has hidden this fact from us but needs digging on why we are taking so long. 
> The cycle seems to be provoked by hbase-archetypes module but I got 'mvn 
> log glaze disease' as soon as I tried digging in.
> Filing issue in case someone else wants to have a go at this before I. Also 
> filing if only to note that the thing does eventually finish in case I 
> forget
> * I go to build the doc/site and the build never seems to end. First there is 
> the issue HBASE-18821 where we were NPE'ing after a bunch of time had passed. 
> My fix for HBASE-18821 then got me further but after what seemed hours, it 
> failed with a cryptic message (Thanks [~Apache9] for figuring that I'd made 
> an incorrect fix over in HBASE-18821).  Next up I'm looking at a cycle that 
> never seems to end... only it eventually does after 90minutes.



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

[jira] [Commented] (HBASE-19625) Maven enforcer findings

2018-03-03 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384992#comment-16384992
 ] 

Sean Busbey commented on HBASE-19625:
-

For example, our current stable release line (1.2.z as of this writing) would 
be a good choice.

> Maven enforcer findings
> ---
>
> Key: HBASE-19625
> URL: https://issues.apache.org/jira/browse/HBASE-19625
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.1.12
>Reporter: Olaf Flebbe
>Priority: Major
>
> While compiling for centos-7 maven enforcer is triggered by several licenses:
> https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/COMPONENTS=hbase,OS=centos-7/ws/build/hbase/rpm/BUILD/hbase-1.1.12/hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE/*view*/
> Here are the diagnostics:
> {code}
> This product includes OkHttp licensed under the Apache 2.0.
> ERROR: Please check  this License for acceptability here:
> https://www.apache.org/legal/resolved
> If it is okay, then update the list named 'non_aggregate_fine' in the 
> LICENSE.vm file.
> If it isn't okay, then revert the change that added the dependency.
> More info on the dependency:
> com.squareup.okhttp
> okhttp
> 2.4.0
> maven central search
> g:com.squareup.okhttp AND a:okhttp AND v:2.4.0
> project website
> https://github.com/square/okhttp/okhttp
> project source
> https://github.com/square/okhttp/okhttp/
> --
> This product includes Okio licensed under the Apache 2.0.
> ERROR: Please check  this License for acceptability here:
> https://www.apache.org/legal/resolved
> If it is okay, then update the list named 'non_aggregate_fine' in the 
> LICENSE.vm file.
> If it isn't okay, then revert the change that added the dependency.
> More info on the dependency:
> com.squareup.okio
> okio
> 1.4.0
> maven central search
> g:com.squareup.okio AND a:okio AND v:1.4.0
> project website
> https://github.com/square/okio/okio
> project source
> https://github.com/square/okio/okio/
> ERROR: "Java Concurrency in Practice" book annotations dependency found 
> without license information!
> Please find the appropriate license and update supplemental-models.xml or
> revert the change that added this dependency.
> More info on the dependency:
> net.jcip
> jcip-annotations
> 1.0
> maven central search
> g:net.jcip AND a:jcip-annotations AND v:1.0
> project website
> http://jcip.net/
> project source
> ${dep.scm.url}
> {code}



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

[jira] [Commented] (HBASE-19625) Maven enforcer findings

2018-03-03 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384991#comment-16384991
 ] 

Sean Busbey commented on HBASE-19625:
-

HBase 1.1 is EOM. Can you reproduce this on a maintained version? Do y'all 
patch the source checkout?

> Maven enforcer findings
> ---
>
> Key: HBASE-19625
> URL: https://issues.apache.org/jira/browse/HBASE-19625
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.1.12
>Reporter: Olaf Flebbe
>Priority: Major
>
> While compiling for centos-7 maven enforcer is triggered by several licenses:
> https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/COMPONENTS=hbase,OS=centos-7/ws/build/hbase/rpm/BUILD/hbase-1.1.12/hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE/*view*/
> Here are the diagnostics:
> {code}
> This product includes OkHttp licensed under the Apache 2.0.
> ERROR: Please check  this License for acceptability here:
> https://www.apache.org/legal/resolved
> If it is okay, then update the list named 'non_aggregate_fine' in the 
> LICENSE.vm file.
> If it isn't okay, then revert the change that added the dependency.
> More info on the dependency:
> com.squareup.okhttp
> okhttp
> 2.4.0
> maven central search
> g:com.squareup.okhttp AND a:okhttp AND v:2.4.0
> project website
> https://github.com/square/okhttp/okhttp
> project source
> https://github.com/square/okhttp/okhttp/
> --
> This product includes Okio licensed under the Apache 2.0.
> ERROR: Please check  this License for acceptability here:
> https://www.apache.org/legal/resolved
> If it is okay, then update the list named 'non_aggregate_fine' in the 
> LICENSE.vm file.
> If it isn't okay, then revert the change that added the dependency.
> More info on the dependency:
> com.squareup.okio
> okio
> 1.4.0
> maven central search
> g:com.squareup.okio AND a:okio AND v:1.4.0
> project website
> https://github.com/square/okio/okio
> project source
> https://github.com/square/okio/okio/
> ERROR: "Java Concurrency in Practice" book annotations dependency found 
> without license information!
> Please find the appropriate license and update supplemental-models.xml or
> revert the change that added this dependency.
> More info on the dependency:
> net.jcip
> jcip-annotations
> 1.0
> maven central search
> g:net.jcip AND a:jcip-annotations AND v:1.0
> project website
> http://jcip.net/
> project source
> ${dep.scm.url}
> {code}



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

[jira] [Commented] (HBASE-20076) Maven site generation fails

2018-03-03 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384990#comment-16384990
 ] 

Sean Busbey commented on HBASE-20076:
-

I suspect this is now fixed thanks to HBASE-20070. just need to get a patch up 
that causes precommit to check mvnsite.

> Maven site generation fails
> ---
>
> Key: HBASE-20076
> URL: https://issues.apache.org/jira/browse/HBASE-20076
> Project: HBase
>  Issue Type: Bug
>  Components: documentation, website
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Priority: Critical
> Attachments: branch-mvnsite-root.txt
>
>
> precommit attempts at mvnsite fail with odd looking results:
> {code}
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:testCompile (default-testCompile) @ 
> hbase-it ---
> [INFO] Compiling 101 source files to 
> /testptch/hbase/hbase-it/target/test-classes
> [INFO] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/Action.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/Action.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/factories/MonkeyFactory.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/factories/MonkeyFactory.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/RESTApiClusterManager.java:[250,48]
>  cannot find symbol
>   symbol:   method readEntity(java.lang.Class)
>   location: variable response of type javax.ws.rs.core.Response
> [INFO] 1 error
> {code}
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> hbase-spark: failed to get report for 
> org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:testCompile 
> (default-testCompile) on project hbase-it: Compilation failure
> [ERROR] 
> /testptch/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/RESTApiClusterManager.java:[250,48]
>  cannot find symbol
> [ERROR]   symbol:   method readEntity(java.lang.Class)
> [ERROR]   location: variable response of type javax.ws.rs.core.Response
> [ERROR] 
> {code}
> this is at least true on master. haven't checked other branches



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

[jira] [Updated] (HBASE-15747) Fix illegal character in tablename in generated Maven site

2018-03-03 Thread Sean Busbey (JIRA)


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

Sean Busbey updated HBASE-15747:

Labels: beginner  (was: newbie)

> Fix illegal character in tablename in generated Maven site
> --
>
> Key: HBASE-15747
> URL: https://issues.apache.org/jira/browse/HBASE-15747
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Misty Stanley-Jones
>Priority: Trivial
>  Labels: beginner
>
> See 
> https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/37/artifact/link_report/warnX.html.



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

[jira] [Updated] (HBASE-20070) website generation is failing

2018-03-03 Thread Sean Busbey (JIRA)


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

Sean Busbey updated HBASE-20070:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

it probably only really needed to go to master, no harm in the website 
generation script working on branch-2 AFAIK.

as of build #1276 around 20 minutes ago, the website has successfully updated, 
so closing this out. thanks again everyone!

> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
>  Issue Type: Bug
>  Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-beta-2
>
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1, 
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch, 
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch, 
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch, 
> HBASE-20070.addendum.8.patch, 
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
>  is not yet mentioned in the hbase-site commit log. Assuming we don't have it 
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable 
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm 
> guessing the version of git changed on the build hosts and upended our 
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as 
> soon as that git command fails



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

[jira] [Comment Edited] (HBASE-20006) TestRestoreSnapshotFromClientWithRegionReplicas is flakey

2018-03-03 Thread Toshihiro Suzuki (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384979#comment-16384979
 ] 

Toshihiro Suzuki edited comment on HBASE-20006 at 3/4/18 6:10 AM:
--

I attached the v1 patch.

It seems like the problem occurs when taking a snapshot for a table some of 
whose regions has parent reference files, and when opening a replica region, 
HFileLink References aren't handled correctly.

I added the handle in the v1 patch.


was (Author: brfrn169):
I attached the v1 patch.

It seems like the problem occurs when taking a snapshot for a table some of 
whose regions has parent reference files, and when opening a replica region, a 
HFileLink References aren't handled correctly.

I added the handle in the v1 patch.

> TestRestoreSnapshotFromClientWithRegionReplicas is flakey
> -
>
> Key: HBASE-20006
> URL: https://issues.apache.org/jira/browse/HBASE-20006
> Project: HBase
>  Issue Type: Bug
>  Components: read replicas
>Reporter: stack
>Assignee: Toshihiro Suzuki
>Priority: Critical
> Attachments: HBASE-20006.branch-2.001.patch, 
> HBASE-20006.master.001.patch
>
>
> Failing 10% of the time. Interestingly, it is below that causes fail. We go 
> to split but it is already split. We will then fail the split with an 
> internal assert which messes up procedures; at a minimum we should just not 
> split (this is in the prepare stage).
> {code}
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> procedure.MasterProcedureScheduler(571): pid=105, 
> state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd, 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> assignment.SplitTableRegionProcedure(440): Split of {ENCODED => 
> 3f850cea7d71a7ebd019f2f009efca4d, NAME => 
> 'testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.',
>  STARTKEY => '', ENDKEY => '1'} skipped; state is already SPLIT
> 2018-02-15 23:21:42,163 ERROR [PEWorker-12] 
> procedure2.ProcedureExecutor(1480): CODE-BUG: Uncaught runtime exception: 
> pid=105, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd
> java.lang.AssertionError: split region should have an exception here
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:228)
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:89)
>   at 
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:180)
>   at 
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1455)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1224)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:78)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1734)
> {code}



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

[jira] [Commented] (HBASE-20006) TestRestoreSnapshotFromClientWithRegionReplicas is flakey

2018-03-03 Thread Toshihiro Suzuki (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384979#comment-16384979
 ] 

Toshihiro Suzuki commented on HBASE-20006:
--

I attached the v1 patch.

It seems like the problem occurs when taking a snapshot for a table some of 
whose regions has parent reference files, and when opening a replica region, a 
HFileLink References aren't handled correctly.

I added the handle in the v1 patch.

> TestRestoreSnapshotFromClientWithRegionReplicas is flakey
> -
>
> Key: HBASE-20006
> URL: https://issues.apache.org/jira/browse/HBASE-20006
> Project: HBase
>  Issue Type: Bug
>  Components: read replicas
>Reporter: stack
>Assignee: Toshihiro Suzuki
>Priority: Critical
> Attachments: HBASE-20006.branch-2.001.patch, 
> HBASE-20006.master.001.patch
>
>
> Failing 10% of the time. Interestingly, it is below that causes fail. We go 
> to split but it is already split. We will then fail the split with an 
> internal assert which messes up procedures; at a minimum we should just not 
> split (this is in the prepare stage).
> {code}
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> procedure.MasterProcedureScheduler(571): pid=105, 
> state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd, 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> assignment.SplitTableRegionProcedure(440): Split of {ENCODED => 
> 3f850cea7d71a7ebd019f2f009efca4d, NAME => 
> 'testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.',
>  STARTKEY => '', ENDKEY => '1'} skipped; state is already SPLIT
> 2018-02-15 23:21:42,163 ERROR [PEWorker-12] 
> procedure2.ProcedureExecutor(1480): CODE-BUG: Uncaught runtime exception: 
> pid=105, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd
> java.lang.AssertionError: split region should have an exception here
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:228)
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:89)
>   at 
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:180)
>   at 
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1455)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1224)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:78)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1734)
> {code}



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

[jira] [Updated] (HBASE-20006) TestRestoreSnapshotFromClientWithRegionReplicas is flakey

2018-03-03 Thread Toshihiro Suzuki (JIRA)


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

Toshihiro Suzuki updated HBASE-20006:
-
Status: Patch Available  (was: Open)

> TestRestoreSnapshotFromClientWithRegionReplicas is flakey
> -
>
> Key: HBASE-20006
> URL: https://issues.apache.org/jira/browse/HBASE-20006
> Project: HBase
>  Issue Type: Bug
>  Components: read replicas
>Reporter: stack
>Assignee: Toshihiro Suzuki
>Priority: Critical
> Attachments: HBASE-20006.branch-2.001.patch, 
> HBASE-20006.master.001.patch
>
>
> Failing 10% of the time. Interestingly, it is below that causes fail. We go 
> to split but it is already split. We will then fail the split with an 
> internal assert which messes up procedures; at a minimum we should just not 
> split (this is in the prepare stage).
> {code}
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> procedure.MasterProcedureScheduler(571): pid=105, 
> state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd, 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> assignment.SplitTableRegionProcedure(440): Split of {ENCODED => 
> 3f850cea7d71a7ebd019f2f009efca4d, NAME => 
> 'testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.',
>  STARTKEY => '', ENDKEY => '1'} skipped; state is already SPLIT
> 2018-02-15 23:21:42,163 ERROR [PEWorker-12] 
> procedure2.ProcedureExecutor(1480): CODE-BUG: Uncaught runtime exception: 
> pid=105, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd
> java.lang.AssertionError: split region should have an exception here
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:228)
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:89)
>   at 
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:180)
>   at 
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1455)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1224)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:78)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1734)
> {code}



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

[jira] [Updated] (HBASE-20006) TestRestoreSnapshotFromClientWithRegionReplicas is flakey

2018-03-03 Thread Toshihiro Suzuki (JIRA)


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

Toshihiro Suzuki updated HBASE-20006:
-
Attachment: HBASE-20006.master.001.patch

> TestRestoreSnapshotFromClientWithRegionReplicas is flakey
> -
>
> Key: HBASE-20006
> URL: https://issues.apache.org/jira/browse/HBASE-20006
> Project: HBase
>  Issue Type: Bug
>  Components: read replicas
>Reporter: stack
>Assignee: Toshihiro Suzuki
>Priority: Critical
> Attachments: HBASE-20006.branch-2.001.patch, 
> HBASE-20006.master.001.patch
>
>
> Failing 10% of the time. Interestingly, it is below that causes fail. We go 
> to split but it is already split. We will then fail the split with an 
> internal assert which messes up procedures; at a minimum we should just not 
> split (this is in the prepare stage).
> {code}
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> procedure.MasterProcedureScheduler(571): pid=105, 
> state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd, 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.
> 2018-02-15 23:21:42,162 INFO  [PEWorker-12] 
> assignment.SplitTableRegionProcedure(440): Split of {ENCODED => 
> 3f850cea7d71a7ebd019f2f009efca4d, NAME => 
> 'testOnlineSnapshotAfterSplittingRegions-1518736887838,,1518736887882.3f850cea7d71a7ebd019f2f009efca4d.',
>  STARTKEY => '', ENDKEY => '1'} skipped; state is already SPLIT
> 2018-02-15 23:21:42,163 ERROR [PEWorker-12] 
> procedure2.ProcedureExecutor(1480): CODE-BUG: Uncaught runtime exception: 
> pid=105, state=RUNNABLE:SPLIT_TABLE_REGION_PREPARE; SplitTableRegionProcedure 
> table=testOnlineSnapshotAfterSplittingRegions-1518736887838, 
> parent=3f850cea7d71a7ebd019f2f009efca4d, 
> daughterA=06b5e6366efbef155d70e56cfdf58dc9, 
> daughterB=8c175de1b33765a5683ac1e502edb0bd
> java.lang.AssertionError: split region should have an exception here
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:228)
>   at 
> org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.executeFromState(SplitTableRegionProcedure.java:89)
>   at 
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:180)
>   at 
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1455)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1224)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:78)
>   at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1734)
> {code}



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

[jira] [Updated] (HBASE-19973) Implement a procedure to replay sync replication wal for standby cluster

2018-03-03 Thread Guanghao Zhang (JIRA)


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

Guanghao Zhang updated HBASE-19973:
---
Attachment: HBASE-19973.HBASE-19064.004.patch

> Implement a procedure to replay sync replication wal for standby cluster
> 
>
> Key: HBASE-19973
> URL: https://issues.apache.org/jira/browse/HBASE-19973
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>Priority: Major
> Attachments: HBASE-19973.HBASE-19064.001.patch, 
> HBASE-19973.HBASE-19064.002.patch, HBASE-19973.HBASE-19064.003.patch, 
> HBASE-19973.HBASE-19064.004.patch
>
>




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

[jira] [Comment Edited] (HBASE-20070) website generation is failing

2018-03-03 Thread Appy (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384947#comment-16384947
 ] 

Appy edited comment on HBASE-20070 at 3/4/18 3:34 AM:
--

+1 on addendum

Pushed to master to branch-2, is that alright?


was (Author: appy):
+1 on addendum

> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
>  Issue Type: Bug
>  Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-beta-2
>
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1, 
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch, 
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch, 
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch, 
> HBASE-20070.addendum.8.patch, 
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
>  is not yet mentioned in the hbase-site commit log. Assuming we don't have it 
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable 
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm 
> guessing the version of git changed on the build hosts and upended our 
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as 
> soon as that git command fails



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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-03 Thread Appy (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384947#comment-16384947
 ] 

Appy commented on HBASE-20070:
--

+1 on addendum

> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
>  Issue Type: Bug
>  Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-beta-2
>
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1, 
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch, 
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch, 
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch, 
> HBASE-20070.addendum.8.patch, 
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
>  is not yet mentioned in the hbase-site commit log. Assuming we don't have it 
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable 
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm 
> guessing the version of git changed on the build hosts and upended our 
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as 
> soon as that git command fails



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

[jira] [Created] (HBASE-20124) Make hbase-spark module work with hadoop3

2018-03-03 Thread Ted Yu (JIRA)

Ted Yu created HBASE-20124:
--

 Summary: Make hbase-spark module work with hadoop3
 Key: HBASE-20124
 URL: https://issues.apache.org/jira/browse/HBASE-20124
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu


The following error can be observed when running tests in hbase-spark module 
against hadoop3:
{code}
HBaseDStreamFunctionsSuite:
*** RUN ABORTED ***
  java.lang.NoClassDefFoundError: org/apache/hadoop/ipc/ExternalCall
  at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getStorageDirs(FSNamesystem.java:1464)
  at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNamespaceDirs(FSNamesystem.java:1444)
  at 
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:939)
  at 
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:815)
  at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:746)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:668)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:640)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:979)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:859)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:853)
  ...
  Cause: java.lang.ClassNotFoundException: org.apache.hadoop.ipc.ExternalCall
  at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
  at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getStorageDirs(FSNamesystem.java:1464)
  at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getNamespaceDirs(FSNamesystem.java:1444)
  at 
org.apache.hadoop.hdfs.MiniDFSCluster.createNameNodesAndSetConf(MiniDFSCluster.java:939)
  at 
org.apache.hadoop.hdfs.MiniDFSCluster.initMiniDFSCluster(MiniDFSCluster.java:815)
  at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:746)
  at 
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:668)
{code}
The dependency tree shows mixture of hadoop 2.7.4 and hadoop3 for the 
hbase-spark module.

This should be addressed by adding proper profile in pom.xml



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

[jira] [Commented] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0

2018-03-03 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384917#comment-16384917
 ] 

Ted Yu commented on HBASE-16179:


[~mdrob]:
Mind taking a look ?

Thanks

> 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: 3.0.0
>
> Attachments: 16179.v0.txt, 16179.v1.txt, 16179.v1.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.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.v29.txt, 
> 16179.v4.txt, 16179.v5.txt, 16179.v7.txt, 16179.v8.txt, 16179.v9.txt, 
> HBASE-16179.v29.patch
>
>
> 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0

2018-03-03 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384913#comment-16384913
 ] 

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 
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue}  0m  
3s{color} | {color:blue} The patch file was not named according to hbase's 
naming conventions. Please see 
https://yetus.apache.org/documentation/0.7.0/precommit-patchnames for 
instructions. {color} |
|| || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 10m 
 8s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green}  0m 
57s{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  
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
42s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
18m 33s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} scaladoc {color} | {color:red}  0m 
31s{color} | {color:red} hbase-spark in the patch failed. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  4m  
5s{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
10s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 40m 20s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-16179 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912897/16179.v29.txt |
| Optional Tests |  asflicense  javac  javadoc  unit  shadedjars  hadoopcheck  
xml  compile  scalac  scaladoc  |
| uname | Linux c1e2eec3a368 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9 
14:43:09 UTC 2018 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 / ff550edabf |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| scaladoc | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11791/artifact/patchprocess/patch-scaladoc-hbase-spark.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11791/testReport/ |
| Max. process+thread count | 913 (vs. ulimit of 1) |
| modules | C: hbase-spark U: hbase-spark |
| Console

[jira] [Commented] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0

2018-03-03 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384899#comment-16384899
 ] 

Ted Yu commented on HBASE-16179:


Patch v29 is rebased onto current master branch.

> 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: 3.0.0
>
> Attachments: 16179.v0.txt, 16179.v1.txt, 16179.v1.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.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.v29.txt, 
> 16179.v4.txt, 16179.v5.txt, 16179.v7.txt, 16179.v8.txt, 16179.v9.txt, 
> HBASE-16179.v29.patch
>
>
> 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
(v7.6.3#76005)

[jira] [Updated] (HBASE-16179) Fix compilation errors when building hbase-spark against Spark 2.0

2018-03-03 Thread Ted Yu (JIRA)


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

Ted Yu updated HBASE-16179:
---
Attachment: 16179.v29.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: 3.0.0
>
> Attachments: 16179.v0.txt, 16179.v1.txt, 16179.v1.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.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.v29.txt, 
> 16179.v4.txt, 16179.v5.txt, 16179.v7.txt, 16179.v8.txt, 16179.v9.txt, 
> HBASE-16179.v29.patch
>
>
> 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-20122) Up timeout on nightlies to 9 hours from 8 on branch-2 and master

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384853#comment-16384853
 ] 

Hudson commented on HBASE-20122:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4684 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4684/])
HBASE-20122 Up timeout on nightlies to 9 hours from 8 on branch-2 and (stack: 
rev 2b1b2c849051b6ba033988fccd74a2285bd1f474)
* (edit) dev-support/Jenkinsfile


> Up timeout on nightlies to 9 hours from 8 on branch-2 and master
> 
>
> Key: HBASE-20122
> URL: https://issues.apache.org/jira/browse/HBASE-20122
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: stack
>Assignee: stack
>Priority: Major
>
> I know its ridiculous and we need to profile the test run to cut down the 
> time taken, but for now am going to up the timeout from 8 to 9 hours Last 
> night tests failed because they took > 8 hours: 
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Looks like they'd 
> even made through all the unit testing and were just doing findbugs and 
> tarball making 



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

[jira] [Commented] (HBASE-19114) Split out o.a.h.h.zookeeper from hbase-server and hbase-client

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384854#comment-16384854
 ] 

Hudson commented on HBASE-19114:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4684 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4684/])
HBASE-19114 addendum. Split out o.a.h.h.zookeeper from hbase-server and (appy: 
rev ff550edabff1ba78b392f6e0eeb805aa3170b335)
* (edit) bin/get-active-master.rb
* (edit) bin/draining_servers.rb


> Split out o.a.h.h.zookeeper from hbase-server and hbase-client
> --
>
> Key: HBASE-19114
> URL: https://issues.apache.org/jira/browse/HBASE-19114
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
>Priority: Major
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19114.master.001.patch, 
> HBASE-19114.master.002.patch, HBASE-19114.master.003.patch, 
> HBASE-19114.master.004.patch, HBASE-19114.master.005.patch, 
> HBASE-19114.master.006.patch, HBASE-19114.master.007.patch, 
> HBASE-19114.master.008.patch, HBASE-19114_addendum.patch
>
>
> Changes so far:
> - Moved DrainingServerTracker and RegionServerTracker to 
> hbase-server:o.a.h.h.master.
> - Moved SplitOrMergeTracker to oahh.master (because it depends on a PB)
> - Moving hbase-client:oahh.zookeeper.*  to hbase-zookeeper module.  After 
> [~Apache9]'s cleanup (HBASE-19200), hbase-client doesn't need them anymore 
> (except 3 classes).
> - Renamed some classes to use a consistent naming for classes - ZK instead of 
> mix of ZK, Zk , ZooKeeper. Couldn't rename following public classes: 
> MiniZooKeeperCluster, ZooKeeperConnectionException. Left RecoverableZooKeeper 
> for lack of better name. (suggestions?)
> - Sadly, can't move tests out because they depend on HBaseTestingUtility 
> (which defeats part of the purpose - trimming down hbase-server tests. We 
> need to promote more use of mocks in our tests)



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

[jira] [Created] (HBASE-20123) Backup test fails against hadoop 3

2018-03-03 Thread Ted Yu (JIRA)

Ted Yu created HBASE-20123:
--

 Summary: Backup test fails against hadoop 3
 Key: HBASE-20123
 URL: https://issues.apache.org/jira/browse/HBASE-20123
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu


When running backup unit test against hadoop3, I saw:
{code}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 88.862 
s <<< FAILURE! - in org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes
[ERROR] 
testBackupMultipleDeletes(org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes)
  Time elapsed: 86.206 s  <<< ERROR!
java.io.IOException: java.io.IOException: Failed copy from 
hdfs://localhost:40578/backupUT/.tmp/backup_1520088356047 to 
hdfs://localhost:40578/backupUT
  at 
org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes.testBackupMultipleDeletes(TestBackupMultipleDeletes.java:82)
Caused by: java.io.IOException: Failed copy from 
hdfs://localhost:40578/backupUT/.tmp/backup_1520088356047 to 
hdfs://localhost:40578/backupUT
  at 
org.apache.hadoop.hbase.backup.TestBackupMultipleDeletes.testBackupMultipleDeletes(TestBackupMultipleDeletes.java:82)
{code}
In the test output, I found:
{code}
2018-03-03 14:46:10,858 ERROR [Time-limited test] 
mapreduce.MapReduceBackupCopyJob$BackupDistCp(237): java.io.IOException: Path 
hdfs://localhost:40578/backupUT/.tmp/backup_1520088356047 is not a symbolic link
java.io.IOException: Path 
hdfs://localhost:40578/backupUT/.tmp/backup_1520088356047 is not a symbolic link
  at org.apache.hadoop.fs.FileStatus.getSymlink(FileStatus.java:338)
  at org.apache.hadoop.fs.FileStatus.readFields(FileStatus.java:461)
  at 
org.apache.hadoop.tools.CopyListingFileStatus.readFields(CopyListingFileStatus.java:155)
  at 
org.apache.hadoop.io.SequenceFile$Reader.getCurrentValue(SequenceFile.java:2308)
  at 
org.apache.hadoop.tools.CopyListing.validateFinalListing(CopyListing.java:163)
  at org.apache.hadoop.tools.CopyListing.buildListing(CopyListing.java:91)
  at 
org.apache.hadoop.tools.GlobbedCopyListing.doBuildListing(GlobbedCopyListing.java:90)
  at org.apache.hadoop.tools.CopyListing.buildListing(CopyListing.java:84)
  at org.apache.hadoop.tools.DistCp.createInputFileListing(DistCp.java:382)
  at 
org.apache.hadoop.hbase.backup.mapreduce.MapReduceBackupCopyJob$BackupDistCp.createInputFileListing(MapReduceBackupCopyJob.java:297)
  at org.apache.hadoop.tools.DistCp.createAndSubmitJob(DistCp.java:181)
  at org.apache.hadoop.tools.DistCp.execute(DistCp.java:153)
  at 
org.apache.hadoop.hbase.backup.mapreduce.MapReduceBackupCopyJob$BackupDistCp.execute(MapReduceBackupCopyJob.java:196)
  at org.apache.hadoop.tools.DistCp.run(DistCp.java:126)
  at 
org.apache.hadoop.hbase.backup.mapreduce.MapReduceBackupCopyJob.copy(MapReduceBackupCopyJob.java:408)
  at 
org.apache.hadoop.hbase.backup.impl.IncrementalTableBackupClient.incrementalCopyHFiles(IncrementalTableBackupClient.java:348)
  at 
org.apache.hadoop.hbase.backup.impl.IncrementalTableBackupClient.execute(IncrementalTableBackupClient.java:290)
  at 
org.apache.hadoop.hbase.backup.impl.BackupAdminImpl.backupTables(BackupAdminImpl.java:605)
{code}
It seems the failure was related to how we use distcp.



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

[jira] [Commented] (HBASE-20115) Reimplement serial replication based on the new replication storage layer

2018-03-03 Thread Hadoop QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384717#comment-16384717
 ] 

Hadoop QA commented on HBASE-20115:
---

| (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:brown} Prechecks {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 4 new or modified test 
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
21s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
 2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
48s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  3m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
3s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
13s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
20s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
31s{color} | {color:red} hbase-client: The patch generated 2 new + 146 
unchanged - 2 fixed = 148 total (was 148) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  1m 
10s{color} | {color:red} hbase-server: The patch generated 4 new + 221 
unchanged - 22 fixed = 225 total (was 243) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 1s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
42s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
18m 27s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  1m  
2s{color} | {color:red} hbase-client generated 1 new + 0 unchanged - 0 fixed = 
1 total (was 0) {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red}  0m 
20s{color} | {color:red} hbase-client generated 2 new + 2 unchanged - 0 fixed = 
4 total (was 2) {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
16s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
57s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}104m  3s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  1m 
 0s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}159m 51s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-client |
|  |  "." or "|" used for regular expression in 
org.apache.hadoop.hbase.MetaTableAccessor.getReplicationBarrierResult(Result)  
At MetaTableAccessor.java:regular expression in 
org.apache.hadoop.hbase.MetaTableAccessor.getReplicationBarrierResult(Result)  
At

[jira] [Resolved] (HBASE-19114) Split out o.a.h.h.zookeeper from hbase-server and hbase-client

2018-03-03 Thread Appy (JIRA)


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

Appy resolved HBASE-19114.
--
Resolution: Fixed

> Split out o.a.h.h.zookeeper from hbase-server and hbase-client
> --
>
> Key: HBASE-19114
> URL: https://issues.apache.org/jira/browse/HBASE-19114
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
>Priority: Major
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19114.master.001.patch, 
> HBASE-19114.master.002.patch, HBASE-19114.master.003.patch, 
> HBASE-19114.master.004.patch, HBASE-19114.master.005.patch, 
> HBASE-19114.master.006.patch, HBASE-19114.master.007.patch, 
> HBASE-19114.master.008.patch, HBASE-19114_addendum.patch
>
>
> Changes so far:
> - Moved DrainingServerTracker and RegionServerTracker to 
> hbase-server:o.a.h.h.master.
> - Moved SplitOrMergeTracker to oahh.master (because it depends on a PB)
> - Moving hbase-client:oahh.zookeeper.*  to hbase-zookeeper module.  After 
> [~Apache9]'s cleanup (HBASE-19200), hbase-client doesn't need them anymore 
> (except 3 classes).
> - Renamed some classes to use a consistent naming for classes - ZK instead of 
> mix of ZK, Zk , ZooKeeper. Couldn't rename following public classes: 
> MiniZooKeeperCluster, ZooKeeperConnectionException. Left RecoverableZooKeeper 
> for lack of better name. (suggestions?)
> - Sadly, can't move tests out because they depend on HBaseTestingUtility 
> (which defeats part of the purpose - trimming down hbase-server tests. We 
> need to promote more use of mocks in our tests)



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

[jira] [Resolved] (HBASE-20122) Up timeout on nightlies to 9 hours from 8 on branch-2 and master

2018-03-03 Thread stack (JIRA)


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

stack resolved HBASE-20122.
---
Resolution: Fixed
  Assignee: stack

I pushed the below...


commit 2b1b2c849051b6ba033988fccd74a2285bd1f474
Author: Michael Stack 
Date:   Sat Mar 3 07:33:25 2018 -0800

HBASE-20122 Up timeout on nightlies to 9 hours from 8 on branch-2 and
master

diff --git a/dev-support/Jenkinsfile b/dev-support/Jenkinsfile
index fa7c8ba6cd..f74ab91e5d 100644
--- a/dev-support/Jenkinsfile
+++ b/dev-support/Jenkinsfile
@@ -21,7 +21,7 @@ pipeline {
   }
   options {
 buildDiscarder(logRotator(numToKeepStr: '30'))
-timeout (time: 8, unit: 'HOURS')
+timeout (time: 9, unit: 'HOURS')
 timestamps()
 skipDefaultCheckout()
   }

> Up timeout on nightlies to 9 hours from 8 on branch-2 and master
> 
>
> Key: HBASE-20122
> URL: https://issues.apache.org/jira/browse/HBASE-20122
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: stack
>Assignee: stack
>Priority: Major
>
> I know its ridiculous and we need to profile the test run to cut down the 
> time taken, but for now am going to up the timeout from 8 to 9 hours Last 
> night tests failed because they took > 8 hours: 
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Looks like they'd 
> even made through all the unit testing and were just doing findbugs and 
> tarball making 



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

[jira] [Commented] (HBASE-19985) Redundant instanceof check in ProtobufUtil#getServiceException

2018-03-03 Thread Appy (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384696#comment-16384696
 ] 

Appy commented on HBASE-19985:
--

Sorry for late reply, was traveling in a 15hr flight.

I'd recommend using {{dev-support/submit-patch.py}} tool instead, since it also 
does the work of uploading the patch to Jira and creating review board (unless 
specified not to). Have a look at it's help (--help).

That tool will need that base branch is set for the current branch, so run 
{{git branch --set-upstream-to=apache/branch-1.4}} before running the tool, 
then it should work.

If you have any further issues, please let me know, happy to help.

> Redundant instanceof check in ProtobufUtil#getServiceException
> --
>
> Key: HBASE-19985
> URL: https://issues.apache.org/jira/browse/HBASE-19985
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.4.1
>Reporter: Ted Yu
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 1.5.0, 1.4.3
>
> Attachments: HBASE-19985.branch-1.v01.patch, HBASE-19985.v01.patch
>
>
> {code}
>   public static IOException getServiceException(ServiceException e) {
> Throwable t = e;
> if (e instanceof ServiceException) {
>   t = e.getCause();
> {code}
> The instanceof check would always return true.
> This was reported by 
> https://builds.apache.org/job/PreCommit-HBASE-Build/11495/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html#Warnings_STYLE



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

[jira] [Updated] (HBASE-20122) Up timeout on nightlies to 9 hours from 8 on branch-2 and master

2018-03-03 Thread stack (JIRA)


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

stack updated HBASE-20122:
--
Description: I know its ridiculous and we need to profile the test run to 
cut down the time taken, but for now am going to up the timeout from 8 to 9 
hours Last night tests failed because they took > 8 hours: 
https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Looks like they'd 
even made through all the unit testing and were just doing findbugs and tarball 
making   (was: I know its ridiculous and we need to profile the test run to 
cut down the time taken, but for now am going to up the timeout from 8 to 9 
hours Last night tests failed because they took > 8 hours: 
https://builds.apache.org/job/HBase%20Nightly/job/branch-2/)

> Up timeout on nightlies to 9 hours from 8 on branch-2 and master
> 
>
> Key: HBASE-20122
> URL: https://issues.apache.org/jira/browse/HBASE-20122
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: stack
>Priority: Major
>
> I know its ridiculous and we need to profile the test run to cut down the 
> time taken, but for now am going to up the timeout from 8 to 9 hours Last 
> night tests failed because they took > 8 hours: 
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Looks like they'd 
> even made through all the unit testing and were just doing findbugs and 
> tarball making 



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

[jira] [Created] (HBASE-20122) Up timeout on nightlies to 9 hours from 8 on branch-2 and master

2018-03-03 Thread stack (JIRA)

stack created HBASE-20122:
-

 Summary: Up timeout on nightlies to 9 hours from 8 on branch-2 and 
master
 Key: HBASE-20122
 URL: https://issues.apache.org/jira/browse/HBASE-20122
 Project: HBase
  Issue Type: Task
  Components: build
Reporter: stack


I know its ridiculous and we need to profile the test run to cut down the time 
taken, but for now am going to up the timeout from 8 to 9 hours Last night 
tests failed because they took > 8 hours: 
https://builds.apache.org/job/HBase%20Nightly/job/branch-2/



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

[jira] [Commented] (HBASE-19114) Split out o.a.h.h.zookeeper from hbase-server and hbase-client

2018-03-03 Thread Appy (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384681#comment-16384681
 ] 

Appy commented on HBASE-19114:
--

Sorry on my part for missing out those ones.

Thanks for the followup [~cskrabak]. Let me commit this to master and all the 
way back to branch-2.

> Split out o.a.h.h.zookeeper from hbase-server and hbase-client
> --
>
> Key: HBASE-19114
> URL: https://issues.apache.org/jira/browse/HBASE-19114
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Appy
>Assignee: Appy
>Priority: Major
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19114.master.001.patch, 
> HBASE-19114.master.002.patch, HBASE-19114.master.003.patch, 
> HBASE-19114.master.004.patch, HBASE-19114.master.005.patch, 
> HBASE-19114.master.006.patch, HBASE-19114.master.007.patch, 
> HBASE-19114.master.008.patch, HBASE-19114_addendum.patch
>
>
> Changes so far:
> - Moved DrainingServerTracker and RegionServerTracker to 
> hbase-server:o.a.h.h.master.
> - Moved SplitOrMergeTracker to oahh.master (because it depends on a PB)
> - Moving hbase-client:oahh.zookeeper.*  to hbase-zookeeper module.  After 
> [~Apache9]'s cleanup (HBASE-19200), hbase-client doesn't need them anymore 
> (except 3 classes).
> - Renamed some classes to use a consistent naming for classes - ZK instead of 
> mix of ZK, Zk , ZooKeeper. Couldn't rename following public classes: 
> MiniZooKeeperCluster, ZooKeeperConnectionException. Left RecoverableZooKeeper 
> for lack of better name. (suggestions?)
> - Sadly, can't move tests out because they depend on HBaseTestingUtility 
> (which defeats part of the purpose - trimming down hbase-server tests. We 
> need to promote more use of mocks in our tests)



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

[jira] [Created] (HBASE-20121) Fix findbugs warning for RestoreTablesClient

2018-03-03 Thread Ted Yu (JIRA)

Ted Yu created HBASE-20121:
--

 Summary: Fix findbugs warning for RestoreTablesClient
 Key: HBASE-20121
 URL: https://issues.apache.org/jira/browse/HBASE-20121
 Project: HBase
  Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Ted Yu


In RestoreTablesClient#restore(), the following variable is not used:
{code}
Set backupIdSet = new HashSet<>();
{code}
There is backupIdSet#add() call later in the method but the variable doesn't 
appear in any other part of the code.



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

[jira] [Commented] (HBASE-20115) Reimplement serial replication based on the new replication storage layer

2018-03-03 Thread Duo Zhang (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384671#comment-16384671
 ] 

Duo Zhang commented on HBASE-20115:
---

Review board link:

https://reviews.apache.org/r/65892/

> Reimplement serial replication based on the new replication storage layer
> -
>
> Key: HBASE-20115
> URL: https://issues.apache.org/jira/browse/HBASE-20115
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-20115.patch
>
>




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

[jira] [Updated] (HBASE-20115) Reimplement serial replication based on the new replication storage layer

2018-03-03 Thread Duo Zhang (JIRA)


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

Duo Zhang updated HBASE-20115:
--
Assignee: Duo Zhang
  Status: Patch Available  (was: Open)

An initial version. Still need to add tests for split and merge.

And I plan to add more tests in another issue. Now we have a separated 
SerialReplicationChecker class. So it is possible to add tests for it directly 
to test more corner cases.

> Reimplement serial replication based on the new replication storage layer
> -
>
> Key: HBASE-20115
> URL: https://issues.apache.org/jira/browse/HBASE-20115
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Attachments: HBASE-20115.patch
>
>




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

[jira] [Updated] (HBASE-20115) Reimplement serial replication based on the new replication storage layer

2018-03-03 Thread Duo Zhang (JIRA)


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

Duo Zhang updated HBASE-20115:
--
Attachment: HBASE-20115.patch

> Reimplement serial replication based on the new replication storage layer
> -
>
> Key: HBASE-20115
> URL: https://issues.apache.org/jira/browse/HBASE-20115
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Duo Zhang
>Priority: Major
> Attachments: HBASE-20115.patch
>
>




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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384648#comment-16384648
 ] 

Hudson commented on HBASE-20070:


Results for branch master, done in 4 hr 0 min and counting
[build #248 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/248/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
>  Issue Type: Bug
>  Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-beta-2
>
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1, 
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch, 
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch, 
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch, 
> HBASE-20070.addendum.8.patch, 
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
>  is not yet mentioned in the hbase-site commit log. Assuming we don't have it 
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable 
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm 
> guessing the version of git changed on the build hosts and upended our 
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as 
> soon as that git command fails



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

[jira] [Commented] (HBASE-19437) Batch operation can't handle the null result for Append/Increment

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384649#comment-16384649
 ] 

Hudson commented on HBASE-19437:


Results for branch master, done in 4 hr 0 min and counting
[build #248 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/248/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Batch operation can't handle the null result for Append/Increment
> -
>
> Key: HBASE-19437
> URL: https://issues.apache.org/jira/browse/HBASE-19437
> Project: HBase
>  Issue Type: Bug
>  Components: Usability
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-19437.v0.patch, HBASE-19437.v0.patch, 
> HBASE-19437.v1.patch
>
>
> But the Table#append and #increment can handle the null result...that is an 
> inconsistent behavior for user.
> I have noticed two scenarios that server will return null result to user.
> # postAppend/postIncrement return null
> # mutation.isReturnResults() is false and 
> preIncrementAfterRowLock/preAppendAfterRowLock doesn't return null
> We should wrap the null to empty result on server side. CP user should throw 
> Exception rather than return null if they intend to say something is broken.



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

[jira] [Commented] (HBASE-20114) Fix IllegalFormatConversionException in rsgroup.jsp

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384650#comment-16384650
 ] 

Hudson commented on HBASE-20114:


Results for branch master, done in 4 hr 0 min and counting
[build #248 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/248/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Fix IllegalFormatConversionException in rsgroup.jsp
> ---
>
> Key: HBASE-20114
> URL: https://issues.apache.org/jira/browse/HBASE-20114
> Project: HBase
>  Issue Type: Bug
>  Components: UI
>Affects Versions: 3.0.0, 2.0.0-beta-2
>Reporter: Xiaolin Ha
>Assignee: Xiaolin Ha
>Priority: Major
> Attachments: HBASE-20114.branch-2.001.patch
>
>
> IllegalFormatConversionException at
> {code:java}
> String.format("%.0f", sl.getRequestCountPerSecond()) 
> {code}



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

[jira] [Commented] (HBASE-20120) Remove some unused classes/ java files from hbase-server

2018-03-03 Thread Chia-Ping Tsai (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384623#comment-16384623
 ] 

Chia-Ping Tsai commented on HBASE-20120:


WALEntryFilters is annotated as LimitedPrivate so it should be fine to break it 
in 2.0 I guess

> Remove some unused classes/ java files from hbase-server
> 
>
> Key: HBASE-20120
> URL: https://issues.apache.org/jira/browse/HBASE-20120
> Project: HBase
>  Issue Type: Improvement
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: hbase-20120.master.001.patch
>
>
> Following classes/ Java files are not used, can be removed:
> hbase-server/src/main/java/org/apache/hadoop/hbase/util/ProtoUtil.java
> hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSMapRUtils.java
> hbase-server/src/main/java/org/apache/hadoop/hbase/replication/BaseWALEntryFilter.java
> hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/NoOpHeapMemoryTuner.java
>  



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

[jira] [Updated] (HBASE-19985) Redundant instanceof check in ProtobufUtil#getServiceException

2018-03-03 Thread Ted Yu (JIRA)


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

Ted Yu updated HBASE-19985:
---
  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Thanks for the patch, Artem.
Thanks for the review, Chia-ping

> Redundant instanceof check in ProtobufUtil#getServiceException
> --
>
> Key: HBASE-19985
> URL: https://issues.apache.org/jira/browse/HBASE-19985
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.4.1
>Reporter: Ted Yu
>Assignee: Artem Ervits
>Priority: Trivial
> Fix For: 1.5.0, 1.4.3
>
> Attachments: HBASE-19985.branch-1.v01.patch, HBASE-19985.v01.patch
>
>
> {code}
>   public static IOException getServiceException(ServiceException e) {
> Throwable t = e;
> if (e instanceof ServiceException) {
>   t = e.getCause();
> {code}
> The instanceof check would always return true.
> This was reported by 
> https://builds.apache.org/job/PreCommit-HBASE-Build/11495/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html#Warnings_STYLE



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

[jira] [Commented] (HBASE-20109) Add Admin#getMaster API to branch-1

2018-03-03 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16384587#comment-16384587
 ] 

Hudson commented on HBASE-20109:


Results for branch branch-1, done in 2 hr 11 min and counting
[build #237 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/237/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(x) {color:red}-1 source release artifact{color}
-- See build output for details.


> Add Admin#getMaster API to branch-1
> ---
>
> Key: HBASE-20109
> URL: https://issues.apache.org/jira/browse/HBASE-20109
> Project: HBase
>  Issue Type: Improvement
>  Components: Client
>Affects Versions: 1.4.2
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 1.5.0
>
> Attachments: HBASE-20109-branch-1.patch, HBASE-20109-branch-1.patch
>
>
> Right now the only public API available in branch-1 to the client to learn 
> the server name of the active master is Admin#getClusterStatus#getMaster, 
> returning ServerName. On a cluster of any size getClusterStatus is expensive, 
> especially if used only to retrieve the active master name. 
> Later versions have
> {code}
> ServerName Admin#getMaster()
> {code}
> for lightweight discovery of the active master location. Add this to branch-1.



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

42 matches

Mail list logo