[jira] [Commented] (HBASE-16379) [replication] Minor improvement to replication/copy_tables_desc.rb

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16379:


FAILURE: Integrated in HBase-Trunk_matrix #1392 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1392/])
HBASE-16379 [replication] Minor improvement to (esteban: rev 
b3888eadf8ac081729385b434f8da626d02d031a)
* bin/replication/copy_tables_desc.rb


> [replication] Minor improvement to replication/copy_tables_desc.rb
> --
>
> Key: HBASE-16379
> URL: https://issues.apache.org/jira/browse/HBASE-16379
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication, shell
>Affects Versions: 1.3.0, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> HBASE-16379.patch
>
>
> copy_tables_desc.rb is helpful for quickly setting up a table remotely based 
> on an existing schema. However it does copy by default all tables. Now you 
> can pass a list of tables as an optional third argument and it will also 
> display what table descriptors where copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16379) [replication] Minor improvement to replication/copy_tables_desc.rb

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16379:


SUCCESS: Integrated in HBase-1.1-JDK8 #1849 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1849/])
HBASE-16379 [replication] Minor improvement to (esteban: rev 
3259f03a592b42abe05ae1b89540b15ee4245cbe)
* bin/replication/copy_tables_desc.rb


> [replication] Minor improvement to replication/copy_tables_desc.rb
> --
>
> Key: HBASE-16379
> URL: https://issues.apache.org/jira/browse/HBASE-16379
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication, shell
>Affects Versions: 1.3.0, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> HBASE-16379.patch
>
>
> copy_tables_desc.rb is helpful for quickly setting up a table remotely based 
> on an existing schema. However it does copy by default all tables. Now you 
> can pass a list of tables as an optional third argument and it will also 
> display what table descriptors where copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14345) Consolidate printUsage in IntegrationTestLoadAndVerify

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-14345:


SUCCESS: Integrated in HBase-1.1-JDK8 #1849 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1849/])
HBASE-14345 Consolidate printUsage in IntegrationTestLoadAndVerify (Reid (appy: 
rev e5697bdb1bc63e832db57542420181348605b475)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestLoadAndVerify.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestWithCellVisibilityLoadAndVerify.java


> Consolidate printUsage in IntegrationTestLoadAndVerify
> --
>
> Key: HBASE-14345
> URL: https://issues.apache.org/jira/browse/HBASE-14345
> Project: HBase
>  Issue Type: Improvement
>  Components: integration tests
>Reporter: Nick Dimiduk
>Assignee: Reid Chan
>Priority: Trivial
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-14345.002.patch, HBASE-14345.003.patch, 
> HBASE-14345.004.patch, HBASE-14345.master.001.patch, 
> HBASE-14345.master.002.patch, HBASE-14345.patch, itlav-2016-07-07.png, 
> itlv.png
>
>
> Investigating the use of {{itlav}} is a little screwy. Subclasses are not 
> overriding the {{printUsage()}} methods correctly, so you have to pass 
> {{--help}} to get some info and no arguments to get the rest.
> {noformat}
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify --help
> usage: bin/hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify 
> 
> Options:
>  -h,--help Show usage
>  -m,--monkey  Which chaos monkey to run
>  -monkeyProps The properties file for specifying chaos monkey 
> properties.
>  -ncc,--noClusterCleanUp   Don't clean up the cluster at the end
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> IntegrationTestLoadAndVerify [-Doptions] 
>   Loads a table with row dependencies and verifies the dependency chains
> Options
>   -Dloadmapper.table=Table to write/verify (default autogen)
>   -Dloadmapper.backrefs=Number of backreferences per row (default 
> 50)
>   -Dloadmapper.num_to_write=Number of rows per mapper (default 100,000 
> per mapper)
>   -Dloadmapper.deleteAfter=  Delete after a successful verify (default 
> true)
>   -Dloadmapper.numPresplits=Number of presplit regions to start with 
> (default 40)
>   -Dloadmapper.map.tasks=   Number of map tasks for load (default 200)
>   -Dverify.reduce.tasks=Number of reduce tasks for verify (default 
> 35)
>   -Dverify.scannercaching=  Number hbase scanner caching rows to read 
> (default 50)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-1.2-IT #577 (See 
[https://builds.apache.org/job/HBase-1.2-IT/577/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (stack: 
rev 3de063cf03b6475f02f938fd751e42799df297f4)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-1.2 #699 (See 
[https://builds.apache.org/job/HBase-1.2/699/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (Yi 
(stack: rev 3de063cf03b6475f02f938fd751e42799df297f4)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14345) Consolidate printUsage in IntegrationTestLoadAndVerify

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-14345:


FAILURE: Integrated in HBase-1.4 #349 (See 
[https://builds.apache.org/job/HBase-1.4/349/])
HBASE-14345 Consolidate printUsage in IntegrationTestLoadAndVerify (Reid (appy: 
rev 89e3373096b3adfc6357b0aba42cbf3b06532485)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestLoadAndVerify.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestWithCellVisibilityLoadAndVerify.java


> Consolidate printUsage in IntegrationTestLoadAndVerify
> --
>
> Key: HBASE-14345
> URL: https://issues.apache.org/jira/browse/HBASE-14345
> Project: HBase
>  Issue Type: Improvement
>  Components: integration tests
>Reporter: Nick Dimiduk
>Assignee: Reid Chan
>Priority: Trivial
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-14345.002.patch, HBASE-14345.003.patch, 
> HBASE-14345.004.patch, HBASE-14345.master.001.patch, 
> HBASE-14345.master.002.patch, HBASE-14345.patch, itlav-2016-07-07.png, 
> itlv.png
>
>
> Investigating the use of {{itlav}} is a little screwy. Subclasses are not 
> overriding the {{printUsage()}} methods correctly, so you have to pass 
> {{--help}} to get some info and no arguments to get the rest.
> {noformat}
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify --help
> usage: bin/hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify 
> 
> Options:
>  -h,--help Show usage
>  -m,--monkey  Which chaos monkey to run
>  -monkeyProps The properties file for specifying chaos monkey 
> properties.
>  -ncc,--noClusterCleanUp   Don't clean up the cluster at the end
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> IntegrationTestLoadAndVerify [-Doptions] 
>   Loads a table with row dependencies and verifies the dependency chains
> Options
>   -Dloadmapper.table=Table to write/verify (default autogen)
>   -Dloadmapper.backrefs=Number of backreferences per row (default 
> 50)
>   -Dloadmapper.num_to_write=Number of rows per mapper (default 100,000 
> per mapper)
>   -Dloadmapper.deleteAfter=  Delete after a successful verify (default 
> true)
>   -Dloadmapper.numPresplits=Number of presplit regions to start with 
> (default 40)
>   -Dloadmapper.map.tasks=   Number of map tasks for load (default 200)
>   -Dverify.reduce.tasks=Number of reduce tasks for verify (default 
> 35)
>   -Dverify.scannercaching=  Number hbase scanner caching rows to read 
> (default 50)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16379) [replication] Minor improvement to replication/copy_tables_desc.rb

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16379:


FAILURE: Integrated in HBase-1.4 #349 (See 
[https://builds.apache.org/job/HBase-1.4/349/])
HBASE-16379 [replication] Minor improvement to (esteban: rev 
429f398c0769bfc76eddefcaa0230f6c3de40933)
* bin/replication/copy_tables_desc.rb


> [replication] Minor improvement to replication/copy_tables_desc.rb
> --
>
> Key: HBASE-16379
> URL: https://issues.apache.org/jira/browse/HBASE-16379
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication, shell
>Affects Versions: 1.3.0, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> HBASE-16379.patch
>
>
> copy_tables_desc.rb is helpful for quickly setting up a table remotely based 
> on an existing schema. However it does copy by default all tables. Now you 
> can pass a list of tables as an optional third argument and it will also 
> display what table descriptors where copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-1.4 #349 (See 
[https://builds.apache.org/job/HBase-1.4/349/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (Yi 
(stack: rev 2933795822d28a6da0889e90b0bed1f9868e667f)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-1.3 #815 (See 
[https://builds.apache.org/job/HBase-1.3/815/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (Yi 
(stack: rev 2831850de713d3e044f582394a2683a1b5da9a5f)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16379) [replication] Minor improvement to replication/copy_tables_desc.rb

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16379:


SUCCESS: Integrated in HBase-1.1-JDK7 #1763 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1763/])
HBASE-16379 [replication] Minor improvement to (esteban: rev 
3259f03a592b42abe05ae1b89540b15ee4245cbe)
* bin/replication/copy_tables_desc.rb


> [replication] Minor improvement to replication/copy_tables_desc.rb
> --
>
> Key: HBASE-16379
> URL: https://issues.apache.org/jira/browse/HBASE-16379
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication, shell
>Affects Versions: 1.3.0, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> HBASE-16379.patch
>
>
> copy_tables_desc.rb is helpful for quickly setting up a table remotely based 
> on an existing schema. However it does copy by default all tables. Now you 
> can pass a list of tables as an optional third argument and it will also 
> display what table descriptors where copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14345) Consolidate printUsage in IntegrationTestLoadAndVerify

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-14345:


SUCCESS: Integrated in HBase-1.1-JDK7 #1763 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1763/])
HBASE-14345 Consolidate printUsage in IntegrationTestLoadAndVerify (Reid (appy: 
rev e5697bdb1bc63e832db57542420181348605b475)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestLoadAndVerify.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestWithCellVisibilityLoadAndVerify.java


> Consolidate printUsage in IntegrationTestLoadAndVerify
> --
>
> Key: HBASE-14345
> URL: https://issues.apache.org/jira/browse/HBASE-14345
> Project: HBase
>  Issue Type: Improvement
>  Components: integration tests
>Reporter: Nick Dimiduk
>Assignee: Reid Chan
>Priority: Trivial
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-14345.002.patch, HBASE-14345.003.patch, 
> HBASE-14345.004.patch, HBASE-14345.master.001.patch, 
> HBASE-14345.master.002.patch, HBASE-14345.patch, itlav-2016-07-07.png, 
> itlv.png
>
>
> Investigating the use of {{itlav}} is a little screwy. Subclasses are not 
> overriding the {{printUsage()}} methods correctly, so you have to pass 
> {{--help}} to get some info and no arguments to get the rest.
> {noformat}
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify --help
> usage: bin/hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify 
> 
> Options:
>  -h,--help Show usage
>  -m,--monkey  Which chaos monkey to run
>  -monkeyProps The properties file for specifying chaos monkey 
> properties.
>  -ncc,--noClusterCleanUp   Don't clean up the cluster at the end
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> IntegrationTestLoadAndVerify [-Doptions] 
>   Loads a table with row dependencies and verifies the dependency chains
> Options
>   -Dloadmapper.table=Table to write/verify (default autogen)
>   -Dloadmapper.backrefs=Number of backreferences per row (default 
> 50)
>   -Dloadmapper.num_to_write=Number of rows per mapper (default 100,000 
> per mapper)
>   -Dloadmapper.deleteAfter=  Delete after a successful verify (default 
> true)
>   -Dloadmapper.numPresplits=Number of presplit regions to start with 
> (default 40)
>   -Dloadmapper.map.tasks=   Number of map tasks for load (default 200)
>   -Dverify.reduce.tasks=Number of reduce tasks for verify (default 
> 35)
>   -Dverify.scannercaching=  Number hbase scanner caching rows to read 
> (default 50)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-Trunk_matrix #1393 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1393/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (Yi 
(stack: rev 88956676d7e7164f3a5b0dfbb31ad67bd3d5ed87)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-Trunk_matrix #1393 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1393/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev 7e3251051313d6ef8fd173c7b530c1822667410e)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16285) Drop RPC requests if it must be considered as timeout at client

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16285:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16285 Drop RPC requests if it must be considered as timeout at (zhangduo: 
rev 974dab0f03c5e3db3234a7425c532157b660b10e)
* hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestHCM.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServerInterface.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/CallRunner.java


> Drop RPC requests if it must be considered as timeout at client
> ---
>
> Key: HBASE-16285
> URL: https://issues.apache.org/jira/browse/HBASE-16285
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 2.0.0, 1.3.0, 1.4.0
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: HBASE-16285-branch-1-v1.patch, 
> HBASE-16285-branch-1-v2.patch, HBASE-16285-branch-1-v3.patch, 
> HBASE-16285-branch-1-v4.patch, HBASE-16285-branch-1-v5.patch, 
> HBASE-16285-branch-1-v5.patch, HBASE-16285-branch-1-v6.patch, 
> HBASE-16285-v1.patch, HBASE-16285-v2.patch, HBASE-16285-v3.patch, 
> HBASE-16285-v4.patch, HBASE-16285-v5.patch, HBASE-16285-v6.patch, 
> HBASE-16285-v7.patch, HBASE-16285-v7.patch, HBASE-16285-v8.patch, 
> HBASE-16285-v9.patch
>
>
> After HBASE-15593, we have a timeout param in header of RPC requests. We can 
> use it in more scenes.
> A straightforward scene is to drop requests if it has waited so long in RPC 
> queue and has been dropped by client. Even if we handle this request and send 
> the response back, it will not be used any more. And client may have sent a 
> retry. In an extreme case, if the server is slow, all requests may be timeout 
> or queue-full-exception because we should handle previous requests which have 
> been dropped by client and many resources at server are wasted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16379) [replication] Minor improvement to replication/copy_tables_desc.rb

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16379:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16379 [replication] Minor improvement to (esteban: rev 
66c23e37003a97778840f12cb25f65f51ce677fe)
* bin/replication/copy_tables_desc.rb


> [replication] Minor improvement to replication/copy_tables_desc.rb
> --
>
> Key: HBASE-16379
> URL: https://issues.apache.org/jira/browse/HBASE-16379
> Project: HBase
>  Issue Type: Improvement
>  Components: Replication, shell
>Affects Versions: 1.3.0, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> 0001-HBASE-16379-replication-Minor-improvement-to-replica.patch, 
> HBASE-16379.patch
>
>
> copy_tables_desc.rb is helpful for quickly setting up a table remotely based 
> on an existing schema. However it does copy by default all tables. Now you 
> can pass a list of tables as an optional third argument and it will also 
> display what table descriptors where copied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16368) test*WhenRegionMove in TestPartialResultsFromClientSide is flaky

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16368:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16368 test*WhenRegionMove in TestPartialResultsFromClientSide is 
(zhangduo: rev 8f5b70ac3235a463708245ac83baa23ddc5b5867)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestPartialResultsFromClientSide.java


> test*WhenRegionMove in TestPartialResultsFromClientSide is flaky
> 
>
> Key: HBASE-16368
> URL: https://issues.apache.org/jira/browse/HBASE-16368
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2
>Reporter: Guanghao Zhang
>Assignee: Phil Yang
>  Labels: trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16368-v1.patch, HBASE-16368-v1.patch, 
> HBASE-16368-v1.patch
>
>
> This test fail when Hadoop QA run preCommit:
> https://builds.apache.org/job/PreCommit-HBASE-Build/2971/testReport/org.apache.hadoop.hbase/TestPartialResultsFromClientSide/testReversedCompleteResultWhenRegionMove/.
> And I found it is in Flaky Tests Dashboard: 
> http://hbase.x10host.com/flaky-tests/. I run it in my local machine and it 
> may fail, too.
> Test results show that the region location didn't update when scanner 
> callable get a NotServingRegionException or RegionMovedException.
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
> attempts=36, exceptions:
> Sat Aug 06 05:55:52 UTC 2016, null, java.net.SocketTimeoutException: 
> callTimeout=2000, callDuration=2157: 
> org.apache.hadoop.hbase.NotServingRegionException: 
> testReversedCompleteResultWhenRegionMove,,1470462949504.5069bd63bf6eda5108acec4fcc087b0e.
>  is closing
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:8233)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2634)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2629)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2623)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2490)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:34950)
>   at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2264)
>   at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:118)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:189)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:169)
>  row '' on table 'testReversedCompleteResultWhenRegionMove' at 
> region=testReversedCompleteResultWhenRegionMove,,1470462949504.5069bd63bf6eda5108acec4fcc087b0e.,
>  hostname=asf907.gq1.ygridcore.net,38914,1470462943053, seqNum=2
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedException(RpcRetryingCallerWithReadReplicas.java:281)
>   at 
> org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:213)
>   at 
> org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:61)
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:212)
>   at 
> org.apache.hadoop.hbase.client.ReversedClientScanner.nextScanner(ReversedClientScanner.java:118)
>   at 
> org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:166)
>   at 
> org.apache.hadoop.hbase.client.ClientScanner.(ClientScanner.java:161)
>   at 
> org.apache.hadoop.hbase.client.ReversedClientScanner.(ReversedClientScanner.java:56)
>   at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:785)
>   at 
> org.apache.hadoop.hbase.TestPartialResultsFromClientSide.testReversedCompleteResultWhenRegionMove(TestPartialResultsFromClientSide.java:986)
> {code}
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
> attempts=36, exceptions:
> Sat Aug 06 16:27:22 CST 2016, null, java.net.SocketTimeoutException: 
> callTimeout=2000, callDuration=3035: Region moved to: hostname=localhost 
> port=58351 startCode=1470472007714. As of locationSeqNum=6. row 'testRow0' on 
> table 'testPartialResultWhenRegionMove' at 
> region=testPartialResultWhenRegionMove,,1470472035048.977faf05c1d6d9990b5559b17aa18913.,
>  hostname=localhost,40425,1470472007646, seqNum=2
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedE

[jira] [Commented] (HBASE-16385) Have hbase-rest pull hbase.rest.port from Constants.java

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16385:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16385 Have hbase-rest pull hbase.rest.port from Constants.java (Yi 
(stack: rev 2831850de713d3e044f582394a2683a1b5da9a5f)
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java


> Have hbase-rest pull hbase.rest.port from Constants.java
> 
>
> Key: HBASE-16385
> URL: https://issues.apache.org/jira/browse/HBASE-16385
> Project: HBase
>  Issue Type: Improvement
>  Components: REST
>Reporter: Dima Spivak
>Assignee: Yi Liang
>Priority: Minor
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16385-V1.patch
>
>
> [A while back|https://issues.apache.org/jira/browse/HBASE-3272], we 
> [hardcoded|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java#L266]
>  the {{hbase.rest.port}} instead of getting it from 
> [Constants.java|https://github.com/apache/hbase/blob/master/hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/Constants.java#L36].
>  We should fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14345) Consolidate printUsage in IntegrationTestLoadAndVerify

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-14345:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-14345 Consolidate printUsage in IntegrationTestLoadAndVerify (Reid (appy: 
rev 2759b4a4a36b62f0d5595785ab5e91bd7a863a83)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestLoadAndVerify.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestWithCellVisibilityLoadAndVerify.java


> Consolidate printUsage in IntegrationTestLoadAndVerify
> --
>
> Key: HBASE-14345
> URL: https://issues.apache.org/jira/browse/HBASE-14345
> Project: HBase
>  Issue Type: Improvement
>  Components: integration tests
>Reporter: Nick Dimiduk
>Assignee: Reid Chan
>Priority: Trivial
>  Labels: beginner
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-14345.002.patch, HBASE-14345.003.patch, 
> HBASE-14345.004.patch, HBASE-14345.master.001.patch, 
> HBASE-14345.master.002.patch, HBASE-14345.patch, itlav-2016-07-07.png, 
> itlv.png
>
>
> Investigating the use of {{itlav}} is a little screwy. Subclasses are not 
> overriding the {{printUsage()}} methods correctly, so you have to pass 
> {{--help}} to get some info and no arguments to get the rest.
> {noformat}
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify --help
> usage: bin/hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify 
> 
> Options:
>  -h,--help Show usage
>  -m,--monkey  Which chaos monkey to run
>  -monkeyProps The properties file for specifying chaos monkey 
> properties.
>  -ncc,--noClusterCleanUp   Don't clean up the cluster at the end
> [hbase@ndimiduk-112rc2-7 ~]$ hbase 
> org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify
> IntegrationTestLoadAndVerify [-Doptions] 
>   Loads a table with row dependencies and verifies the dependency chains
> Options
>   -Dloadmapper.table=Table to write/verify (default autogen)
>   -Dloadmapper.backrefs=Number of backreferences per row (default 
> 50)
>   -Dloadmapper.num_to_write=Number of rows per mapper (default 100,000 
> per mapper)
>   -Dloadmapper.deleteAfter=  Delete after a successful verify (default 
> true)
>   -Dloadmapper.numPresplits=Number of presplit regions to start with 
> (default 40)
>   -Dloadmapper.map.tasks=   Number of map tasks for load (default 200)
>   -Dverify.reduce.tasks=Number of reduce tasks for verify (default 
> 35)
>   -Dverify.scannercaching=  Number hbase scanner caching rows to read 
> (default 50)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-1.3-IT #790 (See 
[https://builds.apache.org/job/HBase-1.3-IT/790/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev 9aed64173b4f360e3029a0936ae986cd5c916062)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-1.2-IT #578 (See 
[https://builds.apache.org/job/HBase-1.2-IT/578/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev 470667420caff382963cc7510b2f71d9b679a116)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-1.2 #700 (See 
[https://builds.apache.org/job/HBase-1.2/700/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev 470667420caff382963cc7510b2f71d9b679a116)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-1.4 #350 (See 
[https://builds.apache.org/job/HBase-1.4/350/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev cf9878f77e5176296c107e3850f8a2c01e48c812)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16368) test*WhenRegionMove in TestPartialResultsFromClientSide is flaky

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16368:


FAILURE: Integrated in HBase-1.3 #816 (See 
[https://builds.apache.org/job/HBase-1.3/816/])
HBASE-16368 test*WhenRegionMove in TestPartialResultsFromClientSide is 
(zhangduo: rev 8f5b70ac3235a463708245ac83baa23ddc5b5867)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/TestPartialResultsFromClientSide.java


> test*WhenRegionMove in TestPartialResultsFromClientSide is flaky
> 
>
> Key: HBASE-16368
> URL: https://issues.apache.org/jira/browse/HBASE-16368
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.0.0, 1.3.0, 1.4.0, 1.1.5, 1.2.2
>Reporter: Guanghao Zhang
>Assignee: Phil Yang
>  Labels: trivial
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16368-v1.patch, HBASE-16368-v1.patch, 
> HBASE-16368-v1.patch
>
>
> This test fail when Hadoop QA run preCommit:
> https://builds.apache.org/job/PreCommit-HBASE-Build/2971/testReport/org.apache.hadoop.hbase/TestPartialResultsFromClientSide/testReversedCompleteResultWhenRegionMove/.
> And I found it is in Flaky Tests Dashboard: 
> http://hbase.x10host.com/flaky-tests/. I run it in my local machine and it 
> may fail, too.
> Test results show that the region location didn't update when scanner 
> callable get a NotServingRegionException or RegionMovedException.
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
> attempts=36, exceptions:
> Sat Aug 06 05:55:52 UTC 2016, null, java.net.SocketTimeoutException: 
> callTimeout=2000, callDuration=2157: 
> org.apache.hadoop.hbase.NotServingRegionException: 
> testReversedCompleteResultWhenRegionMove,,1470462949504.5069bd63bf6eda5108acec4fcc087b0e.
>  is closing
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:8233)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2634)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2629)
>   at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2623)
>   at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2490)
>   at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:34950)
>   at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2264)
>   at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:118)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:189)
>   at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:169)
>  row '' on table 'testReversedCompleteResultWhenRegionMove' at 
> region=testReversedCompleteResultWhenRegionMove,,1470462949504.5069bd63bf6eda5108acec4fcc087b0e.,
>  hostname=asf907.gq1.ygridcore.net,38914,1470462943053, seqNum=2
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedException(RpcRetryingCallerWithReadReplicas.java:281)
>   at 
> org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:213)
>   at 
> org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:61)
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:212)
>   at 
> org.apache.hadoop.hbase.client.ReversedClientScanner.nextScanner(ReversedClientScanner.java:118)
>   at 
> org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:166)
>   at 
> org.apache.hadoop.hbase.client.ClientScanner.(ClientScanner.java:161)
>   at 
> org.apache.hadoop.hbase.client.ReversedClientScanner.(ReversedClientScanner.java:56)
>   at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:785)
>   at 
> org.apache.hadoop.hbase.TestPartialResultsFromClientSide.testReversedCompleteResultWhenRegionMove(TestPartialResultsFromClientSide.java:986)
> {code}
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after 
> attempts=36, exceptions:
> Sat Aug 06 16:27:22 CST 2016, null, java.net.SocketTimeoutException: 
> callTimeout=2000, callDuration=3035: Region moved to: hostname=localhost 
> port=58351 startCode=1470472007714. As of locationSeqNum=6. row 'testRow0' on 
> table 'testPartialResultWhenRegionMove' at 
> region=testPartialResultWhenRegionMove,,1470472035048.977faf05c1d6d9990b5559b17aa18913.,
>  hostname=localhost,40425,1470472007646, seqNum=2
>   at 
> org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.throwEnrichedExcepti

[jira] [Commented] (HBASE-16363) Correct javadoc for qualifier length and value length in Cell interface

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16363:


FAILURE: Integrated in HBase-1.3 #816 (See 
[https://builds.apache.org/job/HBase-1.3/816/])
HBASE-16363 Correct javadoc for qualifier length and value (Xiang Li) (stack: 
rev 9aed64173b4f360e3029a0936ae986cd5c916062)
* hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java


> Correct javadoc for qualifier length and value length in Cell interface
> ---
>
> Key: HBASE-16363
> URL: https://issues.apache.org/jira/browse/HBASE-16363
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Xiang Li
>Assignee: Xiang Li
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.2.3
>
> Attachments: HBASE-16363.master.000.patch
>
>
> In Cell interface 
> (hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java)
> (1) We have the following comment for "qualifier"
> {code}
> /**
>   * Contiguous raw bytes that may start at any index in the containing array. 
> Max length is
>   * Short.MAX_VALUE which is 32,767 bytes.
>   * @return The array containing the qualifier bytes.
>   */
> {code}
> But getQualifierLength() returns int
> {code}
> int getQualifierLength();
> {code}
> (2) We have the following comment for "value"
> {code}
>   /**
>* Contiguous raw bytes that may start at any index in the containing 
> array. Max length is
>* Integer.MAX_VALUE which is 2,147,483,648 bytes.
>* @return The array containing the value bytes.
>*/
> {code}
> Integer.MAX_VALUE is not 2,147,483,648 (2^31), but 2,147,483,647 (2^31-1)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16267) Remove commons-httpclient dependency from hbase-rest module

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16267:


FAILURE: Integrated in HBase-Trunk_matrix #1394 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1394/])
HBASE-16267 Remove commons-httpclient dependency from hbase-rest module (tedyu: 
rev fb668a0d3f8bde2e228527a9c45d0458ea7597e8)
* hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/Client.java
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/Response.java
* hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/MultiRowResource.java
* hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestScannerResource.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/http/log/TestLogLevel.java
* 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestGetAndPutResource.java
* 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java
* 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestMultiRowResource.java
* hbase-rest/pom.xml
* pom.xml
* hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestGzipFilter.java


> Remove commons-httpclient dependency from hbase-rest module
> ---
>
> Key: HBASE-16267
> URL: https://issues.apache.org/jira/browse/HBASE-16267
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 16267.v10.txt, 16267.v11.txt, 16267.v12.txt, 
> 16267.v13.txt, 16267.v14.txt, 16267.v15.txt, 16267.v15.txt, 16267.v2.txt, 
> 16267.v4.txt, 16267.v6.txt, 16267.v8.txt, 16267.v9.txt
>
>
> hbase-rest module still has imports from org.apache.commons.httpclient .
> There is more work to be done after HBASE-15767 was integrated.
> In master branch, there seems to be transitive dependency which allows the 
> code to compile:
> {code}
> [INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile
> [INFO] |  +- org.apache.hadoop:hadoop-annotations:jar:2.7.1:compile
> [INFO] |  +- commons-cli:commons-cli:jar:1.2:compile
> [INFO] |  +- org.apache.commons:commons-math3:jar:3.1.1:compile
> [INFO] |  +- xmlenc:xmlenc:jar:0.52:compile
> [INFO] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
> {code}
> HADOOP-12767
> to move the uses of httpclient HADOOP-10105
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5262 : 
> http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents 
> HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting 
> during an SSL handshake, which allows remote attackers to cause a denial of 
> service (HTTPS call hang) via unspecified vectors.
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6153
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-5783
> Apache Commons HttpClient 3.x, as used in Amazon Flexible Payments 
> Service (FPS) merchant Java SDK and other products, does not verify that the 
> server hostname matches a domain name in the subject's Common Name (CN) or 
> subjectAltName field of the X.509 certificate, which allows man-in-the-middle 
> attackers to spoof SSL servers via an arbitrary valid certificate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16389) Thread leak in CoprocessorHost#getTable(TableName) API

2016-08-10 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16389:


FAILURE: Integrated in HBase-Trunk_matrix #1394 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1394/])
HBASE-16389 Thread leak in CoprocessorHost#getTable(TableName) API (tedyu: rev 
9e116e048b91ee2fef056e4140cb4091a7fd8425)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java


> Thread leak in CoprocessorHost#getTable(TableName) API
> --
>
> Key: HBASE-16389
> URL: https://issues.apache.org/jira/browse/HBASE-16389
> Project: HBase
>  Issue Type: Bug
>Reporter: Ankit Singhal
>Assignee: Ankit Singhal
> Fix For: 2.0.0
>
> Attachments: HBASE-16389.patch
>
>
> There is a thread leak in below method, we are creating a default pool while 
> calling 
> {code}
> @Override
> public HTableInterface getTable(TableName tableName) throws IOException {
>   return this.getTable(tableName, 
> HTable.getDefaultExecutor(getConfiguration()));
> }
> {code}
> which will never be shutdown because in HTable,   we are setting 
> this.cleanupPoolOnClose to false
> {code}
>  @InterfaceAudience.Private
>   public HTable(TableName tableName, final ClusterConnection connection,
>   final TableConfiguration tableConfig,
>   final RpcRetryingCallerFactory rpcCallerFactory,
>   final RpcControllerFactory rpcControllerFactory,
>   final ExecutorService pool) throws IOException {
> if (connection == null || connection.isClosed()) {
>   throw new IllegalArgumentException("Connection is null or closed.");
> }
> this.tableName = tableName;
> this.cleanupConnectionOnClose = false;
> this.connection = connection;
> this.configuration = connection.getConfiguration();
> this.tableConfiguration = tableConfig;
> this.pool = pool;
> if (pool == null) {
>   this.pool = getDefaultExecutor(this.configuration);
>   this.cleanupPoolOnClose = true;
> } else {
>   this.cleanupPoolOnClose = false;
> }
> {code}
> resulted in pool to stay forever ,which eventually can lead other processes 
> or the same process to starve for a threads.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15554) StoreFile$Writer.appendGeneralBloomFilter generates extra KV

2016-08-11 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15554:


FAILURE: Integrated in HBase-Trunk_matrix #1400 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1400/])
HBASE-15554 - StoreFile$Writer.appendGeneralBloomFilter generates extra 
(ramkrishna: rev 285e104176bf848dc81657ac5358ad3beb49cc57)
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomContext.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/HashKey.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteArrayHashKey.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterWriter.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterUtil.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileWriter.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterFactory.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/Hash.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/MurmurHash.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/MurmurHash3.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CompoundBloomFilter.java
* 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/RowColBloomHashKey.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/CellHashKey.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/RowColBloomContext.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CompoundBloomFilterWriter.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/JenkinsHash.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/util/RowBloomHashKey.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/RowBloomContext.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterChunk.java


> StoreFile$Writer.appendGeneralBloomFilter generates extra KV
> 
>
> Key: HBASE-15554
> URL: https://issues.apache.org/jira/browse/HBASE-15554
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: Vladimir Rodionov
>Assignee: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
> Attachments: HBASE-15554.patch, HBASE-15554_10.patch, 
> HBASE-15554_11.patch, HBASE-15554_12.patch, HBASE-15554_13.patch, 
> HBASE-15554_14.patch, HBASE-15554_3.patch, HBASE-15554_4.patch, 
> HBASE-15554_6.patch, HBASE-15554_7.patch, HBASE-15554_9.patch
>
>
> Accounts for 10% memory allocation in compaction thread when BloomFilterType 
> is ROWCOL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16402) RegionServerCoprocessorHost should be initialized before RpcServer starts

2016-08-12 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16402:


FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1260 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1260/])
HBASE-16402 RegionServerCoprocessorHost should be initialized before (apurtell: 
rev 8168667f3aeb08bce70d9812bed40ecf9bd02bd1)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java


> RegionServerCoprocessorHost should be initialized before RpcServer starts
> -
>
> Key: HBASE-16402
> URL: https://issues.apache.org/jira/browse/HBASE-16402
> Project: HBase
>  Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 0.98.22
>
> Attachments: HBASE-16402-0.98.patch
>
>
> We found NPE in our 0.98 production cluster because 
> RegionServerCoprocessorHost is not initialized before RpcServer start service.
> {code}
>   // Try and register with the Master; tell it we are here.  Break if
>   // server is stopped or the clusterup flag is down or hdfs went wacky.
>   while (keepLooping()) {
> RegionServerStartupResponse w = reportForDuty();
> if (w == null) {
>   LOG.warn("reportForDuty failed; sleeping and then retrying.");
>   this.sleeper.sleep();
> } else {
>   handleReportForDutyResponse(w);
>   break;
> }
>   }
>   // Initialize the RegionServerCoprocessorHost now that our ephemeral
>   // node was created by reportForDuty, in case any coprocessors want
>   // to use ZooKeeper
>   this.rsHost = new RegionServerCoprocessorHost(this, this.conf);
> {code}
> RpcServer start service in handleReportForDutyResponse(), then it can serve 
> rpc call replicateWALEntry(). But the RegionServerCoprocessorHost is not 
> initialized and it is used in replicateWALEntry, so it will throw a NPE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16400) TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build

2016-08-12 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16400:


FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1260 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1260/])
HBASE-16400 TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build (tedyu: rev 
510d1176907706ae35ce1b0a6a1b94fbd9023a4d)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/hbck/HFileCorruptionChecker.java


> TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build
> -
>
> Key: HBASE-16400
> URL: https://issues.apache.org/jira/browse/HBASE-16400
> Project: HBase
>  Issue Type: Test
>Affects Versions: 0.98.21
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 0.98.22
>
> Attachments: 16400-0.98.v1.txt
>
>
> From 
> https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1259/testReport/org.apache.hadoop.hbase.util/TestHBaseFsck/testQuarantineMissingRegionDir/
>  :
> {code}
> java.lang.NullPointerException: null
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker.checkRegionDir(HFileCorruptionChecker.java:201)
>   at 
> org.apache.hadoop.hbase.util.TestHBaseFsck$3$1.checkRegionDir(TestHBaseFsck.java:2013)
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker$RegionDirChecker.call(HFileCorruptionChecker.java:293)
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker$RegionDirChecker.call(HFileCorruptionChecker.java:284)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> {code}
> Local run with hadoop-1.1 reproduced the above test failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16402) RegionServerCoprocessorHost should be initialized before RpcServer starts

2016-08-12 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16402:


FAILURE: Integrated in HBase-0.98-matrix #387 (See 
[https://builds.apache.org/job/HBase-0.98-matrix/387/])
HBASE-16402 RegionServerCoprocessorHost should be initialized before (apurtell: 
rev 8168667f3aeb08bce70d9812bed40ecf9bd02bd1)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java


> RegionServerCoprocessorHost should be initialized before RpcServer starts
> -
>
> Key: HBASE-16402
> URL: https://issues.apache.org/jira/browse/HBASE-16402
> Project: HBase
>  Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 0.98.22
>
> Attachments: HBASE-16402-0.98.patch
>
>
> We found NPE in our 0.98 production cluster because 
> RegionServerCoprocessorHost is not initialized before RpcServer start service.
> {code}
>   // Try and register with the Master; tell it we are here.  Break if
>   // server is stopped or the clusterup flag is down or hdfs went wacky.
>   while (keepLooping()) {
> RegionServerStartupResponse w = reportForDuty();
> if (w == null) {
>   LOG.warn("reportForDuty failed; sleeping and then retrying.");
>   this.sleeper.sleep();
> } else {
>   handleReportForDutyResponse(w);
>   break;
> }
>   }
>   // Initialize the RegionServerCoprocessorHost now that our ephemeral
>   // node was created by reportForDuty, in case any coprocessors want
>   // to use ZooKeeper
>   this.rsHost = new RegionServerCoprocessorHost(this, this.conf);
> {code}
> RpcServer start service in handleReportForDutyResponse(), then it can serve 
> rpc call replicateWALEntry(). But the RegionServerCoprocessorHost is not 
> initialized and it is used in replicateWALEntry, so it will throw a NPE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16400) TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build

2016-08-12 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16400:


FAILURE: Integrated in HBase-0.98-matrix #387 (See 
[https://builds.apache.org/job/HBase-0.98-matrix/387/])
HBASE-16400 TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build (tedyu: rev 
510d1176907706ae35ce1b0a6a1b94fbd9023a4d)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/hbck/HFileCorruptionChecker.java


> TestHBaseFsck fails on HBase-0.98-on-Hadoop-1.1 build
> -
>
> Key: HBASE-16400
> URL: https://issues.apache.org/jira/browse/HBASE-16400
> Project: HBase
>  Issue Type: Test
>Affects Versions: 0.98.21
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 0.98.22
>
> Attachments: 16400-0.98.v1.txt
>
>
> From 
> https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1259/testReport/org.apache.hadoop.hbase.util/TestHBaseFsck/testQuarantineMissingRegionDir/
>  :
> {code}
> java.lang.NullPointerException: null
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker.checkRegionDir(HFileCorruptionChecker.java:201)
>   at 
> org.apache.hadoop.hbase.util.TestHBaseFsck$3$1.checkRegionDir(TestHBaseFsck.java:2013)
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker$RegionDirChecker.call(HFileCorruptionChecker.java:293)
>   at 
> org.apache.hadoop.hbase.util.hbck.HFileCorruptionChecker$RegionDirChecker.call(HFileCorruptionChecker.java:284)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> {code}
> Local run with hadoop-1.1 reproduced the above test failure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16404) Make DeleteBloomFilters work with BloomContext

2016-08-12 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16404:


FAILURE: Integrated in HBase-Trunk_matrix #1402 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1402/])
HBASE-16404 Make DeleteBloomFilters work with BloomContext (Ram) (ramkrishna: 
rev 65c03b058c7b4a74f991acc07958be5e7d0e05e6)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileWriter.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomContext.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/util/RowBloomContext.java


> Make DeleteBloomFilters work with BloomContext
> --
>
> Key: HBASE-16404
> URL: https://issues.apache.org/jira/browse/HBASE-16404
> Project: HBase
>  Issue Type: Sub-task
>  Components: Compaction
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16404.patch, HBASE-16404_1.patch
>
>
> Since we have added BloomFiltercontext to work with RowBlooms the same can be 
> applied for DeleteBloomFilters also. Should be a simple change considering we 
> have the infrastructure in place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16341) Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16341:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1421 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1421/])
HBASE-16341 Missing bit on "Regression: Random Read/WorkloadC slower in (stack: 
rev 907ac1f6552e9e1cd7e33adeaf51fda2f3f19734)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java


> Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"
> --
>
> Key: HBASE-16341
> URL: https://issues.apache.org/jira/browse/HBASE-16341
> Project: HBase
>  Issue Type: Bug
>  Components: rpc
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16341.master.001.patch, HBASE-16341.patch, 
> HBASE-16341.patch
>
>
> [~larsgeorge] found a missing bit in HBASE-15971 "Regression: Random 
> Read/WorkloadC slower in 1.x than 0.98" Let me fix here. Let me quote the man:
> {code}
> BTW, in constructor we do this
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
> CALL_QUEUE_TYPE_FIFO_CONF_VALUE);
> ```
> (edited)
> [8:19]  
> but in `onConfigurationChange()` we do
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
>   CALL_QUEUE_TYPE_DEADLINE_CONF_VALUE);
> ```
> (edited)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16341) Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16341:


FAILURE: Integrated in Jenkins build HBase-1.3-IT #791 (See 
[https://builds.apache.org/job/HBase-1.3-IT/791/])
HBASE-16341 Missing bit on "Regression: Random Read/WorkloadC slower in (stack: 
rev f320166142c00b8bb60574d3ba7b586c07c6780c)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java


> Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"
> --
>
> Key: HBASE-16341
> URL: https://issues.apache.org/jira/browse/HBASE-16341
> Project: HBase
>  Issue Type: Bug
>  Components: rpc
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16341.master.001.patch, HBASE-16341.patch, 
> HBASE-16341.patch
>
>
> [~larsgeorge] found a missing bit in HBASE-15971 "Regression: Random 
> Read/WorkloadC slower in 1.x than 0.98" Let me fix here. Let me quote the man:
> {code}
> BTW, in constructor we do this
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
> CALL_QUEUE_TYPE_FIFO_CONF_VALUE);
> ```
> (edited)
> [8:19]  
> but in `onConfigurationChange()` we do
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
>   CALL_QUEUE_TYPE_DEADLINE_CONF_VALUE);
> ```
> (edited)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16341) Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16341:


FAILURE: Integrated in Jenkins build HBase-1.4 #351 (See 
[https://builds.apache.org/job/HBase-1.4/351/])
HBASE-16341 Missing bit on "Regression: Random Read/WorkloadC slower in (stack: 
rev 6976a7b3125e851df8558ca4cc505daeff24adf6)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java


> Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"
> --
>
> Key: HBASE-16341
> URL: https://issues.apache.org/jira/browse/HBASE-16341
> Project: HBase
>  Issue Type: Bug
>  Components: rpc
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16341.master.001.patch, HBASE-16341.patch, 
> HBASE-16341.patch
>
>
> [~larsgeorge] found a missing bit in HBASE-15971 "Regression: Random 
> Read/WorkloadC slower in 1.x than 0.98" Let me fix here. Let me quote the man:
> {code}
> BTW, in constructor we do this
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
> CALL_QUEUE_TYPE_FIFO_CONF_VALUE);
> ```
> (edited)
> [8:19]  
> but in `onConfigurationChange()` we do
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
>   CALL_QUEUE_TYPE_DEADLINE_CONF_VALUE);
> ```
> (edited)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16341) Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16341:


FAILURE: Integrated in Jenkins build HBase-1.3 #817 (See 
[https://builds.apache.org/job/HBase-1.3/817/])
HBASE-16341 Missing bit on "Regression: Random Read/WorkloadC slower in (stack: 
rev f320166142c00b8bb60574d3ba7b586c07c6780c)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java


> Missing bit on "Regression: Random Read/WorkloadC slower in 1.x than 0.98"
> --
>
> Key: HBASE-16341
> URL: https://issues.apache.org/jira/browse/HBASE-16341
> Project: HBase
>  Issue Type: Bug
>  Components: rpc
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16341.master.001.patch, HBASE-16341.patch, 
> HBASE-16341.patch
>
>
> [~larsgeorge] found a missing bit in HBASE-15971 "Regression: Random 
> Read/WorkloadC slower in 1.x than 0.98" Let me fix here. Let me quote the man:
> {code}
> BTW, in constructor we do this
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
> CALL_QUEUE_TYPE_FIFO_CONF_VALUE);
> ```
> (edited)
> [8:19]  
> but in `onConfigurationChange()` we do
> ```String callQueueType = conf.get(CALL_QUEUE_TYPE_CONF_KEY,
>   CALL_QUEUE_TYPE_DEADLINE_CONF_VALUE);
> ```
> (edited)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16418) Reduce duration of sleep waiting for region reopen in IntegrationTestBulkLoad#installSlowingCoproc()

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16418:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1422 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1422/])
HBASE-16418 Reduce duration of sleep waiting for region reopen in (tedyu: rev 
d5080e82fb47b5499b72fbafbbc52f4f432622d3)
* (edit) 
hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestBulkLoad.java


> Reduce duration of sleep waiting for region reopen in 
> IntegrationTestBulkLoad#installSlowingCoproc()
> 
>
> Key: HBASE-16418
> URL: https://issues.apache.org/jira/browse/HBASE-16418
> Project: HBase
>  Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16418.v1.txt
>
>
> Currently we have the following code:
> {code}
> desc.addCoprocessor(SlowMeCoproScanOperations.class.getName());
> HBaseTestingUtility.modifyTableSync(admin, desc);
> //sleep for sometime. Hope is that the regions are closed/opened before
> //the sleep returns. TODO: do this better
> Thread.sleep(3);
> {code}
> Instead of sleeping for fixed duration, we should detect when the regions 
> have reopened with custom Coprocessor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16418) Reduce duration of sleep waiting for region reopen in IntegrationTestBulkLoad#installSlowingCoproc()

2016-08-15 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16418:


FAILURE: Integrated in Jenkins build HBase-1.4 #352 (See 
[https://builds.apache.org/job/HBase-1.4/352/])
HBASE-16418 Reduce duration of sleep waiting for region reopen in (tedyu: rev 
8d93b62f0402dabc77bf2cfaf7f12a6b17bf4155)
* (edit) 
hbase-it/src/test/java/org/apache/hadoop/hbase/mapreduce/IntegrationTestBulkLoad.java


> Reduce duration of sleep waiting for region reopen in 
> IntegrationTestBulkLoad#installSlowingCoproc()
> 
>
> Key: HBASE-16418
> URL: https://issues.apache.org/jira/browse/HBASE-16418
> Project: HBase
>  Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16418.v1.txt
>
>
> Currently we have the following code:
> {code}
> desc.addCoprocessor(SlowMeCoproScanOperations.class.getName());
> HBaseTestingUtility.modifyTableSync(admin, desc);
> //sleep for sometime. Hope is that the regions are closed/opened before
> //the sleep returns. TODO: do this better
> Thread.sleep(3);
> {code}
> Instead of sleeping for fixed duration, we should detect when the regions 
> have reopened with custom Coprocessor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16420) Fix source incompatibility of Table interface

2016-08-16 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16420:


FAILURE: Integrated in Jenkins build HBase-1.2 #701 (See 
[https://builds.apache.org/job/HBase-1.2/701/])
HBASE-16420 Fix source incompatibility of Table interface (Phil Yang) (stack: 
rev 45beeec0fbfe99bf41d166f00973d0c5efd025c9)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java


> Fix source incompatibility of Table interface
> -
>
> Key: HBASE-16420
> URL: https://issues.apache.org/jira/browse/HBASE-16420
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.5, 1.2.2
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 1.1.6, 1.2.3
>
> Attachments: HBASE-16420-branch-1.2-v1.patch
>
>
> HBASE-15645 broke source compatibility of Table interface. We need revert the 
> changing on branch-1.1 and branch-1.2. There is also a bugfix for timeout, so 
> we should keep the bugfix code. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16420) Fix source incompatibility of Table interface

2016-08-16 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16420:


FAILURE: Integrated in Jenkins build HBase-1.2-IT #579 (See 
[https://builds.apache.org/job/HBase-1.2-IT/579/])
HBASE-16420 Fix source incompatibility of Table interface (Phil Yang) (stack: 
rev 45beeec0fbfe99bf41d166f00973d0c5efd025c9)
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java


> Fix source incompatibility of Table interface
> -
>
> Key: HBASE-16420
> URL: https://issues.apache.org/jira/browse/HBASE-16420
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.5, 1.2.2
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 1.1.6, 1.2.3
>
> Attachments: HBASE-16420-branch-1.2-v1.patch
>
>
> HBASE-15645 broke source compatibility of Table interface. We need revert the 
> changing on branch-1.1 and branch-1.2. There is also a bugfix for timeout, so 
> we should keep the bugfix code. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16420) Fix source incompatibility of Table interface

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16420:


FAILURE: Integrated in Jenkins build HBase-1.1-JDK7 #1765 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1765/])
HBASE-16420 Fix source incompatibility of Table interface (Phil Yang) (stack: 
rev 176040bd7da31132511adb905557c9a94a17855c)
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java


> Fix source incompatibility of Table interface
> -
>
> Key: HBASE-16420
> URL: https://issues.apache.org/jira/browse/HBASE-16420
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.5, 1.2.2
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 1.1.6, 1.2.3
>
> Attachments: HBASE-16420-branch-1.2-v1.patch
>
>
> HBASE-15645 broke source compatibility of Table interface. We need revert the 
> changing on branch-1.1 and branch-1.2. There is also a bugfix for timeout, so 
> we should keep the bugfix code. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16420) Fix source incompatibility of Table interface

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16420:


FAILURE: Integrated in Jenkins build HBase-1.1-JDK8 #1851 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1851/])
HBASE-16420 Fix source incompatibility of Table interface (Phil Yang) (stack: 
rev 176040bd7da31132511adb905557c9a94a17855c)
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java


> Fix source incompatibility of Table interface
> -
>
> Key: HBASE-16420
> URL: https://issues.apache.org/jira/browse/HBASE-16420
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.5, 1.2.2
>Reporter: Phil Yang
>Assignee: Phil Yang
> Fix For: 1.1.6, 1.2.3
>
> Attachments: HBASE-16420-branch-1.2-v1.patch
>
>
> HBASE-15645 broke source compatibility of Table interface. We need revert the 
> changing on branch-1.1 and branch-1.2. There is also a bugfix for timeout, so 
> we should keep the bugfix code. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16419) check REPLICATION_SCOPE's value more stringently

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16419:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1432 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1432/])
HBASE-16419 check REPLICATION_SCOPE's value more stringently (Guangxu (tedyu: 
rev 233ca65b8f1c180f9099c0f35d6cc44fd43d5131)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java


> check REPLICATION_SCOPE's value more stringently
> 
>
> Key: HBASE-16419
> URL: https://issues.apache.org/jira/browse/HBASE-16419
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 2.0.0, 1.2.2
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16419-branch-1.2-v1.patch, 
> HBASE-16419-branch-1.2-v2.patch, HBASE-16419-v1.patch
>
>
> When create table or modify table, the master will check if the value of 
> REPLICATION_SCOPE is less than 0, however the value of REPLICATION_SCOPE must 
> be 0 or 1. Otherwise will lead to  regionserver shutdown, so I think should 
> be check the values of REPLICATION_SCOPE more stringent.
> Beginning I don't fully understand the usage of REPLICATION_SCOPE, then set 
> REPLICATION_SCOPE to 2 by mistake.when I insert data to table,the 
> regionservers abort one by one,finanly
> the cluster abort,the exceptions as follow:
> {quote}
> 2016-08-16 12:34:45,245 WARN  [regionserver/host:60023.append-pool1-t1] 
> wal.FSHLog: Append sequenceId=94, requesting roll of WAL
> java.lang.NullPointerException
> at 
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$FamilyScope$Builder.setScopeType(WALProtos.java:3939)
> at org.apache.hadoop.hbase.wal.WALKey.getBuilder(WALKey.java:618)
> at 
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogWriter.append(ProtobufLogWriter.java:118)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.append(FSHLog.java:1886)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1750)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1672)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2016-08-16 12:34:45,293 INFO  [MemStoreFlusher.0] regionserver.HStore: Added 
> hdfs://hbase-test-27/hbase1.2.2/data/default/usertable/2aa98c17845c9c6d5c8760b87b3ba09a/i/35825c94e72945c0bf7df3f0adefa1b6,
>  entries=1161600, sequenceid=59, filesize=167.6 M
> 2016-08-16 12:34:45,296 FATAL [MemStoreFlusher.0] regionserver.HRegionServer: 
> ABORTING region server hbase-10-166-141-99,60023,1471262434177: Replay of WAL 
> required. Forcing server shutdown
> org.apache.hadoop.hbase.DroppedSnapshotException: region: 
> usertable,,1471262560009.2aa98c17845c9c6d5c8760b87b3ba09a.
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2427)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2105)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2067)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1958)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.flush(HRegion.java:1884)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:510)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:471)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$900(MemStoreFlusher.java:75)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:259)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.apache.hadoop.hbase.regionserver.wal.DamagedWALException: 
> Append sequenceId=94, requesting roll of WAL
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.append(FSHLog.java:1898)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1750)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1672)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  

[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


FAILURE: Integrated in Jenkins build HBase-1.4 #353 (See 
[https://builds.apache.org/job/HBase-1.4/353/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (stack: 
rev 3d7bcd020e03ca89dccab18dd87cde453beeeafa)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.4.0, 1.3.1, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_v1.patch, 
> HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16419) check REPLICATION_SCOPE's value more stringently

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16419:


FAILURE: Integrated in Jenkins build HBase-1.4 #353 (See 
[https://builds.apache.org/job/HBase-1.4/353/])
HBASE-16419 check REPLICATION_SCOPE's value more stringently (Guangxu (tedyu: 
rev a944a198791859331f9541ee454afe810db69c45)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java


> check REPLICATION_SCOPE's value more stringently
> 
>
> Key: HBASE-16419
> URL: https://issues.apache.org/jira/browse/HBASE-16419
> Project: HBase
>  Issue Type: Improvement
>Affects Versions: 2.0.0, 1.2.2
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-16419-branch-1.2-v1.patch, 
> HBASE-16419-branch-1.2-v2.patch, HBASE-16419-v1.patch
>
>
> When create table or modify table, the master will check if the value of 
> REPLICATION_SCOPE is less than 0, however the value of REPLICATION_SCOPE must 
> be 0 or 1. Otherwise will lead to  regionserver shutdown, so I think should 
> be check the values of REPLICATION_SCOPE more stringent.
> Beginning I don't fully understand the usage of REPLICATION_SCOPE, then set 
> REPLICATION_SCOPE to 2 by mistake.when I insert data to table,the 
> regionservers abort one by one,finanly
> the cluster abort,the exceptions as follow:
> {quote}
> 2016-08-16 12:34:45,245 WARN  [regionserver/host:60023.append-pool1-t1] 
> wal.FSHLog: Append sequenceId=94, requesting roll of WAL
> java.lang.NullPointerException
> at 
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$FamilyScope$Builder.setScopeType(WALProtos.java:3939)
> at org.apache.hadoop.hbase.wal.WALKey.getBuilder(WALKey.java:618)
> at 
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogWriter.append(ProtobufLogWriter.java:118)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.append(FSHLog.java:1886)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1750)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1672)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> 2016-08-16 12:34:45,293 INFO  [MemStoreFlusher.0] regionserver.HStore: Added 
> hdfs://hbase-test-27/hbase1.2.2/data/default/usertable/2aa98c17845c9c6d5c8760b87b3ba09a/i/35825c94e72945c0bf7df3f0adefa1b6,
>  entries=1161600, sequenceid=59, filesize=167.6 M
> 2016-08-16 12:34:45,296 FATAL [MemStoreFlusher.0] regionserver.HRegionServer: 
> ABORTING region server hbase-10-166-141-99,60023,1471262434177: Replay of WAL 
> required. Forcing server shutdown
> org.apache.hadoop.hbase.DroppedSnapshotException: region: 
> usertable,,1471262560009.2aa98c17845c9c6d5c8760b87b3ba09a.
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2427)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2105)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2067)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1958)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.flush(HRegion.java:1884)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:510)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:471)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$900(MemStoreFlusher.java:75)
> at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:259)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: org.apache.hadoop.hbase.regionserver.wal.DamagedWALException: 
> Append sequenceId=94, requesting roll of WAL
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.append(FSHLog.java:1898)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1750)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1672)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.c

[jira] [Commented] (HBASE-16384) Update report-flakies.py script to allow specifying a list of build ids to be excluded

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16384:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1433 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1433/])
HBASE-16384 Update report-flakies.py script to allow specifying a list (appy: 
rev 7999bb9bd379550d0b537c088005b73ff63f1857)
* (edit) dev-support/report-flakies.py
* (edit) dev-support/findHangingTests.py


> Update report-flakies.py script to allow specifying a list of build ids to be 
> excluded
> --
>
> Key: HBASE-16384
> URL: https://issues.apache.org/jira/browse/HBASE-16384
> Project: HBase
>  Issue Type: Bug
>Reporter: Appy
>Assignee: Appy
> Fix For: 2.0.0
>
> Attachments: HBASE-16384.master.001.patch, 
> HBASE-16384.master.002.patch, HBASE-16384.master.003.patch, 
> HBASE-16384.master.004.patch, HBASE-16384.master.005.patch, 
> HBASE-16384.master.006.patch, HBASE-16384.master.007.patch, 
> HBASE-16384.master.008.patch, HBASE-16384.master.009.patch
>
>
> Sometimes, builds fail mysteriously and leave lots of tests hanging. This 
> makes  [flaky 
> list|https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
>  go crazy.
> This patch adds that feature to specify build ids to exclude in 
> report-flakies.py.
> If we find that a build screwed up, we can exclude it using "exclude=" option 
> in --urls param and rerun the job to fix the flaky list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1433 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1433/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (stack: 
rev fb4ef5357115c708b0857bdce0a0c2f4d38fdd10)
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.4.0, 1.3.1, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_v1.patch, 
> HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-12721) Create Docker container cluster infrastructure to enable better testing

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-12721:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1433 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1433/])
HBASE-12721 Create Docker container cluster infrastructure to enable (busbey: 
rev ccf5d27d7aa238c8398d2818928a71f39bd749a0)
* (add) dev-support/apache_hbase_topology/profile.cfg
* (add) dev-support/apache_hbase_topology/Dockerfile
* (add) dev-support/apache_hbase_topology/configurations.cfg
* (add) dev-support/apache_hbase_topology/ssh/id_rsa.pub
* (add) dev-support/apache_hbase_topology/__init__.py
* (add) dev-support/apache_hbase_topology/actions.py
* (add) dev-support/apache_hbase_topology/ssh/id_rsa
* (add) dev-support/apache_hbase_topology/README.md


> Create Docker container cluster infrastructure to enable better testing
> ---
>
> Key: HBASE-12721
> URL: https://issues.apache.org/jira/browse/HBASE-12721
> Project: HBase
>  Issue Type: New Feature
>  Components: build, community, documentation, test
>Reporter: Dima Spivak
>Assignee: Dima Spivak
> Fix For: 2.0.0
>
> Attachments: HBASE-12721_v5.patch, HBASE-12721_v6.patch, 
> HBASE-12721_v7.patch
>
>
> Some simple work on using HBase with Docker was committed into /dev-support 
> as "hbase_docker;" all this did was stand up a standalone cluster from source 
> and start a shell. Now seems like a good time to extend this to be useful for 
> applications that could actual benefit the community, especially around 
> testing. Some ideas:
> - Integration testing would be much more accessible if people could stand up 
> distributed HBase clusters on a single host machine in a couple minutes and 
> run our awesome hbase-it suite against it.
> - Binary compatibility testing of an HBase client is easiest when standing up 
> an HBase cluster can be done once and then different client source/binary 
> permutations run against it.
> - Upgrade testing, and especially rolling upgrade testing, doesn't have any 
> upstream automation on build.apache.org, in part because it's a pain to set 
> up x-node clusters on Apache infrastructure.
> This proposal, whether it stays under /dev-support or moves out into it's own 
> top-level module ("hbase-docker" would conveniently fit the existing schema 
> :-)), strives to create a simple framework for deploying "distributed," 
> multi-container Apache HBase clusters.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16422) Tighten our guarantees on compatibility across patch versions

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16422:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1433 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1433/])
HBASE-16422 Tighten our guarantees on compatibility across patch (stack: rev 
2261c8c31a46fc79d9b930db90752ab60945b74a)
* (edit) src/main/asciidoc/_chapters/upgrading.adoc


> Tighten our guarantees on compatibility across patch versions
> -
>
> Key: HBASE-16422
> URL: https://issues.apache.org/jira/browse/HBASE-16422
> Project: HBase
>  Issue Type: Improvement
>  Components: documentation
>Reporter: stack
>Assignee: stack
> Attachments: HBASE-16422.master.001.patch, 
> HBASE-16422.master.002.patch
>
>
> Out of the dev discussion [1], comes this change that tightens up our 
> guarantees adding new API; that we'll do it in a non-breaking way across 
> patch versions.
> 1. http://mail-archives.apache.org/mod_mbox/hbase-dev/201608.mbox/browser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1433 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1433/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
cc12be39e568b873c7699e38c18d299db037453b)
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev e51fcdd7788271d33cf02240155429358d71627b)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-1.3-IT #792 (See 
[https://builds.apache.org/job/HBase-1.3-IT/792/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
75950de09ea9b0f1dc893f0724c73fb2a618e4ed)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) pom.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev 4e78f7a99e4d3fd264fb64446b52bf082b4ee6e6)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-1.4 #354 (See 
[https://builds.apache.org/job/HBase-1.4/354/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
df4953c22e8578922d5f4fa77b7a78c30a9b0a1a)
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev 0175e432c81bb97070e0d584689e41f368ace82a)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-1.3 #818 (See 
[https://builds.apache.org/job/HBase-1.3/818/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
75950de09ea9b0f1dc893f0724c73fb2a618e4ed)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) pom.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev 4e78f7a99e4d3fd264fb64446b52bf082b4ee6e6)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1766 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1766/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
5eb0a540f885c99a87a55a2c38765a1a89a16bdc)
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) pom.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev d82cf96f2253cbd5bf7684f5d6ffb5642a44e739)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16378) Procedure v2 - Make ProcedureException extend HBaseException

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16378:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1434 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1434/])
HBASE-16378 Procedure v2 - Make ProcedureException extend HBaseException 
(matteo.bertozzi: rev e637a61e26aeb442ea1c1593fdbd0b15b48f5642)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/RemoteProcedureException.java
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/ProcedureException.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/ForeignExceptionUtil.java


> Procedure v2 - Make ProcedureException extend HBaseException
> 
>
> Key: HBASE-16378
> URL: https://issues.apache.org/jira/browse/HBASE-16378
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Trivial
> Fix For: 2.0.0
>
> Attachments: HBASE-16378-v0.patch, HBASE-16378-v1.patch
>
>
> Make ProcedureException extend HBaseException, so we can avoid stuff like 
> HBASE-15591. and avoid try/catch ProcedureException and direct rethrows



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #3 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/3/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
3f30d420c773ab173252d2bfadf2df095d715878)
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev ca1b49dd04db6d94b19dc097c52df763baa60f39)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #3 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/3/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
3f30d420c773ab173252d2bfadf2df095d715878)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev ca1b49dd04db6d94b19dc097c52df763baa60f39)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


FAILURE: Integrated in Jenkins build HBase-1.4 #355 (See 
[https://builds.apache.org/job/HBase-1.4/355/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
e05b002ed53c20cb885e773c7189efe90977858a)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.r

[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


FAILURE: Integrated in Jenkins build HBase-1.3 #819 (See 
[https://builds.apache.org/job/HBase-1.3/819/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
e3ed8ecdb3ce7ee727b525f88bc58650559ebc7e)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.r

[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #4 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/4/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
e09b52fdb182135100d759d76ae7cee15007dd11)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Wo

[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #4 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/4/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (chenheng: 
rev a84ff653ad2af8102d2acbf6102634b477cb7c8b)
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.0.4, 1.4.0, 1.1.6, 1.3.1, 1.2.3, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_branch-1.2.patch, 
> HBASE-15635_v1.patch, HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


FAILURE: Integrated in Jenkins build HBase-1.3-IT #793 (See 
[https://builds.apache.org/job/HBase-1.3-IT/793/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
e3ed8ecdb3ce7ee727b525f88bc58650559ebc7e)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Wo

[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1435 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1435/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
642d2fe0f8d82b8ed5b9738baca0c1e2551272d4)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadP

[jira] [Commented] (HBASE-16426) Remove company affiliations from committer list

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16426:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1435 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1435/])
HBASE-16426 Remove organization affiliations from developer list 
(mstanleyjones: rev e60a4302fd35fb13b5a93d8798126f996c5f59f3)
* (edit) pom.xml


> Remove company affiliations from committer list
> ---
>
> Key: HBASE-16426
> URL: https://issues.apache.org/jira/browse/HBASE-16426
> Project: HBase
>  Issue Type: Task
>  Components: documentation, website
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-16426.patch
>
>
> An email thread on the dev mailing list came to the consensus that company 
> affiliations in the committer list are difficult to keep up to date and not 
> worth it. This JIRA is to track removing them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #4 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/4/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (chenheng: 
rev a84ff653ad2af8102d2acbf6102634b477cb7c8b)
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.0.4, 1.4.0, 1.1.6, 1.3.1, 1.2.3, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_branch-1.2.patch, 
> HBASE-15635_v1.patch, HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #4 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/4/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
e09b52fdb182135100d759d76ae7cee15007dd11)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Wo

[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1767 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1767/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
b3d69bc029a3b8a4db29b3c266c16643108938dd)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecu

[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1767 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1767/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (chenheng: 
rev 941ad56e7fac6defe4978a35e46f28098f3e1439)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.0.4, 1.4.0, 1.1.6, 1.3.1, 1.2.3, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_branch-1.2.patch, 
> HBASE-15635_v1.patch, HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1852 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1852/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
5eb0a540f885c99a87a55a2c38765a1a89a16bdc)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev d82cf96f2253cbd5bf7684f5d6ffb5642a44e739)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16429) FSHLog: deadlock if rollWriter called when ring buffer filled with appends

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16429:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1852 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1852/])
HBASE-16429 FSHLog: deadlock if rollWriter called when ring buffer (liyu: rev 
b3d69bc029a3b8a4db29b3c266c16643108938dd)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java


> FSHLog: deadlock if rollWriter called when ring buffer filled with appends
> --
>
> Key: HBASE-16429
> URL: https://issues.apache.org/jira/browse/HBASE-16429
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 1.1.2, 1.2.2
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 1.1.7
>
> Attachments: HBASE-16429.patch
>
>
> Recently we experienced an online problem that all handlers are stuck. 
> Checking the jstack we could see all handler threads waiting for 
> RingBuffer.next, while the single ring buffer consumer dead waiting for 
> {{safePointReleasedLatch}} to count down:
> {noformat}
> Normal handler thread:
> "B.defaultRpcServer.handler=126,queue=9,port=16020" daemon prio=10 
> tid=0x7efd4b44f800 nid=0x15f29 runnable [0x7efd3db7b000]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:349)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136)
> at 
> com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105)
> at com.lmax.disruptor.RingBuffer.next(RingBuffer.java:246)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog.append(FSHLog.java:1222)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutation(HRegion.java:3188)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:2819)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:736)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:698)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2095)
> at 
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32213)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:774)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:102)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:756)
> RingBufferEventHandler thread waiting for safePointReleasedLatch:
> "regionserver/hadoop0369.et2.tbsite.net/11.251.152.226:16020.append-pool2-t1" 
> prio=10 tid=0x7efd320d nid=0x1777b waiting on condition 
> [0x7efd2d2fa000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7f01b48d9178> (a 
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$SafePointZigZagLatch.safePointAttained(FSHLog.java:1866)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.attainSafePoint(FSHLog.java:2066)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.wal.FSHLog$RingBufferEventHandler.onEvent(FSHLog.java:1909)
> at 
> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecu

[jira] [Commented] (HBASE-15635) Mean age of Blocks in cache (seconds) on webUI should be greater than zero

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-15635:


SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1852 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1852/])
HBASE-15635 Mean age of Blocks in cache (seconds) on webUI should be (chenheng: 
rev 941ad56e7fac6defe4978a35e46f28098f3e1439)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheStats.java
* (edit) 
hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/regionserver/BlockCacheTmpl.jamon
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java


> Mean age of Blocks in cache (seconds) on webUI should be greater than zero
> --
>
> Key: HBASE-15635
> URL: https://issues.apache.org/jira/browse/HBASE-15635
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.17
>Reporter: Heng Chen
>Assignee: Heng Chen
> Fix For: 2.0.0, 1.0.4, 1.4.0, 1.1.6, 1.3.1, 1.2.3, 0.98.22
>
> Attachments: 0.98.png, 7BFFAF68-0807-400C-853F-706B498449E1.png, 
> HBASE-15635.0.98.patch, HBASE-15635.patch, HBASE-15635_branch-1.2.patch, 
> HBASE-15635_v1.patch, HBASE-15635_v2.patch, HBASE-15635_v2.patch, master.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-0.98-matrix #388 (See 
[https://builds.apache.org/job/HBase-0.98-matrix/388/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
0f455127b3e6f080400f09b76d87cfd1be8cbc81)
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev efe57b1962780ee3fd04778f4f1f3a2dacbc2a1c)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-0.98-on-Hadoop-1.1 #1261 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1261/])
HBASE-16318 consistently use the correct name for 'Apache License, (busbey: rev 
0f455127b3e6f080400f09b76d87cfd1be8cbc81)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* (edit) pom.xml
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml
HBASE-16318 fail build while rendering velocity template if dependency (busbey: 
rev efe57b1962780ee3fd04778f4f1f3a2dacbc2a1c)
* (edit) hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16094) Procedure v2 - Improve cleaning up of proc wals

2016-08-18 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16094:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1439 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1439/])
HBASE-16094 Improve cleaning up of proc wals. Makes the proc log cleaner (appy: 
rev ce88270340872b43083ee7b79ac3027557597224)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/ProcedureStoreTracker.java
* (edit) 
hbase-procedure/src/test/java/org/apache/hadoop/hbase/procedure2/store/wal/TestWALProcedureStore.java
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/WALProcedureStore.java
* (edit) 
hbase-procedure/src/test/java/org/apache/hadoop/hbase/procedure2/store/TestProcedureStoreTracker.java
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFormat.java
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALFile.java


> Procedure v2 - Improve cleaning up of proc wals
> ---
>
> Key: HBASE-16094
> URL: https://issues.apache.org/jira/browse/HBASE-16094
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Reporter: Appy
>Assignee: Appy
> Fix For: 2.0.0
>
> Attachments: HBASE-16094.master.001.patch, 
> HBASE-16094.master.002.patch, HBASE-16094.master.003.patch, 
> HBASE-16094.master.004.patch, HBASE-16094.master.005.patch, 
> HBASE-16094.master.006.patch
>
>
> Avoid accumulating too many wals.
> We remove logs in 3 cases:
>  - No procedures are running. We can remove all the logs.
>  - All procedures are updated/written in the last log. We can remove all the 
> logs, aside the active one.  
>  - Remove log if does not contains “active” procIds
> https://github.com/apache/hbase/blob/master/hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/WALProcedureStore.java#L865
> The last point, Remove log if does not contains “active” procIds, needs to be 
> improved. Basically, even if a log contains state of an active proc, we can 
> delete it if a later log contains a newer state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16405) Change read path Bloom check to work with Cells with out any copy

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16405:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1442 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1442/])
HBASE-16405 Change read path Bloom check to work with Cells with out any 
(anoopsamjohn: rev 5f61f9cc5c9333d474ceb1e3cae555f5fd7ab623)
* (edit) 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/PerformanceEvaluation.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileReader.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilter.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/MurmurHash3.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/JenkinsHash.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterChunk.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/RowColBloomHashKey.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CompoundBloomFilter.java
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/MurmurHash.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/RowBloomHashKey.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/Hash.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestBloomFilterChunk.java
* (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/HashKey.java
* (edit) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteArrayHashKey.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/BloomFilterUtil.java


> Change read path Bloom check to work with Cells with out any copy
> -
>
> Key: HBASE-16405
> URL: https://issues.apache.org/jira/browse/HBASE-16405
> Project: HBase
>  Issue Type: Sub-task
>  Components: Compaction
>Reporter: ramkrishna.s.vasudevan
>Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-16405.patch, HBASE-16405_V2.patch, 
> HBASE-16405_V3.patch, HBASE-16405_V4.patch, HBASE-16405_V4.patch
>
>
> Currently the read path though it works with Cells, still does go with the 
> assumption that we need to copy the Cells to KeyValue's key format and then 
> use the byte[] version of hash() function to calculate the Bloom hash. In 
> case of incoming cell's being KeyValue type we try to use the 
> KeyValue.getKey(), KeyValue.getKeyOffset() APIs. With this sub-task we will 
> get rid of all those and things will work with Cells. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1444 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1444/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev 34b668b0a9e02ffb05cb4e25127dee674482520a)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16434) Improve flaky dashboard

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16434:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1444 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1444/])
HBASE-16434 - Add date and count of flaky tests - Sort tests by (appy: rev 
0d6c4d92edd7adfbe902cbd1cce53964c8855406)
* (edit) dev-support/flaky-dashboard-template.html
* (edit) dev-support/findHangingTests.py
* (edit) dev-support/report-flakies.py


> Improve flaky dashboard
> ---
>
> Key: HBASE-16434
> URL: https://issues.apache.org/jira/browse/HBASE-16434
> Project: HBase
>  Issue Type: Improvement
>Reporter: Appy
>Assignee: Appy
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-16434.master.001.patch, 
> HBASE-16434.master.002.patch, HBASE-16434.master.003.patch
>
>
> - Sort list of tests in descending order of flakyness
> - add date and flaky tests count
> - local hrefs to job results



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16430) Fix RegionServer Group's bug when moving multiple tables

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16430:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1444 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1444/])
Revert commit for HBASE-16430 which didn't have JIRA number (tedyu: rev 
fbd87f91bc968172b0347ec45d5686c7444ea665)
* (edit) 
hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java
* (edit) 
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java
HBASE-16430 Fix RegionServer Group's bug when moving multiple tables (tedyu: 
rev 741d0a4511b9c397b2eb821aef49e858e217bf1e)
* (edit) 
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java
* (edit) 
hbase-rsgroup/src/test/java/org/apache/hadoop/hbase/rsgroup/TestRSGroupsBase.java


> Fix RegionServer Group's bug when moving multiple tables
> 
>
> Key: HBASE-16430
> URL: https://issues.apache.org/jira/browse/HBASE-16430
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Affects Versions: 2.0.0
>Reporter: Guangxu Cheng
> Fix For: 2.0.0
>
> Attachments: HBASE-16430-v1.patch, HBASE-16430-v2.patch
>
>
> It will be good when move one table at the same time. 
> However,will appear abnormal when move two or more tables at once.
> For example,move tableA and tableB from Group foo to Group bar:
> {code}
> hbase(main):001:0> get_rsgroup 'foo'
> GROUP INFORMATION 
>   
>  
> Servers:  
>   
>  
> hbase-rs1:60020   
>   
> 
> Tables:   
>   
>  
> tableA
>   
>  
> tableB
>   
>  
> 5 row(s) in 0.2800 seconds
> hbase(main):002:0> get_rsgroup 'bar'
> GROUP INFORMATION 
>   
>  
> Servers:  
>   
>  
> hbase-rs2:60020   
>   
> 
> Tables:   
>   
>  
> 3 row(s) in 0.0050 seconds
> hbase(main):003:0> move_rsgroup_tables 'bar',['tableA','tableB']
> hbase(main):004:0> get_rsgroup 'foo'
> GROUP INFORMATION 
>   
>  
> Servers:  
>   
>  
> hbase-rs1:60020   
>   
> 
> Tables:   
>   
>  
> tableB
>   
>  
> 4 row(s) in 0.0120 seconds
> hbase(main):005:0> get_rsgroup 'bar'
> GROUP INFORMATION   

[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.3-IT #794 (See 
[https://builds.apache.org/job/HBase-1.3-IT/794/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev aba2b03378d2acaa033aedd2a7d775b77e05a1af)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-7621) REST client (RemoteHTable) doesn't support binary row keys

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-7621:
---

FAILURE: Integrated in Jenkins build HBase-1.4 #356 (See 
[https://builds.apache.org/job/HBase-1.4/356/])
HBASE-7621 REST client (RemoteHTable) doesn't support binary row keys 
(apurtell: rev b3ca9a9b2f91ce5d43c30113cbfbbbaf8cade9c0)
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java


> REST client (RemoteHTable) doesn't support binary row keys
> --
>
> Key: HBASE-7621
> URL: https://issues.apache.org/jira/browse/HBASE-7621
> Project: HBase
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 0.94.0, 0.95.2, 0.98.4, 2.0.0
>Reporter: Craig Muchinsky
>Assignee: Keith David Winkler
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-7621.master.001.patch
>
>
> The REST server doesn't seem to support using binary (MD5 for example) row 
> keys. I believe the root cause of this is the use of Bytes.toBytes() in the 
> RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() 
> within RemoteHTable.buildRowSpec(), I believe the converse function 
> Bytes.toBytesBinary() should be used for row key parsing in 
> RowSpec.parseRowKeys().
> I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding 
> the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which 
> performs URL decoding for both the start and stop row keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.4 #356 (See 
[https://builds.apache.org/job/HBase-1.4/356/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev a857a60ccb969387ff66b3dfcf736a14b2785120)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.3 #820 (See 
[https://builds.apache.org/job/HBase-1.3/820/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev aba2b03378d2acaa033aedd2a7d775b77e05a1af)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #6 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/6/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev 444910ec7c57f703d80bcb95ca325d8c0c0d9ffe)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-7621) REST client (RemoteHTable) doesn't support binary row keys

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-7621:
---

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1445 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1445/])
HBASE-7621 REST client (RemoteHTable) doesn't support binary row keys 
(apurtell: rev 7145e46b7afd6d76df1ef001557c7b60bfc6055b)
* (edit) 
hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java
* (edit) 
hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/client/TestRemoteTable.java


> REST client (RemoteHTable) doesn't support binary row keys
> --
>
> Key: HBASE-7621
> URL: https://issues.apache.org/jira/browse/HBASE-7621
> Project: HBase
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 0.94.0, 0.95.2, 0.98.4, 2.0.0
>Reporter: Craig Muchinsky
>Assignee: Keith David Winkler
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-7621.master.001.patch
>
>
> The REST server doesn't seem to support using binary (MD5 for example) row 
> keys. I believe the root cause of this is the use of Bytes.toBytes() in the 
> RowSpec.parseRowKeys() method. Based on the use of Bytes.toStringBinary() 
> within RemoteHTable.buildRowSpec(), I believe the converse function 
> Bytes.toBytesBinary() should be used for row key parsing in 
> RowSpec.parseRowKeys().
> I also noticed that the RemoteHTable.buildRowSpec() method isn't URL encoding 
> the row key, which is a mismatch to the logic in RowSpec.parseRowKeys() which 
> performs URL decoding for both the start and stop row keys.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #6 (See 
[https://builds.apache.org/job/HBase-1.2-JDK7/6/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev 444910ec7c57f703d80bcb95ca325d8c0c0d9ffe)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.1-JDK8 #1853 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1853/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev 1c92f4c0be0fb03a1385e718cf98d7a05e1fce82)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16452) Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool

2016-08-19 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16452:


FAILURE: Integrated in Jenkins build HBase-1.1-JDK7 #1768 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1768/])
HBASE-16452 Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool 
(matteo.bertozzi: rev 1c92f4c0be0fb03a1385e718cf98d7a05e1fce82)
* (edit) 
hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/store/wal/ProcedureWALPrettyPrinter.java


> Procedure v2 - Make ProcedureWALPrettyPrinter extend Tool
> -
>
> Key: HBASE-16452
> URL: https://issues.apache.org/jira/browse/HBASE-16452
> Project: HBase
>  Issue Type: Sub-task
>  Components: proc-v2
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
>Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.1.6, 1.2.3
>
> Attachments: HBASE-16452-v0.patch
>
>
> Make the ProcedureWALPrettyPrinter tool extend Tool, and adjust a couple of 
> print without new line



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-20 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-0.98-matrix #389 (See 
[https://builds.apache.org/job/HBase-0.98-matrix/389/])
HBASE-16318 ADDENDUM additional Apache License references for Hadoop 1.1 
(busbey: rev 3186d3d706d0b3248874aafc5997002d88837f4d)
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch, HBASE-16318.v3addendum.0.98.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16318) fail build if license isn't in whitelist

2016-08-20 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16318:


FAILURE: Integrated in Jenkins build HBase-0.98-on-Hadoop-1.1 #1262 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1262/])
HBASE-16318 ADDENDUM additional Apache License references for Hadoop 1.1 
(busbey: rev 3186d3d706d0b3248874aafc5997002d88837f4d)
* (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml


> fail build if license isn't in whitelist
> 
>
> Key: HBASE-16318
> URL: https://issues.apache.org/jira/browse/HBASE-16318
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, dependencies
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.3, 0.98.22, 1.1.7
>
> Attachments: HBASE-16318.0.patch, HBASE-16318.1.patch, 
> HBASE-16318.2.patch, HBASE-16318.3.patch, HBASE-16318.v3addendum.0.98.patch
>
>
> we use supplemental-models.xml to make sure we have consistent names and 
> descriptions for licenses. we also know what licenses we expect to see in our 
> build. If we see a different one
> # fail the velocity template process
> # if possible, include some information about why this happened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16409) Row key for bad row should be properly delimited in VerifyReplication

2016-08-20 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16409:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1452 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1452/])
HBASE-16409 Row key for bad row should be properly delimited in (tedyu: rev 
d077219d3a5f6f9393b1ae66a3db75503632e02a)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java


> Row key for bad row should be properly delimited in VerifyReplication
> -
>
> Key: HBASE-16409
> URL: https://issues.apache.org/jira/browse/HBASE-16409
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
>  Labels: replication
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16409.v1.txt, 16409.v2.txt
>
>
> In logFailRowAndIncreaseCounter():
> {code}
>   LOG.error(counter.toString() + ", rowkey=" + 
> Bytes.toString(row.getRow()));
> {code}
> In some cases, the row key has trailing whitespace(s).
> The whitespace wouldn't be easily observable in the above log.
> A delimiter should be put toward the end of the log line.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16409) Row key for bad row should be properly delimited in VerifyReplication

2016-08-20 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16409:


FAILURE: Integrated in Jenkins build HBase-1.4 #357 (See 
[https://builds.apache.org/job/HBase-1.4/357/])
HBASE-16409 Row key for bad row should be properly delimited in (tedyu: rev 
d260108e39eb41853fa5856885db82236cf3dbca)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java


> Row key for bad row should be properly delimited in VerifyReplication
> -
>
> Key: HBASE-16409
> URL: https://issues.apache.org/jira/browse/HBASE-16409
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
>  Labels: replication
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16409.v1.txt, 16409.v2.txt
>
>
> In logFailRowAndIncreaseCounter():
> {code}
>   LOG.error(counter.toString() + ", rowkey=" + 
> Bytes.toString(row.getRow()));
> {code}
> In some cases, the row key has trailing whitespace(s).
> The whitespace wouldn't be easily observable in the above log.
> A delimiter should be put toward the end of the log line.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16455) Provide API for obtaining all the WAL files

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16455:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1460 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1460/])
HBASE-16455 Provide API for obtaining all the WAL files (tedyu: rev 
f174fec391f604f56c12cbc3ad6062d7fe640866)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/AbstractFSWAL.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/DisabledWALProvider.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/MockRegionServer.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/AbstractFSWALProvider.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALProvider.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALFactory.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/RegionGroupingProvider.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/MockRegionServerServices.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/IOTestProvider.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionServerServices.java


> Provide API for obtaining all the WAL files
> ---
>
> Key: HBASE-16455
> URL: https://issues.apache.org/jira/browse/HBASE-16455
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16455.branch-1.v4.txt, 16455.branch-1.v5.txt, 
> 16455.v1.txt, 16455.v2.txt, 16455.v3.txt, 16455.v4.txt, 16455.v5.txt
>
>
> Currently RegionServerServices has the following API:
> {code}
>   WAL getWAL(HRegionInfo regionInfo) throws IOException;
> {code}
> Caller can only obtain filenum for a specific WAL.
> When multi wal is in use, we should add API for obtaining highest file number 
> among all the outstanding WAL files.
> User can pass null to getWAL() method above, but the filenum for the returned 
> WAL may not be the highest among all the WAL files.
> See log snippet in the first comment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16455) Provide API for obtaining all the WAL files

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16455:


FAILURE: Integrated in Jenkins build HBase-1.4 #358 (See 
[https://builds.apache.org/job/HBase-1.4/358/])
HBASE-16455 Provide API for obtaining all the WAL files (tedyu: rev 
2a35019a31e5616b364a0363b3ee1be1d3aaefcf)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/DisabledWALProvider.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/FSHLog.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALProvider.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/DefaultWALProvider.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/wal/IOTestProvider.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/RegionGroupingProvider.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/MockRegionServer.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALFactory.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionServerServices.java


> Provide API for obtaining all the WAL files
> ---
>
> Key: HBASE-16455
> URL: https://issues.apache.org/jira/browse/HBASE-16455
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 16455.branch-1.v4.txt, 16455.branch-1.v5.txt, 
> 16455.v1.txt, 16455.v2.txt, 16455.v3.txt, 16455.v4.txt, 16455.v5.txt
>
>
> Currently RegionServerServices has the following API:
> {code}
>   WAL getWAL(HRegionInfo regionInfo) throws IOException;
> {code}
> Caller can only obtain filenum for a specific WAL.
> When multi wal is in use, we should add API for obtaining highest file number 
> among all the outstanding WAL files.
> User can pass null to getWAL() method above, but the filenum for the returned 
> WAL may not be the highest among all the WAL files.
> See log snippet in the first comment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16467) Move AbstractHBaseTool to hbase-common

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16467:


FAILURE: Integrated in Jenkins build HBase-1.4 #359 (See 
[https://builds.apache.org/job/HBase-1.4/359/])
HBASE-16467 Move AbstractHBaseTool to hbase-common. (appy: rev 
a8909f5cbad6f68426d433861319063272762336)
* (add) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java
* (delete) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java


> Move AbstractHBaseTool to hbase-common
> --
>
> Key: HBASE-16467
> URL: https://issues.apache.org/jira/browse/HBASE-16467
> Project: HBase
>  Issue Type: Task
>Reporter: Appy
>Assignee: Appy
>Priority: Trivial
> Attachments: HBASE-16467.master.001.patch
>
>
> So it can be used by perf tools going to be added in hbase-procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16467) Move AbstractHBaseTool to hbase-common

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16467:


FAILURE: Integrated in Jenkins build HBase-1.3 #821 (See 
[https://builds.apache.org/job/HBase-1.3/821/])
HBASE-16467 Move AbstractHBaseTool to hbase-common. (appy: rev 
b30ad10a99389bb1e014c11583a2485cc8cf87fe)
* (delete) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java
* (add) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java


> Move AbstractHBaseTool to hbase-common
> --
>
> Key: HBASE-16467
> URL: https://issues.apache.org/jira/browse/HBASE-16467
> Project: HBase
>  Issue Type: Task
>Reporter: Appy
>Assignee: Appy
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3, 0.98.22
>
> Attachments: HBASE-16467.master.001.patch
>
>
> So it can be used by perf tools going to be added in hbase-procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16467) Move AbstractHBaseTool to hbase-common

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16467:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1464 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1464/])
HBASE-16467 Move AbstractHBaseTool to hbase-common. (appy: rev 
ae42a934d81e6b79cc07e6ff3f74383ed3e306e2)
* (delete) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java
* (add) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java


> Move AbstractHBaseTool to hbase-common
> --
>
> Key: HBASE-16467
> URL: https://issues.apache.org/jira/browse/HBASE-16467
> Project: HBase
>  Issue Type: Task
>Reporter: Appy
>Assignee: Appy
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3, 0.98.22
>
> Attachments: HBASE-16467.master.001.patch
>
>
> So it can be used by perf tools going to be added in hbase-procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16467) Move AbstractHBaseTool to hbase-common

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16467:


FAILURE: Integrated in Jenkins build HBase-1.3-IT #795 (See 
[https://builds.apache.org/job/HBase-1.3-IT/795/])
HBASE-16467 Move AbstractHBaseTool to hbase-common. (appy: rev 
b30ad10a99389bb1e014c11583a2485cc8cf87fe)
* (delete) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java
* (add) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java


> Move AbstractHBaseTool to hbase-common
> --
>
> Key: HBASE-16467
> URL: https://issues.apache.org/jira/browse/HBASE-16467
> Project: HBase
>  Issue Type: Task
>Reporter: Appy
>Assignee: Appy
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3, 0.98.22
>
> Attachments: HBASE-16467.master.001.patch
>
>
> So it can be used by perf tools going to be added in hbase-procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16450) Shell tool to dump replication queues

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16450:


FAILURE: Integrated in Jenkins build HBase-1.3 #822 (See 
[https://builds.apache.org/job/HBase-1.3/822/])
HBASE-16450 Shell tool to dump replication queues (esteban: rev 
c3ccbbc8dc2a8fbbdf54dc82458aa7bb477a8a6a)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java
* (add) 
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/DumpReplicationQueues.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java


> Shell tool to dump replication queues 
> --
>
> Key: HBASE-16450
> URL: https://issues.apache.org/jira/browse/HBASE-16450
> Project: HBase
>  Issue Type: Improvement
>  Components: Operability, Replication
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16450.branch-1.001.patch, 
> HBASE-16450.branch-1.002.patch, HBASE-16450.master.001.patch, 
> HBASE-16450.master.002.patch, HBASE-16450.master.003.patch
>
>
> Currently there is no way to dump list of the configured queues and the 
> replication queues when replication is enabled. Unfortunately the HBase 
> master only offers an option to dump the whole content of the znodes but not 
> details on the queues being processed on each RS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16467) Move AbstractHBaseTool to hbase-common

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16467:


SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #7 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/7/])
HBASE-16467 Move AbstractHBaseTool to hbase-common. (appy: rev 
4ef97c32bfbb42311cd8d38236c5e47ad3f56078)
* (add) 
hbase-common/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java
* (delete) 
hbase-server/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java


> Move AbstractHBaseTool to hbase-common
> --
>
> Key: HBASE-16467
> URL: https://issues.apache.org/jira/browse/HBASE-16467
> Project: HBase
>  Issue Type: Task
>Reporter: Appy
>Assignee: Appy
>Priority: Trivial
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.6, 1.2.3, 0.98.22
>
> Attachments: HBASE-16467.master.001.patch
>
>
> So it can be used by perf tools going to be added in hbase-procedure.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-16450) Shell tool to dump replication queues

2016-08-22 Thread Hudson (JIRA)

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

Hudson commented on HBASE-16450:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1465 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1465/])
HBASE-16450 Shell tool to dump replication queues (esteban: rev 
abc64fa69fcdff41611e1b4bd64e67f54617a28a)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java
* (add) 
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/DumpReplicationQueues.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java


> Shell tool to dump replication queues 
> --
>
> Key: HBASE-16450
> URL: https://issues.apache.org/jira/browse/HBASE-16450
> Project: HBase
>  Issue Type: Improvement
>  Components: Operability, Replication
>Affects Versions: 2.0.0, 1.3.0, 1.1.5, 1.2.2
>Reporter: Esteban Gutierrez
>Assignee: Esteban Gutierrez
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-16450.branch-1.001.patch, 
> HBASE-16450.branch-1.002.patch, HBASE-16450.master.001.patch, 
> HBASE-16450.master.002.patch, HBASE-16450.master.003.patch
>
>
> Currently there is no way to dump list of the configured queues and the 
> replication queues when replication is enabled. Unfortunately the HBase 
> master only offers an option to dump the whole content of the znodes but not 
> details on the queues being processed on each RS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


<    1   2   3   4   5   6   7   8   9   10   >