[jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
[
https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831598#comment-15831598
]
Hadoop QA commented on HBASE-17489:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 44s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 58s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
31s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 11s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
59s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
29s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
34s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 24s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 14s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 0s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 0s
{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
26s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 15s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
56s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 17s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 114m 6s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
41s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 181m 57s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestBlockEvictionFromClient |
| | hadoop.hbase.client.TestMobSnapshotCloneIndependence |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848487/HBASE-17489-v4.patch |
| JIRA Issue | HBASE-17489 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux f4652c7b91f0 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 4fdd6ff |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/5362/artifact/patchprocess/patch-unit-hbase-server.txt
|
| unit test logs |
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831704#comment-15831704
]
Hadoop QA commented on HBASE-17491:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 20s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m 53s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
53s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
47s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
36s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
33s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 48s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 54s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 55s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
23s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m 32s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 4m 56s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 7m 18s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 9m 39s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.4. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 11m 59s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.5. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 14m 21s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 16m 42s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 19m 2s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 21m 23s
{color} | {color:red} The patch causes 14 errors with Hadoop v3.0.0-alpha1.
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
50s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 0s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 103m 6s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green}
[jira] [Updated] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Navarro updated HBASE-17357:
--
Attachment: HBASE-17357-1.patch
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-17357-1.patch, HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
[
https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832357#comment-15832357
]
Hadoop QA commented on HBASE-17489:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 18s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
33s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 48s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
18s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 39s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
52s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 46s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 46s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s {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}
23m 9s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
27s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 57s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 78m 46s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
31s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 117m 21s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848597/HBASE-17489-v4.patch |
| JIRA Issue | HBASE-17489 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux a759eeec9efe 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2285c57 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5368/testReport/ |
| modules | C: hbase-client hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5368/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> ClientScanner may send a next request to a
[jira] [Commented] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832284#comment-15832284
]
Hadoop QA commented on HBASE-17357:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 13s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 35s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
44s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
45s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
46s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
44s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
30m 31s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
55s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 100m 35s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 143m 48s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848589/HBASE-17357.patch |
| JIRA Issue | HBASE-17357 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 61ec01ddbe19 3.13.0-103-generic #150-Ubuntu SMP Thu Nov 24
10:34:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 4fdd6ff |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5366/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5366/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832300#comment-15832300
]
stack commented on HBASE-17491:
---
bq. Yes, by means to trigger hbase-server UT and make sure no regression, will
remove in the v5 patch.
Oh. Missed that. Pardon me.
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17501) NullPointerException after Datanodes Decommissioned and Terminated
[ https://issues.apache.org/jira/browse/HBASE-17501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Dignan updated HBASE-17501: --- Description: We recently encountered an interesting NullPointerException in HDFS that bubbles up to HBase, and is resolved be restarting the regionserver. The issue was exhibited while we were replacing a set of nodes in one of our clusters with a new set. We did the following: 1. Turn off the HBase balancer 2. Gracefully move the regions off the nodes we’re shutting off using a tool we wrote to do so 3. Decommission the datanodes using the HDFS exclude hosts file and hdfs dfsadmin -refreshNodes 4. Wait for the datanodes to decommission fully 5. Terminate the VMs the instances are running inside. A few notes. We did not shutdown the datanode processes, and the nodes were therefore not marked as dead by the namenode. We simply terminated the datanode VM (in this case an AWS instance). The nodes were marked as decommissioned. We are running our clusters with DNS, and when we terminate VMs, the associated CName is removed and no longer resolves. The errors do not seem to resolve without a restart. After we did this, the remaining regionservers started throwing NullPointerExceptions with the following stack trace: 2017-01-19 23:09:05,638 DEBUG org.apache.hadoop.hbase.ipc.RpcServer: RpcServer.RW.fifo.Q.read.handler=80,queue=14,port=60020: callId: 1727723891 service: ClientService methodName: Scan size: 216 connection: 172.16.36.128:31538 java.io.IOException at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2214) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:204) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:183) Caused by: java.lang.NullPointerException at org.apache.hadoop.hdfs.DFSInputStream.seek(DFSInputStream.java:1564) at org.apache.hadoop.fs.FSDataInputStream.seek(FSDataInputStream.java:62) at org.apache.hadoop.hbase.io.hfile.HFileBlock$AbstractFSReader.readAtOffset(HFileBlock.java:1434) at org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockDataInternal(HFileBlock.java:1682) at org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockData(HFileBlock.java:1542) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:445) at org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:266) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:642) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:592) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:294) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:199) at org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:343) at org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:198) at org.apache.hadoop.hbase.regionserver.HStore.createScanner(HStore.java:2106) at org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:2096) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:5544) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2569) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2555) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2536) at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2405) at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:33738) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2170) ... 3 more was: Hello everyone, We recently encountered an interesting NullPointerException in HDFS that bubbles up to HBase, and is resolved be restarting the regionserver. The issue was exhibited while we were replacing a set of nodes in one of our clusters with a new set. We did the following: 1. Turn off the HBase balancer 2. Gracefully move the regions off the nodes we’re shutting off using a tool we wrote to do so 3. Decommission the datanodes using the HDFS exclude hosts file and hdfs dfsadmin -refreshNodes 4. Wait for the datanodes to decommission fully 5. Terminate the VMs the instances are running inside. A few notes. We did not shutdown the datanode processes, and the nodes were therefore not marked as dead by the namenode. We simply terminated the datanode VM (in this case an AWS instance). The nodes were marked as decommissioned. We are running our clusters with DNS, and when we terminate VMs, the associated CName is removed and
[jira] [Created] (HBASE-17501) NullPointerException after Datanodes Decommissioned and Terminated
Patrick Dignan created HBASE-17501: -- Summary: NullPointerException after Datanodes Decommissioned and Terminated Key: HBASE-17501 URL: https://issues.apache.org/jira/browse/HBASE-17501 Project: HBase Issue Type: Bug Environment: CentOS Derivative with a derivative of the 3.18.43 kernel. HBase on CDH5.9.0 with some patches. HDFS CDH 5.9.0 with no patches. Reporter: Patrick Dignan Priority: Minor Hello everyone, We recently encountered an interesting NullPointerException in HDFS that bubbles up to HBase, and is resolved be restarting the regionserver. The issue was exhibited while we were replacing a set of nodes in one of our clusters with a new set. We did the following: 1. Turn off the HBase balancer 2. Gracefully move the regions off the nodes we’re shutting off using a tool we wrote to do so 3. Decommission the datanodes using the HDFS exclude hosts file and hdfs dfsadmin -refreshNodes 4. Wait for the datanodes to decommission fully 5. Terminate the VMs the instances are running inside. A few notes. We did not shutdown the datanode processes, and the nodes were therefore not marked as dead by the namenode. We simply terminated the datanode VM (in this case an AWS instance). The nodes were marked as decommissioned. We are running our clusters with DNS, and when we terminate VMs, the associated CName is removed and no longer resolves. The errors do not seem to resolve without a restart. After we did this, the remaining regionservers started throwing NullPointerExceptions with the following stack trace: 2017-01-19 23:09:05,638 DEBUG org.apache.hadoop.hbase.ipc.RpcServer: RpcServer.RW.fifo.Q.read.handler=80,queue=14,port=60020: callId: 1727723891 service: ClientService methodName: Scan size: 216 connection: 172.16.36.128:31538 java.io.IOException at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2214) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:204) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:183) Caused by: java.lang.NullPointerException at org.apache.hadoop.hdfs.DFSInputStream.seek(DFSInputStream.java:1564) at org.apache.hadoop.fs.FSDataInputStream.seek(FSDataInputStream.java:62) at org.apache.hadoop.hbase.io.hfile.HFileBlock$AbstractFSReader.readAtOffset(HFileBlock.java:1434) at org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockDataInternal(HFileBlock.java:1682) at org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockData(HFileBlock.java:1542) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:445) at org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:266) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:642) at org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:592) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:294) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:199) at org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:343) at org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:198) at org.apache.hadoop.hbase.regionserver.HStore.createScanner(HStore.java:2106) at org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:2096) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:5544) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2569) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2555) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2536) at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2405) at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:33738) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2170) ... 3 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-17491:
--
Attachment: HBASE-17491.v5.patch
Patch v5 makes TableBuilder an abstract class.
Now there're two ways to get a table:
1. Through {{ConnectionImplementation#getTable}}, which will return a
thread-safe table instance
2. Use {{ConnectionImplementation#getTableBuilder}} to get a table builder, set
configurations such as different timeouts, and then get the table instance from
the builder. Since it's common sense that we shouldn't share a builder among
multiple threads, there won't be any thread safe issue.
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch, HBASE-17491.v5.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832329#comment-15832329
]
David Navarro commented on HBASE-17357:
---
[~stack]
Fixed space, after if
errCode is non-null per
https://github.com/apache/hbase/blob/master/hbase-server/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java#L2203
yes tried patch. Thanks.
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-17357-1.patch, HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12894) Upgrade Jetty to 9.2.6
[ https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12894: -- Attachment: HBASE-12894.master.001.patch > Upgrade Jetty to 9.2.6 > -- > > Key: HBASE-12894 > URL: https://issues.apache.org/jira/browse/HBASE-12894 > Project: HBase > Issue Type: Improvement > Components: REST, UI >Affects Versions: 0.98.0 >Reporter: Rick Hallihan >Assignee: Guang Yang >Priority: Critical > Labels: MicrosoftSupport > Fix For: 2.0.0 > > Attachments: dependency_list_after, dependency_list_before, > HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v10.patch, > HBASE-12894_Jetty9_v1.patch, HBASE-12894_Jetty9_v1.patch, > HBASE-12894_Jetty9_v2.patch, HBASE-12894_Jetty9_v3.patch, > HBASE-12894_Jetty9_v4.patch, HBASE-12894_Jetty9_v5.patch, > HBASE-12894_Jetty9_v6.patch, HBASE-12894_Jetty9_v7.patch, > HBASE-12894_Jetty9_v8.patch, HBASE-12894.master.001.patch > > > The Jetty component that is used for the HBase Stargate REST endpoint is > version 6.1.26 and is fairly outdated. We recently had a customer inquire > about enabling cross-origin resource sharing (CORS) for the REST endpoint and > found that this older version does not include the necessary filter or > configuration options, highlighted at: > http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter > The Jetty project has had significant updates through versions 7, 8 and 9, > including a transition to be an Eclipse subproject, so updating to the latest > version may be non-trivial. The last update to the Jetty component in > https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update > and did not require significant work. This update will include a package > namespace update so there will likely be a larger number of required changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12894) Upgrade Jetty to 9.2.6
[ https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832298#comment-15832298 ] stack commented on HBASE-12894: --- I uploaded a patch that quietens the findbugs warning using [~yguang11]'s justification above. If findbugs passes this time through, will commit given [~busbey] +1 above > Upgrade Jetty to 9.2.6 > -- > > Key: HBASE-12894 > URL: https://issues.apache.org/jira/browse/HBASE-12894 > Project: HBase > Issue Type: Improvement > Components: REST, UI >Affects Versions: 0.98.0 >Reporter: Rick Hallihan >Assignee: Guang Yang >Priority: Critical > Labels: MicrosoftSupport > Fix For: 2.0.0 > > Attachments: dependency_list_after, dependency_list_before, > HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v10.patch, > HBASE-12894_Jetty9_v1.patch, HBASE-12894_Jetty9_v1.patch, > HBASE-12894_Jetty9_v2.patch, HBASE-12894_Jetty9_v3.patch, > HBASE-12894_Jetty9_v4.patch, HBASE-12894_Jetty9_v5.patch, > HBASE-12894_Jetty9_v6.patch, HBASE-12894_Jetty9_v7.patch, > HBASE-12894_Jetty9_v8.patch, HBASE-12894.master.001.patch > > > The Jetty component that is used for the HBase Stargate REST endpoint is > version 6.1.26 and is fairly outdated. We recently had a customer inquire > about enabling cross-origin resource sharing (CORS) for the REST endpoint and > found that this older version does not include the necessary filter or > configuration options, highlighted at: > http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter > The Jetty project has had significant updates through versions 7, 8 and 9, > including a transition to be an Eclipse subproject, so updating to the latest > version may be non-trivial. The last update to the Jetty component in > https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update > and did not require significant work. This update will include a package > namespace update so there will likely be a larger number of required changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17482) mvcc mechanism fails when using mvccPreAssign
[ https://issues.apache.org/jira/browse/HBASE-17482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832346#comment-15832346 ] Yu Li commented on HBASE-17482: --- A compare of branch-1 and master sir, although I believe master branch should be ok after this JIRA's fix. Thanks for checking [~stack]. > mvcc mechanism fails when using mvccPreAssign > - > > Key: HBASE-17482 > URL: https://issues.apache.org/jira/browse/HBASE-17482 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.. >Reporter: Allan Yang >Assignee: Allan Yang >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-17482.patch, HBASE-17482.v2.patch, > HBASE-17482.v3.patch > > > If mvccPreAssign and ASYNC_WAL is used, then cells may have been commited to > memstore before append thread can stamp seqid to them. The unit test shows > everything. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-17465: -- Attachment: HBASE-17465-HBASE-14850.000.patch v0 added skeleton code. > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832289#comment-15832289
]
Yu Li commented on HBASE-17491:
---
bq. Just seems odd making an interface and not using it
It's also the case for AsyncTableBuilder, and I think maybe it's reserved for
other builder implementations, or mind clarify the design for async builder
[~Apache9]? Thanks. (And I'm ok to only use one single TableBuilder class w/o
any interface introduced for Table, will upload a v5 patch following this way,
and just let me know which looks better, thanks.)
bq. If you passed the tablename separate from the builder (as it is now) would
that help?
I think it's natural to ask for the table name when constructing the builder,
to make it clear instance of which table will be build.
bq. v4 still has...
Yes, by means to trigger hbase-server UT and make sure no regression, will
remove in the v5 patch.
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-17465: -- Attachment: HBASE-17465-HBASE-14850.001.patch v1 added generic callable. > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch, > HBASE-17465-HBASE-14850.001.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-17465: -- Attachment: HBASE-17465-HBASE-14850.002.patch > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch, > HBASE-17465-HBASE-14850.001.patch, HBASE-17465-HBASE-14850.002.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17488) WALEdit should be lazily instantiated
[ https://issues.apache.org/jira/browse/HBASE-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832609#comment-15832609 ] Hudson commented on HBASE-17488: SUCCESS: Integrated in Jenkins build HBase-1.4 #597 (See [https://builds.apache.org/job/HBase-1.4/597/]) HBASE-17488 WALEdit should be lazily instantiated (ChiaPing Tsai) (stack: rev f7d1d25fd757c2e58cbe2ec129dded7fd02a355e) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > WALEdit should be lazily instantiated > - > > Key: HBASE-17488 > URL: https://issues.apache.org/jira/browse/HBASE-17488 > Project: HBase > Issue Type: Improvement >Reporter: ChiaPing Tsai >Assignee: ChiaPing Tsai >Priority: Trivial > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-17488.branch-1.v0.patch, > HBASE-17488.branch-1.v0.patch, HBASE-17488.branch-1.v1.patch, > HBASE-17488.v0.patch > > > Some trivial improvement. > # create the WALEdit on step 3 instead of step 2 > # count the cells from coprocessor > # don’t count the mutations which contain the Durability.SKIP_WAL property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17413) Use isEmpty instead of size() == 0 in hbase-hadoop2-compat
[
https://issues.apache.org/jira/browse/HBASE-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17413:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-hadoop2-compat
> --
>
> Key: HBASE-17413
> URL: https://issues.apache.org/jira/browse/HBASE-17413
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17413.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-hadoop2-compat* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17412) Use isEmpty instead of size() == 0 in hbase-endpoint
[
https://issues.apache.org/jira/browse/HBASE-17412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17412:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-endpoint
>
>
> Key: HBASE-17412
> URL: https://issues.apache.org/jira/browse/HBASE-17412
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17412.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-endpoint* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-17417) Use isEmpty instead of size() == 0 in hbase-rest
[
https://issues.apache.org/jira/browse/HBASE-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-17417.
---
Resolution: Duplicate
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-rest
>
>
> Key: HBASE-17417
> URL: https://issues.apache.org/jira/browse/HBASE-17417
> Project: HBase
> Issue Type: Sub-task
> Components: REST
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17417.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-rest* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17417) Use isEmpty instead of size() == 0 in hbase-rest
[
https://issues.apache.org/jira/browse/HBASE-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17417:
--
Status: Open (was: Patch Available)
> Use isEmpty instead of size() == 0 in hbase-rest
>
>
> Key: HBASE-17417
> URL: https://issues.apache.org/jira/browse/HBASE-17417
> Project: HBase
> Issue Type: Sub-task
> Components: REST
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17417.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-rest* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup
[
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17418:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17418.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-rsgroup* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17473) Set capacity on ArrayList in hbase-client
[ https://issues.apache.org/jira/browse/HBASE-17473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-17473: -- Resolution: Duplicate Status: Resolved (was: Patch Available) This will be part of HBASE-10699. > Set capacity on ArrayList in hbase-client > - > > Key: HBASE-17473 > URL: https://issues.apache.org/jira/browse/HBASE-17473 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Minor > Attachments: HBASE-17473.master.001.patch, > HBASE-17473.master.002.patch > > > Set the capacity on an ArrayList when possible in the *hbase-client* module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10699) Optimize some code
[ https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-10699: -- Status: Patch Available (was: In Progress) > Optimize some code > -- > > Key: HBASE-10699 > URL: https://issues.apache.org/jira/browse/HBASE-10699 > Project: HBase > Issue Type: Improvement >Reporter: @deprecated Yi Deng >Assignee: Jan Hentschel > Attachments: HBASE-10699.master.001.patch > > > 1. Set capacity on ArrayList when possible > 2. Use isEmpty instead of size() == 0 when possible > 3. Reduce some unnecessary allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-17404) Replace explicit type with diamond operator in hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-17404 started by Jan Hentschel. - > Replace explicit type with diamond operator in hbase-annotations > > > Key: HBASE-17404 > URL: https://issues.apache.org/jira/browse/HBASE-17404 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Trivial > Attachments: HBASE-17404.master.001.patch > > > Because HBase uses Java 8 explicit types in the *hbase-annotations* module > (*RootDocProcessor* and *StabilityOptions* classes) can be replaced with the > diamond operator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832660#comment-15832660
]
ronan stokes edited comment on HBASE-14925 at 1/21/17 12:22 AM:
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
\# list_regions
\# return list of regions for a table as an array
\# results are ordered by start key
\# each element of list is hash of \{ "name","size", "requests" \}
\#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
was (Author: rsto...@cloudera.com):
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
\# list_regions
\# return list of regions for a table as an array
\# results are ordered by start key
\# each element of list is hash of { "name","size", "requests" }
\#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832660#comment-15832660
]
ronan stokes edited comment on HBASE-14925 at 1/21/17 12:21 AM:
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
\# list_regions
\# return list of regions for a table as an array
\# results are ordered by start key
\# each element of list is hash of { "name","size", "requests" }
\#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
was (Author: rsto...@cloudera.com):
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
# list_regions
# return list of regions for a table as an array
# results are ordered by start key
# each element of list is hash of { "name","size", "requests" }
#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832660#comment-15832660
]
ronan stokes edited comment on HBASE-14925 at 1/21/17 12:25 AM:
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
{noformat}
# list_regions
# return list of regions for a table as an array
# results are ordered by start key
# each element of list is hash of { "name","size", "requests" }
#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
{noformat}
was (Author: rsto...@cloudera.com):
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
{quote}
# list_regions
# return list of regions for a table as an array
# results are ordered by start key
# each element of list is hash of { "name","size", "requests" }
#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
{quote}
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832579#comment-15832579
]
Enis Soztutar edited comment on HBASE-17491 at 1/20/17 11:07 PM:
-
Will AsyncTableBuilder extend TableBuilder, or will they be separate?
You also have to deprecate/remove methods in Table.java, not just HTable.java.
Looks good otherwise.
was (Author: enis):
Will AsyncTableBuilder extend TableBuilder, or will they be separate?
You also have to deprecate/remove methods in Table.java, not just HTable.java.
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch, HBASE-17491.v5.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832579#comment-15832579
]
Enis Soztutar commented on HBASE-17491:
---
Will AsyncTableBuilder extend TableBuilder, or will they be separate?
You also have to deprecate/remove methods in Table.java, not just HTable.java.
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch, HBASE-17491.v5.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832592#comment-15832592 ] Xiaobing Zhou commented on HBASE-17465: --- v2 implemented SingleRequestCallerBuilder. > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch, > HBASE-17465-HBASE-14850.001.patch, HBASE-17465-HBASE-14850.002.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17488) WALEdit should be lazily instantiated
[ https://issues.apache.org/jira/browse/HBASE-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832600#comment-15832600 ] Hudson commented on HBASE-17488: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2355 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2355/]) HBASE-17488 WALEdit should be lazily instantiated (ChiaPing Tsai) (stack: rev 2285c57a352aa4607636205a8b99ecb8ea1ff51e) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > WALEdit should be lazily instantiated > - > > Key: HBASE-17488 > URL: https://issues.apache.org/jira/browse/HBASE-17488 > Project: HBase > Issue Type: Improvement >Reporter: ChiaPing Tsai >Assignee: ChiaPing Tsai >Priority: Trivial > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-17488.branch-1.v0.patch, > HBASE-17488.branch-1.v0.patch, HBASE-17488.branch-1.v1.patch, > HBASE-17488.v0.patch > > > Some trivial improvement. > # create the WALEdit on step 3 instead of step 2 > # count the cells from coprocessor > # don’t count the mutations which contain the Durability.SKIP_WAL property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10699) Optimize some code
[ https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-10699: -- Attachment: HBASE-10699.master.001.patch > Optimize some code > -- > > Key: HBASE-10699 > URL: https://issues.apache.org/jira/browse/HBASE-10699 > Project: HBase > Issue Type: Improvement >Reporter: @deprecated Yi Deng >Assignee: Jan Hentschel > Attachments: HBASE-10699.master.001.patch > > > 1. Set capacity on ArrayList when possible > 2. Use isEmpty instead of size() == 0 when possible > 3. Reduce some unnecessary allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17411) Use isEmpty instead of size() == 0 in hbase-common
[
https://issues.apache.org/jira/browse/HBASE-17411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17411:
--
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-common
> --
>
> Key: HBASE-17411
> URL: https://issues.apache.org/jira/browse/HBASE-17411
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17411.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-common* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17415) Use isEmpty instead of size() == 0 in hbase-procedure
[
https://issues.apache.org/jira/browse/HBASE-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17415:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-procedure
> -
>
> Key: HBASE-17415
> URL: https://issues.apache.org/jira/browse/HBASE-17415
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17415.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-procedure* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17414) Use isEmpty instead of size() == 0 in hbase-it
[
https://issues.apache.org/jira/browse/HBASE-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17414:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-it
> --
>
> Key: HBASE-17414
> URL: https://issues.apache.org/jira/browse/HBASE-17414
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17414.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-it* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17420) Use isEmpty instead of size() == 0 in hbase-thrift
[
https://issues.apache.org/jira/browse/HBASE-17420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17420:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-thrift
> --
>
> Key: HBASE-17420
> URL: https://issues.apache.org/jira/browse/HBASE-17420
> Project: HBase
> Issue Type: Sub-task
> Components: Thrift
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17420.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-thrift* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17423) Set capacity on ArrayList in hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-17423: -- Resolution: Duplicate Status: Resolved (was: Patch Available) This will be part of HBASE-10699. > Set capacity on ArrayList in hbase-annotations > -- > > Key: HBASE-17423 > URL: https://issues.apache.org/jira/browse/HBASE-17423 > Project: HBase > Issue Type: Sub-task >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Minor > Attachments: HBASE-17423.master.001.patch > > > Set the capacity on an ArrayList when possible in the *hbase-annotations* > module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17419) Use isEmpty instead of size() == 0 in hbase-server
[
https://issues.apache.org/jira/browse/HBASE-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-17419:
--
Resolution: Duplicate
Status: Resolved (was: Patch Available)
This will be part of HBASE-10699.
> Use isEmpty instead of size() == 0 in hbase-server
> --
>
> Key: HBASE-17419
> URL: https://issues.apache.org/jira/browse/HBASE-17419
> Project: HBase
> Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17419.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when
> possible in the *hbase-server* module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17404) Replace explicit type with diamond operator in hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-17404: -- Status: Patch Available (was: In Progress) > Replace explicit type with diamond operator in hbase-annotations > > > Key: HBASE-17404 > URL: https://issues.apache.org/jira/browse/HBASE-17404 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Trivial > Attachments: HBASE-17404.master.001.patch > > > Because HBase uses Java 8 explicit types in the *hbase-annotations* module > (*RootDocProcessor* and *StabilityOptions* classes) can be replaced with the > diamond operator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17477) Set capacity on ArrayList in hbase-common
[ https://issues.apache.org/jira/browse/HBASE-17477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-17477: -- Resolution: Duplicate Status: Resolved (was: Patch Available) This will be part of HBASE-10699. > Set capacity on ArrayList in hbase-common > - > > Key: HBASE-17477 > URL: https://issues.apache.org/jira/browse/HBASE-17477 > Project: HBase > Issue Type: Sub-task >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Minor > Attachments: HBASE-17477.master.001.patch > > > Set the capacity on an ArrayList when possible in the *hbase-common* module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-17502) Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support matrix
Jerry He created HBASE-17502: Summary: Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support matrix Key: HBASE-17502 URL: https://issues.apache.org/jira/browse/HBASE-17502 Project: HBase Issue Type: Task Reporter: Jerry He Hadoop pre-2.6.1 on JDK 1.8 has problem with Kerberos keytabe relogin. HADOOP-10786 fixed the problem in Hadoop 2.6.1. Let's document it in the Hadoop support matrix. This was brought up in HBase 1.3.0 RC0 voting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832660#comment-15832660
]
ronan stokes commented on HBASE-14925:
--
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
# list_regions
# return list of regions for a table as an array
# results are ordered by start key
# each element of list is hash of { "name","size", "requests" }
#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832660#comment-15832660
]
ronan stokes edited comment on HBASE-14925 at 1/21/17 12:23 AM:
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
{quote}
# list_regions
# return list of regions for a table as an array
# results are ordered by start key
# each element of list is hash of { "name","size", "requests" }
#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
{quote}
was (Author: rsto...@cloudera.com):
Here's one mechanism to get the regions for a particular table from the shell -
it would be relatively easy to turn it into a command. It's a little hackish as
it reads an internal variable of the shell admin instance but when integrated
as a command, it could use an appropriate mechanism...
\# list_regions
\# return list of regions for a table as an array
\# results are ordered by start key
\# each element of list is hash of \{ "name","size", "requests" \}
\#
def list_regions(tgtTable)
hbadmin = @hbase.admin(@hbase)
hbjadmin = hbadmin.instance_variable_get("@admin")
cluster_status = hbjadmin.getClusterStatus()
master = cluster_status.getMaster()
results = Array.new
for server in cluster_status.getServers()
for name,region in cluster_status.getLoad(server).getRegionsLoad()
region_name = region.getNameAsString()
regionStoreFileSize = region.getStorefileSizeMB()
regionRequests = region.getRequestsCount()
if region_name.start_with? tgtTable
results << { "server" => server, "name" => region_name, "size" =>
regionStoreFileSize, "requests" => regionRequests }
end
end
end
results.sort!{ |a,b| a["name"].split(',')[1] <=> b["name"].split(',')[1] }
return results
end
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-17503) [C++] Configuration should be settable and used w/o XML files
Enis Soztutar created HBASE-17503: - Summary: [C++] Configuration should be settable and used w/o XML files Key: HBASE-17503 URL: https://issues.apache.org/jira/browse/HBASE-17503 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: HBASE-14850 Configuration right now is read-only, and there is only XML based configuration loader. However, in testing, we need the Config object w/o the XML files, and we need to be able to set specific values in the conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17503) [C++] Configuration should be settable and used w/o XML files
[ https://issues.apache.org/jira/browse/HBASE-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-17503: -- Attachment: hbase-17503_v1.patch [~sudeeps] can you please take a look at this patch. Thanks. > [C++] Configuration should be settable and used w/o XML files > - > > Key: HBASE-17503 > URL: https://issues.apache.org/jira/browse/HBASE-17503 > Project: HBase > Issue Type: Sub-task >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: HBASE-14850 > > Attachments: hbase-17503_v1.patch > > > Configuration right now is read-only, and there is only XML based > configuration loader. > However, in testing, we need the Config object w/o the XML files, and we need > to be able to set specific values in the conf. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10699) Optimize some code
[
https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832770#comment-15832770
]
Hadoop QA commented on HBASE-10699:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 12m 43s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 83 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 18s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m 24s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
1s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
47s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 16s
{color} | {color:red} hbase-prefix-tree in master has 1 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 5s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 2m
25s {color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 3m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
50s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
34s {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}
25m 50s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 8m
33s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 48s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 2m 4s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 6s
{color} | {color:green} hbase-annotations in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 55s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 25s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 2s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 19s
{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 19s
{color} | {color:green} hbase-prefix-tree in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 83m 23s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 28s
{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green}
[jira] [Commented] (HBASE-17498) Implement listTables and listTableNames methods
[ https://issues.apache.org/jira/browse/HBASE-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832799#comment-15832799 ] Hudson commented on HBASE-17498: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2356 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2356/]) HBASE-17498 Implement listTables and listTableNames methods (stack: rev 79018056f542cde5850b1d1fc2fe248f0007fd66) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncHBaseAdmin.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncAdmin.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncAdmin.java > Implement listTables and listTableNames methods > --- > > Key: HBASE-17498 > URL: https://issues.apache.org/jira/browse/HBASE-17498 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-17498.master.001.patch, HBASE-17498-v1.patch, > HBASE-17498-v1.patch, HBASE-17498-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832442#comment-15832442
]
Hadoop QA commented on HBASE-17491:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 13s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
3s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
46s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
7s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m 17s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 4m 33s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 6m 47s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 9m 1s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.4. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 11m 18s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.6.5. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 13m 31s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 15m 52s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 18m 8s
{color} | {color:red} The patch causes 14 errors with Hadoop v2.7.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 20m 24s
{color} | {color:red} The patch causes 14 errors with Hadoop v3.0.0-alpha1.
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
54s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 6s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
6s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 28m 58s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848615/HBASE-17491.v5.patch |
[jira] [Commented] (HBASE-17496) RSGroup shell commands:get_server_rsgroup don't work and commands display an incorrect result size
[
https://issues.apache.org/jira/browse/HBASE-17496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832398#comment-15832398
]
Hudson commented on HBASE-17496:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2354 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2354/])
HBASE-17496 RSGroup shell commands:get_server_rsgroup don't work and (stack:
rev 31f3e8f833b65d87bb70dd47268213ff03be20b9)
* (edit) hbase-shell/src/main/ruby/shell/commands/get_server_rsgroup.rb
* (edit) hbase-shell/src/main/ruby/shell/commands/get_table_rsgroup.rb
* (edit) hbase-shell/src/main/ruby/shell/commands/list_rsgroups.rb
* (edit) hbase-shell/src/main/ruby/shell/commands/get_rsgroup.rb
> RSGroup shell commands:get_server_rsgroup don't work and commands display an
> incorrect result size
> --
>
> Key: HBASE-17496
> URL: https://issues.apache.org/jira/browse/HBASE-17496
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
> Labels: rsgroup
> Fix For: 2.0.0
>
> Attachments: HBASE-17496-master-v1.patch
>
>
> scenario as follows:
> {code}
> hbase(main):001:0> get_server_rsgroup 'hbase-01:16030'
> ERROR: undefined method `getRSGroupOfServer' for
> #
> Here is some help for this command:
> Get the group name the given region server is a member of.
> hbase> get_server_rsgroup 'server1:port1'
> Took 0.0160 seconds
> {code}
> {code}
> hbase(main):002:0> list_rsgroups
> GROUPS
> default
> 1484874115 row(s)
> Took 0.3830 seconds
> {code}
> {code}
> hbase(main):003:0> get_table_rsgroup 't1'
> default
> 1484874133 row(s)
> Took 0.0100 seconds
> {code}
> {code}
> hbase(main):004:0> get_rsgroup 'default'
> GROUP INFORMATION
> Servers:
> hbase-01:16030
> Tables:
> hbase:meta
> t1
> hbase:namespace
> hbase:rsgroup
> 1484874150 row(s)
> Took 0.0140 seconds
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17497) Add first async MetaTableAccessor impl and Implement tableExists method
[ https://issues.apache.org/jira/browse/HBASE-17497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832399#comment-15832399 ] Hudson commented on HBASE-17497: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2354 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2354/]) HBASE-17497 Add first async MetaTableAccessor impl and Implement (stack: rev 2ee3c73f76ea80d50fd921fa8cbe84d21f376785) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncAdmin.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncHBaseAdmin.java * (add) hbase-client/src/main/java/org/apache/hadoop/hbase/AsyncMetaTableAccessor.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncAdmin.java > Add first async MetaTableAccessor impl and Implement tableExists method > --- > > Key: HBASE-17497 > URL: https://issues.apache.org/jira/browse/HBASE-17497 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-17497-v1.patch > > > HBaseAdmin use many MetaTableAccessor's static methods. So add a async > MetaTableAccessor for AsyncHBaseAdmin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17498) Implement listTables and listTableNames methods
[
https://issues.apache.org/jira/browse/HBASE-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832456#comment-15832456
]
Hadoop QA commented on HBASE-17498:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
52s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 53s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
36s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 45s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
1s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 56s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 29s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 3s
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 84m 39s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 128m 57s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848601/HBASE-17498.master.001.patch
|
| JIRA Issue | HBASE-17498 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux cd7180baa15a 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2285c57 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/5369/artifact/patchprocess/whitespace-eol.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5369/testReport/ |
| modules | C: hbase-client hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5369/console |
|
[jira] [Updated] (HBASE-17067) Procedure v2 - remove zklock/tryLock and use wait/wake
[ https://issues.apache.org/jira/browse/HBASE-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17067: -- Attachment: HBASE-17067.master.004.patch > Procedure v2 - remove zklock/tryLock and use wait/wake > -- > > Key: HBASE-17067 > URL: https://issues.apache.org/jira/browse/HBASE-17067 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-17067.master.001.patch, > HBASE-17067.master.002.patch, HBASE-17067.master.003.patch, > HBASE-17067.master.004.patch, HBASE-17067.master.004.patch, > HBASE-17067.master.004.patch, HBASE-17067.master.004.patch > > > Once we have HBASE-16744, HBASE-16786, HBASE-16831. we can remove the > tryLock() methods and replace them with the wait/wake methods that are using > the framework events instead of spinning until we can start the proc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17460) enable_table_replication can not perform cyclic replication of a table
[ https://issues.apache.org/jira/browse/HBASE-17460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832484#comment-15832484 ] NITIN VERMA commented on HBASE-17460: - [~enis] [~ashish singhi] could you please review the new patch? [~enis] we also need to port this patch to HDP. > enable_table_replication can not perform cyclic replication of a table > -- > > Key: HBASE-17460 > URL: https://issues.apache.org/jira/browse/HBASE-17460 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: NITIN VERMA >Assignee: NITIN VERMA > Labels: replication > Attachments: HBASE-17460.patch, HBASE-17460_v2.patch > > Original Estimate: 96h > Remaining Estimate: 96h > > The enable_table_replication operation is broken for cyclic replication of > HBase table as we compare all the properties of column families (including > REPLICATION_SCOPE). > Below is exactly what happens: > 1. Running "enable_table_replication 'table1' " opeartion on first cluster > will set the REPLICATION_SCOPE of all column families to peer id '1'. This > will also create a table on second cluster where REPLICATION_SCOPE is still > set to peer id '0'. > 2. Now when we run "enable_table_replication 'table1'" on second cluster, we > compare all the properties of table (including REPLICATION_SCOPE_, which > obviously is different now. > I am proposing a fix for this issue where we should avoid comparing > REPLICATION_SCOPE inside HColumnDescriotor::compareTo() method, especially > when replication is not already enabled on the desired table. > I have made that change and it is working. I will submit the patch soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17460) enable_table_replication can not perform cyclic replication of a table
[
https://issues.apache.org/jira/browse/HBASE-17460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832503#comment-15832503
]
Ted Yu commented on HBASE-17460:
{code}
+ * @param HColumnDescriptor
+ */
+ public void copyReplicationScope(HColumnDescriptor hcd) {
{code}
Please fix the javadoc warning - parameter name should be hcd.
{code}
+ public boolean hasReplicationEnabled() {
{code}
hasReplicationEnabled -> isReplicationEnabled
{code}
+result = true;
+break;
{code}
You can just return true instead of break'ing.
{code}
+ * @return true if the contents of the the two descriptors match (ignoring
just
{code}
Remove redundant 'the'
{code}
+result = (this.copyReplicationScope(localHtd) == 0);
{code}
Currently, it is up to the caller of compareForReplication() to make a copy.
Shouldn't the copy be made by compareForReplication() ?
> enable_table_replication can not perform cyclic replication of a table
> --
>
> Key: HBASE-17460
> URL: https://issues.apache.org/jira/browse/HBASE-17460
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: NITIN VERMA
>Assignee: NITIN VERMA
> Labels: replication
> Attachments: HBASE-17460.patch, HBASE-17460_v2.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> The enable_table_replication operation is broken for cyclic replication of
> HBase table as we compare all the properties of column families (including
> REPLICATION_SCOPE).
> Below is exactly what happens:
> 1. Running "enable_table_replication 'table1' " opeartion on first cluster
> will set the REPLICATION_SCOPE of all column families to peer id '1'. This
> will also create a table on second cluster where REPLICATION_SCOPE is still
> set to peer id '0'.
> 2. Now when we run "enable_table_replication 'table1'" on second cluster, we
> compare all the properties of table (including REPLICATION_SCOPE_, which
> obviously is different now.
> I am proposing a fix for this issue where we should avoid comparing
> REPLICATION_SCOPE inside HColumnDescriotor::compareTo() method, especially
> when replication is not already enabled on the desired table.
> I have made that change and it is working. I will submit the patch soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17460) enable_table_replication can not perform cyclic replication of a table
[
https://issues.apache.org/jira/browse/HBASE-17460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832561#comment-15832561
]
Enis Soztutar commented on HBASE-17460:
---
In {{compareForReplication}}, you are changing the passed HTD/HCD, effectively
introducing side affects to an otherwise read-only method.
We already have setScope() and getScope(), please use those. They should have
been named set/getReplicationScope, but that is another issue.
Can you please instead do something like this:
- In RepAdmin, close the HTD as you do. Iterate over the HCDs from source, and
set the scope by calling HCD.setScope() from the other.
- Then call regular HTD.compare() without any need for introducing custom
methods in HTD / HCD.
Is the indentation correct? It makes hard to read the patch, and we cannot
commit without fixed indentation. We use 2 spaces, and no tabs.
> enable_table_replication can not perform cyclic replication of a table
> --
>
> Key: HBASE-17460
> URL: https://issues.apache.org/jira/browse/HBASE-17460
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: NITIN VERMA
>Assignee: NITIN VERMA
> Labels: replication
> Attachments: HBASE-17460.patch, HBASE-17460_v2.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> The enable_table_replication operation is broken for cyclic replication of
> HBase table as we compare all the properties of column families (including
> REPLICATION_SCOPE).
> Below is exactly what happens:
> 1. Running "enable_table_replication 'table1' " opeartion on first cluster
> will set the REPLICATION_SCOPE of all column families to peer id '1'. This
> will also create a table on second cluster where REPLICATION_SCOPE is still
> set to peer id '0'.
> 2. Now when we run "enable_table_replication 'table1'" on second cluster, we
> compare all the properties of table (including REPLICATION_SCOPE_, which
> obviously is different now.
> I am proposing a fix for this issue where we should avoid comparing
> REPLICATION_SCOPE inside HColumnDescriotor::compareTo() method, especially
> when replication is not already enabled on the desired table.
> I have made that change and it is working. I will submit the patch soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832574#comment-15832574
]
Hadoop QA commented on HBASE-17357:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 12s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
8s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 36s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
39s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
39s {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 {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
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 57s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 25s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 79m 58s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
13s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 117m 28s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848618/HBASE-17357-1.patch |
| JIRA Issue | HBASE-17357 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 4dbe58c32309 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 2285c57 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5372/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5372/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
>
[jira] [Commented] (HBASE-17067) Procedure v2 - remove zklock/tryLock and use wait/wake
[
https://issues.apache.org/jira/browse/HBASE-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832468#comment-15832468
]
Hadoop QA commented on HBASE-17067:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 21s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 8 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 32s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 6s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 38s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
56s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 51s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 51s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s {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}
27m 21s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
17s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 24s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 92m 35s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
34s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 137m 26s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.TestJMXListener |
| | hadoop.hbase.client.TestMobSnapshotCloneIndependence |
| Timed out junit tests |
org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
| | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer |
| | org.apache.hadoop.hbase.master.TestDistributedLogSplitting |
| | org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster |
| | org.apache.hadoop.hbase.mapred.TestTableSnapshotInputFormat |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.6 Server=1.12.6 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848602/HBASE-17067.master.004.patch
|
| JIRA Issue | HBASE-17067 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 57491b14ba7e 3.13.0-100-generic #147-Ubuntu SMP Tue Oct 18
16:48:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Updated] (HBASE-17498) Implement listTables and listTableNames methods
[ https://issues.apache.org/jira/browse/HBASE-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17498: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master (fixed whitespace on commit). Thanks for the patch [~zghaobac] > Implement listTables and listTableNames methods > --- > > Key: HBASE-17498 > URL: https://issues.apache.org/jira/browse/HBASE-17498 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-17498.master.001.patch, HBASE-17498-v1.patch, > HBASE-17498-v1.patch, HBASE-17498-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17278) [C++] Cell Scanner Implementation to be used by ResultScanner
[ https://issues.apache.org/jira/browse/HBASE-17278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832519#comment-15832519 ] Enis Soztutar commented on HBASE-17278: --- CellScanner should only have Current() and Advance(). You can take a look at the CellScanner.java. You can move CellBlockMetaLength() to the KVCodec::Decoder. Also, you can just use the buffer length, rather then "cell block meta" as a terminology. > [C++] Cell Scanner Implementation to be used by ResultScanner > - > > Key: HBASE-17278 > URL: https://issues.apache.org/jira/browse/HBASE-17278 > Project: HBase > Issue Type: Sub-task >Reporter: Sudeep Sunthankar >Assignee: Sudeep Sunthankar > Attachments: HBASE-17278.HBASE-14850.v1.patch, > HBASE-17278.HBASE-14850.v2.patch, HBASE-17278.HBASE-14850.v3.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832667#comment-15832667
]
ronan stokes commented on HBASE-14925:
--
Above example is ruby - so you can add it to a file and invoke
{noquote}
hbase shell
{noquote}
to load it.
Once shell has loaded, you can use
{noquote}
list_regions ''
{noquote}
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14925) Develop HBase shell command/tool to list table's region info through command line
[
https://issues.apache.org/jira/browse/HBASE-14925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832667#comment-15832667
]
ronan stokes edited comment on HBASE-14925 at 1/21/17 12:29 AM:
Above example is ruby - so you can add it to a file and invoke
{noformat}
hbase shell
{noformat}
to load it.
Once shell has loaded, you can use
{noformat}
list_regions ''
{noformat}
was (Author: rsto...@cloudera.com):
Above example is ruby - so you can add it to a file and invoke
{noquote}
hbase shell
{noquote}
to load it.
Once shell has loaded, you can use
{noquote}
list_regions ''
{noquote}
> Develop HBase shell command/tool to list table's region info through command
> line
> -
>
> Key: HBASE-14925
> URL: https://issues.apache.org/jira/browse/HBASE-14925
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Romil Choksi
>Assignee: huaxiang sun
>
> I am going through the hbase shell commands to see if there is anything I can
> use to get all the regions info just for a particular table. I don’t see any
> such command that provides me that information.
> It would be better to have a command that provides region info, start key,
> end key etc taking a table name as the input parameter. This is available
> through HBase UI on clicking on a particular table's link
> A tool/shell command to get a list of regions for a table or all tables in a
> tabular structured output (that is machine readable)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17502) Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support matrix
[ https://issues.apache.org/jira/browse/HBASE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-17502: - Attachment: HBASE-17502.patch > Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support > matrix > > > Key: HBASE-17502 > URL: https://issues.apache.org/jira/browse/HBASE-17502 > Project: HBase > Issue Type: Task >Reporter: Jerry He > Attachments: HBASE-17502.patch > > > Hadoop pre-2.6.1 on JDK 1.8 has problem with Kerberos keytabe relogin. > HADOOP-10786 fixed the problem in Hadoop 2.6.1. > Let's document it in the Hadoop support matrix. > This was brought up in HBase 1.3.0 RC0 voting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17404) Replace explicit type with diamond operator in hbase-annotations
[
https://issues.apache.org/jira/browse/HBASE-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832675#comment-15832675
]
Hadoop QA commented on HBASE-17404:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 12m 59s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
55s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 7s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
13s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 8s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
8s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
7s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
6s {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}
26m 45s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 8s
{color} | {color:green} hbase-annotations in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
6s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 44m 47s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12845297/HBASE-17404.master.001.patch
|
| JIRA Issue | HBASE-17404 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 8c28628f3e88 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 7901805 |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5375/testReport/ |
| modules | C: hbase-annotations U: hbase-annotations |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5375/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Replace explicit type with diamond operator in hbase-annotations
>
>
> Key: HBASE-17404
> URL: https://issues.apache.org/jira/browse/HBASE-17404
> Project: HBase
> Issue Type: Improvement
>Reporter: Jan Hentschel
>
[jira] [Commented] (HBASE-17067) Procedure v2 - remove zklock/tryLock and use wait/wake
[
https://issues.apache.org/jira/browse/HBASE-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832687#comment-15832687
]
Hadoop QA commented on HBASE-17067:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 12m 45s
{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 8 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 9s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
50s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 45s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 0s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
52s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 47s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 38s {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-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 24s
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 82m 48s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 136m 55s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848634/HBASE-17067.master.004.patch
|
| JIRA Issue | HBASE-17067 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 09d156232c37 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 7901805 |
| Default Java | 1.8.0_121 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/5374/testReport/ |
| modules | C: hbase-procedure hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5374/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Procedure v2 - remove
[jira] [Updated] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-17465: -- Attachment: HBASE-17465-HBASE-14850.003.patch > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch, > HBASE-17465-HBASE-14850.001.patch, HBASE-17465-HBASE-14850.002.patch, > HBASE-17465-HBASE-14850.003.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17502) Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support matrix
[ https://issues.apache.org/jira/browse/HBASE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832699#comment-15832699 ] Ted Yu commented on HBASE-17502: Looks good overall. Please mention 1.7.0_80 for JDK 1.7 (mentioned at the bottom of HADOOP-10786) where the bug was present. > Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support > matrix > > > Key: HBASE-17502 > URL: https://issues.apache.org/jira/browse/HBASE-17502 > Project: HBase > Issue Type: Task >Reporter: Jerry He > Attachments: HBASE-17502.patch > > > Hadoop pre-2.6.1 on JDK 1.8 has problem with Kerberos keytabe relogin. > HADOOP-10786 fixed the problem in Hadoop 2.6.1. > Let's document it in the Hadoop support matrix. > This was brought up in HBase 1.3.0 RC0 voting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17465) [C++] implement request retry mechanism over RPC
[ https://issues.apache.org/jira/browse/HBASE-17465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832702#comment-15832702 ] Xiaobing Zhou commented on HBASE-17465: --- posted v3. # added AsyncSingleRequestRpcRetryingCaller skeleton. # fixed some reference issues. > [C++] implement request retry mechanism over RPC > > > Key: HBASE-17465 > URL: https://issues.apache.org/jira/browse/HBASE-17465 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-17465-HBASE-14850.000.patch, > HBASE-17465-HBASE-14850.001.patch, HBASE-17465-HBASE-14850.002.patch, > HBASE-17465-HBASE-14850.003.patch > > > HBASE-17051 implemented RPC layer. Requests retries will make system > reliable. This JIRA proposes adding it, which corresponds to similar > implementation in SingleRequestCallerBuilder (or BatchCallerBuilder, > ScanSingleRegionCallerBuilder, SmallScanCallerBuilder, etc.) and > AsyncSingleRequestRpcRetryingCaller. As a bonus, retry should be more > generic, decoupled with HRegionLocation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-9774) Provide a way for coprocessors to register and report custom metrics
[ https://issues.apache.org/jira/browse/HBASE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-9774: - Attachment: hbase-9774_v4.patch Patch from RB. Will commit this unless there is more feedback. > Provide a way for coprocessors to register and report custom metrics > > > Key: HBASE-9774 > URL: https://issues.apache.org/jira/browse/HBASE-9774 > Project: HBase > Issue Type: New Feature > Components: Coprocessors, metrics >Reporter: Gary Helmling >Assignee: Enis Soztutar > Attachments: hbase-9774_v1.patch, hbase-9774_v3.patch, > hbase-9774_v4.patch > > > It would help provide better visibility into what coprocessors are doing if > we provided a way for coprocessors to export their own metrics. The general > idea is to: > * extend access to the HBase "metrics bus" down into the coprocessor > environments > * coprocessors can then register and increment custom metrics > * coprocessor metrics are then reported along with all others through normal > mechanisms -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12894) Upgrade Jetty to 9.2.6
[
https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832722#comment-15832722
]
Hadoop QA commented on HBASE-12894:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 29s
{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 10 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 14s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
57s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m 49s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
17s {color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped patched modules with no Java source:
hbase-resource-bundle . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m 15s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 22s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 8s
{color} | {color:red} hbase-thrift in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 10s
{color} | {color:red} hbase-rest in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 46s
{color} | {color:red} hbase-spark in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m 26s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m 26s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
20s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
26s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 0s
{color} | {color:red} The patch 1 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 14s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
37m 26s {color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped patched modules with no Java source:
hbase-resource-bundle . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m 19s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 8s
{color} | {color:green} hbase-resource-bundle in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 5s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 137m 4s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 40s
{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 29s
{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m 51s
{color} | {color:green} hbase-rest in the patch passed. {color} |
|
[jira] [Commented] (HBASE-9774) Provide a way for coprocessors to register and report custom metrics
[
https://issues.apache.org/jira/browse/HBASE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832823#comment-15832823
]
Hadoop QA commented on HBASE-9774:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 13 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 21s
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
57s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m 5s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
14s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
11s {color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped patched modules with no Java source:
hbase-assembly . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m 7s
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 10s
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 7s
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
50s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m 28s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m 28s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
49s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
32s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 9s
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 17s {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-alpha1. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m 0s
{color} | {color:blue} Skipped patched modules with no Java source: .
hbase-assembly {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
28s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m 30s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 41s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 9s
{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 17s
{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 89m 5s {color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 19s
{color} | {color:green} hbase-assembly in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 23s
{color} | {color:green} hbase-examples in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 23s
{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 17s
{color} | {color:green} hbase-metrics in the patch passed. {color}
[jira] [Updated] (HBASE-17502) Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support matrix
[ https://issues.apache.org/jira/browse/HBASE-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-17502: - Attachment: HBASE-17502-v2.patch Addressed Ted's comment. > Document hadoop pre-2.6.1 and Java 1.8 Kerberos problem in our hadoop support > matrix > > > Key: HBASE-17502 > URL: https://issues.apache.org/jira/browse/HBASE-17502 > Project: HBase > Issue Type: Task >Reporter: Jerry He > Attachments: HBASE-17502.patch, HBASE-17502-v2.patch > > > Hadoop pre-2.6.1 on JDK 1.8 has problem with Kerberos keytabe relogin. > HADOOP-10786 fixed the problem in Hadoop 2.6.1. > Let's document it in the Hadoop support matrix. > This was brought up in HBase 1.3.0 RC0 voting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17067) Procedure v2 - remove zklock/tryLock and use wait/wake
[ https://issues.apache.org/jira/browse/HBASE-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17067: -- Attachment: HBASE-17067.master.004.patch That last run was good. Let me try another. > Procedure v2 - remove zklock/tryLock and use wait/wake > -- > > Key: HBASE-17067 > URL: https://issues.apache.org/jira/browse/HBASE-17067 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-17067.master.001.patch, > HBASE-17067.master.002.patch, HBASE-17067.master.003.patch, > HBASE-17067.master.004.patch, HBASE-17067.master.004.patch, > HBASE-17067.master.004.patch, HBASE-17067.master.004.patch, > HBASE-17067.master.004.patch > > > Once we have HBASE-16744, HBASE-16786, HBASE-16831. we can remove the > tryLock() methods and replace them with the wait/wake methods that are using > the framework events instead of spinning until we can start the proc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832832#comment-15832832 ] stack commented on HBASE-14614: --- At least some of the failures above are because split/merge not implemented on AMv2. Working on it (talking to [~syuanjiang]) > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.001.patch, > HBASE-14614.master.002.patch, HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-17357:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.4.0
2.0.0
Status: Resolved (was: Patch Available)
Pushed to master branch and branch-1. Thank you for the fix [~dnavarro]
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-17357-1.patch, HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-10699) Optimize some code; set capacity on arraylist when possible; use isEmpty; reduce allocations
[ https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10699: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Pushed to master. Thats some nice fixup [~Jan Hentschel]. Thanks for the sweet patch. > Optimize some code; set capacity on arraylist when possible; use isEmpty; > reduce allocations > > > Key: HBASE-10699 > URL: https://issues.apache.org/jira/browse/HBASE-10699 > Project: HBase > Issue Type: Improvement >Reporter: @deprecated Yi Deng >Assignee: Jan Hentschel > Fix For: 2.0.0 > > Attachments: HBASE-10699.master.001.patch > > > 1. Set capacity on ArrayList when possible > 2. Use isEmpty instead of size() == 0 when possible > 3. Reduce some unnecessary allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10699) Optimize some code; set capacity on arraylist when possible; use isEmpty; reduce allocations
[ https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832849#comment-15832849 ] stack commented on HBASE-10699: --- Also, thanks for aggregating. > Optimize some code; set capacity on arraylist when possible; use isEmpty; > reduce allocations > > > Key: HBASE-10699 > URL: https://issues.apache.org/jira/browse/HBASE-10699 > Project: HBase > Issue Type: Improvement >Reporter: @deprecated Yi Deng >Assignee: Jan Hentschel > Fix For: 2.0.0 > > Attachments: HBASE-10699.master.001.patch > > > 1. Set capacity on ArrayList when possible > 2. Use isEmpty instead of size() == 0 when possible > 3. Reduce some unnecessary allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10699) Optimize some code; set capacity on arraylist when possible; use isEmpty; reduce allocations
[ https://issues.apache.org/jira/browse/HBASE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10699: -- Summary: Optimize some code; set capacity on arraylist when possible; use isEmpty; reduce allocations (was: Optimize some code) > Optimize some code; set capacity on arraylist when possible; use isEmpty; > reduce allocations > > > Key: HBASE-10699 > URL: https://issues.apache.org/jira/browse/HBASE-10699 > Project: HBase > Issue Type: Improvement >Reporter: @deprecated Yi Deng >Assignee: Jan Hentschel > Attachments: HBASE-10699.master.001.patch > > > 1. Set capacity on ArrayList when possible > 2. Use isEmpty instead of size() == 0 when possible > 3. Reduce some unnecessary allocation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17404) Replace explicit type with diamond operator in hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17404: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Pushed to master. Thanks [~Jan Hentschel] > Replace explicit type with diamond operator in hbase-annotations > > > Key: HBASE-17404 > URL: https://issues.apache.org/jira/browse/HBASE-17404 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17404.master.001.patch > > > Because HBase uses Java 8 explicit types in the *hbase-annotations* module > (*RootDocProcessor* and *StabilityOptions* classes) can be replaced with the > diamond operator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12894) Upgrade Jetty to 9.2.6
[ https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12894: -- Attachment: HBASE-12894.master.002.patch > Upgrade Jetty to 9.2.6 > -- > > Key: HBASE-12894 > URL: https://issues.apache.org/jira/browse/HBASE-12894 > Project: HBase > Issue Type: Improvement > Components: REST, UI >Affects Versions: 0.98.0 >Reporter: Rick Hallihan >Assignee: Guang Yang >Priority: Critical > Labels: MicrosoftSupport > Fix For: 2.0.0 > > Attachments: dependency_list_after, dependency_list_before, > HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v10.patch, > HBASE-12894_Jetty9_v1.patch, HBASE-12894_Jetty9_v1.patch, > HBASE-12894_Jetty9_v2.patch, HBASE-12894_Jetty9_v3.patch, > HBASE-12894_Jetty9_v4.patch, HBASE-12894_Jetty9_v5.patch, > HBASE-12894_Jetty9_v6.patch, HBASE-12894_Jetty9_v7.patch, > HBASE-12894_Jetty9_v8.patch, HBASE-12894.master.001.patch, > HBASE-12894.master.002.patch > > > The Jetty component that is used for the HBase Stargate REST endpoint is > version 6.1.26 and is fairly outdated. We recently had a customer inquire > about enabling cross-origin resource sharing (CORS) for the REST endpoint and > found that this older version does not include the necessary filter or > configuration options, highlighted at: > http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter > The Jetty project has had significant updates through versions 7, 8 and 9, > including a transition to be an Eclipse subproject, so updating to the latest > version may be non-trivial. The last update to the Jetty component in > https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update > and did not require significant work. This update will include a package > namespace update so there will likely be a larger number of required changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12894) Upgrade Jetty to 9.2.6
[ https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832869#comment-15832869 ] stack commented on HBASE-12894: --- -002 fixes the white space issue. The test failures seem unrelated and don't fail for me locally. > Upgrade Jetty to 9.2.6 > -- > > Key: HBASE-12894 > URL: https://issues.apache.org/jira/browse/HBASE-12894 > Project: HBase > Issue Type: Improvement > Components: REST, UI >Affects Versions: 0.98.0 >Reporter: Rick Hallihan >Assignee: Guang Yang >Priority: Critical > Labels: MicrosoftSupport > Fix For: 2.0.0 > > Attachments: dependency_list_after, dependency_list_before, > HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v10.patch, > HBASE-12894_Jetty9_v1.patch, HBASE-12894_Jetty9_v1.patch, > HBASE-12894_Jetty9_v2.patch, HBASE-12894_Jetty9_v3.patch, > HBASE-12894_Jetty9_v4.patch, HBASE-12894_Jetty9_v5.patch, > HBASE-12894_Jetty9_v6.patch, HBASE-12894_Jetty9_v7.patch, > HBASE-12894_Jetty9_v8.patch, HBASE-12894.master.001.patch, > HBASE-12894.master.002.patch > > > The Jetty component that is used for the HBase Stargate REST endpoint is > version 6.1.26 and is fairly outdated. We recently had a customer inquire > about enabling cross-origin resource sharing (CORS) for the REST endpoint and > found that this older version does not include the necessary filter or > configuration options, highlighted at: > http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter > The Jetty project has had significant updates through versions 7, 8 and 9, > including a transition to be an Eclipse subproject, so updating to the latest > version may be non-trivial. The last update to the Jetty component in > https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update > and did not require significant work. This update will include a package > namespace update so there will likely be a larger number of required changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12894) Upgrade Jetty to 9.2.6
[
https://issues.apache.org/jira/browse/HBASE-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832871#comment-15832871
]
Hadoop QA commented on HBASE-12894:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s {color}
| {color:red} HBASE-12894 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12848699/HBASE-12894.master.002.patch
|
| JIRA Issue | HBASE-12894 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/5379/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Upgrade Jetty to 9.2.6
> --
>
> Key: HBASE-12894
> URL: https://issues.apache.org/jira/browse/HBASE-12894
> Project: HBase
> Issue Type: Improvement
> Components: REST, UI
>Affects Versions: 0.98.0
>Reporter: Rick Hallihan
>Assignee: Guang Yang
>Priority: Critical
> Labels: MicrosoftSupport
> Fix For: 2.0.0
>
> Attachments: dependency_list_after, dependency_list_before,
> HBASE-12894_Jetty9_v0.patch, HBASE-12894_Jetty9_v10.patch,
> HBASE-12894_Jetty9_v1.patch, HBASE-12894_Jetty9_v1.patch,
> HBASE-12894_Jetty9_v2.patch, HBASE-12894_Jetty9_v3.patch,
> HBASE-12894_Jetty9_v4.patch, HBASE-12894_Jetty9_v5.patch,
> HBASE-12894_Jetty9_v6.patch, HBASE-12894_Jetty9_v7.patch,
> HBASE-12894_Jetty9_v8.patch, HBASE-12894.master.001.patch,
> HBASE-12894.master.002.patch
>
>
> The Jetty component that is used for the HBase Stargate REST endpoint is
> version 6.1.26 and is fairly outdated. We recently had a customer inquire
> about enabling cross-origin resource sharing (CORS) for the REST endpoint and
> found that this older version does not include the necessary filter or
> configuration options, highlighted at:
> http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter
> The Jetty project has had significant updates through versions 7, 8 and 9,
> including a transition to be an Eclipse subproject, so updating to the latest
> version may be non-trivial. The last update to the Jetty component in
> https://issues.apache.org/jira/browse/HBASE-3377 was a minor version update
> and did not require significant work. This update will include a package
> namespace update so there will likely be a larger number of required changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17462) Investigate using sliding window for read/write request costs in StochasticLoadBalancer
[ https://issues.apache.org/jira/browse/HBASE-17462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831910#comment-15831910 ] Ted Yu commented on HBASE-17462: In CostFromRegionLoadAsRateFunction#getRegionLoadCost(), cost may become negative. Should the negative cost be bounded by zero before returning ? > Investigate using sliding window for read/write request costs in > StochasticLoadBalancer > --- > > Key: HBASE-17462 > URL: https://issues.apache.org/jira/browse/HBASE-17462 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Tim Brown > Labels: patch > Fix For: 2.0.0, 1.4.0 > > Attachments: after_changes.png, before_changes.png, HBASE-17462.patch > > > In the thread, http://search-hadoop.com/m/HBase/YGbbyUZKXWALkX1, Timothy was > asking whether the read/write request costs in StochasticLoadBalancer should > be calculated as rates. > This makes sense since read / write load on region server tends to fluctuate > over time. Using sliding window would reflect more recent trend in read / > write load. > Some factors to consider: > The data structure used by StochasticLoadBalancer should be concise. The > number of regions in a cluster can be expected to approach 1 million. We > cannot afford to store long history of read / write requests in master. > Efficiency of cost calculation should be high - there're many cost > functions the balancer goes through, it is expected for each cost function > to return quickly. Otherwise we would not come up with proper region > movement plan(s) in time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16812) Fix mob locks and correctly override HMobStore.compact()
[ https://issues.apache.org/jira/browse/HBASE-16812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831756#comment-15831756 ] Jingcheng Du commented on HBASE-16812: -- Thanks a lot Mr. [~stack]. It is okay. Anyway I will try to remove all the existing locks in MOB. Sorry for the delay, I had a business trip recently and will resume the patch very soon. Thanks. > Fix mob locks and correctly override HMobStore.compact() > - > > Key: HBASE-16812 > URL: https://issues.apache.org/jira/browse/HBASE-16812 > Project: HBase > Issue Type: Task >Reporter: Appy >Assignee: Jingcheng Du >Priority: Minor > Attachments: HBASE-16812.master.001.patch > > > compact(CompactionContext compaction, CompactionThroughputController > throughputController) is [deprecated in 1.2.0 > release|https://github.com/apache/hbase/blob/rel/1.2.0/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java#L222]. > Store.java is also marked limited private. > Context: I was cleaning up zk table lock which is also used in that method's > [override|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HMobStore.java#L460] > in HMobStore. > This method isn't being called from anywhere except CompactionTool (which > creates HStore object, not HMobStore object). > [~jingcheng...@intel.com] Can you PTAL and help me understand what's going on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17489) ClientScanner may send a next request to a RegionScanner which has been exhausted
[ https://issues.apache.org/jira/browse/HBASE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831744#comment-15831744 ] Duo Zhang commented on HBASE-17489: --- The failed UTs can pass locally, and seems our master build has been failed randomly recently? > ClientScanner may send a next request to a RegionScanner which has been > exhausted > - > > Key: HBASE-17489 > URL: https://issues.apache.org/jira/browse/HBASE-17489 > Project: HBase > Issue Type: Bug > Components: Client, scan >Affects Versions: 2.0.0, 1.3.0, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 2.0.0, 1.4.0, 1.3.1 > > Attachments: HBASE-17489.patch, HBASE-17489-v1.patch, > HBASE-17489-v2.patch, HBASE-17489-v3.patch, HBASE-17489-v4.patch > > > Found it when implementing HBASE-17045. Seems the final result of the scan is > correct but no doubt the logic is broken. We need to fix it to stop things > get worse in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17488) WALEdit should be lazily instantiated
[ https://issues.apache.org/jira/browse/HBASE-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831547#comment-15831547 ] ChiaPing Tsai commented on HBASE-17488: --- [~stack] The patch is ready for review. Would you please take a look? Thanks. > WALEdit should be lazily instantiated > - > > Key: HBASE-17488 > URL: https://issues.apache.org/jira/browse/HBASE-17488 > Project: HBase > Issue Type: Improvement >Reporter: ChiaPing Tsai >Assignee: ChiaPing Tsai >Priority: Trivial > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-17488.branch-1.v0.patch, > HBASE-17488.branch-1.v0.patch, HBASE-17488.branch-1.v1.patch, > HBASE-17488.v0.patch > > > Some trivial improvement. > # create the WALEdit on step 3 instead of step 2 > # count the cells from coprocessor > # don’t count the mutations which contain the Durability.SKIP_WAL property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17487) Throw exception when pushing pipeline to snapshot fails twice
[ https://issues.apache.org/jira/browse/HBASE-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831580#comment-15831580 ] Ted Yu commented on HBASE-17487: CompactingMemStore#snapshot() doesn't declare throwing exception. The loop inside pushPipelineToSnapshot() is supposed to handle temporary error. However, we know there should be no 3rd iteration of the loop. How about just changing the LOG from warn (likely to be ignored by admin) to error ? > Throw exception when pushing pipeline to snapshot fails twice > - > > Key: HBASE-17487 > URL: https://issues.apache.org/jira/browse/HBASE-17487 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Minor > Attachments: 17487.v2.txt > > > In CompactingMemStore#pushPipelineToSnapshot() , there is limit of 3 > iterations of pipeline.swap() call after which an empty ImmutableSegment is > used as snapshot. > However, there should be at most two iterations in pushPipelineToSnapshot() > since during the second iteration there is no concurrent write to memstore. > We should throw exception in the 3rd iteration to signify that this scenario > should never happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17487) Throw exception when pushing pipeline to snapshot fails twice
[ https://issues.apache.org/jira/browse/HBASE-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anastasia Braginsky updated HBASE-17487: Issue Type: Improvement (was: Bug) > Throw exception when pushing pipeline to snapshot fails twice > - > > Key: HBASE-17487 > URL: https://issues.apache.org/jira/browse/HBASE-17487 > Project: HBase > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Minor > Attachments: 17487.v2.txt > > > In CompactingMemStore#pushPipelineToSnapshot() , there is limit of 3 > iterations of pipeline.swap() call after which an empty ImmutableSegment is > used as snapshot. > However, there should be at most two iterations in pushPipelineToSnapshot() > since during the second iteration there is no concurrent write to memstore. > We should throw exception in the 3rd iteration to signify that this scenario > should never happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17491) Remove all setters from HTable interface and introduce a TableBuilder to build Table instance
[
https://issues.apache.org/jira/browse/HBASE-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832116#comment-15832116
]
stack commented on HBASE-17491:
---
Just seems odd making an Interface and not using it. This is nit stuff given
this is all internal. What if you added a getter on the Builder Interface for
tableName? That would 'force' implementations to pass TableName on
construction. Then you'd have a getter to pull on inside in the HTable
constructor...
If you passed the tablename separate from the builder (as it is now) would that
help?
v4 still has
2856// trivial change to trigger UT TODO remove me
2857LOG.trace("HRegionServer#main");
There is still a getTable in the Connection Implementation?
Patch looks great otherwise. Thanks [~carp84]
> Remove all setters from HTable interface and introduce a TableBuilder to
> build Table instance
> -
>
> Key: HBASE-17491
> URL: https://issues.apache.org/jira/browse/HBASE-17491
> Project: HBase
> Issue Type: Sub-task
>Reporter: Yu Li
>Assignee: Yu Li
> Attachments: HBASE-17491.patch, HBASE-17491.v2.patch,
> HBASE-17491.v3.patch, HBASE-17491.v4.patch
>
>
> As titled, we will remove all setters in HTable for master branch and
> deprecate them for branch-1 to make HTable thread-safe. And a new
> {{TableBuilder}} interface will be introduced to build Table instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832126#comment-15832126
]
stack commented on HBASE-17357:
---
[~dnavarro] You want to be consistent w/ your spacing. The if has no space
before the bracket but it does before the curly. See the rest of the code in
the class and follow its model.
Is the errCode non-null? Did you try your patch? Thanks [~dnavarro]
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17496) RSGroup shell commands:get_server_rsgroup don't work and commands display an incorrect result size
[
https://issues.apache.org/jira/browse/HBASE-17496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-17496:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master branch. Thank you for the patch [~andrewcheng]
> RSGroup shell commands:get_server_rsgroup don't work and commands display an
> incorrect result size
> --
>
> Key: HBASE-17496
> URL: https://issues.apache.org/jira/browse/HBASE-17496
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
> Labels: rsgroup
> Fix For: 2.0.0
>
> Attachments: HBASE-17496-master-v1.patch
>
>
> scenario as follows:
> {code}
> hbase(main):001:0> get_server_rsgroup 'hbase-01:16030'
> ERROR: undefined method `getRSGroupOfServer' for
> #
> Here is some help for this command:
> Get the group name the given region server is a member of.
> hbase> get_server_rsgroup 'server1:port1'
> Took 0.0160 seconds
> {code}
> {code}
> hbase(main):002:0> list_rsgroups
> GROUPS
> default
> 1484874115 row(s)
> Took 0.3830 seconds
> {code}
> {code}
> hbase(main):003:0> get_table_rsgroup 't1'
> default
> 1484874133 row(s)
> Took 0.0100 seconds
> {code}
> {code}
> hbase(main):004:0> get_rsgroup 'default'
> GROUP INFORMATION
> Servers:
> hbase-01:16030
> Tables:
> hbase:meta
> t1
> hbase:namespace
> hbase:rsgroup
> 1484874150 row(s)
> Took 0.0140 seconds
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17497) Add first async MetaTableAccessor impl and Implement tableExists method
[ https://issues.apache.org/jira/browse/HBASE-17497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17497: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master branch. Thank you for the patch [~zghaobac] > Add first async MetaTableAccessor impl and Implement tableExists method > --- > > Key: HBASE-17497 > URL: https://issues.apache.org/jira/browse/HBASE-17497 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-17497-v1.patch > > > HBaseAdmin use many MetaTableAccessor's static methods. So add a async > MetaTableAccessor for AsyncHBaseAdmin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17488) WALEdit should be lazily instantiated
[ https://issues.apache.org/jira/browse/HBASE-17488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17488: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master and branch-1. Thank you for the patch [~chia7712]. Consider using the nice ./dev-tools/submit-patch.py in future. It will do proper formatting of the patch for you, makes the commiter's life a little easier getting stuff in, and it ensures you get credit for your work. Go easy. > WALEdit should be lazily instantiated > - > > Key: HBASE-17488 > URL: https://issues.apache.org/jira/browse/HBASE-17488 > Project: HBase > Issue Type: Improvement >Reporter: ChiaPing Tsai >Assignee: ChiaPing Tsai >Priority: Trivial > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-17488.branch-1.v0.patch, > HBASE-17488.branch-1.v0.patch, HBASE-17488.branch-1.v1.patch, > HBASE-17488.v0.patch > > > Some trivial improvement. > # create the WALEdit on step 3 instead of step 2 > # count the cells from coprocessor > # don’t count the mutations which contain the Durability.SKIP_WAL property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17067) Procedure v2 - remove zklock/tryLock and use wait/wake
[ https://issues.apache.org/jira/browse/HBASE-17067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17067: -- Attachment: HBASE-17067.master.004.patch Retry. These tests don't fail locally (they just passed in the previous run... only minor change in last version of patch) > Procedure v2 - remove zklock/tryLock and use wait/wake > -- > > Key: HBASE-17067 > URL: https://issues.apache.org/jira/browse/HBASE-17067 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-17067.master.001.patch, > HBASE-17067.master.002.patch, HBASE-17067.master.003.patch, > HBASE-17067.master.004.patch, HBASE-17067.master.004.patch > > > Once we have HBASE-16744, HBASE-16786, HBASE-16831. we can remove the > tryLock() methods and replace them with the wait/wake methods that are using > the framework events instead of spinning until we can start the proc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832085#comment-15832085
]
David Navarro commented on HBASE-17357:
---
I would like to work on this.
Can someone assign this to me?
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Priority: Minor
> Labels: beginner
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Navarro updated HBASE-17357:
--
Status: Patch Available (was: Open)
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Navarro updated HBASE-17357:
--
Attachment: HBASE-17357.patch
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-17357.patch
>
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14614) Procedure v2: Core Assignment Manager
[ https://issues.apache.org/jira/browse/HBASE-14614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-14614: -- Attachment: HBASE-14614.master.008.patch > Procedure v2: Core Assignment Manager > - > > Key: HBASE-14614 > URL: https://issues.apache.org/jira/browse/HBASE-14614 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Affects Versions: 2.0.0 >Reporter: Stephen Yuan Jiang >Assignee: Matteo Bertozzi > Fix For: 2.0.0 > > Attachments: HBASE-14614.master.001.patch, > HBASE-14614.master.002.patch, HBASE-14614.master.003.patch, > HBASE-14614.master.004.patch, HBASE-14614.master.005.patch, > HBASE-14614.master.006.patch, HBASE-14614.master.007.patch, > HBASE-14614.master.008.patch > > > New AssignmentManager implemented using proc-v2. > - AssignProcedure handle assignment operation > - UnassignProcedure handle unassign operation > - MoveRegionProcedure handle move/balance operation > Concurrent Assign operations are batched together and sent to the balancer > Concurrent Assign and Unassign operation ready to be sent to the RS are > batched together > This patch is an intermediate state where we add the new AM as > AssignmentManager2() to the master, to be reached by tests. but the new AM > will not be integrated with the rest of the system. Only new am unit-tests > will exercise the new assigment manager. The integration with the master code > is part of HBASE-14616 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-17357) PerformanceEvaluation parameters parsing triggers NPE.
[
https://issues.apache.org/jira/browse/HBASE-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-17357:
--
Assignee: David Navarro
> PerformanceEvaluation parameters parsing triggers NPE.
> --
>
> Key: HBASE-17357
> URL: https://issues.apache.org/jira/browse/HBASE-17357
> Project: HBase
> Issue Type: Bug
> Components: Performance, test
>Affects Versions: 1.2.4
>Reporter: Jean-Marc Spaggiari
>Assignee: David Navarro
>Priority: Minor
> Labels: beginner
>
> When using wrong parameters, PE triggers an NPE. Should not
> {code}
> @hbasetest1:~# hbase pe --nomapred
> 16/12/21 16:38:50 INFO Configuration.deprecation: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.determineCommandClass(PerformanceEvaluation.java:2145)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.run(PerformanceEvaluation.java:2127)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.PerformanceEvaluation.main(PerformanceEvaluation.java:2150)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
