[jira] [Updated] (HBASE-19007) Align Services Interfaces in Master and RegionServer

2017-10-19 Thread stack (JIRA)

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

stack updated HBASE-19007:
--
Attachment: HBASE-19007.master.009.patch

> Align Services Interfaces in Master and RegionServer
> 
>
> Key: HBASE-19007
> URL: https://issues.apache.org/jira/browse/HBASE-19007
> Project: HBase
>  Issue Type: Task
>Reporter: stack
>Assignee: stack
>Priority: Blocker
>  Labels: coprocessor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19007.master.001.patch, 
> HBASE-19007.master.002.patch, HBASE-19007.master.003.patch, 
> HBASE-19007.master.004.patch, HBASE-19007.master.005.patch, 
> HBASE-19007.master.006.patch, HBASE-19007.master.007.patch, 
> HBASE-19007.master.008.patch, HBASE-19007.master.009.patch
>
>
> HBASE-18183 adds a CoprocessorRegionServerService to give a view on 
> RegionServiceServices that is safe to expose to Coprocessors.
> On the Master-side, MasterServices becomes an Interface for exposing to 
> Coprocessors.
> We need to align the two.
> For background, see 
> https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820
>  



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


SUCCESS: Integrated in Jenkins build HBase-1.4 #957 (See 
[https://builds.apache.org/job/HBase-1.4/957/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
11dfb6753c7cafe4ecd818d96a2e1b71b3fcc5f6)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


SUCCESS: Integrated in Jenkins build HBase-1.4 #957 (See 
[https://builds.apache.org/job/HBase-1.4/957/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
11dfb6753c7cafe4ecd818d96a2e1b71b3fcc5f6)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


SUCCESS: Integrated in Jenkins build HBase-1.5 #102 (See 
[https://builds.apache.org/job/HBase-1.5/102/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
78014fdcc0e51a6c6fefbecdc8287f568c82dabb)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


SUCCESS: Integrated in Jenkins build HBase-1.5 #102 (See 
[https://builds.apache.org/job/HBase-1.5/102/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
78014fdcc0e51a6c6fefbecdc8287f568c82dabb)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2010 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/2010/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
f99d9146d2a616b0d101c25d4a53126ed509ceee)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2010 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/2010/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
f99d9146d2a616b0d101c25d4a53126ed509ceee)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-18873) Hide protobufs in GlobalQuotaSettings

2017-10-19 Thread Anoop Sam John (JIRA)

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

Anoop Sam John commented on HBASE-18873:


I think this make sense. 
I can see some private marked methods in Public exposed QuotaSettings. (Not 
this patch)..Any way we can avoid this way?  Just like the way we have 
GlobalQuotaSettings and GlobalQuotaSettingsImpl way now?  Just asking. It would 
have been better if we dont have such APIs in Public class. Fine even if there.
computeQuotaSettings should be called as getQuotaSettings? It is doing a 
conversion but that is any way internal impl detail.

Else I believe this approach is fine.

> Hide protobufs in GlobalQuotaSettings
> -
>
> Key: HBASE-18873
> URL: https://issues.apache.org/jira/browse/HBASE-18873
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18873.001.branch-2.patch, 
> HBASE-18873.002.branch-2.patch
>
>
> HBASE-18807 cleaned up direct protobuf use in the Coprocessor APIs for 
> quota-related functions. However, one new POJO introduced to hide these 
> protocol buffers still exposes PBs via some methods.
> We should try to hide those as well.



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


[jira] [Commented] (HBASE-17934) Backport HBASE-17779 "disable_table_replication returns misleading message and does not turn off replication" to branch-1.3

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-17934:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 20m 
55s{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}  1m 
24s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
58s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
53s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
59s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
44s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
11s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
56s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
57s{color} | {color:green} branch-1.3 passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
27s{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} shadedjars {color} | {color:green}  2m 
28s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
26m 24s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3. 
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  3m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  1m 
41s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 33m 51s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
39s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}109m 12s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | 
org.apache.hadoop.hbase.master.balancer.TestRegionLocationFinder |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:899bf27 |
| JIRA Issue | HBASE-17934 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893163/17934.branch-1.3.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux fcce5179ad4f 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26 
18:04:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 

[jira] [Updated] (HBASE-19043) Purge TableWrapper and CoprocessorHConnnection

2017-10-19 Thread stack (JIRA)

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

stack updated HBASE-19043:
--
Attachment: HBASE-19043.master.006.patch

> Purge TableWrapper and CoprocessorHConnnection
> --
>
> Key: HBASE-19043
> URL: https://issues.apache.org/jira/browse/HBASE-19043
> Project: HBase
>  Issue Type: Task
>  Components: Coprocessors
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19043.master.001.patch, 
> HBASE-19043.master.002.patch, HBASE-19043.master.003.patch, 
> HBASE-19043.master.004.patch, HBASE-19043.master.005.patch, 
> HBASE-19043.master.006.patch
>
>
> Repeating note from dev list today which had assent from [~apurtell] and 
> [~appy]:
> {code}
> Subject: [DISCUSS] Punt the Coprocessor TableWrapper and 
> CoprocessorHConnection?
> To: HBase Dev List 
> tl;dr I believe the original intent for TableWrapper and
> CoprocessorHConnection can now be gotten elsewhere so we should purge these
> classes.
> In base CoprocessorEnvironment, there are methods to return a Table
> instance. There are none to return an Admin. In our code base, the only
> user is the AccessController. Phoenix uses it twice in its Indexer
> implementation.
> When you call CE#getTable, the default implementation in
> BaseEnvironemnt calls HTableWrapper.createWrapper which takes a
> BaseEnvironment List in which we keep all Table instances. On shutdown of
> the coprocessor, the list is iterated and all tables are closed.
> Going via TableWrapper, the class comment says:
> * A wrapper for HTable. Can be used to restrict privilege.
> *
> * Currently it just helps to track tables opened by a Coprocessor and
> * facilitate close of them if it is aborted.
> *
> * We also disallow row locking.
> *
> * There is nothing now that will stop a coprocessor from using HTable
> * objects directly instead of this API, but in the future we intend to
> * analyze coprocessor implementations as they are loaded and reject those
> * which attempt to use objects and methods outside the Environment
> * sandbox.
> TableWrapper by my reading delegates all calls to a Table instance with no
> interception (there is not rowlocking to override anymore). On open, we do
> ensure the Table is up on a CoprocessorHConnection which does the following:
> * Connection to an HTable from within a Coprocessor. We can do some
> nice tricks since we know we
> * are on a regionserver, for instance skipping the full
> serialization/deserialization of objects
> * when talking to the server.
> The above 'trick' is now commonplace in servers as the Master and
> RegionServer always make Connections that will short-circuit if an
> opportunity.
> As I read TableWrapper and CoprocessorHConnection, they were written at
> another time when Table construction was heavyweight and Table#close was
> not expected of clients and before the introduction of the general
> Server-side short-circuit Connection facility.
> Unless objection, I think we should purge them.
> Writing here in case I'm missing some key facility they provide.
> {code}
> See 
> http://search-hadoop.com/m/HBase/YGbb8uCtg26VkBy?subj=+DISCUSS+Punt+the+Coprocessor+TableWrapper+and+CoprocessorHConnection+
> This issue is about removing these classes.



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


[jira] [Created] (HBASE-19056) TestCompactionInDeadRegionServer is top of the flakies charts!

2017-10-19 Thread stack (JIRA)
stack created HBASE-19056:
-

 Summary:  TestCompactionInDeadRegionServer is top of the flakies 
charts!
 Key: HBASE-19056
 URL: https://issues.apache.org/jira/browse/HBASE-19056
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: stack


The test came in recently as part of HBASE-17712 "Remove/Simplify the logic of 
RegionScannerImpl.handleFileNotFound"

[~Apache9] when you have a chance, help me out. I was going to just remove the 
test since it made no sense to me but then I saw you wrote it  (smile).

When the region.compact(true); is called on the end, what is supposed to be 
going on?

When I trace, the compact is not done because the Region is not writeEnabled 
(we check if Region is writeEnabled down in Store before we go ahead and 
compact). So, I thought the problem was that the region reference was stale 
because it came from the rsToSuspend which had just been killed.

After a while, I figured that you intend the region reference to be stale so 
you can try an append AFTER the WAL has been taken over by WAL splitter.

But the writeEnabled flag is set so compactions don't run. I tried unsetting 
this flag and closed flags and but compaction won't run.

Was this your intent sir? If so, I'll work w/ it np. Just looking for clarity. 
Thanks. 



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Attachment: HBASE-19014.branch-1.v0.patch

retry for branch-1. If no objections, i will commit it after QA.

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Status: Patch Available  (was: Open)

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Status: Open  (was: Patch Available)

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Commented] (HBASE-10367) RegionServer graceful stop / decommissioning

2017-10-19 Thread Anoop Sam John (JIRA)

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

Anoop Sam John commented on HBASE-10367:


Sorry did not check this patch any time.. Just seeing the Release notes.
What abt the Access control mechanism for the new APIs?  When AC is present, we 
will check?
bq.void recommissionRegionServer(ServerName server, List 
encodedRegionNames)
The mentioned regions will get moved to this server eventually.  What if 
previous decommission did not remove the regions from that server. Still more 
regions will come in?  Sorry for asking late

> RegionServer graceful stop / decommissioning
> 
>
> Key: HBASE-10367
> URL: https://issues.apache.org/jira/browse/HBASE-10367
> Project: HBase
>  Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Jerry He
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: HBASE-10367-master-2.patch, HBASE-10367-master.patch, 
> HBASE-10367-master.patch
>
>
> Right now, we have a weird way of node decommissioning / graceful stop, which 
> is a graceful_stop.sh bash script, and a region_mover ruby script, and some 
> draining server support which you have to manually write to a znode 
> (really!). Also draining servers is only partially supported in LB operations 
> (LB does take that into account for roundRobin assignment, but not for normal 
> balance) 
> See 
> http://hbase.apache.org/book/node.management.html and HBASE-3071
> I think we should support graceful stop as a first class citizen. Thinking 
> about it, it seems that the difference between regionserver stop and graceful 
> stop is that regionserver stop will close the regions, but the master will 
> only assign them after the znode is deleted. 
> In the new master design (or even before), if we allow RS to be able to close 
> regions on its own (without master initiating it), then graceful stop becomes 
> regular stop. The RS already closes the regions cleanly, and will reject new 
> region assignments, so that we don't need much of the balancer or draining 
> server trickery. 
> This ties into the new master/AM redesign (HBASE-5487), but still deserves 
> it's own jira. Let's use this to brainstorm on the design. 



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


[jira] [Resolved] (HBASE-17369) Add ACL to the new region server drain related API

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He resolved HBASE-17369.
--
Resolution: Implemented

Implemented as part of HBASE-10367.

> Add ACL to the new region server drain related API
> --
>
> Key: HBASE-17369
> URL: https://issues.apache.org/jira/browse/HBASE-17369
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 2.0.0
>Reporter: Jerry He
>Priority: Critical
>
> Add ACL to the new region server drain related API.



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


[jira] [Updated] (HBASE-10367) RegionServer graceful stop / decommissioning

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He updated HBASE-10367:
-
   Resolution: Fixed
Fix Version/s: (was: 2.0.0-beta-1)
   2.0.0-alpha-4
   3.0.0
   Status: Resolved  (was: Patch Available)

Committed to branch-2 and master.  Thanks for the review, [~stack]

> RegionServer graceful stop / decommissioning
> 
>
> Key: HBASE-10367
> URL: https://issues.apache.org/jira/browse/HBASE-10367
> Project: HBase
>  Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Jerry He
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: HBASE-10367-master-2.patch, HBASE-10367-master.patch, 
> HBASE-10367-master.patch
>
>
> Right now, we have a weird way of node decommissioning / graceful stop, which 
> is a graceful_stop.sh bash script, and a region_mover ruby script, and some 
> draining server support which you have to manually write to a znode 
> (really!). Also draining servers is only partially supported in LB operations 
> (LB does take that into account for roundRobin assignment, but not for normal 
> balance) 
> See 
> http://hbase.apache.org/book/node.management.html and HBASE-3071
> I think we should support graceful stop as a first class citizen. Thinking 
> about it, it seems that the difference between regionserver stop and graceful 
> stop is that regionserver stop will close the regions, but the master will 
> only assign them after the znode is deleted. 
> In the new master design (or even before), if we allow RS to be able to close 
> regions on its own (without master initiating it), then graceful stop becomes 
> regular stop. The RS already closes the regions cleanly, and will reject new 
> region assignments, so that we don't need much of the balancer or draining 
> server trickery. 
> This ties into the new master/AM redesign (HBASE-5487), but still deserves 
> it's own jira. Let's use this to brainstorm on the design. 



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1926 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1926/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
f99d9146d2a616b0d101c25d4a53126ed509ceee)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19014:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
11s{color} | {color:blue} Docker mode activated. {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:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 11m 
19s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
43s{color} | {color:green} the patch passed {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} 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}  3m 
26s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
33m 20s{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}  2m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}163m 
17s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
25s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}221m 26s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19014 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893153/HBASE-19014.v0.patch |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  xml  compile  
|
| uname | Linux 77b6369e1b95 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 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 / af479c5 |
| Default Java | 1.8.0_141 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9250/testReport/ |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9250/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.v0.patch, 

[jira] [Updated] (HBASE-10367) RegionServer graceful stop / decommissioning

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He updated HBASE-10367:
-
Hadoop Flags: Reviewed
Release Note: 
Added three top level Admin APIs to help decommissioning and graceful stop of 
region servers.

{code}
  /**
   * Mark region server(s) as decommissioned to prevent additional regions from 
getting
   * assigned to them. Optionally unload the regions on the servers. If there 
are multiple servers
   * to be decommissioned, decommissioning them at the same time can prevent 
wasteful region
   * movements. Region unloading is asynchronous.
   * @param servers The list of servers to decommission.
   * @param offload True to offload the regions from the decommissioned servers
   */
  void decommissionRegionServers(List servers, boolean offload) 
throws IOException;

  /**
   * List region servers marked as decommissioned, which can not be assigned 
regions.
   * @return List of decommissioned region servers.
   */
  List listDecommissionedRegionServers() throws IOException;

  /**
   * Remove decommission marker from a region server to allow regions 
assignments.
   * Load regions onto the server if a list of regions is given. Region loading 
is
   * asynchronous.
   * @param server The server to recommission.
   * @param encodedRegionNames Regions to load onto the server.
   */
  void recommissionRegionServer(ServerName server, List 
encodedRegionNames)
  throws IOException;
{code}



> RegionServer graceful stop / decommissioning
> 
>
> Key: HBASE-10367
> URL: https://issues.apache.org/jira/browse/HBASE-10367
> Project: HBase
>  Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Jerry He
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-10367-master-2.patch, HBASE-10367-master.patch, 
> HBASE-10367-master.patch
>
>
> Right now, we have a weird way of node decommissioning / graceful stop, which 
> is a graceful_stop.sh bash script, and a region_mover ruby script, and some 
> draining server support which you have to manually write to a znode 
> (really!). Also draining servers is only partially supported in LB operations 
> (LB does take that into account for roundRobin assignment, but not for normal 
> balance) 
> See 
> http://hbase.apache.org/book/node.management.html and HBASE-3071
> I think we should support graceful stop as a first class citizen. Thinking 
> about it, it seems that the difference between regionserver stop and graceful 
> stop is that regionserver stop will close the regions, but the master will 
> only assign them after the znode is deleted. 
> In the new master design (or even before), if we allow RS to be able to close 
> regions on its own (without master initiating it), then graceful stop becomes 
> regular stop. The RS already closes the regions cleanly, and will reject new 
> region assignments, so that we don't need much of the balancer or draining 
> server trickery. 
> This ties into the new master/AM redesign (HBASE-5487), but still deserves 
> it's own jira. Let's use this to brainstorm on the design. 



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


[jira] [Updated] (HBASE-10367) RegionServer graceful stop / decommissioning

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He updated HBASE-10367:
-
Release Note: 
Added three top level Admin APIs to help decommissioning and graceful stop of 
region servers.

  /**
   * Mark region server(s) as decommissioned to prevent additional regions from 
getting
   * assigned to them. Optionally unload the regions on the servers. If there 
are multiple servers
   * to be decommissioned, decommissioning them at the same time can prevent 
wasteful region
   * movements. Region unloading is asynchronous.
   * @param servers The list of servers to decommission.
   * @param offload True to offload the regions from the decommissioned servers
   */
  void decommissionRegionServers(List servers, boolean offload) 
throws IOException;

  /**
   * List region servers marked as decommissioned, which can not be assigned 
regions.
   * @return List of decommissioned region servers.
   */
  List listDecommissionedRegionServers() throws IOException;

  /**
   * Remove decommission marker from a region server to allow regions 
assignments.
   * Load regions onto the server if a list of regions is given. Region loading 
is
   * asynchronous.
   * @param server The server to recommission.
   * @param encodedRegionNames Regions to load onto the server.
   */
  void recommissionRegionServer(ServerName server, List 
encodedRegionNames)  throws IOException;



  was:
Added three top level Admin APIs to help decommissioning and graceful stop of 
region servers.

  /**
   * Mark region server(s) as decommissioned to prevent additional regions from 
getting
   * assigned to them. Optionally unload the regions on the servers. If there 
are multiple servers
   * to be decommissioned, decommissioning them at the same time can prevent 
wasteful region
   * movements. Region unloading is asynchronous.
   * @param servers The list of servers to decommission.
   * @param offload True to offload the regions from the decommissioned servers
   */
  void decommissionRegionServers(List servers, boolean offload) 
throws IOException;

  /**
   * List region servers marked as decommissioned, which can not be assigned 
regions.
   * @return List of decommissioned region servers.
   */
  List listDecommissionedRegionServers() throws 
 IOException;

  /**
   * Remove decommission marker from a region server to allow regions 
assignments.
   * Load regions onto the server if a list of regions is given. Region loading 
is
   * asynchronous.
   * @param server The server to recommission.
   * @param encodedRegionNames Regions to load onto the server.
   */
  void recommissionRegionServer(ServerName server, List 
encodedRegionNames)  throws IOException;




> RegionServer graceful stop / decommissioning
> 
>
> Key: HBASE-10367
> URL: https://issues.apache.org/jira/browse/HBASE-10367
> Project: HBase
>  Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Jerry He
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-10367-master-2.patch, HBASE-10367-master.patch, 
> HBASE-10367-master.patch
>
>
> Right now, we have a weird way of node decommissioning / graceful stop, which 
> is a graceful_stop.sh bash script, and a region_mover ruby script, and some 
> draining server support which you have to manually write to a znode 
> (really!). Also draining servers is only partially supported in LB operations 
> (LB does take that into account for roundRobin assignment, but not for normal 
> balance) 
> See 
> http://hbase.apache.org/book/node.management.html and HBASE-3071
> I think we should support graceful stop as a first class citizen. Thinking 
> about it, it seems that the difference between regionserver stop and graceful 
> stop is that regionserver stop will close the regions, but the master will 
> only assign them after the znode is deleted. 
> In the new master design (or even before), if we allow RS to be able to close 
> regions on its own (without master initiating it), then graceful stop becomes 
> regular stop. The RS already closes the regions cleanly, and will reject new 
> region assignments, so that we don't need much of the balancer or draining 
> server trickery. 
> This ties into the new master/AM redesign (HBASE-5487), but still deserves 
> it's own jira. Let's use this to brainstorm on the design. 



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


[jira] [Updated] (HBASE-10367) RegionServer graceful stop / decommissioning

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He updated HBASE-10367:
-
Release Note: 
Added three top level Admin APIs to help decommissioning and graceful stop of 
region servers.

  /**
   * Mark region server(s) as decommissioned to prevent additional regions from 
getting
   * assigned to them. Optionally unload the regions on the servers. If there 
are multiple servers
   * to be decommissioned, decommissioning them at the same time can prevent 
wasteful region
   * movements. Region unloading is asynchronous.
   * @param servers The list of servers to decommission.
   * @param offload True to offload the regions from the decommissioned servers
   */
  void decommissionRegionServers(List servers, boolean offload) 
throws IOException;

  /**
   * List region servers marked as decommissioned, which can not be assigned 
regions.
   * @return List of decommissioned region servers.
   */
  List listDecommissionedRegionServers() throws 
 IOException;

  /**
   * Remove decommission marker from a region server to allow regions 
assignments.
   * Load regions onto the server if a list of regions is given. Region loading 
is
   * asynchronous.
   * @param server The server to recommission.
   * @param encodedRegionNames Regions to load onto the server.
   */
  void recommissionRegionServer(ServerName server, List 
encodedRegionNames)  throws IOException;



  was:
Added three top level Admin APIs to help decommissioning and graceful stop of 
region servers.

{code}
  /**
   * Mark region server(s) as decommissioned to prevent additional regions from 
getting
   * assigned to them. Optionally unload the regions on the servers. If there 
are multiple servers
   * to be decommissioned, decommissioning them at the same time can prevent 
wasteful region
   * movements. Region unloading is asynchronous.
   * @param servers The list of servers to decommission.
   * @param offload True to offload the regions from the decommissioned servers
   */
  void decommissionRegionServers(List servers, boolean offload) 
throws IOException;

  /**
   * List region servers marked as decommissioned, which can not be assigned 
regions.
   * @return List of decommissioned region servers.
   */
  List listDecommissionedRegionServers() throws IOException;

  /**
   * Remove decommission marker from a region server to allow regions 
assignments.
   * Load regions onto the server if a list of regions is given. Region loading 
is
   * asynchronous.
   * @param server The server to recommission.
   * @param encodedRegionNames Regions to load onto the server.
   */
  void recommissionRegionServer(ServerName server, List 
encodedRegionNames)
  throws IOException;
{code}




> RegionServer graceful stop / decommissioning
> 
>
> Key: HBASE-10367
> URL: https://issues.apache.org/jira/browse/HBASE-10367
> Project: HBase
>  Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Jerry He
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-10367-master-2.patch, HBASE-10367-master.patch, 
> HBASE-10367-master.patch
>
>
> Right now, we have a weird way of node decommissioning / graceful stop, which 
> is a graceful_stop.sh bash script, and a region_mover ruby script, and some 
> draining server support which you have to manually write to a znode 
> (really!). Also draining servers is only partially supported in LB operations 
> (LB does take that into account for roundRobin assignment, but not for normal 
> balance) 
> See 
> http://hbase.apache.org/book/node.management.html and HBASE-3071
> I think we should support graceful stop as a first class citizen. Thinking 
> about it, it seems that the difference between regionserver stop and graceful 
> stop is that regionserver stop will close the regions, but the master will 
> only assign them after the znode is deleted. 
> In the new master design (or even before), if we allow RS to be able to close 
> regions on its own (without master initiating it), then graceful stop becomes 
> regular stop. The RS already closes the regions cleanly, and will reject new 
> region assignments, so that we don't need much of the balancer or draining 
> server trickery. 
> This ties into the new master/AM redesign (HBASE-5487), but still deserves 
> it's own jira. Let's use this to brainstorm on the design. 



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


[jira] [Commented] (HBASE-16338) update jackson to 2.y

2017-10-19 Thread Sean Busbey (JIRA)

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

Sean Busbey commented on HBASE-16338:
-

this is looking excellent! I'm running through some local checks here, should 
have review feedback in the morning.

> update jackson to 2.y
> -
>
> Key: HBASE-16338
> URL: https://issues.apache.org/jira/browse/HBASE-16338
> Project: HBase
>  Issue Type: Task
>  Components: dependencies
>Reporter: Sean Busbey
>Assignee: Mike Drob
> Fix For: 2.0.0-beta-2
>
> Attachments: 16338.txt, HBASE-16338.v10.patch, HBASE-16338.v11.patch, 
> HBASE-16338.v2.patch, HBASE-16338.v3.patch, HBASE-16338.v5.patch, 
> HBASE-16338.v6.patch, HBASE-16338.v7.patch, HBASE-16338.v8.patch, 
> HBASE-16338.v9.patch
>
>
> Our jackson dependency is from ~3 years ago. Update to the jackson 2.y line, 
> using 2.7.0+.



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


[jira] [Commented] (HBASE-19049) Update kerby to 1.0.0 GA release

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai commented on HBASE-19049:


Why not updating to 1.0.1 used by hadoop 3.0.0-beta1? Not familiar with the 
tempo of how we update the hadoop three version.

> Update kerby to 1.0.0 GA release
> 
>
> Key: HBASE-19049
> URL: https://issues.apache.org/jira/browse/HBASE-19049
> Project: HBase
>  Issue Type: Task
>  Components: dependencies
>Affects Versions: 2.0.0-alpha-3
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19049.0.patch
>
>
> Hadoop 3.0.0-alpha4+ has moved to kerby 1.0.0 GA, so our tests that use their 
> minikdc fail with a version mismatch because we still declare 1.0.0-RC2



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


[jira] [Commented] (HBASE-19010) Reimplement getMasterInfoPort for Admin

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19010:
---

| (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: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:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
49s{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 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
55s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
35s{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} shadedjars {color} | {color:green}  3m 
48s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
33m 44s{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} hbaseprotoc {color} | {color:green}  
1m 15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  6m  
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  0m 
29s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
27s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 22m 48s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
27s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 92m  7s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestClientClusterStatus |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19010 |
| JIRA Patch URL | 

[jira] [Commented] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18950:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
12s{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 9 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
59s{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 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
0s{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}  3m 
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
46s{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} shadedjars {color} | {color:green}  3m 
53s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
38m 46s{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 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
38s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 20m 48s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
23s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
25s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 95m  5s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestHBaseAdminNoCluster |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-18950 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893156/HBASE-18950.master.005.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 0ef189665105 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 
12:48:20 UTC 2017 x86_64 x86_64 

[jira] [Updated] (HBASE-19029) Align RPC timout methods in Table and AsyncTableBase

2017-10-19 Thread Peter Somogyi (JIRA)

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

Peter Somogyi updated HBASE-19029:
--
Attachment: HBASE-19029.master.003.patch

> Align RPC timout methods in Table and AsyncTableBase
> 
>
> Key: HBASE-19029
> URL: https://issues.apache.org/jira/browse/HBASE-19029
> Project: HBase
>  Issue Type: Sub-task
>  Components: asyncclient, Client
>Affects Versions: 2.0.0-alpha-3
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19029.master.001.patch, 
> HBASE-19029.master.002.patch, HBASE-19029.master.002.patch, 
> HBASE-19029.master.003.patch, HBASE-19029.master.003.patch, 
> HBASE-19029.master.003.patch
>
>
> Table and AsyncTableBase have similar RPC timeout methods but the async 
> version supports TimeUtils to be passed.
> To align these 2 interfaces lets depricate the existing methods in Table and 
> add the ones that are currently in AsyncTableBase.
> These methods are the following:
> * long getRpcTimeout(TimeUnit unit)
> * long getReadRpcTimeout(TimeUnit unit)
> * long getWriteRpcTimeout(TimeUnit unit)
> * long getOperationTimeout(TimeUnit unit)
> We do not have {{long getScanTimeout(TimeUnit unit)}} since scan is handled 
> differently. 



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


[jira] [Commented] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18950:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
10s{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 9 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
28s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
38s{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 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
52s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
34s{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}  1m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
41s{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} shadedjars {color} | {color:green}  3m 
53s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
39m 36s{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}  4m 
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
46s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 24m  4s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
51s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
28s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 98m 56s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestHBaseAdminNoCluster |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-18950 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893156/HBASE-18950.master.005.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 1f5762a19181 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 
12:18:55 UTC 2017 x86_64 x86_64 

[jira] [Commented] (HBASE-19010) Reimplement getMasterInfoPort for Admin

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19010:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
10s{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:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
45s{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 
53s{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}  3m 
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green}  1m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
38s{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} shadedjars {color} | {color:green}  3m 
51s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
39m  8s{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} hbaseprotoc {color} | {color:green}  
1m 11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  5m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  0m 
31s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
37s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 22m 19s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
26s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 96m 53s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestClientClusterStatus |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19010 |
| JIRA Patch URL | 

[jira] [Commented] (HBASE-19029) Align RPC timout methods in Table and AsyncTableBase

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19029:
---

| (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 1 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
35s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
 3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
 2s{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 
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
12s{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}  3m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
48s{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} shadedjars {color} | {color:green}  3m 
54s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
38m 10s{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 
48s{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 
30s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 78m 46s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  5m 
39s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  1m 
42s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}157m 26s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | org.apache.hadoop.hbase.regionserver.TestRowTooBig |
|   | org.apache.hadoop.hbase.regionserver.TestSplitLogWorker |
|   | org.apache.hadoop.hbase.client.TestSnapshotCloneIndependence |
|   | org.apache.hadoop.hbase.coprocessor.TestHTableWrapper |
|   | org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy 
|
|   | org.apache.hadoop.hbase.regionserver.wal.TestFSHLog |
|   | org.apache.hadoop.hbase.regionserver.TestCompaction |
|   | org.apache.hadoop.hbase.master.TestGetLastFlushedSequenceId |
|   | 

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #312 (See 
[https://builds.apache.org/job/HBase-1.3-JDK7/312/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
899bf279c7ec2b13157ceceaa2e7e63daa8926f9)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #244 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/244/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
7175cfdf86e29f669a553d5d368d21c2ce7d28a1)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #244 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/244/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
7175cfdf86e29f669a553d5d368d21c2ce7d28a1)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #312 (See 
[https://builds.apache.org/job/HBase-1.3-JDK7/312/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
899bf279c7ec2b13157ceceaa2e7e63daa8926f9)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #241 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/241/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
7175cfdf86e29f669a553d5d368d21c2ce7d28a1)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Updated] (HBASE-18989) Polish the compaction related CP hooks

2017-10-19 Thread Duo Zhang (JIRA)

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

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

Address the comments on rb.

> Polish the compaction related CP hooks
> --
>
> Key: HBASE-18989
> URL: https://issues.apache.org/jira/browse/HBASE-18989
> Project: HBase
>  Issue Type: Sub-task
>  Components: Compaction, Coprocessors
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18989-v1.patch, HBASE-18989.patch, 
> HBASE-18989.patch, HBASE-18989.patch
>
>




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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #327 (See 
[https://builds.apache.org/job/HBase-1.3-JDK8/327/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
899bf279c7ec2b13157ceceaa2e7e63daa8926f9)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


SUCCESS: Integrated in Jenkins build HBase-1.2-IT #978 (See 
[https://builds.apache.org/job/HBase-1.2-IT/978/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
7175cfdf86e29f669a553d5d368d21c2ce7d28a1)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19055:


SUCCESS: Integrated in Jenkins build HBase-1.2-IT #978 (See 
[https://builds.apache.org/job/HBase-1.2-IT/978/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
7175cfdf86e29f669a553d5d368d21c2ce7d28a1)
* (edit) dev-support/docker/Dockerfile


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Resolved] (HBASE-18249) Explicitly mark failed small test(s)

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu resolved HBASE-18249.

Resolution: Later

> Explicitly mark failed small test(s)
> 
>
> Key: HBASE-18249
> URL: https://issues.apache.org/jira/browse/HBASE-18249
> Project: HBase
>  Issue Type: Test
>Reporter: Ted Yu
>
> In some cases, I would remind contributor to re-attach patch if failure of 
> small test(s) prevented medium / large tests from running.
> HBASE-18167 was a recent example where TestSimpleRpcScheduler failed.
> We should explicitly mark failed small test(s) so that people know a big 
> portion of unit tests haven't been run.
> This would reduce potential test failure in Jenkins builds if committer 
> doesn't pay attention (that failed test was small test).



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3918 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3918/])
HBASE-19042 Oracle Java 8u144 downloader broken in precommit check (mdrob: rev 
af479c580c24a78b34052dc4ad16dacd3dd988cd)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 

[jira] [Commented] (HBASE-18383) Upgrade cyrus SASL library to 2.1.27

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu commented on HBASE-18383:


https://www.cyrusimap.org/sasl/sasl/release-notes/2.1/index.html#new-in-2-1-27

> Upgrade cyrus SASL library to 2.1.27
> 
>
> Key: HBASE-18383
> URL: https://issues.apache.org/jira/browse/HBASE-18383
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Ted Yu
>
> On cyrus mailing list, Ken Murchison indicated 2.1.27 would be released in 
> August.
> We should upgrade to the new release - 2.1.26 was several years old.



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


[jira] [Updated] (HBASE-17934) Backport HBASE-17779 "disable_table_replication returns misleading message and does not turn off replication" to branch-1.3

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-17934:
---
Attachment: 17934.branch-1.3.patch

Rerun QA.

> Backport HBASE-17779 "disable_table_replication returns misleading message 
> and does not turn off replication" to branch-1.3
> ---
>
> Key: HBASE-17934
> URL: https://issues.apache.org/jira/browse/HBASE-17934
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Janos Gub
> Fix For: 1.3.2
>
> Attachments: 17934.branch-1.3.patch, 17934.branch-1.3.patch, 
> HBASE-17934.patch
>
>
> Currently HBaseAdmin#isTableRepEnabled() returns false if ANY of the columns 
> families is not replicated.
> Because of this if you have a table where replication is partially enabled, 
> calling disable_table_replication will not have any effect, but will report 
> that replication for a given table is disabled.
> Workaround is enabling table replication before disabling.
> As a solution quoted from HBASE-17460:
> Admin#disableTableReplication() returns nothing and isTableRepEnabled() 
> returns boolean. For master branch, we can let isTableRepEnabled() return 
> enum (partially disabled, disabled, etc) This way, 
> Admin#disableTableReplication() can return meaningful value to the user.
> This issue is to backport the fix to branch-1.3



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


SUCCESS: Integrated in Jenkins build HBase-1.3-IT #241 (See 
[https://builds.apache.org/job/HBase-1.3-IT/241/])
HBASE-19055 Backport HBASE-19042 to other active branches (zhangduo: rev 
899bf279c7ec2b13157ceceaa2e7e63daa8926f9)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Updated] (HBASE-19052) FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-19052:
---
Attachment: 19052.branch-1.txt

> FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x
> 
>
> Key: HBASE-19052
> URL: https://issues.apache.org/jira/browse/HBASE-19052
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 19052.branch-1.txt, 19052.branch-1.txt
>
>
> HBASE-18945 has gone into branch-2 .
> Let's consider rolling upgrade scenario from 1.x to 2.0 where there're three 
> servers: s1, s2, s3
> s1 is upgraded to 2.0 first. It flushes to hfile in region r1 with 
> CellComparatorImpl written in the hfile trailer.
> Somehow s1 crashes and master assigns r1 to s2 which is still running 1.x
> The following code in FixedFileTrailer would be triggered:
> {code}
>   try {
> comparatorKlass = (Class) 
> Class.forName(comparatorClassName);
>   } catch (ClassNotFoundException e) {
> throw new IOException(e);
>   }
> {code}
> since s2 is not aware of CellComparatorImpl.
> This issue is to backport CellComparatorImpl related change to branch-1.x
> Note: CellComparatorImpl wouldn't be used in write path, only in read path.



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


[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19042:


FAILURE: Integrated in Jenkins build HBase-2.0 #718 (See 
[https://builds.apache.org/job/HBase-2.0/718/])
HBASE-19042 Oracle Java 8u144 downloader broken in precommit check (mdrob: rev 
64f024a76c054220d6c85fd6bcacdd39cd939b0e)
* (edit) dev-support/docker/Dockerfile


> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  

[jira] [Updated] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang updated HBASE-19055:
--
Release Note: Precommit switched from Oracle JDK 8 to OpenJDK-8.  (was: Use 
OpenJDK 8 in our pre commit check.)
 Component/s: build

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang updated HBASE-19055:
--
  Resolution: Fixed
Hadoop Flags: Reviewed
Release Note: Use OpenJDK 8 in our pre commit check.
  Status: Resolved  (was: Patch Available)

Pushed to branch-1 and branch-1.x.

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai commented on HBASE-19055:


+1

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-18602) rsgroup cleanup unassign code

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18602:
---

| (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:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
21s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
11s{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} shadedjars {color} | {color:green}  3m 
51s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
39m 30s{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}  0m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
15s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 15m 42s{color} 
| {color:red} hbase-rsgroup in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
 8s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 70m 54s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | org.apache.hadoop.hbase.rsgroup.TestRSGroups |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-18602 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893152/HBASE-18602-master-v3.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux d5c978c51a98 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 / af479c5 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9249/artifact/patchprocess/patch-unit-hbase-rsgroup.txt
 |
|  Test Results | 

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang commented on HBASE-19055:
---

OK, good. Let me commit.

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19055:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 20m 
51s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
8s{color} | {color:blue} Shelldocs was not available. {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} mvninstall {color} | {color:green}  7m 
16s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  2m 
22s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 4s{color} | {color:green} There were no new shellcheck issues. {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}  2m 
11s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
24m 31s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3. 
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
23s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 55m 44s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:6f1cc2c |
| JIRA Issue | HBASE-19055 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893151/HBASE-19055-branch-1.patch
 |
| Optional Tests |  asflicense  shadedjars  shellcheck  shelldocs  |
| uname | Linux f150728c3f15 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | branch-1 / 95e9261 |
| shellcheck | v0.4.6 |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9251/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-16338) update jackson to 2.y

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-16338:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
13s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
5s{color} | {color:blue} Shelldocs was not available. {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 17 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
32s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
 5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  7m 
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  4m 
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  4m 
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
59s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Skipped patched modules with no Java source: 
hbase-resource-bundle hbase-shaded hbase-shaded/hbase-shaded-mapreduce . 
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  5m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  5m 
21s{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}  3m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  7m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  7m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  4m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  4m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} rubocop {color} | {color:green}  0m  
4s{color} | {color:green} There were no new rubocop issues. {color} |
| {color:green}+1{color} | {color:green} ruby-lint {color} | {color:green}  0m  
2s{color} | {color:green} There were no new ruby-lint issues. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 4s{color} | {color:green} There were no new shellcheck issues. {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 
11s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
12s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
39m 32s{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:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Skipped patched modules with no Java source: 
hbase-resource-bundle hbase-shaded hbase-shaded/hbase-shaded-mapreduce . 
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  6m  
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  5m 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}174m 

[jira] [Updated] (HBASE-18950) Remove Optional parameters in AsyncAdmin interface

2017-10-19 Thread Guanghao Zhang (JIRA)

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

Guanghao Zhang updated HBASE-18950:
---
Attachment: HBASE-18950.master.005.patch

> Remove Optional parameters in AsyncAdmin interface
> --
>
> Key: HBASE-18950
> URL: https://issues.apache.org/jira/browse/HBASE-18950
> Project: HBase
>  Issue Type: Sub-task
>  Components: Client
>Reporter: Duo Zhang
>Assignee: Guanghao Zhang
>Priority: Blocker
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18950.master.001.patch, 
> HBASE-18950.master.002.patch, HBASE-18950.master.003.patch, 
> HBASE-18950.master.004.patch, HBASE-18950.master.005.patch, 
> HBASE-18950.master.005.patch
>
>




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


[jira] [Updated] (HBASE-19010) Reimplement getMasterInfoPort for Admin

2017-10-19 Thread Guanghao Zhang (JIRA)

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

Guanghao Zhang updated HBASE-19010:
---
Attachment: HBASE-19010.master.003.patch

Retry to trigger Hadoop QA.

> Reimplement getMasterInfoPort for Admin
> ---
>
> Key: HBASE-19010
> URL: https://issues.apache.org/jira/browse/HBASE-19010
> Project: HBase
>  Issue Type: Sub-task
>  Components: Client
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19010.master.001.patch, 
> HBASE-19010.master.002.patch, HBASE-19010.master.002.patch, 
> HBASE-19010.master.002.patch, HBASE-19010.master.002.patch, 
> HBASE-19010.master.003.patch, HBASE-19010.master.003.patch
>
>
> Current implementation.
> {code}
>   public int getMasterInfoPort() throws IOException {
> // TODO: Fix!  Reaching into internal implementation
> ConnectionImplementation connection = 
> (ConnectionImplementation)this.connection;
> ZooKeeperKeepAliveConnection zkw = 
> connection.getKeepAliveZooKeeperWatcher();
> try {
>   return MasterAddressTracker.getMasterInfoPort(zkw);
> } catch (KeeperException e) {
>   throw new IOException("Failed to get master info port from 
> MasterAddressTracker", e);
> }
>   }
> {code}
> Open this issue to fix TODO.



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


[jira] [Commented] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19021:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
10s{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}  3m 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
47s{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} shadedjars {color} | {color:green}  5m 
 6s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch 2 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  3m 
54s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
38m 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}  2m 
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}116m 17s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
23s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}177m 47s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestSplitTransactionOnCluster |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19021 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893132/HBASE-19021-master.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 6adc974bc543 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 
12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | master / af479c5 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| whitespace | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9247/artifact/patchprocess/whitespace-tabs.txt
 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9247/artifact/patchprocess/patch-unit-hbase-server.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9247/testReport/ |
| 

[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19055:
---

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at 
https://builds.apache.org/job/PreCommit-HBASE-Build/9251/console in case of 
problems.


> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang commented on HBASE-19055:
---

I made the patch manually as it is small but I guess it could be applied 
cleanly. Seems the only difference is that there is an extra openjdk-7-jdk in 
the huge apt-get install at the top of the Dockerfile for branch-1.x.

Anyway, let's see the pre commit result. If OK then let's commit.

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Status: Patch Available  (was: Open)

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Attachment: HBASE-19014.v0.patch

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Updated] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-19014:
---
Status: Open  (was: Patch Available)

> surefire fails; When writing xml report stdout/stderr ... No such file or 
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch, 
> HBASE-19014.branch-1.v0.patch, HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test 
> (secondPartTestsExecution) on project hbase-server: ExecutionException: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.maven.surefire.report.ReporterException: When writing xml report 
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or 
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and 
> then the failure doesn't happen again. see SUREFIRE-1239.



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


[jira] [Updated] (HBASE-18602) rsgroup cleanup unassign code

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-18602:
---
Status: Open  (was: Patch Available)

> rsgroup cleanup unassign code
> -
>
> Key: HBASE-18602
> URL: https://issues.apache.org/jira/browse/HBASE-18602
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup
>Reporter: Wang, Xinglong
>Assignee: Wang, Xinglong
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18602-master-v1.patch, 
> HBASE-18602-master-v2.patch, HBASE-18602-master-v3.patch, 
> HBASE-18602-master-v3.patch, HBASE-18602-master-v3.patch
>
>
> While walking through rsgroup code, I found that variable misplacedRegions 
> has never been added any element into. This makes the unassign region code is 
> not functional. And according to my test, it is actually unnecessary to do 
> that.
> RSGroupBasedLoadBalancer.java
> {code:java}
> private Map correctAssignments(
>Map existingAssignments)
>   throws HBaseIOException{
> Map correctAssignments = new TreeMap<>();
> List misplacedRegions = new LinkedList<>();
> correctAssignments.put(LoadBalancer.BOGUS_SERVER_NAME, new 
> LinkedList<>());
> for (Map.Entry assignments : 
> existingAssignments.entrySet()){
>   ServerName sName = assignments.getKey();
>   correctAssignments.put(sName, new LinkedList<>());
>   List regions = assignments.getValue();
>   for (HRegionInfo region : regions) {
> RSGroupInfo info = null;
> try {
>   info = rsGroupInfoManager.getRSGroup(
>   rsGroupInfoManager.getRSGroupOfTable(region.getTable()));
> } catch (IOException exp) {
>   LOG.debug("RSGroup information null for region of table " + 
> region.getTable(),
>   exp);
> }
> if ((info == null) || (!info.containsServer(sName.getAddress( {
>   correctAssignments.get(LoadBalancer.BOGUS_SERVER_NAME).add(region);
> } else {
>   correctAssignments.get(sName).add(region);
> }
>   }
> }
> //TODO bulk unassign?
> //unassign misplaced regions, so that they are assigned to correct groups.
> for(HRegionInfo info: misplacedRegions) {
>   try {
> this.masterServices.getAssignmentManager().unassign(info);
>   } catch (IOException e) {
> throw new HBaseIOException(e);
>   }
> }
> return correctAssignments;
>   }
> {code}



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


[jira] [Updated] (HBASE-18602) rsgroup cleanup unassign code

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-18602:
---
Attachment: HBASE-18602-master-v3.patch

retry v3

> rsgroup cleanup unassign code
> -
>
> Key: HBASE-18602
> URL: https://issues.apache.org/jira/browse/HBASE-18602
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup
>Reporter: Wang, Xinglong
>Assignee: Wang, Xinglong
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18602-master-v1.patch, 
> HBASE-18602-master-v2.patch, HBASE-18602-master-v3.patch, 
> HBASE-18602-master-v3.patch, HBASE-18602-master-v3.patch
>
>
> While walking through rsgroup code, I found that variable misplacedRegions 
> has never been added any element into. This makes the unassign region code is 
> not functional. And according to my test, it is actually unnecessary to do 
> that.
> RSGroupBasedLoadBalancer.java
> {code:java}
> private Map correctAssignments(
>Map existingAssignments)
>   throws HBaseIOException{
> Map correctAssignments = new TreeMap<>();
> List misplacedRegions = new LinkedList<>();
> correctAssignments.put(LoadBalancer.BOGUS_SERVER_NAME, new 
> LinkedList<>());
> for (Map.Entry assignments : 
> existingAssignments.entrySet()){
>   ServerName sName = assignments.getKey();
>   correctAssignments.put(sName, new LinkedList<>());
>   List regions = assignments.getValue();
>   for (HRegionInfo region : regions) {
> RSGroupInfo info = null;
> try {
>   info = rsGroupInfoManager.getRSGroup(
>   rsGroupInfoManager.getRSGroupOfTable(region.getTable()));
> } catch (IOException exp) {
>   LOG.debug("RSGroup information null for region of table " + 
> region.getTable(),
>   exp);
> }
> if ((info == null) || (!info.containsServer(sName.getAddress( {
>   correctAssignments.get(LoadBalancer.BOGUS_SERVER_NAME).add(region);
> } else {
>   correctAssignments.get(sName).add(region);
> }
>   }
> }
> //TODO bulk unassign?
> //unassign misplaced regions, so that they are assigned to correct groups.
> for(HRegionInfo info: misplacedRegions) {
>   try {
> this.masterServices.getAssignmentManager().unassign(info);
>   } catch (IOException e) {
> throw new HBaseIOException(e);
>   }
> }
> return correctAssignments;
>   }
> {code}



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


[jira] [Updated] (HBASE-18602) rsgroup cleanup unassign code

2017-10-19 Thread Chia-Ping Tsai (JIRA)

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

Chia-Ping Tsai updated HBASE-18602:
---
Status: Patch Available  (was: Open)

> rsgroup cleanup unassign code
> -
>
> Key: HBASE-18602
> URL: https://issues.apache.org/jira/browse/HBASE-18602
> Project: HBase
>  Issue Type: Improvement
>  Components: rsgroup
>Reporter: Wang, Xinglong
>Assignee: Wang, Xinglong
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-18602-master-v1.patch, 
> HBASE-18602-master-v2.patch, HBASE-18602-master-v3.patch, 
> HBASE-18602-master-v3.patch, HBASE-18602-master-v3.patch
>
>
> While walking through rsgroup code, I found that variable misplacedRegions 
> has never been added any element into. This makes the unassign region code is 
> not functional. And according to my test, it is actually unnecessary to do 
> that.
> RSGroupBasedLoadBalancer.java
> {code:java}
> private Map correctAssignments(
>Map existingAssignments)
>   throws HBaseIOException{
> Map correctAssignments = new TreeMap<>();
> List misplacedRegions = new LinkedList<>();
> correctAssignments.put(LoadBalancer.BOGUS_SERVER_NAME, new 
> LinkedList<>());
> for (Map.Entry assignments : 
> existingAssignments.entrySet()){
>   ServerName sName = assignments.getKey();
>   correctAssignments.put(sName, new LinkedList<>());
>   List regions = assignments.getValue();
>   for (HRegionInfo region : regions) {
> RSGroupInfo info = null;
> try {
>   info = rsGroupInfoManager.getRSGroup(
>   rsGroupInfoManager.getRSGroupOfTable(region.getTable()));
> } catch (IOException exp) {
>   LOG.debug("RSGroup information null for region of table " + 
> region.getTable(),
>   exp);
> }
> if ((info == null) || (!info.containsServer(sName.getAddress( {
>   correctAssignments.get(LoadBalancer.BOGUS_SERVER_NAME).add(region);
> } else {
>   correctAssignments.get(sName).add(region);
> }
>   }
> }
> //TODO bulk unassign?
> //unassign misplaced regions, so that they are assigned to correct groups.
> for(HRegionInfo info: misplacedRegions) {
>   try {
> this.masterServices.getAssignmentManager().unassign(info);
>   } catch (IOException e) {
> throw new HBaseIOException(e);
>   }
> }
> return correctAssignments;
>   }
> {code}



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Mike Drob (JIRA)

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

Mike Drob commented on HBASE-19055:
---

Is that a clean cherry-pick from the other patch? I had assumed it wouldn't 
work due to needing multiple JDKs in branch-1 builds (7 for general use, 8 for 
findbugs, I think), but if it actually works fine then just push it.

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang updated HBASE-19055:
--
Attachment: HBASE-19055-branch-1.patch

Apply the same tricks to branch-1.

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Commented] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Mike Drob (JIRA)

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

Mike Drob commented on HBASE-19055:
---

Thanks Duo!

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang updated HBASE-19055:
--
Priority: Blocker  (was: Major)

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)

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

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

> Backport HBASE-19042 to other active branches
> -
>
> Key: HBASE-19055
> URL: https://issues.apache.org/jira/browse/HBASE-19055
> Project: HBase
>  Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13
>
> Attachments: HBASE-19055-branch-1.patch
>
>
> Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Created] (HBASE-19055) Backport HBASE-19042 to other active branches

2017-10-19 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-19055:
-

 Summary: Backport HBASE-19042 to other active branches
 Key: HBASE-19055
 URL: https://issues.apache.org/jira/browse/HBASE-19055
 Project: HBase
  Issue Type: Bug
Reporter: Duo Zhang
Assignee: Duo Zhang
 Fix For: 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13


Mainly the jdk switching. And also some other dependencies upgrade.



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


[jira] [Updated] (HBASE-19029) Align RPC timout methods in Table and AsyncTableBase

2017-10-19 Thread Peter Somogyi (JIRA)

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

Peter Somogyi updated HBASE-19029:
--
Attachment: HBASE-19029.master.003.patch

> Align RPC timout methods in Table and AsyncTableBase
> 
>
> Key: HBASE-19029
> URL: https://issues.apache.org/jira/browse/HBASE-19029
> Project: HBase
>  Issue Type: Sub-task
>  Components: asyncclient, Client
>Affects Versions: 2.0.0-alpha-3
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19029.master.001.patch, 
> HBASE-19029.master.002.patch, HBASE-19029.master.002.patch, 
> HBASE-19029.master.003.patch, HBASE-19029.master.003.patch
>
>
> Table and AsyncTableBase have similar RPC timeout methods but the async 
> version supports TimeUtils to be passed.
> To align these 2 interfaces lets depricate the existing methods in Table and 
> add the ones that are currently in AsyncTableBase.
> These methods are the following:
> * long getRpcTimeout(TimeUnit unit)
> * long getReadRpcTimeout(TimeUnit unit)
> * long getWriteRpcTimeout(TimeUnit unit)
> * long getOperationTimeout(TimeUnit unit)
> We do not have {{long getScanTimeout(TimeUnit unit)}} since scan is handled 
> differently. 



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


[jira] [Updated] (HBASE-19029) Align RPC timout methods in Table and AsyncTableBase

2017-10-19 Thread Peter Somogyi (JIRA)

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

Peter Somogyi updated HBASE-19029:
--
Attachment: HBASE-19029.master.003.patch

Rebased

> Align RPC timout methods in Table and AsyncTableBase
> 
>
> Key: HBASE-19029
> URL: https://issues.apache.org/jira/browse/HBASE-19029
> Project: HBase
>  Issue Type: Sub-task
>  Components: asyncclient, Client
>Affects Versions: 2.0.0-alpha-3
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Critical
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19029.master.001.patch, 
> HBASE-19029.master.002.patch, HBASE-19029.master.002.patch, 
> HBASE-19029.master.003.patch, HBASE-19029.master.003.patch
>
>
> Table and AsyncTableBase have similar RPC timeout methods but the async 
> version supports TimeUtils to be passed.
> To align these 2 interfaces lets depricate the existing methods in Table and 
> add the ones that are currently in AsyncTableBase.
> These methods are the following:
> * long getRpcTimeout(TimeUnit unit)
> * long getReadRpcTimeout(TimeUnit unit)
> * long getWriteRpcTimeout(TimeUnit unit)
> * long getOperationTimeout(TimeUnit unit)
> We do not have {{long getScanTimeout(TimeUnit unit)}} since scan is handled 
> differently. 



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


[jira] [Commented] (HBASE-19049) Update kerby to 1.0.0 GA release

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19049:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 23m 
57s{color} | {color:blue} Docker mode activated. {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:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 11m 
27s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
40s{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} shadedjars {color} | {color:green}  3m 
22s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
32m 28s{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}  2m 
24s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}106m 28s{color} 
| {color:red} root 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}187m 25s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.coprocessor.TestRegionObserverInterface |
| Timed out junit tests | 
org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
|   | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
|   | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer |
|   | org.apache.hadoop.hbase.master.snapshot.TestSnapshotFileCache |
|   | org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient |
|   | org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient |
|   | org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient |
|   | org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19049 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893051/HBASE-19049.0.patch |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  xml  compile  
|
| uname | Linux aef229c4eda4 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 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 / af479c5 |
| Default Java | 1.8.0_141 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9245/artifact/patchprocess/patch-unit-root.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9245/testReport/ |
| modules 

[jira] [Commented] (HBASE-19050) Improve javadoc of Scan#setMvccReadPoint

2017-10-19 Thread Duo Zhang (JIRA)

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

Duo Zhang commented on HBASE-19050:
---

Yes, just like what [~anoopsamjohn] said above. The method is for internal 
usage only.

> Improve javadoc of Scan#setMvccReadPoint
> 
>
> Key: HBASE-19050
> URL: https://issues.apache.org/jira/browse/HBASE-19050
> Project: HBase
>  Issue Type: Task
>  Components: scan
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Minor
> Fix For: 2.0.0-beta-1
>
>
> This is to improve the javadoc of scan#setMvccReadPoint. Ya it was added for 
> internal thing so that the scan is able to use the mvcc point. 
> But the java doc is not explicit and does not tell the importance of using it 
> and I think internally the code just ignores it. I can confirm that once 
> where exactly it happens but javadoc should  highlight it I believe. 
> At least we should mention that user setting any value will be ignored.



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


[jira] [Commented] (HBASE-19029) Align RPC timout methods in Table and AsyncTableBase

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19029:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 14m 
11s{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 
35s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
 0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
49s{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 
40s{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 
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
30s{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} javac {color} | {color:green}  1m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
42s{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} shadedjars {color} | {color:green}  3m 
52s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
34m 30s{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}  4m  
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
35s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}100m 57s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  3m 
33s{color} | {color:green} hbase-rest in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
45s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}185m 46s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestSplitTransactionOnCluster |
|   | hadoop.hbase.client.TestBlockEvictionFromClient |
|   | hadoop.hbase.regionserver.TestCompactionInDeadRegionServer |
|   | hadoop.hbase.security.token.TestZKSecretWatcher |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19029 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893126/HBASE-19029.master.002.patch
 |
| Optional Tests |  asflicense  shadedjars  

[jira] [Commented] (HBASE-18410) FilterList Improvement.

2017-10-19 Thread Zheng Hu (JIRA)

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

Zheng Hu commented on HBASE-18410:
--

bq. It looks like the branch only ended up being 3 patches that haven't already 
been on master.
More than 3 patches actually,  after HBASE-18957, we revert some previous 
committed patches.  So I would prefer to merge.   

> FilterList  Improvement. 
> -
>
> Key: HBASE-18410
> URL: https://issues.apache.org/jira/browse/HBASE-18410
> Project: HBase
>  Issue Type: Umbrella
>  Components: Filters
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 2.0.0-beta-1
>
>
> FilterList.java is complex now, and we have found some improvements for it.  
> So create an issue to address it.



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


[jira] [Commented] (HBASE-19051) Add new split algorithm for num string

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu commented on HBASE-19051:


lgtm.

Attach patch for branch-1 if you want.

Thanks

> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
>  Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Attachments: HBASE-19051.master.001.patch, 
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part 
> of rowkey, there is no split algorithm to create a pre-split table, only by 
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}



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


[jira] [Commented] (HBASE-19018) Use of hadoop internals that require bouncycastle should declare bouncycastle dependency

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19018:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
10s{color} | {color:blue} Docker mode activated. {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:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
32s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  2m 
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 14m 
29s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  3m  
6s{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}  3m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  3m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  2m 
17s{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  
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
 0s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
38m 56s{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}  2m 
55s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}102m 16s{color} 
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
27s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}172m 57s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestSplitTransactionOnCluster |
| 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.TestGetLastFlushedSequenceId |
|   | org.apache.hadoop.hbase.master.TestMasterFailover |
|   | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
|   | org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics |
|   | org.apache.hadoop.hbase.master.assignment.TestAssignmentManager |
|   | org.apache.hadoop.hbase.TestHBaseTestingUtility |
|   | org.apache.hadoop.hbase.client.TestAsyncProcedureAdminApi |
|   | org.apache.hadoop.hbase.client.TestAsyncTableBatch |
|   | org.apache.hadoop.hbase.TestZooKeeper |
|   | org.apache.hadoop.hbase.master.TestAssignmentListener |
|   | org.apache.hadoop.hbase.master.TestMasterFailoverBalancerPersistence |
|   | org.apache.hadoop.hbase.master.cleaner.TestSnapshotFromMaster |
|   | 

[jira] [Commented] (HBASE-19051) Add new split algorithm for num string

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19051:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
9s{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}  3m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
57s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{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} shadedjars {color} | {color:green}  3m 
56s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
38m 50s{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}  2m 
32s{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:green}+1{color} | {color:green} unit {color} | {color:green}111m 
58s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
15s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}172m 33s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19051 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893088/HBASE-19051.master.002.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 746ffe896fe6 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 / af479c5 |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9237/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9237/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Add new split algorithm for num string
> --
>

[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check

2017-10-19 Thread Zheng Hu (JIRA)

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

Zheng Hu commented on HBASE-19042:
--

I think we have the same problem for branch-1,  see 
https://issues.apache.org/jira/browse/HBASE-18090?focusedCommentId=16210533=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16210533

Need a patch for branch-1 ? 



> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
>  Issue Type: Bug
>  Components: build
>Reporter: Peter Somogyi
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-4
>
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch, 
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch, 
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch, 
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch, 
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to 
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8 
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 No /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)... 
> 23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving edelivery.oracle.com (edelivery.oracle.com)... 
> 23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com 
> (edelivery.oracle.com)|23.39.16.136|:443... connected.
> 06:45:14 HTTP request sent, awaiting response... 302 Moved 
> Temporarily
> 06:45:14 Location: 
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
>  [following]
> 06:45:14 --2017-10-18 13:45:14--  
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com 
> (download.oracle.com)|23.59.189.81|:80... connected.
> 06:45:14 HTTP request sent, awaiting response... 404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14 
> 06:45:14 download failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 dpkg: error processing package oracle-java8-installer 
> (--configure):
> 06:45:14  subprocess installed post-installation script returned error exit 
> status 1
> 06:45:14 Errors were encountered while processing:
> 06:45:14  oracle-java8-installer
> 06:45:29 E: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 The command '/bin/sh -c apt-get -q update && apt-get -q install 
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code: 
> 100
> 06:45:29 
> 06:45:29 Total Elapsed time:   3m 19s
> 06:45:29 
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|' 
> oracle-java8-installer.*
> sudo sed -i 
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
>  oracle-java8-installer.*
> sudo sed -i 
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
>  oracle-java8-installer.*
> 

[jira] [Commented] (HBASE-18873) Hide protobufs in GlobalQuotaSettings

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18873:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 19m 
43s{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}  7m 
 0s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
36s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
48s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
19s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
56s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m  
5s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
33s{color} | {color:green} branch-2 passed {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  1m 
32s{color} | {color:red} root in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
24s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 24s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
45s{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:red}-1{color} | {color:red} shadedjars {color} | {color:red}  2m 
11s{color} | {color:red} patch has 14 errors when building our shaded 
downstream artifacts. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  3m 
27s{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.1. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  4m 
42s{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.2. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  5m 
56s{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.3. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  7m 
11s{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.4. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  8m 
25s{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.5. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red}  9m 
38s{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.1. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 10m 
54s{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.2. {color} 
|
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 12m  
9s{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 13m 
27s{color} | {color:red} The patch causes 14 errors with Hadoop v3.0.0-alpha4. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
25s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}  0m 24s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
12s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | 

[jira] [Commented] (HBASE-18090) Improve TableSnapshotInputFormat to allow more multiple mappers per region

2017-10-19 Thread Zheng Hu (JIRA)

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

Zheng Hu commented on HBASE-18090:
--

Seems like branch-1 pre-commit has the same problem as HBASE-19042 described. 

> Improve TableSnapshotInputFormat to allow more multiple mappers per region
> --
>
> Key: HBASE-18090
> URL: https://issues.apache.org/jira/browse/HBASE-18090
> Project: HBase
>  Issue Type: Improvement
>  Components: mapreduce
>Reporter: Mikhail Antonov
>Assignee: xinxin fan
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18090-V3-master.patch, 
> HBASE-18090-V4-master.patch, HBASE-18090-V5-master.patch, 
> HBASE-18090-branch-1.3-v1.patch, HBASE-18090-branch-1.3-v2.patch, 
> HBASE-18090.branch-1.patch
>
>
> TableSnapshotInputFormat runs one map task per region in the table snapshot. 
> This places unnecessary restriction that the region layout of the original 
> table needs to take the processing resources available to MR job into 
> consideration. Allowing to run multiple mappers per region (assuming 
> reasonably even key distribution) would be useful.



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


[jira] [Commented] (HBASE-18893) Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using ModifyTableProcedure

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18893:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m 
24s{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 6 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
35s{color} | {color:blue} Maven dependency ordering for branch {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}  1m  
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
23s{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 
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
36s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green}  1m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
25s{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} shadedjars {color} | {color:green}  3m 
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} 
35m 29s{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} hbaseprotoc {color} | {color:green}  
0m 53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
17s{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:green}+1{color} | {color:green} unit {color} | {color:green}  0m 
26s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 73m 20s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
47s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}151m 45s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.security.token.TestZKSecretWatcher |
|   | hadoop.hbase.client.TestSnapshotWithAcl |
|   | hadoop.hbase.master.procedure.TestDeleteColumnFamilyProcedureFromClient |
| Timed out junit tests | org.apache.hadoop.hbase.client.TestReplicasClient |
|   | org.apache.hadoop.hbase.regionserver.wal.TestSecureWALReplay |
|   | org.apache.hadoop.hbase.regionserver.wal.TestAsyncWALReplay |
|   | 

[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19007:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 21m  
0s{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 25 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
 4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  7m 
26s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  5m 
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
39s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
 7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  1m 
13s{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} shadedjars {color} | {color:green}  3m 
52s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
37m 28s{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:red}-1{color} | {color:red} findbugs {color} | {color:red}  2m 
47s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed = 
1 total (was 0) {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
44s{color} | {color:red} hbase-rsgroup generated 1 new + 0 unchanged - 0 fixed 
= 1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
36s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 22m 43s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
15s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  3m 
47s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  4m 
14s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
41s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}134m  6s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | 

[jira] [Commented] (HBASE-18961) doMiniBatchMutate() is big, split it into smaller methods

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18961:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 21m 
34s{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:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
33s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
38s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
25s{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} shadedjars {color} | {color:green}  3m 
28s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
34m 26s{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}  2m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  2m 
26s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 23m 36s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
19s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}104m 38s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.io.TestHeapSize |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-18961 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893073/hbase-18961.master.001.patch
 |
| Optional Tests |  asflicense  shadedjars  javac  javadoc  unit  findbugs  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 6d41b0cc0459 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 
13:48:03 UTC 2016 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
 |

[jira] [Commented] (HBASE-18873) Hide protobufs in GlobalQuotaSettings

2017-10-19 Thread Josh Elser (JIRA)

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

Josh Elser commented on HBASE-18873:


[~anoop.hbase], let me know what you think about v2. I think the new method is 
an improvement. Please let me know if you have a suggestion for something 
instead of {{GlobalQuotaSettingsImpl}} (or if you have a suggested class 
hierarchy instead of what I've created).

Maybe [~Apache9] or [~chia7712], any input? I'd like to get this locked down :)

> Hide protobufs in GlobalQuotaSettings
> -
>
> Key: HBASE-18873
> URL: https://issues.apache.org/jira/browse/HBASE-18873
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18873.001.branch-2.patch, 
> HBASE-18873.002.branch-2.patch
>
>
> HBASE-18807 cleaned up direct protobuf use in the Coprocessor APIs for 
> quota-related functions. However, one new POJO introduced to hide these 
> protocol buffers still exposes PBs via some methods.
> We should try to hide those as well.



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


[jira] [Updated] (HBASE-18873) Hide protobufs in GlobalQuotaSettings

2017-10-19 Thread Josh Elser (JIRA)

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

Josh Elser updated HBASE-18873:
---
Attachment: HBASE-18873.002.branch-2.patch

.002 - This adds a {{List}} method to GlobalQuotaSettings to 
give users access to the quotas in a non-protobuf form. This is an equivalent 
API to what we have in QuotaSettingsFactory so there should be some rough 
consistency from client-side to server-side.

> Hide protobufs in GlobalQuotaSettings
> -
>
> Key: HBASE-18873
> URL: https://issues.apache.org/jira/browse/HBASE-18873
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18873.001.branch-2.patch, 
> HBASE-18873.002.branch-2.patch
>
>
> HBASE-18807 cleaned up direct protobuf use in the Coprocessor APIs for 
> quota-related functions. However, one new POJO introduced to hide these 
> protocol buffers still exposes PBs via some methods.
> We should try to hide those as well.



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


[jira] [Commented] (HBASE-19026) TestLockProcedure#testRemoteNamespaceLockRecovery fails in master

2017-10-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-19026:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3917 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3917/])
HBASE-19026 TestLockProcedure#testRemoteNamespaceLockRecovery fails (tedyu: rev 
909e5f2f14186709ceb4697f76103c83125c8b49)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/locking/TestLockProcedure.java


> TestLockProcedure#testRemoteNamespaceLockRecovery fails in master
> -
>
> Key: HBASE-19026
> URL: https://issues.apache.org/jira/browse/HBASE-19026
> Project: HBase
>  Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.0.0-alpha-4
>
> Attachments: 19026.v1.txt
>
>
> This can be reproduced locally:
> {code}
> testRemoteNamespaceLockRecovery(org.apache.hadoop.hbase.master.locking.TestLockProcedure)
>   Time elapsed: 8.722 sec  <<< FAILURE!
> java.lang.AssertionError: expected: but was:
>   at 
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.sendHeartbeatAndCheckLocked(TestLockProcedure.java:219)
>   at 
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.testRemoteLockRecovery(TestLockProcedure.java:401)
>   at 
> org.apache.hadoop.hbase.master.locking.TestLockProcedure.testRemoteNamespaceLockRecovery(TestLockProcedure.java:415)
> {code}
> See also 
> https://builds.apache.org/job/HBase-TRUNK_matrix/3902/jdk=JDK%201.8%20(latest),label=Hadoop/testReport/org.apache.hadoop.hbase.master.locking/TestLockProcedure/testRemoteNamespaceLockRecovery/



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


[jira] [Commented] (HBASE-19054) Switch precommit docker image to one based on maven images

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19054:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  2m 
16s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
8s{color} | {color:blue} Shelldocs was not available. {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} mvninstall {color} | {color:green}  5m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
21s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 5s{color} | {color:green} There were no new shellcheck issues. {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 
19s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
49m 12s{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} asflicense {color} | {color:green}  0m 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 61m 43s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19054 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893121/HBASE-19054.patch |
| Optional Tests |  asflicense  shadedjars  shellcheck  shelldocs  |
| uname | Linux a1b88639baca 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11 
12:48:20 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | master / af479c580c |
| shellcheck | v0.4.4 |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9240/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Switch precommit docker image to one based on maven images
> --
>
> Key: HBASE-19054
> URL: https://issues.apache.org/jira/browse/HBASE-19054
> Project: HBase
>  Issue Type: Bug
>  Components: build, community
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-19054.patch
>
>
> In HBASE-19042 we discuss moving to a maven-based image for docker instead of 
> going through gymnastics ourselves. We got a short term fix in there, but 
> let's do the bulk of the cleanup here.



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


[jira] [Comment Edited] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He edited comment on HBASE-19021 at 10/19/17 10:09 PM:
-

More explanation.

In the branch-1 RegionStates.getAssignmentsByTable()
https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java#L1115
there is a part to deal with servers w/o assignments and draining mode.  This 
is missing after AMv2.

But the draining mode is actually ok after a 'detour' in AMv2.
The balancer's balanceCluster() can pick a plan to move regions to the draining 
servers. The regions will be 'unassigned'. But in the 'assign' phase, when 
going thru retainAssignment check, the plan is checked against the server list 
obtained from ServerManager.createDestinationServersList().  This list is a 
good list without the draining servers. So it is like a detour, but the end 
result is ok.
But I restored the branch-1 behavior, which is to take the draining servers out 
of consideration from the beginning.

The balancer's retainAssignment, randomAssignment and roundRobinAssignment all 
take a server list as parameter.  We seem to be always calling 
ServerManager.createDestinationServersList() to pass the server list. They are 
all good.  Only the big balanceCluster() call has the issue.


was (Author: jinghe):
More explanation.

In the branch-1 RegionStates.getAssignmentsByTable()
https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java#L1115
there is a part to deal with servers w/o assignments and draining mode.  This 
is missing after AMv2.

But the draining mode is actually ok after a 'detour' in AMv2.
The balancer's balanceCluster() can pick a plan to move regions to the draining 
servers. The regions will be 'unassigned'. But in the 'assign' phase, when 
going thru retainAssignment check, the plan is checked against the server list 
obtained from ServerManager.createDestinationServersList().  This list is a 
good list without the draining servers. So it is like a detour, but the end 
result is ok.
But I restored the branch-1 behavior, which is to take the draining servers out 
of consideration from the beginning.

The balancer's retainAssignment, randomAssignment and roundRobinAssignment all 
take a server list an parameters.  We seem to be always calling 
ServerManager.createDestinationServersList() to pass the server list. They are 
all good.  Only the big balanceCluster() call has the issue.

> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
>  Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master.patch, HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are 
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. 
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in 
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a 
> {{testRebalanceOnRegionServerNumberChange}}



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


[jira] [Updated] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He updated HBASE-19021:
-
Attachment: HBASE-19021-master.patch

> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
>  Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master.patch, HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are 
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. 
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in 
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a 
> {{testRebalanceOnRegionServerNumberChange}}



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


[jira] [Commented] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He commented on HBASE-19021:
--

All the timeout tests passed locally for me.  There is already a successful QA 
run earlier.
But retry QA again.

> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
>  Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are 
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. 
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in 
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a 
> {{testRebalanceOnRegionServerNumberChange}}



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


[jira] [Commented] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He commented on HBASE-19021:
--

More explanation.

In the branch-1 RegionStates.getAssignmentsByTable()
https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java#L1115
there is a part to deal with servers w/o assignments and draining mode.  This 
is missing after AMv2.

But the draining mode is actually ok after a 'detour' in AMv2.
The balancer's balanceCluster() can pick a plan to move regions to the draining 
servers. The regions will be 'unassigned'. But in the 'assign' phase, when 
going thru retainAssignment check, the plan is checked against the server list 
obtained from ServerManager.createDestinationServersList().  This list is a 
good list without the draining servers. So it is like a detour, but the end 
result is ok.
But I restored the branch-1 behavior, which is to take the draining servers out 
of consideration from the beginning.

The balancer's retainAssignment, randomAssignment and roundRobinAssignment all 
take a server list an parameters.  We seem to be always calling 
ServerManager.createDestinationServersList() to pass the server list. They are 
all good.  Only the big balanceCluster() call has the issue.

> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
>  Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are 
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. 
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in 
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a 
> {{testRebalanceOnRegionServerNumberChange}}



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


[jira] [Commented] (HBASE-19052) FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19052:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{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:red}-1{color} | {color:red} docker {color} | {color:red}  6m 
55s{color} | {color:red} Docker failed to build yetus/hbase:6f1cc2c. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-19052 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12893093/19052.branch-1.txt |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/9246/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x
> 
>
> Key: HBASE-19052
> URL: https://issues.apache.org/jira/browse/HBASE-19052
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 19052.branch-1.txt
>
>
> HBASE-18945 has gone into branch-2 .
> Let's consider rolling upgrade scenario from 1.x to 2.0 where there're three 
> servers: s1, s2, s3
> s1 is upgraded to 2.0 first. It flushes to hfile in region r1 with 
> CellComparatorImpl written in the hfile trailer.
> Somehow s1 crashes and master assigns r1 to s2 which is still running 1.x
> The following code in FixedFileTrailer would be triggered:
> {code}
>   try {
> comparatorKlass = (Class) 
> Class.forName(comparatorClassName);
>   } catch (ClassNotFoundException e) {
> throw new IOException(e);
>   }
> {code}
> since s2 is not aware of CellComparatorImpl.
> This issue is to backport CellComparatorImpl related change to branch-1.x
> Note: CellComparatorImpl wouldn't be used in write path, only in read path.



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


[jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS

2017-10-19 Thread huaxiang sun (JIRA)

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

huaxiang sun commented on HBASE-18946:
--

For the case with increased replica count, even with  HBASE-19017, it needs the 
same logic. As with some of regions with known location, there are new ones 
which needs to be assigned, these new ones could be assigned to the same region 
server which hosts the primary or other replica region. wdyt? [~ram_krish]

> Stochastic load balancer assigns replica regions to the same RS
> ---
>
> Key: HBASE-18946
> URL: https://issues.apache.org/jira/browse/HBASE-18946
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.0.0-alpha-3
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18946.patch, HBASE-18946.patch, 
> TestRegionReplicasWithRestartScenarios.java
>
>
> Trying out region replica and its assignment I can see that some times the 
> default LB Stocahstic load balancer assigns replica regions to the same RS. 
> This happens when we have 3 RS checked in and we have a table with 3 
> replicas. When a RS goes down then the replicas being assigned to same RS is 
> acceptable but the case when we have enough RS to assign this behaviour is 
> undesirable and does not solve the purpose of replicas. 
> [~huaxiang] and [~enis]. 



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


[jira] [Updated] (HBASE-19052) FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x

2017-10-19 Thread Ted Yu (JIRA)

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

Ted Yu updated HBASE-19052:
---
Status: Patch Available  (was: Open)

> FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x
> 
>
> Key: HBASE-19052
> URL: https://issues.apache.org/jira/browse/HBASE-19052
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 19052.branch-1.txt
>
>
> HBASE-18945 has gone into branch-2 .
> Let's consider rolling upgrade scenario from 1.x to 2.0 where there're three 
> servers: s1, s2, s3
> s1 is upgraded to 2.0 first. It flushes to hfile in region r1 with 
> CellComparatorImpl written in the hfile trailer.
> Somehow s1 crashes and master assigns r1 to s2 which is still running 1.x
> The following code in FixedFileTrailer would be triggered:
> {code}
>   try {
> comparatorKlass = (Class) 
> Class.forName(comparatorClassName);
>   } catch (ClassNotFoundException e) {
> throw new IOException(e);
>   }
> {code}
> since s2 is not aware of CellComparatorImpl.
> This issue is to backport CellComparatorImpl related change to branch-1.x
> Note: CellComparatorImpl wouldn't be used in write path, only in read path.



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


[jira] [Commented] (HBASE-19021) Restore a few important missing logics for balancer in 2.0

2017-10-19 Thread Jerry He (JIRA)

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

Jerry He commented on HBASE-19021:
--

Hi, [~stack] 
bq.  bytable is not implemented in AMv2 IIRC
It is implemented RegionStates,  but just missing a call to it. 
 {code}
   * @param forceByCluster a flag to force to aggregate the server-load to the 
cluster level
   * @return A clone of current assignments by table.
   */
  public Map> 
getAssignmentsByTable(
  final boolean forceByCluster) {
if (!forceByCluster) return getAssignmentsByTable();
{code}

bq. You saying when you add a Server, it doesn't get Regions? (I don't recall 
this in testing but perhaps so).
Yes.  From looking at the code, and some testing.  Tested it again today.
{noformat}
ServerName  Start time  Last contactVersion 
Requests Per Second Num. Regions
throb1,16020,1508446443086  Thu Oct 19 13:54:03 PDT 20172 s 
3.0.0-SNAPSHOT  0   0
throb1,45403,1508440236028  Thu Oct 19 12:10:36 PDT 20170 s 
3.0.0-SNAPSHOT  0   6
Total:2 0   6
{noformat}
bq. You are fixing this over in another issue?
The draining issue is dealt with in this patch too.

> Restore a few important missing logics for balancer in 2.0
> --
>
> Key: HBASE-19021
> URL: https://issues.apache.org/jira/browse/HBASE-19021
> Project: HBase
>  Issue Type: Bug
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Critical
> Attachments: HBASE-19021-master.patch
>
>
> After looking at the code, and some testing, I see the following things are 
> missing for balancer to work properly after AMv2.
> # hbase.master.loadbalance.bytable is not respected. It is always 'bytable'. 
> Previous default is cluster wide, not by table.
> # Servers with no assignments is not added for balance consideration.
> # Crashed server is not removed from the in-memory server map in 
> RegionStates, which affects balance.
> # Draining marker is not respected when balance.
> Also try to re-enable {{TestRegionRebalancing}}, which has a 
> {{testRebalanceOnRegionServerNumberChange}}



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


[jira] [Commented] (HBASE-19049) Update kerby to 1.0.0 GA release

2017-10-19 Thread Mike Drob (JIRA)

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

Mike Drob commented on HBASE-19049:
---

Triggered retry on Jenkins

> Update kerby to 1.0.0 GA release
> 
>
> Key: HBASE-19049
> URL: https://issues.apache.org/jira/browse/HBASE-19049
> Project: HBase
>  Issue Type: Task
>  Components: dependencies
>Affects Versions: 2.0.0-alpha-3
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19049.0.patch
>
>
> Hadoop 3.0.0-alpha4+ has moved to kerby 1.0.0 GA, so our tests that use their 
> minikdc fail with a version mismatch because we still declare 1.0.0-RC2



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


[jira] [Commented] (HBASE-18961) doMiniBatchMutate() is big, split it into smaller methods

2017-10-19 Thread Mike Drob (JIRA)

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

Mike Drob commented on HBASE-18961:
---

Triggered retry on Jenkins

> doMiniBatchMutate() is big, split it into smaller methods
> -
>
> Key: HBASE-18961
> URL: https://issues.apache.org/jira/browse/HBASE-18961
> Project: HBase
>  Issue Type: Sub-task
>  Components: regionserver
>Affects Versions: 2.0.0-alpha-3
>Reporter: Umesh Agashe
>Assignee: Umesh Agashe
> Fix For: 2.0.0-beta-1
>
> Attachments: hbase-18961.master.001.patch, 
> hbase-18961.master.001.patch, hbase-18961.master.001.patch
>
>
> Split doMiniBatchMutate() and improve readability.



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


[jira] [Commented] (HBASE-19054) Switch precommit docker image to one based on maven images

2017-10-19 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-19054:
---

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at 
https://builds.apache.org/job/PreCommit-HBASE-Build/9240/console in case of 
problems.


> Switch precommit docker image to one based on maven images
> --
>
> Key: HBASE-19054
> URL: https://issues.apache.org/jira/browse/HBASE-19054
> Project: HBase
>  Issue Type: Bug
>  Components: build, community
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-19054.patch
>
>
> In HBASE-19042 we discuss moving to a maven-based image for docker instead of 
> going through gymnastics ourselves. We got a short term fix in there, but 
> let's do the bulk of the cleanup here.



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


  1   2   3   >