[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[
https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213748#comment-16213748
]
Hadoop QA commented on HBASE-19007:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 21m
50s{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 28 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
38s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
22s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
26s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
47s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
38m 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-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
29s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}122m 24s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
13s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
14s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
35s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
28s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}235m 52s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19007 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893387/HBASE-19007.master.012.patch
|
| Optional Tests | asflicense
[jira] [Commented] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[
https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213745#comment-16213745
]
Hadoop QA commented on HBASE-19053:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 18m
11s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 38 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
45s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 4m
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 12m
49s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 7m
7s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 8m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 4m
45s{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 110 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
13s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 6m
15s{color} | {color:red} patch has 12 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
56m 22s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
28s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
22s{color} | {color:red} hbase-common generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 4m
3s{color} | {color:red} root generated 1 new + 25 unchanged - 0 fixed = 26
total (was 25) {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 10m 31s{color}
| {color:red} root in the patch failed. {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}165m 55s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
|
[jira] [Commented] (HBASE-19049) Update kerby to 1.0.1 GA release
[
https://issues.apache.org/jira/browse/HBASE-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213741#comment-16213741
]
Hadoop QA commented on HBASE-19049:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m
9s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 13m
55s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
10s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
41m 32s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
8s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}106m 27s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}193m 29s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.security.token.TestZKSecretWatcher |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19049 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893285/HBASE-19049.1.patch |
| Optional Tests | asflicense javac javadoc unit shadedjars hadoopcheck
xml compile |
| uname | Linux c9bb4f215829 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / cb5c477 |
| Default Java | 1.8.0_141 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/9289/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9289/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9289/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Update kerby to 1.0.1 GA release
>
>
> Key: HBASE-19049
> URL: https://issues.apache.org/jira/browse/HBASE-19049
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Affects Versions: 2.0.0-alpha-3
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>
[jira] [Updated] (HBASE-16290) Dump summary of callQueue content; can help debugging
[ https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreeram Venkatasubramanian updated HBASE-16290: --- Attachment: HBASE-16290.master.006.patch > Dump summary of callQueue content; can help debugging > - > > Key: HBASE-16290 > URL: https://issues.apache.org/jira/browse/HBASE-16290 > Project: HBase > Issue Type: Bug > Components: Operability >Affects Versions: 2.0.0 >Reporter: stack >Assignee: Sreeram Venkatasubramanian > Labels: beginner > Fix For: 2.0.0 > > Attachments: DebugDump_screenshot.png, HBASE-16290.master.001.patch, > HBASE-16290.master.002.patch, HBASE-16290.master.003.patch, > HBASE-16290.master.004.patch, HBASE-16290.master.005.patch, > HBASE-16290.master.006.patch, Sample Summary.txt > > > Being able to get a clue what is in a backedup callQueue could give insight > on what is going on on a jacked server. Just needs to summarize count, sizes, > call types. Useful debugging. In a servlet? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213735#comment-16213735
]
Hadoop QA commented on HBASE-18846:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 14m
24s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
38s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
22s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 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
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 2m
39s{color} | {color:red} patch has 10 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 55s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
26s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 54m 2s{color}
| {color:red} root in the patch failed. {color} |
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m
13s{color} | {color:red} The patch generated 1 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}147m 22s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.procedure.TestProcedureManager |
| | hadoop.hbase.master.balancer.TestRegionLocationFinder |
| | hadoop.hbase.ipc.TestNettyRpcServer |
| | hadoop.hbase.regionserver.TestHRegionFileSystem |
| | hadoop.hbase.master.locking.TestLockProcedure |
| | hadoop.hbase.master.locking.TestLockManager |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213732#comment-16213732 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3922 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3922/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev b10ad9e97f67b462a4ab58ee1d449c9c319c4176) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213731#comment-16213731
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3922 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3922/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev dd4dbae7643a7fb0beaa4e75a51d5a9c921c89b2)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213729#comment-16213729
]
Peter Somogyi commented on HBASE-19019:
---
Master works, attaching for branch-1.
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19019) QA fails on hbase-thrift module with timeout
[
https://issues.apache.org/jira/browse/HBASE-19019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated HBASE-19019:
--
Attachment: HBASE-19019.branch-1.001.patch
> QA fails on hbase-thrift module with timeout
>
>
> Key: HBASE-19019
> URL: https://issues.apache.org/jira/browse/HBASE-19019
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Reporter: Peter Somogyi
>Priority: Critical
> Attachments: HBASE-19019.branch-1.001.patch,
> HBASE-19019.master.001.patch
>
>
> For any modification in hbase-thrift module the precommit build fails with
> timeout for {{TestThriftServerCmdLine}}. I noticed this failure on multiple
> patches: HBASE-18967 and HBASE-18996 even when the patch did not contain any
> modification
> (https://issues.apache.org/jira/secure/attachment/12892414/HBASE-18967.branch-1.3.002.patch)
> The {{TestThriftServerCmdLine}} test passes locally on both mentioned patches.
> One failure: https://builds.apache.org/job/PreCommit-HBASE-Build/9127/
> {code}
> [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ hbase-thrift ---
> [INFO] Surefire report directory:
> /testptch/hbase/hbase-thrift/target/surefire-reports
> [INFO] Using configured provider
> org.apache.maven.surefire.junitcore.JUnitCoreProvider
> [INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
> useUnlimitedThreads=false, threadCountSuites=0, threadCountClasses=0,
> threadCountMethods=0, parallelOptimized=true
> ---
> T E S T S
> ---
> Running org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Tests run: 29, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 48.201 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.257 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithReadOnly
> Running
> org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.621 sec -
> in org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandlerWithLabels
> Running org.apache.hadoop.hbase.thrift.TestCallQueue
> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.473 sec -
> in org.apache.hadoop.hbase.thrift.TestCallQueue
> Running org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.239 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftHttpServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServer
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 75.55 sec -
> in org.apache.hadoop.hbase.thrift.TestThriftServer
> Running org.apache.hadoop.hbase.thrift.TestThriftServerCmdLine
> Results :
> Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 18:33.104s
> [INFO] Finished at: Mon Oct 16 03:42:59 UTC 2017
> [INFO] Final Memory: 61M/1299M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on
> project hbase-thrift: There was a timeout or other error in the fork -> [Help
> 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213726#comment-16213726
]
Hudson commented on HBASE-19058:
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2012 (See
[https://builds.apache.org/job/HBase-1.1-JDK8/2012/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
a52770851afdeaba06cd7b849520996c4a07e289)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213728#comment-16213728 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-1.4 #961 (See [https://builds.apache.org/job/HBase-1.4/961/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 122fceb53431e664848943829dbb66d52fd1cceb) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213724#comment-16213724
]
Hudson commented on HBASE-19060:
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2012 (See
[https://builds.apache.org/job/HBase-1.1-JDK8/2012/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev daaa3cffca7b37153141b3ec23248012dfcca9c9)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213725#comment-16213725 ] Hudson commented on HBASE-19039: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2012 (See [https://builds.apache.org/job/HBase-1.1-JDK8/2012/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 1c137096e26821e944898d0b3659e49c6b0b50a5) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213727#comment-16213727
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-1.4 #961 (See
[https://builds.apache.org/job/HBase-1.4/961/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev bb1fd4af66fbfba5a716a4fd514be5c5e6c3ab4c)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19030) nightly runs should attempt to log test results after archiving
[
https://issues.apache.org/jira/browse/HBASE-19030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213723#comment-16213723
]
Hadoop QA commented on HBASE-19030:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
4s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
6s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 59s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:cb5c477 |
| JIRA Issue | HBASE-19030 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893053/HBASE-19030.0.patch |
| Optional Tests | asflicense shellcheck shelldocs |
| uname | Linux 19af92635f89 3.13.0-117-generic #164-Ubuntu SMP Fri Apr 7
11:05:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / cb5c477 |
| shellcheck | v0.4.6 |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9297/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> nightly runs should attempt to log test results after archiving
> ---
>
> Key: HBASE-19030
> URL: https://issues.apache.org/jira/browse/HBASE-19030
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Attachments: HBASE-19030.0.patch
>
>
> right now on the nightly tests the first post-action we do is log junit
> results. due to current limitations of Jenkins DSL, if this step fails none
> of the other post actions will happen.
> Since we might not make junit test results, e.g. in the case of a timeout of
> yetus itself, we should log the junit results after we've saved whatever we
> can of yetus output.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213711#comment-16213711 ] Hudson commented on HBASE-19039: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1928 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1928/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 1c137096e26821e944898d0b3659e49c6b0b50a5) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213710#comment-16213710
]
Hudson commented on HBASE-19060:
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1928 (See
[https://builds.apache.org/job/HBase-1.1-JDK7/1928/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev daaa3cffca7b37153141b3ec23248012dfcca9c9)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213712#comment-16213712
]
Hudson commented on HBASE-19058:
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1928 (See
[https://builds.apache.org/job/HBase-1.1-JDK7/1928/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
a52770851afdeaba06cd7b849520996c4a07e289)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18893) Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using ModifyTableProcedure
[ https://issues.apache.org/jira/browse/HBASE-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213706#comment-16213706 ] Mike Drob commented on HBASE-18893: --- Looks like the check happens in prepareAdd/Delete. I don't think we have enough information anymore to do the same check in prepareModify of the ModifyTable proc. We could fail in TableDescBuilder instead, or in the admin API directly. Or just fail silently - the invariant will be correct that after add the column will exist and after delete it won't although an add turning into a modify will likely surprise users so I don't think this is a great idea. > Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using > ModifyTableProcedure > > > Key: HBASE-18893 > URL: https://issues.apache.org/jira/browse/HBASE-18893 > Project: HBase > Issue Type: Bug > Components: Coprocessors, master >Reporter: Mike Drob >Assignee: Mike Drob > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18893.patch, HBASE-18893.v2.patch, > HBASE-18893.v3.patch > > > The shell changed from using separate add/modify/delete column calls to > funneling everything through modify table for performance reasons. We know > that using modify table works for everything. Let's drop the old code for > Add/Modify/Delete Column so that we have a lower maintenance burden and fewer > code paths to reason about. > Was: shell 'alter' command no longer distinguishes column > add/modify/delete > After HBASE-15641 all 'alter' commands go through a single modifyTable call > at the end, so we no longer can easily distinguish add, modify, and delete > column events. This potentially affects coprocessors that needed the update > notifications for new or removed columns. > Let's let the shell still make separate behaviour calls like it did before > without undoing the batching that seems pretty useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213703#comment-16213703
]
Hudson commented on HBASE-19058:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #983 (See
[https://builds.apache.org/job/HBase-1.2-IT/983/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f29f1702ac1099052ad19153a2a364b3141bb059)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18873) Hide protobufs in GlobalQuotaSettings
[
https://issues.apache.org/jira/browse/HBASE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213701#comment-16213701
]
Hadoop QA commented on HBASE-18873:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 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 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
27s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
17s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
4s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
31s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
52s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
37s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
53s{color} | {color:green} branch-2 passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
23s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
8s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 43s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
25s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}117m 55s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
57s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}185m 31s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.regionserver.TestCompactionInDeadRegionServer |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:64f024a |
| JIRA Issue | HBASE-18873 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893362/HBASE-18873.003.branch-2.patch
|
| Optional Tests | asflicense shadedjars javac javadoc unit findbugs
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux f8a5feddc6ac 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-18893) Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using ModifyTableProcedure
[ https://issues.apache.org/jira/browse/HBASE-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213697#comment-16213697 ] Mike Drob commented on HBASE-18893: --- Test failures are probably legitimate, assuming that we want to continue to fail on adding an already existing column and deleting a non-existent column. I have to go spelunking to see where the error originates from in the current incarnation though. > Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using > ModifyTableProcedure > > > Key: HBASE-18893 > URL: https://issues.apache.org/jira/browse/HBASE-18893 > Project: HBase > Issue Type: Bug > Components: Coprocessors, master >Reporter: Mike Drob >Assignee: Mike Drob > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18893.patch, HBASE-18893.v2.patch, > HBASE-18893.v3.patch > > > The shell changed from using separate add/modify/delete column calls to > funneling everything through modify table for performance reasons. We know > that using modify table works for everything. Let's drop the old code for > Add/Modify/Delete Column so that we have a lower maintenance burden and fewer > code paths to reason about. > Was: shell 'alter' command no longer distinguishes column > add/modify/delete > After HBASE-15641 all 'alter' commands go through a single modifyTable call > at the end, so we no longer can easily distinguish add, modify, and delete > column events. This potentially affects coprocessors that needed the update > notifications for new or removed columns. > Let's let the shell still make separate behaviour calls like it did before > without undoing the batching that seems pretty useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213690#comment-16213690
]
Hudson commented on HBASE-19061:
SUCCESS: Integrated in Jenkins build HBase-1.5 #105 (See
[https://builds.apache.org/job/HBase-1.5/105/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
c782e494078a3fe0cc20a4cf7cc8bd0cfd682feb)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16338) update jackson to 2.y
[ https://issues.apache.org/jira/browse/HBASE-16338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213689#comment-16213689 ] Hadoop QA commented on HBASE-16338: --- (!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://builds.apache.org/job/PreCommit-HBASE-Build/9295/console in case of problems. > update jackson to 2.y > - > > Key: HBASE-16338 > URL: https://issues.apache.org/jira/browse/HBASE-16338 > Project: HBase > Issue Type: Task > Components: dependencies >Reporter: Sean Busbey >Assignee: Mike Drob > Fix For: 2.0.0-beta-2 > > Attachments: 16338.txt, HBASE-16338.branch-2.patch, > HBASE-16338.v10.patch, HBASE-16338.v11.patch, HBASE-16338.v2.patch, > HBASE-16338.v3.patch, HBASE-16338.v5.patch, HBASE-16338.v6.patch, > HBASE-16338.v7.patch, HBASE-16338.v8.patch, HBASE-16338.v9.patch > > > Our jackson dependency is from ~3 years ago. Update to the jackson 2.y line, > using 2.7.0+. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19052) FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x
[
https://issues.apache.org/jira/browse/HBASE-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213688#comment-16213688
]
Ted Yu commented on HBASE-19052:
https://builds.apache.org/job/PreCommit-HBASE-Build/9277/console :
01:46:25 Build was aborted
01:46:25 Aborted by busbey
Let me trigger test run again.
> FixedFileTrailer should recognize CellComparatorImpl class in branch-1.x
>
>
> Key: HBASE-19052
> URL: https://issues.apache.org/jira/browse/HBASE-19052
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 19052.branch-1.txt
>
>
> HBASE-18945 has gone into branch-2 .
> Let's consider rolling upgrade scenario from 1.x to 2.0 where there're three
> servers: s1, s2, s3
> s1 is upgraded to 2.0 first. It flushes to hfile in region r1 with
> CellComparatorImpl written in the hfile trailer.
> Somehow s1 crashes and master assigns r1 to s2 which is still running 1.x
> The following code in FixedFileTrailer would be triggered:
> {code}
> try {
> comparatorKlass = (Class)
> Class.forName(comparatorClassName);
> } catch (ClassNotFoundException e) {
> throw new IOException(e);
> }
> {code}
> since s2 is not aware of CellComparatorImpl.
> This issue is to backport CellComparatorImpl related change to branch-1.x
> Note: CellComparatorImpl wouldn't be used in write path, only in read path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213679#comment-16213679
]
Hudson commented on HBASE-19058:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #248 (See
[https://builds.apache.org/job/HBase-1.3-IT/248/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f0e31ea0b3d4ea2788bf937cccaae62c85a9ed68)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213674#comment-16213674
]
Mike Drob commented on HBASE-18846:
---
Skimmed the patch. Makes sense. Did you mean to include the hbase-site.xml and
IndexerConnection in the patch when in the RN you mentioned not committing them?
There's a lot of unrelated whitespace/formatting changes in the patch. I'll try
to go through sometime and read it with a tool that can ignore those.
Replication service always starts? Not hidden behind a flag? I understand that
is the raison d'être here, but I can imagine somebody wanting an RS without
that too (but maybe one of the other features still on, like web server). I
guess we still check if the handler is enabled, but it looks less clean than
the other options we're exposing.
On the health check, can we get into a false positive state where a thread is
null but shouldn't be? Is it better to check the configuration source of truth
there instead?
In the TestStandaloneRegionServer, let's put some of the cleanup (like the
join) in either a finally block or a {{@After}} method so that we don't pollute
other tests if we fail.
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
>
[jira] [Updated] (HBASE-18993) Backport patches in HBASE-18410 to branch-1.x branches.
[ https://issues.apache.org/jira/browse/HBASE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-18993: - Status: Patch Available (was: Open) > Backport patches in HBASE-18410 to branch-1.x branches. > --- > > Key: HBASE-18993 > URL: https://issues.apache.org/jira/browse/HBASE-18993 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Zheng Hu >Assignee: Zheng Hu > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18993-branch-1.4.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18993) Backport patches in HBASE-18410 to branch-1.x branches.
[ https://issues.apache.org/jira/browse/HBASE-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-18993: - Attachment: HBASE-18993-branch-1.4.v1.patch > Backport patches in HBASE-18410 to branch-1.x branches. > --- > > Key: HBASE-18993 > URL: https://issues.apache.org/jira/browse/HBASE-18993 > Project: HBase > Issue Type: Sub-task > Components: Filters >Reporter: Zheng Hu >Assignee: Zheng Hu > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18993-branch-1.4.v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213673#comment-16213673
]
Yun Zhao commented on HBASE-19051:
--
I have added a release note that is not necessarily accurate. You can modify
it, Thanks～. [~mdrob]
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19010) Reimplement getMasterInfoPort for Admin
[
https://issues.apache.org/jira/browse/HBASE-19010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213671#comment-16213671
]
Guanghao Zhang commented on HBASE-19010:
Failed ut TestReplicationKillMasterRSCompressed is not related. Will commit it
later if no objection.
> Reimplement getMasterInfoPort for Admin
> ---
>
> Key: HBASE-19010
> URL: https://issues.apache.org/jira/browse/HBASE-19010
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19010.master.001.patch,
> HBASE-19010.master.002.patch, HBASE-19010.master.002.patch,
> HBASE-19010.master.002.patch, HBASE-19010.master.002.patch,
> HBASE-19010.master.003.patch, HBASE-19010.master.003.patch,
> HBASE-19010.master.004.patch, HBASE-19010.master.004.patch
>
>
> Current implementation.
> {code}
> public int getMasterInfoPort() throws IOException {
> // TODO: Fix! Reaching into internal implementation
> ConnectionImplementation connection =
> (ConnectionImplementation)this.connection;
> ZooKeeperKeepAliveConnection zkw =
> connection.getKeepAliveZooKeeperWatcher();
> try {
> return MasterAddressTracker.getMasterInfoPort(zkw);
> } catch (KeeperException e) {
> throw new IOException("Failed to get master info port from
> MasterAddressTracker", e);
> }
> }
> {code}
> Open this issue to fix TODO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213668#comment-16213668
]
Hudson commented on HBASE-19058:
FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #248 (See
[https://builds.apache.org/job/HBase-1.2-JDK7/248/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f29f1702ac1099052ad19153a2a364b3141bb059)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213669#comment-16213669
]
Hudson commented on HBASE-19058:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #332 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/332/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f0e31ea0b3d4ea2788bf937cccaae62c85a9ed68)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213667#comment-16213667
]
Hudson commented on HBASE-19058:
FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #245 (See
[https://builds.apache.org/job/HBase-1.2-JDK8/245/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f29f1702ac1099052ad19153a2a364b3141bb059)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Release Note:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
The split point will be 1000,2000,...,9000
was:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
{code}
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
The split point will be 1000,2000,...,9000
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Release Note:
Add new split algorithm DecimalStringSplit，row are decimal-encoded long values
in the range "" => "" .
{code}
create 't1','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
The split point will be 1000,2000,...,9000
Description:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
was:
We will use the reversed sequential number or phone number as the first part of
rowkey, there is no split algorithm to create a pre-split table, only by
specify the split points.
{code}
create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
{code}
Add new split algorithm DecimalStringSplit.
{code}
create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
{code}
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19054) Switch precommit docker image to one based on maven images
[ https://issues.apache.org/jira/browse/HBASE-19054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213665#comment-16213665 ] Sean Busbey commented on HBASE-19054: - https://builds.apache.org/job/HBase%20Nightly/job/HBASE-19054/ > Switch precommit docker image to one based on maven images > -- > > Key: HBASE-19054 > URL: https://issues.apache.org/jira/browse/HBASE-19054 > Project: HBase > Issue Type: Bug > Components: build, community >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-19054.patch, HBASE-19054.v2.patch > > > In HBASE-19042 we discuss moving to a maven-based image for docker instead of > going through gymnastics ourselves. We got a short term fix in there, but > let's do the bulk of the cleanup here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213664#comment-16213664 ] Hudson commented on HBASE-19039: SUCCESS: Integrated in Jenkins build HBase-1.2-IT #982 (See [https://builds.apache.org/job/HBase-1.2-IT/982/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 770e5837a18fac089cc7a2c21b85f0641e5da28f) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213663#comment-16213663
]
Hudson commented on HBASE-19060:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #982 (See
[https://builds.apache.org/job/HBase-1.2-IT/982/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev f5c118bc7ea8843445556f277784c38bb7091f7b)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16338) update jackson to 2.y
[
https://issues.apache.org/jira/browse/HBASE-16338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213661#comment-16213661
]
Mike Drob commented on HBASE-16338:
---
The whitespace errors are based on {{./hbase-server/hs_err_pid24104.log}} which
isn't included in the patch... Something strange happened there, let's retry.
> update jackson to 2.y
> -
>
> Key: HBASE-16338
> URL: https://issues.apache.org/jira/browse/HBASE-16338
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Reporter: Sean Busbey
>Assignee: Mike Drob
> Fix For: 2.0.0-beta-2
>
> Attachments: 16338.txt, HBASE-16338.branch-2.patch,
> HBASE-16338.v10.patch, HBASE-16338.v11.patch, HBASE-16338.v2.patch,
> HBASE-16338.v3.patch, HBASE-16338.v5.patch, HBASE-16338.v6.patch,
> HBASE-16338.v7.patch, HBASE-16338.v8.patch, HBASE-16338.v9.patch
>
>
> Our jackson dependency is from ~3 years ago. Update to the jackson 2.y line,
> using 2.7.0+.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213660#comment-16213660
]
Hudson commented on HBASE-19058:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #317 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/317/])
HBASE-19058. The wget isn't installed in building docker image (busbey: rev
f0e31ea0b3d4ea2788bf937cccaae62c85a9ed68)
* (edit) dev-support/docker/Dockerfile
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19062) nightly jobs should make a single comment for all branches on jira.
Sean Busbey created HBASE-19062: --- Summary: nightly jobs should make a single comment for all branches on jira. Key: HBASE-19062 URL: https://issues.apache.org/jira/browse/HBASE-19062 Project: HBase Issue Type: Improvement Components: build, community Reporter: Sean Busbey Priority: Minor it'd be nice if instead of getting a comment per branch a patch goes into jira could get a single comment with e.g. all the branches that had a nightly run in the last 24 hours. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213658#comment-16213658 ] Hudson commented on HBASE-19039: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #247 (See [https://builds.apache.org/job/HBase-1.3-IT/247/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 95f22b60195b53fdf9606cd8de233c613c9ad062) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213657#comment-16213657
]
Hudson commented on HBASE-19060:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #247 (See
[https://builds.apache.org/job/HBase-1.3-IT/247/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev 990a322b470cecd550fcf7200ab538bc860ed232)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Zhao updated HBASE-19051:
-
Attachment: HBASE-19051.branch-1.001.patch
[~yuzhih...@gmail.com] - I just uploaded a patch for branch-1 :D
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.branch-1.001.patch,
> HBASE-19051.master.001.patch, HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213650#comment-16213650
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #247 (See
[https://builds.apache.org/job/HBase-1.2-JDK7/247/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev f5c118bc7ea8843445556f277784c38bb7091f7b)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-19058:
Resolution: Fixed
Status: Resolved (was: Patch Available)
checked the build output and everything looked good. excludes downloaded and
then used. pushed to all branches.
> The wget isn't installed in building docker image
> -
>
> Key: HBASE-19058
> URL: https://issues.apache.org/jira/browse/HBASE-19058
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19058.v0.patch, HBASE-19058.v0.tests.patch
>
>
> see
> [console|https://builds.apache.org/job/PreCommit-HBASE-Build/9259/consoleFull].
>
> {quote}
> 05:38:19 /testptch/patchprocess/precommit/personality/provided.sh: line 121:
> wget: command not found
> 05:38:19 Wget error 127 in fetching excludes file from url
> https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/.
> Ignoring and proceeding.
> 05:38:22 cd /testptch/hbase/hbase-server
> {quote}
> We don't force docker to install {{wget}} before because {{wget}} is in the
> pre-depends of oracle-java8-installer.
> {code}
> $ sudo apt-rdepends oracle-java8-installer | grep "wget"
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> PreDepends: wget
> wget
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213651#comment-16213651 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #247 (See [https://builds.apache.org/job/HBase-1.2-JDK7/247/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 770e5837a18fac089cc7a2c21b85f0641e5da28f) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213646#comment-16213646
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #244 (See
[https://builds.apache.org/job/HBase-1.2-JDK8/244/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev f5c118bc7ea8843445556f277784c38bb7091f7b)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213647#comment-16213647 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #244 (See [https://builds.apache.org/job/HBase-1.2-JDK8/244/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 770e5837a18fac089cc7a2c21b85f0641e5da28f) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-19060:
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-4
1.1.13
1.2.7
1.5.0
1.3.2
1.4.0
3.0.0
Status: Resolved (was: Patch Available)
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19039: Resolution: Fixed Status: Resolved (was: Patch Available) > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213637#comment-16213637
]
Hudson commented on HBASE-19061:
FAILURE: Integrated in Jenkins build HBase-1.4 #960 (See
[https://builds.apache.org/job/HBase-1.4/960/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
d026ca65158ec0f5d691059fc661f9b68aaecb18)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213635#comment-16213635
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #316 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/316/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev 990a322b470cecd550fcf7200ab538bc860ed232)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213636#comment-16213636 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #316 (See [https://builds.apache.org/job/HBase-1.3-JDK7/316/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 95f22b60195b53fdf9606cd8de233c613c9ad062) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19060) "Hadoop check" test is running all the time instead of just when changes to java
[
https://issues.apache.org/jira/browse/HBASE-19060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213632#comment-16213632
]
Hudson commented on HBASE-19060:
FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #331 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/331/])
HBASE-19060 precommit plugin test 'hadoopcheck' should only run when (busbey:
rev 990a322b470cecd550fcf7200ab538bc860ed232)
* (edit) dev-support/hbase-personality.sh
> "Hadoop check" test is running all the time instead of just when changes to
> java
>
>
> Key: HBASE-19060
> URL: https://issues.apache.org/jira/browse/HBASE-19060
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Critical
> Attachments: HBASE-19060.0.patch
>
>
> see for example HBASE-19058, which just changes the dockerfile in dev-support.
> {quote}
> +1hadoopcheck 39m 59s Patch does not cause any errors with Hadoop
> 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4.
> {quote}
> that's 30-40 minutes we're adding to precommit builds that don't need it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213633#comment-16213633 ] Hudson commented on HBASE-19039: FAILURE: Integrated in Jenkins build HBase-1.3-JDK8 #331 (See [https://builds.apache.org/job/HBase-1.3-JDK8/331/]) HBASE-19039 refactor shadedjars test to only run on java changes. (busbey: rev 95f22b60195b53fdf9606cd8de233c613c9ad062) * (edit) dev-support/hbase-personality.sh > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[ https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213626#comment-16213626 ] stack commented on HBASE-19007: --- .012 fix a few tests (maybe not all -- let me see) > Align Services Interfaces in Master and RegionServer > > > Key: HBASE-19007 > URL: https://issues.apache.org/jira/browse/HBASE-19007 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Blocker > Labels: coprocessor > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19007.master.001.patch, > HBASE-19007.master.002.patch, HBASE-19007.master.003.patch, > HBASE-19007.master.004.patch, HBASE-19007.master.005.patch, > HBASE-19007.master.006.patch, HBASE-19007.master.007.patch, > HBASE-19007.master.008.patch, HBASE-19007.master.009.patch, > HBASE-19007.master.009.patch, HBASE-19007.master.010.patch, > HBASE-19007.master.011.patch, HBASE-19007.master.012.patch > > > HBASE-18183 adds a CoprocessorRegionServerService to give a view on > RegionServiceServices that is safe to expose to Coprocessors. > On the Master-side, MasterServices becomes an Interface for exposing to > Coprocessors. > We need to align the two. > For background, see > https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[ https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19007: -- Attachment: HBASE-19007.master.012.patch > Align Services Interfaces in Master and RegionServer > > > Key: HBASE-19007 > URL: https://issues.apache.org/jira/browse/HBASE-19007 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Blocker > Labels: coprocessor > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19007.master.001.patch, > HBASE-19007.master.002.patch, HBASE-19007.master.003.patch, > HBASE-19007.master.004.patch, HBASE-19007.master.005.patch, > HBASE-19007.master.006.patch, HBASE-19007.master.007.patch, > HBASE-19007.master.008.patch, HBASE-19007.master.009.patch, > HBASE-19007.master.009.patch, HBASE-19007.master.010.patch, > HBASE-19007.master.011.patch, HBASE-19007.master.012.patch > > > HBASE-18183 adds a CoprocessorRegionServerService to give a view on > RegionServiceServices that is safe to expose to Coprocessors. > On the Master-side, MasterServices becomes an Interface for exposing to > Coprocessors. > We need to align the two. > For background, see > https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820 > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18893) Remove Add/Modify/DeleteColumnFamilyProcedure in favor of using ModifyTableProcedure
[
https://issues.apache.org/jira/browse/HBASE-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213624#comment-16213624
]
Hadoop QA commented on HBASE-18893:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 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 6 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
19s{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
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
52s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
23s{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
22s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
22s{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
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
5s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
44m 18s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
32s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}129m 51s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}207m 58s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAsyncTableAdminApi |
| | hadoop.hbase.master.procedure.TestDeleteColumnFamilyProcedureFromClient |
| | hadoop.hbase.client.TestAdmin1 |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-18893 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893336/HBASE-18893.v3.patch
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213619#comment-16213619
]
Hudson commented on HBASE-19061:
FAILURE: Integrated in Jenkins build HBase-2.0 #721 (See
[https://builds.apache.org/job/HBase-2.0/721/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
bd9c37367e0d8ea88d9d6f03d136a0484caa653a)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19043) Purge TableWrapper and CoprocessorHConnnection
[
https://issues.apache.org/jira/browse/HBASE-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213617#comment-16213617
]
Hudson commented on HBASE-19043:
FAILURE: Integrated in Jenkins build HBase-2.0 #721 (See
[https://builds.apache.org/job/HBase-2.0/721/])
HBASE-19043 Purge TableWrapper and CoprocessorHConnnection Also purge (stack:
rev 9b4caf4b1bd86be77d5661d75ecf16dc83158140)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/security/token/TestTokenAuthentication.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestOpenTableInCoprocessor.java
* (delete)
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorHost.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/CoprocessorEnvironment.java
* (delete)
hbase-server/src/main/java/org/apache/hadoop/hbase/client/CoprocessorHConnection.java
* (delete)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestHTableWrapper.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseEnvironment.java
> Purge TableWrapper and CoprocessorHConnnection
> --
>
> Key: HBASE-19043
> URL: https://issues.apache.org/jira/browse/HBASE-19043
> Project: HBase
> Issue Type: Task
> Components: Coprocessors
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19043.master.001.patch,
> HBASE-19043.master.002.patch, HBASE-19043.master.003.patch,
> HBASE-19043.master.004.patch, HBASE-19043.master.005.patch,
> HBASE-19043.master.006.patch, HBASE-19043.master.007.patch,
> HBASE-19043.master.007.patch
>
>
> Repeating note from dev list today which had assent from [~apurtell] and
> [~appy]:
> {code}
> Subject: [DISCUSS] Punt the Coprocessor TableWrapper and
> CoprocessorHConnection?
> To: HBase Dev List
> tl;dr I believe the original intent for TableWrapper and
> CoprocessorHConnection can now be gotten elsewhere so we should purge these
> classes.
> In base CoprocessorEnvironment, there are methods to return a Table
> instance. There are none to return an Admin. In our code base, the only
> user is the AccessController. Phoenix uses it twice in its Indexer
> implementation.
> When you call CE#getTable, the default implementation in
> BaseEnvironemnt calls HTableWrapper.createWrapper which takes a
> BaseEnvironment List in which we keep all Table instances. On shutdown of
> the coprocessor, the list is iterated and all tables are closed.
> Going via TableWrapper, the class comment says:
> * A wrapper for HTable. Can be used to restrict privilege.
> *
> * Currently it just helps to track tables opened by a Coprocessor and
> * facilitate close of them if it is aborted.
> *
> * We also disallow row locking.
> *
> * There is nothing now that will stop a coprocessor from using HTable
> * objects directly instead of this API, but in the future we intend to
> * analyze coprocessor implementations as they are loaded and reject those
> * which attempt to use objects and methods outside the Environment
> * sandbox.
> TableWrapper by my reading delegates all calls to a Table instance with no
> interception (there is not rowlocking to override anymore). On open, we do
> ensure the Table is up on a CoprocessorHConnection which does the following:
> * Connection to an HTable from within a Coprocessor. We can do some
> nice tricks since we know we
> * are on a regionserver, for instance skipping the full
> serialization/deserialization of objects
> * when talking to the server.
> The above 'trick' is now commonplace in servers as the Master and
> RegionServer always make Connections that will short-circuit if an
> opportunity.
> As I read TableWrapper and CoprocessorHConnection, they were written at
> another time when Table construction was heavyweight and Table#close was
> not expected of clients and before the introduction of the general
> Server-side short-circuit Connection facility.
> Unless objection, I think we should purge them.
> Writing here in case I'm missing some key facility they provide.
> {code}
> See
> http://search-hadoop.com/m/HBase/YGbb8uCtg26VkBy?subj=+DISCUSS+Punt+the+Coprocessor+TableWrapper+and+CoprocessorHConnection+
> This issue is about removing these classes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213615#comment-16213615
]
Hudson commented on HBASE-19051:
FAILURE: Integrated in Jenkins build HBase-2.0 #721 (See
[https://builds.apache.org/job/HBase-2.0/721/])
HBASE-19051 Add new split algorithm for num string (tedyu: rev
af950a6608f61a187392666d372a0b4763f077c9)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestRegionSplitter.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/util/RegionSplitter.java
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory
[
https://issues.apache.org/jira/browse/HBASE-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213616#comment-16213616
]
Hudson commented on HBASE-19014:
FAILURE: Integrated in Jenkins build HBase-2.0 #721 (See
[https://builds.apache.org/job/HBase-2.0/721/])
HBASE-19014 surefire fails; When writing xml report stdout/stderr ... No
(chia7712: rev a038f180c198cabdda08d2b128cafcde08e910af)
* (edit) pom.xml
> surefire fails; When writing xml report stdout/stderr ... No such file or
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch,
> HBASE-19014.branch-1.v0.patch, HBASE-19014.branch-1.v0.patch,
> HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> (secondPartTestsExecution) on project hbase-server: ExecutionException:
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.maven.surefire.report.ReporterException: When writing xml report
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and
> then the failure doesn't happen again. see SUREFIRE-1239.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19045) Deprecate RegionObserver#postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213618#comment-16213618 ] Hudson commented on HBASE-19045: FAILURE: Integrated in Jenkins build HBase-2.0 #721 (See [https://builds.apache.org/job/HBase-2.0/721/]) HBASE-19045 Deprecate RegionObserver#postInstantiateDeleteTracker. (anoopsamjohn: rev 2962aa2d3e2a8719d2841e6496564e5f1d060be8) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java > Deprecate RegionObserver#postInstantiateDeleteTracker > - > > Key: HBASE-19045 > URL: https://issues.apache.org/jira/browse/HBASE-19045 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19045.patch > > > Too much of an internal thing to be exposed to CPs. > This was added a VC feature as that is implemented as a CP , no other choice > then. > We can deprecate this now with a warn that not be used. > We might be changing AC/VC etc to be core service than CP impl for 3.0 (?) > DeleteTracker is IA Private even -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213603#comment-16213603
]
Hudson commented on HBASE-19061:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3921/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
89d3b0b07f2ce7a84780e7088efaf9e3bce1ee5f)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19043) Purge TableWrapper and CoprocessorHConnnection
[
https://issues.apache.org/jira/browse/HBASE-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213601#comment-16213601
]
Hudson commented on HBASE-19043:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3921/])
HBASE-19043 Purge TableWrapper and CoprocessorHConnnection Also purge (stack:
rev d7985412610b612c09cf377ab87963e897c72afa)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/security/token/TestTokenAuthentication.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorHost.java
* (delete)
hbase-server/src/main/java/org/apache/hadoop/hbase/client/CoprocessorHConnection.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseEnvironment.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestOpenTableInCoprocessor.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/CoprocessorEnvironment.java
* (delete)
hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTableWrapper.java
* (delete)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestHTableWrapper.java
> Purge TableWrapper and CoprocessorHConnnection
> --
>
> Key: HBASE-19043
> URL: https://issues.apache.org/jira/browse/HBASE-19043
> Project: HBase
> Issue Type: Task
> Components: Coprocessors
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19043.master.001.patch,
> HBASE-19043.master.002.patch, HBASE-19043.master.003.patch,
> HBASE-19043.master.004.patch, HBASE-19043.master.005.patch,
> HBASE-19043.master.006.patch, HBASE-19043.master.007.patch,
> HBASE-19043.master.007.patch
>
>
> Repeating note from dev list today which had assent from [~apurtell] and
> [~appy]:
> {code}
> Subject: [DISCUSS] Punt the Coprocessor TableWrapper and
> CoprocessorHConnection?
> To: HBase Dev List
> tl;dr I believe the original intent for TableWrapper and
> CoprocessorHConnection can now be gotten elsewhere so we should purge these
> classes.
> In base CoprocessorEnvironment, there are methods to return a Table
> instance. There are none to return an Admin. In our code base, the only
> user is the AccessController. Phoenix uses it twice in its Indexer
> implementation.
> When you call CE#getTable, the default implementation in
> BaseEnvironemnt calls HTableWrapper.createWrapper which takes a
> BaseEnvironment List in which we keep all Table instances. On shutdown of
> the coprocessor, the list is iterated and all tables are closed.
> Going via TableWrapper, the class comment says:
> * A wrapper for HTable. Can be used to restrict privilege.
> *
> * Currently it just helps to track tables opened by a Coprocessor and
> * facilitate close of them if it is aborted.
> *
> * We also disallow row locking.
> *
> * There is nothing now that will stop a coprocessor from using HTable
> * objects directly instead of this API, but in the future we intend to
> * analyze coprocessor implementations as they are loaded and reject those
> * which attempt to use objects and methods outside the Environment
> * sandbox.
> TableWrapper by my reading delegates all calls to a Table instance with no
> interception (there is not rowlocking to override anymore). On open, we do
> ensure the Table is up on a CoprocessorHConnection which does the following:
> * Connection to an HTable from within a Coprocessor. We can do some
> nice tricks since we know we
> * are on a regionserver, for instance skipping the full
> serialization/deserialization of objects
> * when talking to the server.
> The above 'trick' is now commonplace in servers as the Master and
> RegionServer always make Connections that will short-circuit if an
> opportunity.
> As I read TableWrapper and CoprocessorHConnection, they were written at
> another time when Table construction was heavyweight and Table#close was
> not expected of clients and before the introduction of the general
> Server-side short-circuit Connection facility.
> Unless objection, I think we should purge them.
> Writing here in case I'm missing some key facility they provide.
> {code}
> See
> http://search-hadoop.com/m/HBase/YGbb8uCtg26VkBy?subj=+DISCUSS+Punt+the+Coprocessor+TableWrapper+and+CoprocessorHConnection+
> This issue is about removing these classes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory
[
https://issues.apache.org/jira/browse/HBASE-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213600#comment-16213600
]
Hudson commented on HBASE-19014:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3921/])
HBASE-19014 surefire fails; When writing xml report stdout/stderr ... No
(chia7712: rev d59ed234ef0ba4f9c61961de306965ff39bec05f)
* (edit) pom.xml
> surefire fails; When writing xml report stdout/stderr ... No such file or
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch,
> HBASE-19014.branch-1.v0.patch, HBASE-19014.branch-1.v0.patch,
> HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> (secondPartTestsExecution) on project hbase-server: ExecutionException:
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.maven.surefire.report.ReporterException: When writing xml report
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and
> then the failure doesn't happen again. see SUREFIRE-1239.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19045) Deprecate RegionObserver#postInstantiateDeleteTracker
[ https://issues.apache.org/jira/browse/HBASE-19045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213602#comment-16213602 ] Hudson commented on HBASE-19045: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3921/]) HBASE-19045 Deprecate RegionObserver#postInstantiateDeleteTracker. (anoopsamjohn: rev 64d164b86d32f6d6e987722bf223a809743f9f47) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java > Deprecate RegionObserver#postInstantiateDeleteTracker > - > > Key: HBASE-19045 > URL: https://issues.apache.org/jira/browse/HBASE-19045 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-19045.patch > > > Too much of an internal thing to be exposed to CPs. > This was added a VC feature as that is implemented as a CP , no other choice > then. > We can deprecate this now with a warn that not be used. > We might be changing AC/VC etc to be core service than CP impl for 3.0 (?) > DeleteTracker is IA Private even -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19051) Add new split algorithm for num string
[
https://issues.apache.org/jira/browse/HBASE-19051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213599#comment-16213599
]
Hudson commented on HBASE-19051:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3921/])
HBASE-19051 Add new split algorithm for num string (tedyu: rev
8c6ddc1aa5497a38018fdcf100bd33b385ca2c84)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/util/RegionSplitter.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestRegionSplitter.java
> Add new split algorithm for num string
> --
>
> Key: HBASE-19051
> URL: https://issues.apache.org/jira/browse/HBASE-19051
> Project: HBase
> Issue Type: Improvement
>Reporter: Yun Zhao
>Assignee: Yun Zhao
>Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19051.master.001.patch,
> HBASE-19051.master.002.patch
>
>
> We will use the reversed sequential number or phone number as the first part
> of rowkey, there is no split algorithm to create a pre-split table, only by
> specify the split points.
> {code}
> create 't1','f', SPLITS => ['1','2','3','4','5','6','7','8','9']
> {code}
> Add new split algorithm DecimalStringSplit.
> {code}
> create 't2','f', { NUMREGIONS => 10 , SPLITALGO => 'DecimalStringSplit' }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16338) update jackson to 2.y
[ https://issues.apache.org/jira/browse/HBASE-16338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213598#comment-16213598 ] Hudson commented on HBASE-16338: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3921 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3921/]) HBASE-16338 Remove Jackson1 deps (mdrob: rev 5facaded902a13556952b1f9d26b768cb86e6599) * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestBlockCacheReporting.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableSchemaModel.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/ScannerModel.java * (edit) hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/PerformanceEvaluation.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALPrettyPrinter.java * (edit) hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestOperation.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * (edit) hbase-client/pom.xml * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/NamespacesModel.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/JSONBean.java * (edit) hbase-server/src/main/resources/hbase-webapps/master/processMaster.jsp * (delete) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/ProtobufStreamingUtil.java * (edit) hbase-shaded/pom.xml * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/TableScanResource.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/util/JSONMetricUtil.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestDeleteRow.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestVersionResource.java * (edit) hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/TestPerformanceEvaluation.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/ColumnSchemaModel.java * (edit) hbase-server/pom.xml * (edit) pom.xml * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestMultiRowResource.java * (edit) hbase-rest/pom.xml * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/model/TestColumnSchemaModel.java * (edit) hbase-spark/pom.xml * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/AgeSnapshot.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/TableSchemaModel.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterStatusModel.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/model/TestModelBase.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/LruBlockCache.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/RowModel.java * (edit) hbase-server/src/main/resources/hbase-webapps/master/processRS.jsp * (edit) hbase-resource-bundle/src/main/resources/supplemental-models.xml * (edit) hbase-server/src/main/resources/hbase-webapps/regionserver/processRS.jsp * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/monitoring/MonitoredTaskImpl.java * (edit) hbase-mapreduce/pom.xml * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestJSONMetricUtil.java * (edit) hbase-shaded/hbase-shaded-mapreduce/pom.xml * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestTableScan.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestNamespacesInstanceResource.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java * (edit) hbase-it/src/test/java/org/apache/hadoop/hbase/RESTApiClusterManager.java * (edit) hbase-shell/src/main/ruby/hbase/taskmonitor.rb * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/CellModel.java * (edit) dev-support/hbase-personality.sh * (edit) hbase-it/pom.xml * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/RowResourceBase.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/util/JsonMapper.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterVersionModel.java * (add) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/ProtobufStreamingOutput.java * (edit) hbase-rest/src/test/java/org/apache/hadoop/hbase/rest/HBaseRESTTestingUtility.java * (edit) hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/bucket/BucketAllocator.java > update jackson to 2.y > - > > Key: HBASE-16338 > URL: https://issues.apache.org/jira/browse/HBASE-16338 > Project: HBase > Issue Type: Task > Components: dependencies >Reporter: Sean Busbey >Assignee: Mike Drob > Fix For: 2.0.0-beta-2 > >
[jira] [Updated] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19039: Summary: refactor shadedjars test to only run on java changes. (was: remove shadejars clean precommit check) > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19010) Reimplement getMasterInfoPort for Admin
[
https://issues.apache.org/jira/browse/HBASE-19010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213591#comment-16213591
]
Hadoop QA commented on HBASE-19010:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 17m
50s{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 3 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
44s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
3s{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
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
20s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
23s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
46s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
49m 35s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 8m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
42s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
20s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}141m 29s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}258m 43s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19010 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893282/HBASE-19010.master.004.patch
|
| Optional Tests | asflicense shadedjars javac javadoc
[jira] [Updated] (HBASE-19039) refactor shadedjars test to only run on java changes.
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19039: Description: per HBASE-18760 ; the shadejars clean check is currently broken due to a typo, we should excise it. needs to be done in all the branches. Also limit runs of the test to changes that alter poms or java files. probably that's all that can break this. Any edge cases will come up in nightly. was: per HBASE-18760 ; the shadejars clean check is currently broken due to a typo, we should excise it. needs to be done in all the branches. > refactor shadedjars test to only run on java changes. > - > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. > Also limit runs of the test to changes that alter poms or java files. > probably that's all that can break this. Any edge cases will come up in > nightly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[ https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-19053: - Attachment: HBASE-19053.master.002.patch > Split out o.a.h.h.http from hbase-server into a separate module > --- > > Key: HBASE-19053 > URL: https://issues.apache.org/jira/browse/HBASE-19053 > Project: HBase > Issue Type: Bug >Reporter: Appy >Assignee: Appy > Attachments: HBASE-19053.master.001.patch, > HBASE-19053.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18846:
--
Fix Version/s: (was: 2.0.0-beta-1)
2.0.0-alpha-4
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
> stream to the remote cluster via the CPEP registered channel.
> But time is short. Hopefully we can figure something that will work in 2.0
> timeframe w/o too much code movement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18846:
--
Status: Patch Available (was: Open)
Submitting patch. Trying to get this into alpha-4 because my guess is that
there will be adjustment needed by hbase-indexer which we can do in time for
beta-1.
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
> stream to the remote cluster via the CPEP registered channel.
> But time is short. Hopefully we can figure something that will work in 2.0
> timeframe w/o too much code movement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213583#comment-16213583
]
stack commented on HBASE-18846:
---
.001 Moves bulk of startup to startServices method, as much as possible into
one place. Adds a few flags to disable Services and to skip registering with
Master. See Release Note for how to use.
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
> stream to the remote cluster via the CPEP registered channel.
> But time is short. Hopefully we can figure something that will work in 2.0
> timeframe w/o too much code movement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19039) remove shadejars clean precommit check
[ https://issues.apache.org/jira/browse/HBASE-19039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213582#comment-16213582 ] Sean Busbey commented on HBASE-19039: - I like to think the "!" represents how surprised and happy you were to see a test run in 47 seconds that does not appear to be a false positive. ;) > remove shadejars clean precommit check > -- > > Key: HBASE-19039 > URL: https://issues.apache.org/jira/browse/HBASE-19039 > Project: HBase > Issue Type: Bug > Components: build >Reporter: Mike Drob >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 1.1.13, 2.0.0-alpha-4 > > Attachments: HBASE-19039.0.patch > > > per HBASE-18760 ; the shadejars clean check is currently broken due to a > typo, we should excise it. > needs to be done in all the branches. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18846) Accommodate the hbase-indexer/lily/SEP consumer deploy-type
[
https://issues.apache.org/jira/browse/HBASE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18846:
--
Attachment: HBASE-18846.master.004.patch
> Accommodate the hbase-indexer/lily/SEP consumer deploy-type
> ---
>
> Key: HBASE-18846
> URL: https://issues.apache.org/jira/browse/HBASE-18846
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18846.master.001.patch,
> HBASE-18846.master.002.patch, HBASE-18846.master.003.patch,
> HBASE-18846.master.004.patch, IndexerConnection.java, hbase-site.xml,
> javadoc.txt
>
>
> This is a follow-on from HBASE-10504, Define a Replication Interface. There
> we defined a new, flexible replication endpoint for others to implement but
> it did little to help the case of the lily hbase-indexer. This issue takes up
> the case of the hbase-indexer.
> The hbase-indexer poses to hbase as a 'fake' peer cluster (For why
> hbase-indexer is implemented so, the advantage to having the indexing done in
> a separate process set that can be independently scaled, can participate in
> the same security realm, etc., see discussion in HBASE-10504). The
> hbase-indexer will start up a cut-down "RegionServer" processes that are just
> an instance of hbase RpcServer hosting an AdminProtos Service. They make
> themselves 'appear' to the Replication Source by hoisting up an ephemeral
> znode 'registering' as a RegionServer. The source cluster then streams
> WALEdits to the Admin Protos method:
> {code}
> public ReplicateWALEntryResponse replicateWALEntry(final RpcController
> controller,
> final ReplicateWALEntryRequest request) throws ServiceException {
> {code}
> The hbase-indexer relies on other hbase internals like Server so it can get a
> ZooKeeperWatcher instance and know the 'name' to use for this cut-down server.
> Thoughts on how to proceed include:
>
> * Better formalize its current digestion of hbase internals; make it so
> rpcserver is allowed to be used by others, etc. This would be hard to do
> given they use basics like Server, Protobuf serdes for WAL types, and
> AdminProtos Service. Any change in this wide API breaks (again)
> hbase-indexer. We have made a 'channel' for Coprocessor Endpoints so they
> continue to work though they use 'internal' types. They can use protos in
> hbase-protocol. hbase-protocol protos are in a limbo currently where they are
> sort-of 'public'; a TODO. Perhaps the hbase-indexer could do similar relying
> on the hbase-protocol (pb2.5) content and we could do something to reveal
> rpcserver and zk for hbase-indexer safe use.
> * Start an actual RegionServer only have it register the AdminProtos Service
> only -- not ClientProtos and the Service that does Master interaction, etc.
> [I checked, this is not as easy to do as I at first thought -- St.Ack] Then
> have the hbase-indexer implement an AdminCoprocessor to override the
> replicateWALEntry method (the Admin CP implementation may need work). This
> would narrow the hbase-indexer exposure to that of the Admin Coprocessor
> Interface
> * Over in HBASE-10504, [~enis] suggested "... if we want to provide
> isolation for the replication services in hbase, we can have a simple host as
> another daemon which hosts the ReplicationEndpoint implementation. RS's will
> use a built-in RE to send the edits to this layer, and the host will delegate
> it to the RE implementation. The flow would be something like: RS --> RE
> inside RS --> Host daemon for RE --> Actual RE implementation --> third party
> system..."
>
> Other crazy notions occur including the setup of an Admin Interface
> Coprocessor Endpoint. A new ReplicationEndpoint would feed the replication
> stream to the remote cluster via the CPEP registered channel.
> But time is short. Hopefully we can figure something that will work in 2.0
> timeframe w/o too much code movement.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19058) The wget isn't installed in building docker image
[
https://issues.apache.org/jira/browse/HBASE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213572#comment-16213572
]
Hadoop QA commented on HBASE-19058:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
4s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
22s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
5s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
17s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
5s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
2s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
39m 51s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: . {color}
|
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 3m
2s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}208m 40s{color}
| {color:red} root in the patch failed. {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}284m 44s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19058
[jira] [Commented] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[ https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213563#comment-16213563 ] Vladimir Rodionov commented on HBASE-17852: --- That is not a deadlock - its synchronization mechanism through access serialization. Only one critical operation at a time. > Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental > backup) > > > Key: HBASE-17852 > URL: https://issues.apache.org/jira/browse/HBASE-17852 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch, > HBASE-17852-v3.patch, HBASE-17852-v4.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213561#comment-16213561
]
Hudson commented on HBASE-19061:
FAILURE: Integrated in Jenkins build HBase-1.1-JDK7 #1927 (See
[https://builds.apache.org/job/HBase-1.1-JDK7/1927/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
abb4f3b988fe0633023c1e68f97f12717205f6f5)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213556#comment-16213556
]
Hudson commented on HBASE-19061:
FAILURE: Integrated in Jenkins build HBase-1.1-JDK8 #2011 (See
[https://builds.apache.org/job/HBase-1.1-JDK8/2011/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
abb4f3b988fe0633023c1e68f97f12717205f6f5)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[ https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213524#comment-16213524 ] Ted Yu commented on HBASE-17852: See comment from Sept 17th: https://issues.apache.org/jira/browse/HBASE-17852?focusedCommentId=16169471=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16169471 > Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental > backup) > > > Key: HBASE-17852 > URL: https://issues.apache.org/jira/browse/HBASE-17852 > Project: HBase > Issue Type: Sub-task >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch, > HBASE-17852-v3.patch, HBASE-17852-v4.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[
https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213523#comment-16213523
]
Hadoop QA commented on HBASE-19053:
---
| (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 4s{color}
| {color:red} HBASE-19053 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-19053 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893106/HBASE-19053.master.001.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9284/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Split out o.a.h.h.http from hbase-server into a separate module
> ---
>
> Key: HBASE-19053
> URL: https://issues.apache.org/jira/browse/HBASE-19053
> Project: HBase
> Issue Type: Bug
>Reporter: Appy
>Assignee: Appy
> Attachments: HBASE-19053.master.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213521#comment-16213521
]
Hudson commented on HBASE-19061:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #246 (See
[https://builds.apache.org/job/HBase-1.3-IT/246/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
1a206ba1f69ff06f6ea4653376651acef16dd7a6)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213512#comment-16213512
]
Vladimir Rodionov commented on HBASE-17852:
---
{quote}
Is it possible to add new test case which shows the potential dead lock being
solved by the patch ?
{quote}
What deadlock are you referring to, [~te...@apache.org]?
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
>
>
> Key: HBASE-17852
> URL: https://issues.apache.org/jira/browse/HBASE-17852
> Project: HBase
> Issue Type: Sub-task
>Reporter: Vladimir Rodionov
>Assignee: Vladimir Rodionov
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch,
> HBASE-17852-v3.patch, HBASE-17852-v4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16338) update jackson to 2.y
[
https://issues.apache.org/jira/browse/HBASE-16338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213501#comment-16213501
]
Hadoop QA commented on HBASE-16338:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
6s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 17 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
16s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
24s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 17m
5s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
35s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
52s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: .
hbase-shaded hbase-shaded/hbase-shaded-mapreduce {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
58s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 7m
20s{color} | {color:green} branch-2 passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
23s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 8m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 5m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 4m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} rubocop {color} | {color:green} 0m
5s{color} | {color:green} There were no new rubocop issues. {color} |
| {color:green}+1{color} | {color:green} ruby-lint {color} | {color:green} 0m
2s{color} | {color:green} There were no new ruby-lint issues. {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
6s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 615 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
19s{color} | {color:red} The patch 384 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
13s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
38s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
38m 23s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-shaded hbase-shaded/hbase-shaded-mapreduce . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
58s{color} | {color:green} the patch passed {color} |
|
[jira] [Commented] (HBASE-17852) Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental backup)
[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213498#comment-16213498
]
Hadoop QA commented on HBASE-17852:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
41s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s{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} shadedjars {color} | {color:green} 4m
52s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
56m 33s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 14m
40s{color} | {color:green} hbase-backup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 93m 0s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-17852 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893340/HBASE-17852-v4.patch |
| Optional Tests | asflicense shadedjars javac javadoc unit findbugs
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 41c0564a0570 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 89d3b0b |
| Default Java | 1.8.0_141 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9283/testReport/ |
| modules | C: hbase-backup U: hbase-backup |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9283/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
>
[jira] [Updated] (HBASE-18873) Hide protobufs in GlobalQuotaSettings
[ https://issues.apache.org/jira/browse/HBASE-18873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-18873: --- Attachment: HBASE-18873.003.branch-2.patch .003 addressed the comments from Anoop and Chia-Ping > Hide protobufs in GlobalQuotaSettings > - > > Key: HBASE-18873 > URL: https://issues.apache.org/jira/browse/HBASE-18873 > Project: HBase > Issue Type: Sub-task >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-18873.001.branch-2.patch, > HBASE-18873.002.branch-2.patch, HBASE-18873.003.branch-2.patch > > > HBASE-18807 cleaned up direct protobuf use in the Coprocessor APIs for > quota-related functions. However, one new POJO introduced to hide these > protocol buffers still exposes PBs via some methods. > We should try to hide those as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15631) Backport Regionserver Groups (HBASE-6721) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213492#comment-16213492 ] Andrew Purtell commented on HBASE-15631: Thanks for the +1 [~lhofhansl]. I'll do a final rebase, check for any new failures or flakes, and commit over the weekend. > Backport Regionserver Groups (HBASE-6721) to branch-1 > -- > > Key: HBASE-15631 > URL: https://issues.apache.org/jira/browse/HBASE-15631 > Project: HBase > Issue Type: New Feature >Affects Versions: 1.4.0 >Reporter: Francis Liu >Assignee: Andrew Purtell > Fix For: 1.4.0, 1.5.0 > > Attachments: HBASE-15631-branch-1.patch, HBASE-15631-branch-1.patch, > HBASE-15631.branch-1.patch, HBASE-15631.patch > > > Based on dev list discussion backporting region server group should not be an > issue as it does not: 1. destabilize the code. 2. cause backward > incompatibility. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18090) Improve TableSnapshotInputFormat to allow more multiple mappers per region
[ https://issues.apache.org/jira/browse/HBASE-18090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213486#comment-16213486 ] xinxin fan commented on HBASE-18090: Yes, the oracle seems download failed. > Improve TableSnapshotInputFormat to allow more multiple mappers per region > -- > > Key: HBASE-18090 > URL: https://issues.apache.org/jira/browse/HBASE-18090 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Reporter: Mikhail Antonov >Assignee: xinxin fan > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18090-V3-master.patch, > HBASE-18090-V4-master.patch, HBASE-18090-V5-master.patch, > HBASE-18090-branch-1.3-v1.patch, HBASE-18090-branch-1.3-v2.patch, > HBASE-18090.branch-1.patch > > > TableSnapshotInputFormat runs one map task per region in the table snapshot. > This places unnecessary restriction that the region layout of the original > table needs to take the processing resources available to MR job into > consideration. Allowing to run multiple mappers per region (assuming > reasonably even key distribution) would be useful. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19049) Update kerby to 1.0.1 GA release
[
https://issues.apache.org/jira/browse/HBASE-19049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213481#comment-16213481
]
Hadoop QA commented on HBASE-19049:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 13m
33s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
4s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
39m 37s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
52s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}157m 26s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
24s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}226m 48s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.regionserver.TestCompactionInDeadRegionServer |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:af479c5 |
| JIRA Issue | HBASE-19049 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12893285/HBASE-19049.1.patch |
| Optional Tests | asflicense shadedjars javac javadoc unit xml compile
|
| uname | Linux a7d0786b77cc 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 64d164b |
| Default Java | 1.8.0_141 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/9271/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9271/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9271/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Update kerby to 1.0.1 GA release
>
>
> Key: HBASE-19049
> URL: https://issues.apache.org/jira/browse/HBASE-19049
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Affects Versions: 2.0.0-alpha-3
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>
[jira] [Updated] (HBASE-18703) Inconsistent behavior for preBatchMutate in doMiniBatchMutate and processRowsWithLocks
[ https://issues.apache.org/jira/browse/HBASE-18703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18703: - Status: In Progress (was: Patch Available) > Inconsistent behavior for preBatchMutate in doMiniBatchMutate and > processRowsWithLocks > -- > > Key: HBASE-18703 > URL: https://issues.apache.org/jira/browse/HBASE-18703 > Project: HBase > Issue Type: Bug > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Umesh Agashe >Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: hbase-18703.master.001.patch, > hbase-18703.master.002.patch, hbase-18703.master.003.patch, > hbase-18703.master.004.patch, hbase-18703.master.005.patch, > hbase-18703.master.005.patch, hbase-18703.master.005.patch, > hbase-18703.master.006.patch, hbase-18703.master.007.patch > > > In doMiniBatchMutate, the preBatchMutate is called before building WAL, but > in processRowsWithLocks, we suggest the RowProcessor implementation to build > WAL in process method, which is ahead of preBatchMutate. > If a CP modifies the mutations, especially if it removes some cells from the > mutations, then the behavior of processRowsWithLocks is broken. The changes > applied to memstore and WAL will be different. And there is no way to remove > entries from a WALEdit through CP. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19007) Align Services Interfaces in Master and RegionServer
[
https://issues.apache.org/jira/browse/HBASE-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213468#comment-16213468
]
Hadoop QA commented on HBASE-19007:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m
52s{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 28 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
7s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
25s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
46s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
39m 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-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
33s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}109m 33s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
19s{color} | {color:green} hbase-thrift in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
50s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
35s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
15s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}214m 31s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.coprocessor.TestRegionObserverScannerOpenHook |
| | hadoop.hbase.client.TestBlockEvictionFromClient |
| | hadoop.hbase.regionserver.TestSplitTransactionOnCluster |
| |
[jira] [Commented] (HBASE-18984) [AMv2] Retain assignment does not work well in AMv2
[
https://issues.apache.org/jira/browse/HBASE-18984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213443#comment-16213443
]
Yi Liang commented on HBASE-18984:
--
It seems above two comments does not clearly state why {quote}// 2.
UnAssignProcedure can run first, this region will be assigned as OPEN
finally.{quote} would happen.
For example, during master unassign region A, and then master crashed, and
also the RS has region A crashed. So when master restart, it may reload region
A's state as OPEN, and since RS crashed, this Master will create a
ServerCrashProcedure for that RS, so there will be both assign(created by SCP)
and unassign (old procedure) for region A. And it is really hard to guarantee
which one run first(not so sure).
> [AMv2] Retain assignment does not work well in AMv2
> ---
>
> Key: HBASE-18984
> URL: https://issues.apache.org/jira/browse/HBASE-18984
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
>Affects Versions: 2.0.0
>Reporter: Yi Liang
>Assignee: Yi Liang
> Fix For: 2.0.0
>
> Attachments: HBASE-18984-V1-master.patch, Screen Shot 2017-10-10 at
> 2.24.19 PM.png
>
>
> work on 8.17 Retain assignment in
> https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.epjn9nege80k
> To reproduce this error, in hbase shell:
> createTable t1 --> list_regions 't1' --> disable 't1' ---> enable 't1' -->
> list_reigons 't1' (maybe you need to try enable/disable multiple times)
> See attached images. same region assigned to different region servers
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19061) enforcer NPE on hbase-shaded-invariants
[
https://issues.apache.org/jira/browse/HBASE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213434#comment-16213434
]
Hudson commented on HBASE-19061:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #981 (See
[https://builds.apache.org/job/HBase-1.2-IT/981/])
HBASE-19061 update enforcer rules for NPE (mdrob: rev
e8124ab8c4181d2cedff02078f7c76d3e44c219f)
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
> enforcer NPE on hbase-shaded-invariants
> ---
>
> Key: HBASE-19061
> URL: https://issues.apache.org/jira/browse/HBASE-19061
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 1.1.13, 2.0.0-alpha-4
>
> Attachments: HBASE-19061.patch
>
>
> {{mvn validate -Prelease}} fails on {{hbase-shaded-check-invariants}} with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) on project hbase-shaded-check-invariants:
> Execution min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> min-maven-min-java-banned-xerces of goal
> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.isBadArtifact(EnforceBytecodeVersion.java:221)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.checkDependencies(EnforceBytecodeVersion.java:206)
> at
> org.apache.maven.plugins.enforcer.EnforceBytecodeVersion.handleArtifacts(EnforceBytecodeVersion.java:132)
> at
> org.apache.maven.plugins.enforcer.AbstractResolveDependencies.execute(AbstractResolveDependencies.java:77)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:202)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> {noformat}
> cc: [~busbey]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19014) surefire fails; When writing xml report stdout/stderr ... No such file or directory
[
https://issues.apache.org/jira/browse/HBASE-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213416#comment-16213416
]
Hudson commented on HBASE-19014:
FAILURE: Integrated in Jenkins build HBase-1.5 #104 (See
[https://builds.apache.org/job/HBase-1.5/104/])
HBASE-19014 surefire fails; When writing xml report stdout/stderr ... No
(chia7712: rev 7f6ab255cd34effb39087b96c93ea5c4e7744e6a)
* (edit) pom.xml
> surefire fails; When writing xml report stdout/stderr ... No such file or
> directory
> ---
>
> Key: HBASE-19014
> URL: https://issues.apache.org/jira/browse/HBASE-19014
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> Attachments: HBASE-19014.branch-1.v0.patch,
> HBASE-19014.branch-1.v0.patch, HBASE-19014.branch-1.v0.patch,
> HBASE-19014.v0.patch, HBASE-19014.v0.patch
>
>
> {code}
> 17:22:33 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test
> (secondPartTestsExecution) on project hbase-server: ExecutionException:
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.maven.surefire.report.ReporterException: When writing xml report
> stdout/stderr: /tmp/stderr1114622923250399196deferred (No such file or
> directory) -> [Help 1]
> {code}
> It happens frequently on my jenkins...I update the surefire to 2.20.1, and
> then the failure doesn't happen again. see SUREFIRE-1239.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19053) Split out o.a.h.h.http from hbase-server into a separate module
[ https://issues.apache.org/jira/browse/HBASE-19053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213384#comment-16213384 ] Appy commented on HBASE-19053: -- I see that the other one has been work-in-progress for a while, and it's internal, so it likely won't have any time pressure. Unless it's getting committing today/tomorrow, in which case it makes sense to get the other one in first, i don't think we should add this prerequisite, otherwise it'll block all the dependency cleanup work am doing. Also, i did dependency:analyze on this pom to get rid of unused dependency and add all used deps, so it's not that bad. Also, whatever gets applied to hbase-server/pom.xml can be applied here too. So it'll probably be 10-30 min of extra work on the other jira, but that reasonable cost of unblocking a whole domain of changes. What do you say [~mdrob]? > Split out o.a.h.h.http from hbase-server into a separate module > --- > > Key: HBASE-19053 > URL: https://issues.apache.org/jira/browse/HBASE-19053 > Project: HBase > Issue Type: Bug >Reporter: Appy >Assignee: Appy > Attachments: HBASE-19053.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
