[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-17 Thread Hudson (JIRA)

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

Hudson commented on HBASE-18533:


FAILURE: Integrated in Jenkins build HBASE-14070.HLC #233 (See 
[https://builds.apache.org/job/HBASE-14070.HLC/233/])
HBASE-18533 Expose BucketCache values to be configured (tedyu: rev 
0e32869f01697abf29292aa786d0cdcca10213c6)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketCache.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketCache.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketWriterThread.java


> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-14 Thread Hudson (JIRA)

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

Hudson commented on HBASE-18533:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3533 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/3533/])
HBASE-18533 Expose BucketCache values to be configured (tedyu: rev 
0e32869f01697abf29292aa786d0cdcca10213c6)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketWriterThread.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketCache.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketCache.java


> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-14 Thread Hudson (JIRA)

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

Hudson commented on HBASE-18533:


FAILURE: Integrated in Jenkins build HBase-1.4 #856 (See 
[https://builds.apache.org/job/HBase-1.4/856/])
HBASE-18533 Expose BucketCache values to be configured (tedyu: rev 
81f5da7af8525c34018df345eb8936b1b9851cc3)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketWriterThread.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketCache.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketCache.java


> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-14 Thread Hudson (JIRA)

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

Hudson commented on HBASE-18533:


FAILURE: Integrated in Jenkins build HBase-1.5 #3 (See 
[https://builds.apache.org/job/HBase-1.5/3/])
HBASE-18533 Expose BucketCache values to be configured (tedyu: rev 
d6a781cf0823b5051d929455218d6a4720150394)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketCache.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketCache.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketWriterThread.java


> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-14 Thread Hudson (JIRA)

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

Hudson commented on HBASE-18533:


FAILURE: Integrated in Jenkins build HBase-2.0 #330 (See 
[https://builds.apache.org/job/HBase-2.0/330/])
HBASE-18533 Expose BucketCache values to be configured (tedyu: rev 
26bbc8ad6c683a9965f61e2bce0e7caf5fd2a37e)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketCache.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketCache.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/bucket/TestBucketWriterThread.java


> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-14 Thread Zach York (JIRA)

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

Zach York commented on HBASE-18533:
---

[~tedyu] Any more issues with this patch? The test run is clean (with the 
exception of HBASE-18587)

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-10 Thread Zach York (JIRA)

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

Zach York commented on HBASE-18533:
---

Looks like this test is flaky. I ran a few times and got it to fail 
inconsistently. I will file a follow up JIRA to fix this test.

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-10 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18533:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
19s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  2m 
 8s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
44s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
40s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 2s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
20s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
14s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
32s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
39s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
18m  2s{color} | {color:green} The patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
46s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 21m 53s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
12s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 57m 17s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.io.hfile.bucket.TestFileIOEngine |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:6f1cc2c |
| JIRA Issue | HBASE-18533 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12881294/HBASE-18533.branch-1.003.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux 05368c5e2dee 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/hbase.sh |
| git revision | branch-1 / 685ab19 |

[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-10 Thread Zach York (JIRA)

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

Zach York commented on HBASE-18533:
---

Attached master and branch-1 patches again to trigger QA

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Fix For: 2.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.branch-1.003.patch, 
> HBASE-18533.master.001.patch, HBASE-18533.master.002.patch, 
> HBASE-18533.master.003.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Anoop Sam John (JIRA)

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

Anoop Sam John commented on HBASE-18533:


bq.How can I trigger the QA again?
Pls attach the latest patch once more. That will trigger the QA 

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Anoop Sam John (JIRA)

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

Anoop Sam John commented on HBASE-18533:


+1 for branches 1.4+

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Andrew Purtell (JIRA)

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

Andrew Purtell commented on HBASE-18533:


Anything good for branch-1 is still good for branch-1.4, thanks

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Zach York (JIRA)

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

Zach York commented on HBASE-18533:
---

How can I trigger the QA again?

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Ted Yu (JIRA)

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

Ted Yu commented on HBASE-18533:


Can you get a clean QA run ?

Fill out release notes.

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-09 Thread Zach York (JIRA)

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

Zach York commented on HBASE-18533:
---

[~tedyu] Do you have any more comments? I uploaded a new diff to the 
reviewboard and updated both patches.

Also [~stack] and [~apurtell] are you guys okay with this going on branch-2 and 
branch-1.4 respectively? 

> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.branch-1.002.patch, HBASE-18533.master.001.patch, 
> HBASE-18533.master.002.patch
>
>
> BucketCache always uses the default values for all cache configuration. 
> However, this doesn't work for all use cases. In particular, users want to be 
> able to configure the percentage of the cache that is single access, multi 
> access, and in-memory access.



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


[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-08 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18533:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
15s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
32m 12s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  3m 
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
31s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}116m 44s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
22s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}165m 23s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests | 
org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
|   | org.apache.hadoop.hbase.coprocessor.TestCoprocessorMetrics |
|   | org.apache.hadoop.hbase.TestMultiVersions |
|   | org.apache.hadoop.hbase.client.TestAsyncSnapshotAdminApi |
|   | org.apache.hadoop.hbase.TestZooKeeper |
|   | org.apache.hadoop.hbase.constraint.TestConstraint |
|   | org.apache.hadoop.hbase.coprocessor.TestMasterObserver |
|   | org.apache.hadoop.hbase.coprocessor.TestWALObserver |
|   | org.apache.hadoop.hbase.TestClusterBootOrder |
|   | 
org.apache.hadoop.hbase.coprocessor.TestRegionObserverForAddingMutationsFromCoprocessors
 |
|   | org.apache.hadoop.hbase.client.TestAvoidCellReferencesIntoShippedBlocks |
|   | org.apache.hadoop.hbase.TestNamespace |
|   | org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor |
|   | org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient |
|   | org.apache.hadoop.hbase.TestIOFencing |
|   | org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient |
|   | 
org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithRemove
 |
|   | org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient |
|   | org.apache.hadoop.hbase.coprocessor.TestRegionObserverBypass |
|   | org.apache.hadoop.hbase.TestHColumnDescriptorDefaultVersions |
|   | org.apache.hadoop.hbase.client.TestSmallReversedScanner |
|   | org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient |
|   | 

[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-08 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18533:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 13m 
56s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
59s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
38s{color} | {color:green} branch-1 passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
36s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
55s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
18s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m  
4s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
28s{color} | {color:green} branch-1 passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
34s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
35s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
36s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
16m 24s{color} | {color:green} The patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  2m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
34s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}104m 39s{color} 
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
25s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}149m 55s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.TestZooKeeper |
|   | hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFiles |
|   | hadoop.hbase.client.TestClientScannerRPCTimeout |
|   | hadoop.hbase.client.TestReplicasClient |
|   | hadoop.hbase.regionserver.TestRSKilledWhenInitializing |
| Timed out junit tests | 
org.apache.hadoop.hbase.security.access.TestCellACLWithMultipleVersions |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:6f1cc2c |
| JIRA Issue | HBASE-18533 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12880915/HBASE-18533.branch-1.002.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  

[jira] [Commented] (HBASE-18533) Expose BucketCache values to be configured

2017-08-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HBASE-18533:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
23s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green}  0m  
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m 
 0s{color} | {color:green} The patch appears to include 2 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  3m 
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  3m  
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
34m 18s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  3m 
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}138m 
20s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
17s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}189m 41s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18533 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12880742/HBASE-18533.master.001.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux e79e8f907905 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31 
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 7e7461e |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/7966/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/7966/console |
| Powered by | Apache Yetus 0.4.0   http://yetus.apache.org |


This message was automatically generated.



> Expose BucketCache values to be configured
> --
>
> Key: HBASE-18533
> URL: https://issues.apache.org/jira/browse/HBASE-18533
> Project: HBase
>  Issue Type: Improvement
>  Components: BucketCache
>Reporter: Zach York
>Assignee: Zach York
> Attachments: HBASE-18533.branch-1.001.patch, 
> HBASE-18533.master.001.patch
>
>
>