[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238795#comment-16238795
]
Hadoop QA commented on HBASE-19178:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
8s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
37s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
9s{color} | {color:red} The patch generated 4 new + 407 unchanged - 25 fixed =
411 total (was 432) {color} |
| {color:red}-1{color} | {color:red} ruby-lint {color} | {color:red} 0m
12s{color} | {color:red} The patch generated 6 new + 457 unchanged - 6 fixed =
463 total (was 463) {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} javadoc {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m
3s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 17m 39s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19178 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896036/HBASE-19178.master.003.patch
|
| Optional Tests | asflicense javac javadoc unit rubocop ruby_lint |
| uname | Linux 724a59d10eab 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 888e584a32 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_141 |
| rubocop | v0.51.0 |
| rubocop |
https://builds.apache.org/job/PreCommit-HBASE-Build/9616/artifact/patchprocess/diff-patch-rubocop.txt
|
| ruby-lint | v2.3.1 |
| ruby-lint |
https://builds.apache.org/job/PreCommit-HBASE-Build/9616/artifact/patchprocess/diff-patch-ruby-lint.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9616/testReport/ |
| modules | C: hbase-shell U: hbase-shell |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9616/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch, HBASE-19178.master.003.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18961) doMiniBatchMutate() is big, split it into smaller methods
[
https://issues.apache.org/jira/browse/HBASE-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238794#comment-16238794
]
Hadoop QA commented on HBASE-18961:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are 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 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
19s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
1s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
19s{color} | {color:red} hbase-server: The patch generated 1 new + 242
unchanged - 9 fixed = 243 total (was 251) {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} 5m
27s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
65m 4s{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} 1m
7s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
16s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}125m
50s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
40s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}222m 2s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-18961 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896015/hbase-18961.master.005.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 4f8e63c4febc 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 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 / 888e584a32 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_141 |
| checkstyle |
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238793#comment-16238793
]
Hadoop QA commented on HBASE-18775:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
1s{color} | {color:blue} Findbugs executables are 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 2 new or modified test
files. {color} |
|| || || || {color:brown} HBASE-18477 Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
38s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
42s{color} | {color:green} HBASE-18477 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
55s{color} | {color:green} HBASE-18477 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
17s{color} | {color:green} HBASE-18477 passed {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 5m
2s{color} | {color:red} branch has 13 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
46s{color} | {color:green} HBASE-18477 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
52s{color} | {color:red} hbase-server: The patch generated 2 new + 467
unchanged - 0 fixed = 469 total (was 467) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 3m
38s{color} | {color:red} patch has 13 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
42m 36s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
37s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 25m 40s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 91m 14s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.TestCheckTestClasses |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:9e78c0e |
| JIRA Issue | HBASE-18775 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896013/HBASE-18775.HBASE-18477.007.patch
|
| Optional Tests | asflicense shadedjars javac javadoc unit findbugs
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 92841f3868ab 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision |
[jira] [Commented] (HBASE-19179) Remove hbase-prefix-tree
[
https://issues.apache.org/jira/browse/HBASE-19179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238792#comment-16238792
]
Hadoop QA commented on HBASE-19179:
---
| (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:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are 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 56 new or modified test
files. {color} |
|| || || || {color:brown} branch-2 Compile Tests {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} 5m
45s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
51s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 5m
23s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 10m
34s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
2s{color} | {color:green} branch-2 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
49s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
12s{color} | {color:red} hbase-server: The patch generated 2 new + 228
unchanged - 12 fixed = 230 total (was 240) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 2m
18s{color} | {color:red} root: The patch generated 2 new + 297 unchanged - 227
fixed = 299 total (was 524) {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
5s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
57s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
46m 6s{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
27s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 30m 58s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}126m 14s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.io.encoding.TestSeekToBlockWithEncoders |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:9f2f2db |
| JIRA Issue | HBASE-19179 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896026/HBASE-19179.branch-2.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile xml |
| uname | Linux 81462082d1d8 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26
18:04:35 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
|
[jira] [Commented] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[
https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238788#comment-16238788
]
Sean Busbey commented on HBASE-19152:
-
okay failures:
{code}
Checking against things we don't expect to include in the source tarball (git
related, hbase-native-client, etc.)
Any output here are unexpected differences between the source artifact we'd
make for an RC and the current branch.
The expected differences are on the < side and the current differences are on
the > side.
In a given set of differences, '.' refers to the branch in the repo and
'unpacked_src_tarball' refers to what we pulled out of the tarball.
0a1
> Only in /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball:
> ${project.basedir}
2,4c3,21
< Only in .: .gitattributes
< Only in .: .gitignore
{code}
the git related files are present in the source tarball now, so those two
expected gaps can be removed.
{code}
< Only in .: hbase-native-client
---
{code}
the hbase-native-client is also now in the source tarball so this line should
be removed. HBASE-19176 would fix this in branch-2, but won't help master or
other branches.
{code}
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-build-configuration:
> src
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-build-support/hbase-error-prone/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-client/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-common/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-external-blockcache/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-hadoop2-compat/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-http/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-metrics/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-protocol/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-protocol-shaded/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-rest/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-server/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-shaded/hbase-shaded-client:
> dependency-reduced-pom.xml
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-shaded/hbase-shaded-mapreduce:
> dependency-reduced-pom.xml
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-shell/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-spark/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-spark-it/src:
> site
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-testing-util:
> src
> Only in
> /tmp/hbase-srctarball-test-27514.1/unpacked_src_tarball/hbase-thrift/src:
> site
{code}
these are made by the build process. They show up now because {{mvn clean}}
doesn't impact non-target directories and we're no longer doing a build in the
component directory.
probably best to generate the diff prior to doing the build in the unpacked
source tarball. we can't do a git clean since it's not a repo and doing a build
in the component directory will add time unnecessarily.
> Update refguide 'how to build an RC' and the make_rc.sh script
> --
>
> Key: HBASE-19152
> URL: https://issues.apache.org/jira/browse/HBASE-19152
> Project: HBase
> Issue Type: Sub-task
> Components: build
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments:
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> HBASE-19152.master.001.patch, HBASE-19152.master.002.patch,
> HBASE-19152.master.003.patch, HBASE-19152.master.004.patch,
> HBASE-19152.master.005.patch, HBASE-19152.master.006.patch,
> HBASE-19152.master.007.patch, HBASE-19152.master.008.patch
>
>
> Update the section on how to build an RC. In particular, note that tags
> should be signed and talk up the new way of building the src tgz (after a
> Sean suggestion) including removal of old means src.xml from hbase-assembly.
> Update the make_rc.sh script so it works for branch-2 builds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238783#comment-16238783
]
Guanghao Zhang commented on HBASE-19178:
bq. We have the nightly tests for this. If TestShell covers this case, then
we'll see fallout from things getting moved out from under the shell there.
Got it. Thanks for your explanation.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch, HBASE-19178.master.003.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
Attachment: HBASE-19178.master.003.patch
003 patch try to fix ruby warnings.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch, HBASE-19178.master.003.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19144) [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the cluster
[
https://issues.apache.org/jira/browse/HBASE-19144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238780#comment-16238780
]
Hudson commented on HBASE-19144:
SUCCESS: Integrated in Jenkins build HBase-1.4 #992 (See
[https://builds.apache.org/job/HBase-1.4/992/])
HBASE-19144 [RSgroups] Retry assignments in FAILED_OPEN state when (apurtell:
rev 28c7315e0b1db7e7fd30ba996b8735ac2d805756)
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManager.java
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java
> [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the
> cluster
> ---
>
> Key: HBASE-19144
> URL: https://issues.apache.org/jira/browse/HBASE-19144
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-19144-branch-1.patch, HBASE-19144-branch-1.patch,
> HBASE-19144.patch, HBASE-19144.patch, HBASE-19144.patch
>
>
> After all servers in the RSgroup are down the regions cannot be opened
> anywhere and transition rapidly into FAILED_OPEN state.
>
> 2017-10-31 21:06:25,449 INFO [ProcedureExecutor-13] master.RegionStates:
> Transition {c6c8150c9f4b8df25ba32073f25a5143 state=OFFLINE, ts=1509483985448,
> server=node-5.cluster,16020,1509482700768} to
> {c6c8150c9f4b8df25ba32073f25a5143 state=FAILED_OPEN, ts=1509483985449,
> server=node-5.cluster,16020,1509482700768}
> 2017-10-31 21:06:25,449 WARN [ProcedureExecutor-13] master.RegionStates:
> Failed to open/close d4e2f173e31ffad6aac140f4bd7b02bc on
> node-5.cluster,16020,1509482700768, set to FAILED_OPEN
>
> Any region in FAILED_OPEN state has to be manually reassigned, or the master
> can be restarted and this will also cause reattempt of assignment of any
> regions in FAILED_OPEN state. This is not unexpected but is an operational
> headache. It would be better if the RSGroupInfoManager could automatically
> kick reassignments of regions in FAILED_OPEN state when servers rejoin the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17819) Reduce the heap overhead for BucketCache
[ https://issues.apache.org/jira/browse/HBASE-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238776#comment-16238776 ] Anoop Sam John commented on HBASE-17819: Typo. eviction of blocks on HFile close is default off only (We have a config to turn this ON). bq.How did you do the size compare? Tested with Java Instrumentation > Reduce the heap overhead for BucketCache > > > Key: HBASE-17819 > URL: https://issues.apache.org/jira/browse/HBASE-17819 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-17819_V1.patch, HBASE-17819_V2.patch, > HBASE-17819_V3.patch > > > We keep Bucket entry map in BucketCache. Below is the math for heapSize for > the key , value into this map. > BlockCacheKey > --- > String hfileName - Ref - 4 > long offset - 8 > BlockType blockType - Ref - 4 > boolean isPrimaryReplicaBlock - 1 > Total = 12 (Object) + 17 = 29 > BucketEntry > > int offsetBase - 4 > int length - 4 > byte offset1 - 1 > byte deserialiserIndex - 1 > long accessCounter - 8 > BlockPriority priority - Ref - 4 > volatile boolean markedForEvict - 1 > AtomicInteger refCount - 16 + 4 > long cachedTime - 8 > Total = 12 (Object) + 51 = 63 > ConcurrentHashMap Map.Entry - 40 > blocksByHFile ConcurrentSkipListSet Entry - 40 > Total = 29 + 63 + 80 = 172 > For 10 million blocks we will end up having 1.6GB of heap size. > This jira aims to reduce this as much as possible -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[
https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238775#comment-16238775
]
Sean Busbey commented on HBASE-19152:
-
all of the references to {{m2_initial}} repo directory can be removed since we
don't use maven to build the source tarball now.
> Update refguide 'how to build an RC' and the make_rc.sh script
> --
>
> Key: HBASE-19152
> URL: https://issues.apache.org/jira/browse/HBASE-19152
> Project: HBase
> Issue Type: Sub-task
> Components: build
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments:
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> HBASE-19152.master.001.patch, HBASE-19152.master.002.patch,
> HBASE-19152.master.003.patch, HBASE-19152.master.004.patch,
> HBASE-19152.master.005.patch, HBASE-19152.master.006.patch,
> HBASE-19152.master.007.patch, HBASE-19152.master.008.patch
>
>
> Update the section on how to build an RC. In particular, note that tags
> should be signed and talk up the new way of building the src tgz (after a
> Sean suggestion) including removal of old means src.xml from hbase-assembly.
> Update the make_rc.sh script so it works for branch-2 builds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[ https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238773#comment-16238773 ] Sean Busbey commented on HBASE-19152: - my test run here got a bunch of errors, let me do it one more time to make sure I haven't missed something. > Update refguide 'how to build an RC' and the make_rc.sh script > -- > > Key: HBASE-19152 > URL: https://issues.apache.org/jira/browse/HBASE-19152 > Project: HBase > Issue Type: Sub-task > Components: build >Reporter: stack >Assignee: stack > Fix For: 2.0.0-beta-1 > > Attachments: > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > HBASE-19152.master.001.patch, HBASE-19152.master.002.patch, > HBASE-19152.master.003.patch, HBASE-19152.master.004.patch, > HBASE-19152.master.005.patch, HBASE-19152.master.006.patch, > HBASE-19152.master.007.patch, HBASE-19152.master.008.patch > > > Update the section on how to build an RC. In particular, note that tags > should be signed and talk up the new way of building the src tgz (after a > Sean suggestion) including removal of old means src.xml from hbase-assembly. > Update the make_rc.sh script so it works for branch-2 builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[
https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238772#comment-16238772
]
Sean Busbey commented on HBASE-19152:
-
{code}
mvn_version=$(mvn -q -N -Dexec.executable="echo"
-Dexec.args='${project.version}' exec:exec)
{code}
this needs a {{#shellcheck disable=SC2016}}
> Update refguide 'how to build an RC' and the make_rc.sh script
> --
>
> Key: HBASE-19152
> URL: https://issues.apache.org/jira/browse/HBASE-19152
> Project: HBase
> Issue Type: Sub-task
> Components: build
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments:
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch,
> HBASE-19152.master.001.patch, HBASE-19152.master.002.patch,
> HBASE-19152.master.003.patch, HBASE-19152.master.004.patch,
> HBASE-19152.master.005.patch, HBASE-19152.master.006.patch,
> HBASE-19152.master.007.patch, HBASE-19152.master.008.patch
>
>
> Update the section on how to build an RC. In particular, note that tags
> should be signed and talk up the new way of building the src tgz (after a
> Sean suggestion) including removal of old means src.xml from hbase-assembly.
> Update the make_rc.sh script so it works for branch-2 builds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19144) [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the cluster
[
https://issues.apache.org/jira/browse/HBASE-19144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238771#comment-16238771
]
Hudson commented on HBASE-19144:
FAILURE: Integrated in Jenkins build HBase-1.5 #135 (See
[https://builds.apache.org/job/HBase-1.5/135/])
HBASE-19144 [RSgroups] Retry assignments in FAILED_OPEN state when (apurtell:
rev 1e227acd654bde80e27799ae16e5a806467141c8)
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManager.java
> [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the
> cluster
> ---
>
> Key: HBASE-19144
> URL: https://issues.apache.org/jira/browse/HBASE-19144
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-19144-branch-1.patch, HBASE-19144-branch-1.patch,
> HBASE-19144.patch, HBASE-19144.patch, HBASE-19144.patch
>
>
> After all servers in the RSgroup are down the regions cannot be opened
> anywhere and transition rapidly into FAILED_OPEN state.
>
> 2017-10-31 21:06:25,449 INFO [ProcedureExecutor-13] master.RegionStates:
> Transition {c6c8150c9f4b8df25ba32073f25a5143 state=OFFLINE, ts=1509483985448,
> server=node-5.cluster,16020,1509482700768} to
> {c6c8150c9f4b8df25ba32073f25a5143 state=FAILED_OPEN, ts=1509483985449,
> server=node-5.cluster,16020,1509482700768}
> 2017-10-31 21:06:25,449 WARN [ProcedureExecutor-13] master.RegionStates:
> Failed to open/close d4e2f173e31ffad6aac140f4bd7b02bc on
> node-5.cluster,16020,1509482700768, set to FAILED_OPEN
>
> Any region in FAILED_OPEN state has to be manually reassigned, or the master
> can be restarted and this will also cause reattempt of assignment of any
> regions in FAILED_OPEN state. This is not unexpected but is an operational
> headache. It would be better if the RSGroupInfoManager could automatically
> kick reassignments of regions in FAILED_OPEN state when servers rejoin the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-13622) document upgrade rollback
[ https://issues.apache.org/jira/browse/HBASE-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238770#comment-16238770 ] Hudson commented on HBASE-13622: FAILURE: Integrated in Jenkins build HBase-2.0 #793 (See [https://builds.apache.org/job/HBase-2.0/793/]) HBASE-13622 document upgrade rollback. (busbey: rev 2485da1a60b8cb51dc5376f7d68de93084cc190f) * (edit) src/main/asciidoc/_chapters/ops_mgt.adoc * (edit) src/main/asciidoc/_chapters/upgrading.adoc > document upgrade rollback > - > > Key: HBASE-13622 > URL: https://issues.apache.org/jira/browse/HBASE-13622 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 0.98.0, 1.0.0, 1.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Labels: operability, upgrade > Fix For: 3.0.0, 2.0.0-beta-1 > > Attachments: HBASE-13622.1.patch > > > I have some docs on doing a rollback of an hbase upgrade that are currently > vendor specific. polish them up, make them suitable for HBase generally, and > add them to the ref guide. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19144) [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the cluster
[
https://issues.apache.org/jira/browse/HBASE-19144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238769#comment-16238769
]
Hudson commented on HBASE-19144:
FAILURE: Integrated in Jenkins build HBase-2.0 #793 (See
[https://builds.apache.org/job/HBase-2.0/793/])
HBASE-19144 [RSgroups] Retry assignments in FAILED_OPEN state when (apurtell:
rev 5df9651581f599ba9bcbb0def660870ab0398ccc)
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java
* (edit)
hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManager.java
> [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the
> cluster
> ---
>
> Key: HBASE-19144
> URL: https://issues.apache.org/jira/browse/HBASE-19144
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-19144-branch-1.patch, HBASE-19144-branch-1.patch,
> HBASE-19144.patch, HBASE-19144.patch, HBASE-19144.patch
>
>
> After all servers in the RSgroup are down the regions cannot be opened
> anywhere and transition rapidly into FAILED_OPEN state.
>
> 2017-10-31 21:06:25,449 INFO [ProcedureExecutor-13] master.RegionStates:
> Transition {c6c8150c9f4b8df25ba32073f25a5143 state=OFFLINE, ts=1509483985448,
> server=node-5.cluster,16020,1509482700768} to
> {c6c8150c9f4b8df25ba32073f25a5143 state=FAILED_OPEN, ts=1509483985449,
> server=node-5.cluster,16020,1509482700768}
> 2017-10-31 21:06:25,449 WARN [ProcedureExecutor-13] master.RegionStates:
> Failed to open/close d4e2f173e31ffad6aac140f4bd7b02bc on
> node-5.cluster,16020,1509482700768, set to FAILED_OPEN
>
> Any region in FAILED_OPEN state has to be manually reassigned, or the master
> can be restarted and this will also cause reattempt of assignment of any
> regions in FAILED_OPEN state. This is not unexpected but is an operational
> headache. It would be better if the RSGroupInfoManager could automatically
> kick reassignments of regions in FAILED_OPEN state when servers rejoin the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19176) Remove hbase-native-client from branch-2
[
https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238768#comment-16238768
]
Hadoop QA commented on HBASE-19176:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 3m
26s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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: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:brown} branch-2 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
25s{color} | {color:green} branch-2 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
23s{color} | {color:green} branch-2 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 4m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
1s{color} | {color:green} The patch generated 0 new + 0 unchanged - 40 fixed =
0 total (was 40) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}152m 56s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
7s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}174m 50s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.assignment.TestSplitTableRegionProcedure |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:9f2f2db |
| JIRA Issue | HBASE-19176 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896012/HBASE-19716-branch-2.patch
|
| Optional Tests | asflicense shellcheck shelldocs cc unit compile |
| uname | Linux 93f33be7dc78 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-2 / 2485da1a60 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| shellcheck | v0.4.4 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/9604/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9604/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9604/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> Remove hbase-native-client from branch-2
>
>
> Key: HBASE-19176
> URL: https://issues.apache.org/jira/browse/HBASE-19176
> Project: HBase
> Issue Type: Task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19716-branch-2.patch
>
>
> As per discussion over in "[DISCUSSION] Items to purge from branch-2 before
> we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19131:
---
Status: Patch Available (was: Open)
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.branch-1.v0.patch, HBASE-19131.v0.patch,
> HBASE-19131.v1.patch, HBASE-19131.v2.patch, HBASE-19131.v3.patch,
> HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19131:
---
Status: Open (was: Patch Available)
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.branch-1.v0.patch, HBASE-19131.v0.patch,
> HBASE-19131.v1.patch, HBASE-19131.v2.patch, HBASE-19131.v3.patch,
> HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-19131:
---
Attachment: HBASE-19131.branch-1.v0.patch
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.branch-1.v0.patch, HBASE-19131.v0.patch,
> HBASE-19131.v1.patch, HBASE-19131.v2.patch, HBASE-19131.v3.patch,
> HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238766#comment-16238766
]
Hadoop QA commented on HBASE-19178:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
29s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
11s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
56s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
10s{color} | {color:red} The patch generated 22 new + 428 unchanged - 4 fixed =
450 total (was 432) {color} |
| {color:red}-1{color} | {color:red} ruby-lint {color} | {color:red} 0m
12s{color} | {color:red} The patch generated 8 new + 463 unchanged - 0 fixed =
471 total (was 463) {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} javadoc {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m
23s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 6s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19178 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896030/HBASE-19178.master.002.patch
|
| Optional Tests | asflicense javac javadoc unit rubocop ruby_lint |
| uname | Linux 7a54b4f81979 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 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 / 888e584a32 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_141 |
| rubocop | v0.51.0 |
| rubocop |
https://builds.apache.org/job/PreCommit-HBASE-Build/9614/artifact/patchprocess/diff-patch-rubocop.txt
|
| ruby-lint | v2.3.1 |
| ruby-lint |
https://builds.apache.org/job/PreCommit-HBASE-Build/9614/artifact/patchprocess/diff-patch-ruby-lint.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9614/testReport/ |
| modules | C: hbase-shell U: hbase-shell |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9614/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18477) Umbrella JIRA for HBase Read Replica clusters
[ https://issues.apache.org/jira/browse/HBASE-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238763#comment-16238763 ] Zach York commented on HBASE-18477: --- Thanks! > Umbrella JIRA for HBase Read Replica clusters > - > > Key: HBASE-18477 > URL: https://issues.apache.org/jira/browse/HBASE-18477 > Project: HBase > Issue Type: New Feature >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase > Read-Replica Clusters Scope doc.pdf, HBase Read-Replica Clusters Scope > doc_v2.docx, HBase Read-Replica Clusters Scope doc_v2.pdf > > > Recently, changes (such as HBASE-17437) have unblocked HBase to run with a > root directory external to the cluster (such as in Amazon S3). This means > that the data is stored outside of the cluster and can be accessible after > the cluster has been terminated. One use case that is often asked about is > pointing multiple clusters to one root directory (sharing the data) to have > read resiliency in the case of a cluster failure. > > This JIRA is an umbrella JIRA to contain all the tasks necessary to create a > read-replica HBase cluster that is pointed at the same root directory. > > This requires making the Read-Replica cluster Read-Only (no metadata > operation or data operations). > Separating the hbase:meta table for each cluster (Otherwise HBase gets > confused with multiple clusters trying to update the meta table with their ip > addresses) > Adding refresh functionality for the meta table to ensure new metadata is > picked up on the read replica cluster. > Adding refresh functionality for HFiles for a given table to ensure new data > is picked up on the read replica cluster. > > This can be used with any existing cluster that is backed by an external > filesystem. > > Please note that this feature is still quite manual (with the potential for > automation later). > > More information on this particular feature can be found here: > https://aws.amazon.com/blogs/big-data/setting-up-read-replica-clusters-with-hbase-on-amazon-s3/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238762#comment-16238762 ] Zach York commented on HBASE-18775: --- Thanks for the help! [~busbey] [~mdrob] > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238760#comment-16238760
]
Sean Busbey commented on HBASE-19178:
-
bq. When a patch only changed hbase-client/hbase-server, then the ut in
hbase-shell can't run. So if we remove some methods, it is not easy to find the
failure. How about we run hbase-client/hbase-shell ut for all precommit job, no
matter the patch modified any code.
We have the nightly tests for this. If TestShell covers this case, then we'll
see fallout from things getting moved out from under the shell there.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238758#comment-16238758 ] Sean Busbey commented on HBASE-18775: - I started another run and it looks like it's going fine: https://builds.apache.org/job/PreCommit-HBASE-Build/9613 > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-12125) Add Hbck option to check and fix WAL's from replication queue
[
https://issues.apache.org/jira/browse/HBASE-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238756#comment-16238756
]
Hadoop QA commented on HBASE-12125:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m
23s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are 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 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
33s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
4s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s{color} | {color:green} hbase-replication: The patch generated 0 new + 8
unchanged - 4 fixed = 8 total (was 12) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
6s{color} | {color:green} hbase-server: The patch generated 0 new + 189
unchanged - 2 fixed = 189 total (was 191) {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
41s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
47m 12s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
13s{color} | {color:green} hbase-replication in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}119m 2s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
42s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}191m 18s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-12125 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12895999/HBASE-12125.v4.master.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 5a1b808294bb 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26
18:04:35 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238755#comment-16238755
]
Guanghao Zhang commented on HBASE-19178:
bq. I'd be surprised if this wasn't already covered by TestShell – maybe those
tests aren't running correctly?
Not covered by TestShell...
When a patch only changed hbase-client/hbase-server, then the ut in hbase-shell
can't run. So if we remove some methods, it is not easy to find the failure.
How about we run hbase-client/hbase-shell ut for all precommit job, no matter
the patch modified any code.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238754#comment-16238754 ] Sean Busbey commented on HBASE-18775: - bq. 00:01:15.085 ERROR: Unsure how to process HBASE-18775. this usually means a problem with the personality. > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238752#comment-16238752
]
Guanghao Zhang commented on HBASE-19178:
Update ut with a delete. And the ut failed without the fix. The ut passed with
the fix.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
Attachment: HBASE-19178.master.002.patch
Add ut in 002 patch.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch,
> HBASE-19178.master.002.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238744#comment-16238744
]
Hadoop QA commented on HBASE-19178:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
31s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
16s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
32s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
8s{color} | {color:red} The patch generated 1 new + 152 unchanged - 1 fixed =
153 total (was 153) {color} |
| {color:green}+1{color} | {color:green} ruby-lint {color} | {color:green} 0m
3s{color} | {color:green} There were no new ruby-lint 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} javadoc {color} | {color:green} 0m
13s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m
42s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 26m 30s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19178 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896025/HBASE-19178.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit rubocop ruby_lint |
| uname | Linux c3b3e4ba6930 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 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 / 888e584a32 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_141 |
| rubocop | v0.51.0 |
| rubocop |
https://builds.apache.org/job/PreCommit-HBASE-Build/9610/artifact/patchprocess/diff-patch-rubocop.txt
|
| ruby-lint | v2.3.1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/9610/testReport/ |
| modules | C: hbase-shell U: hbase-shell |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9610/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238743#comment-16238743 ] Sean Busbey commented on HBASE-19176: - +1 > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238740#comment-16238740
]
Josh Elser commented on HBASE-19178:
I'd be surprised if this wasn't already covered by TestShell -- maybe those
tests aren't running correctly?
If I am wrong, should be very simple to add a test that does exactly what you
describe [~zghaobac]. Happy to help if needed :)
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18891) Upgrade netty-all jar
[ https://issues.apache.org/jira/browse/HBASE-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-18891: --- Attachment: HBASE-18891.002.branch-1.3.patch Retry .002 > Upgrade netty-all jar > - > > Key: HBASE-18891 > URL: https://issues.apache.org/jira/browse/HBASE-18891 > Project: HBase > Issue Type: Bug >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 1.3.2, 1.1.13, 1.2.8 > > Attachments: HBASE-18891.001.branch-1.3.patch, > HBASE-18891.002.branch-1.3.patch, HBASE-18891.002.branch-1.3.patch > > > Upgrade netty-all jar to 4.0.37.Final version to fix latest vulnerabilities > reported. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19179) Remove hbase-prefix-tree
[ https://issues.apache.org/jira/browse/HBASE-19179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19179: -- Status: Patch Available (was: Open) > Remove hbase-prefix-tree > > > Key: HBASE-19179 > URL: https://issues.apache.org/jira/browse/HBASE-19179 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19179.branch-2.001.patch > > > Remove hbase-prefix-tree. As per discussion over in "[DISCUSSION] Items to > purge from branch-2 before we cut hbase-2.0.0-beta1." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19179) Remove hbase-prefix-tree
[ https://issues.apache.org/jira/browse/HBASE-19179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19179: -- Attachment: HBASE-19179.branch-2.001.patch > Remove hbase-prefix-tree > > > Key: HBASE-19179 > URL: https://issues.apache.org/jira/browse/HBASE-19179 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19179.branch-2.001.patch > > > Remove hbase-prefix-tree. As per discussion over in "[DISCUSSION] Items to > purge from branch-2 before we cut hbase-2.0.0-beta1." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238733#comment-16238733
]
Chia-Ping Tsai commented on HBASE-19131:
The failed tests pass locally. Will submit the patch for branch-1.
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.v0.patch, HBASE-19131.v1.patch,
> HBASE-19131.v2.patch, HBASE-19131.v3.patch, HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238731#comment-16238731
]
Ted Yu commented on HBASE-19178:
Is it possible to add a test so that such problem can be caught in the future ?
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
Status: Patch Available (was: Open)
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
Attachment: HBASE-19178.master.001.patch
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Attachments: HBASE-19178.master.001.patch
>
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19179) Remove hbase-prefix-tree
[ https://issues.apache.org/jira/browse/HBASE-19179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19179: -- Description: Remove hbase-prefix-tree. As per discussion over in "[DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1." (was: Remove hbase-prefix-tree.) > Remove hbase-prefix-tree > > > Key: HBASE-19179 > URL: https://issues.apache.org/jira/browse/HBASE-19179 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Critical > Fix For: 2.0.0-beta-1 > > > Remove hbase-prefix-tree. As per discussion over in "[DISCUSSION] Items to > purge from branch-2 before we cut hbase-2.0.0-beta1." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19179) Remove hbase-prefix-tree
stack created HBASE-19179: - Summary: Remove hbase-prefix-tree Key: HBASE-19179 URL: https://issues.apache.org/jira/browse/HBASE-19179 Project: HBase Issue Type: Task Reporter: stack Assignee: stack Priority: Critical Fix For: 2.0.0-beta-1 Remove hbase-prefix-tree. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18477) Umbrella JIRA for HBase Read Replica clusters
[ https://issues.apache.org/jira/browse/HBASE-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238727#comment-16238727 ] Mike Drob commented on HBASE-18477: --- I cherry-picked HBASE-19054 to this branch, since it looked like we were having docker build issues here. > Umbrella JIRA for HBase Read Replica clusters > - > > Key: HBASE-18477 > URL: https://issues.apache.org/jira/browse/HBASE-18477 > Project: HBase > Issue Type: New Feature >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase > Read-Replica Clusters Scope doc.pdf, HBase Read-Replica Clusters Scope > doc_v2.docx, HBase Read-Replica Clusters Scope doc_v2.pdf > > > Recently, changes (such as HBASE-17437) have unblocked HBase to run with a > root directory external to the cluster (such as in Amazon S3). This means > that the data is stored outside of the cluster and can be accessible after > the cluster has been terminated. One use case that is often asked about is > pointing multiple clusters to one root directory (sharing the data) to have > read resiliency in the case of a cluster failure. > > This JIRA is an umbrella JIRA to contain all the tasks necessary to create a > read-replica HBase cluster that is pointed at the same root directory. > > This requires making the Read-Replica cluster Read-Only (no metadata > operation or data operations). > Separating the hbase:meta table for each cluster (Otherwise HBase gets > confused with multiple clusters trying to update the meta table with their ip > addresses) > Adding refresh functionality for the meta table to ensure new metadata is > picked up on the read replica cluster. > Adding refresh functionality for HFiles for a given table to ensure new data > is picked up on the read replica cluster. > > This can be used with any existing cluster that is backed by an external > filesystem. > > Please note that this feature is still quite manual (with the potential for > automation later). > > More information on this particular feature can be found here: > https://aws.amazon.com/blogs/big-data/setting-up-read-replica-clusters-with-hbase-on-amazon-s3/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238720#comment-16238720 ] Hudson commented on HBASE-19097: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3992 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3992/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev 3e4b86d4d6b3608e22abb1fe8db07073eb486da8) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
Description:
create 't1'
put 't1', 'r1', 'f1:c1', 'value'
delete 't1', 'r1'
hbase(main):011:0> scan 't1',
{RAW => true}
ROW COLUMN+CELL
ERROR: undefined method `getType' for
#
Did you mean? get_type_byte
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238718#comment-16238718
]
Mike Drob commented on HBASE-18775:
---
[~busbey] - could there be a regression in YETUS about how it handles branch
patches? v0.4.0 seemed to be working fine here and new version doesn't run the
patch.
https://builds.apache.org/job/PreCommit-HBASE-Build/9605/console
{noformat}
00:00:06.444 Processing: HBASE-18775
00:01:15.085 ERROR: Unsure how to process HBASE-18775.
{noformat}
> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
> Issue Type: Sub-task
> Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
>Priority: Major
> Attachments: HBASE-18775.HBASE-18477.001.patch,
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch,
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch,
> HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a
> cluster. This patch extends the read only mode used by replication to disable
> all data and metadata operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang reassigned HBASE-19178:
--
Assignee: Guanghao Zhang
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
>
> create 't1'
> put 't1', 'r1', 'f1:c1', 'value'
> delete 't1', 'r1'
> hbase(main):011:0> scan 't1',
> {RAW => true}
> ROW COLUMN+CELL
> ERROR: undefined method `getType' for
> #
> Did you mean? get_type_byte
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
[
https://issues.apache.org/jira/browse/HBASE-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-19178:
---
create 't1'
put 't1', 'r1', 'f1:c1', 'value'
delete 't1', 'r1'
hbase(main):011:0> scan 't1', {RAW => true}
ROW COLUMN+CELL
ERROR: undefined method `getType' for
#
Did you mean? get_type_byte
> table.rb use undefined method 'getType' for Cell interface
> --
>
> Key: HBASE-19178
> URL: https://issues.apache.org/jira/browse/HBASE-19178
> Project: HBase
> Issue Type: Bug
>Reporter: Guanghao Zhang
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19111) Add missing CellUtil#isXXX(Cell) methods
[ https://issues.apache.org/jira/browse/HBASE-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-19111: --- Attachment: HBASE-19111.002.branch-2.patch .002 rebased on branch-2. Also removed some javadoc warnings in TestFromClientSide which were bugging me. > Add missing CellUtil#isXXX(Cell) methods > > > Key: HBASE-19111 > URL: https://issues.apache.org/jira/browse/HBASE-19111 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19111.001.branch-2.patch, > HBASE-19111.002.branch-2.patch > > > Over in HBASE-19002 while trying to write some RegionObservers, I found that > I couldn't find a public-API method to determine if a Cell was for a Put. We > seem to only have API for determining if it's a Delete. > Let's get some methods added to CellUtil for users to consume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19178) table.rb use undefined method 'getType' for Cell interface
Guanghao Zhang created HBASE-19178: -- Summary: table.rb use undefined method 'getType' for Cell interface Key: HBASE-19178 URL: https://issues.apache.org/jira/browse/HBASE-19178 Project: HBase Issue Type: Bug Reporter: Guanghao Zhang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19111) Add missing CellUtil#isPut(Cell) methods
[ https://issues.apache.org/jira/browse/HBASE-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-19111: --- Summary: Add missing CellUtil#isPut(Cell) methods (was: Add missing CellUtil#isXXX(Cell) methods) > Add missing CellUtil#isPut(Cell) methods > > > Key: HBASE-19111 > URL: https://issues.apache.org/jira/browse/HBASE-19111 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19111.001.branch-2.patch, > HBASE-19111.002.branch-2.patch > > > Over in HBASE-19002 while trying to write some RegionObservers, I found that > I couldn't find a public-API method to determine if a Cell was for a Put. We > seem to only have API for determining if it's a Delete. > Let's get some methods added to CellUtil for users to consume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238709#comment-16238709
]
Reid Chan commented on HBASE-19131:
---
+1
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.v0.patch, HBASE-19131.v1.patch,
> HBASE-19131.v2.patch, HBASE-19131.v3.patch, HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238708#comment-16238708 ] Josh Elser commented on HBASE-19176: +1 Thanks for the clarification. Assumed that was the case, but wanted to double check. > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19174) Update link to HBase presentations
[
https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238707#comment-16238707
]
Hadoop QA commented on HBASE-19174:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
16s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 36m
39s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 34m
57s{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:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 77m 12s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19174 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896001/HBASE-19174.master.001.patch
|
| Optional Tests | asflicense mvnsite |
| uname | Linux 8917fb2d5334 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 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 / 888e584a32 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9602/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> Update link to HBase presentations
> --
>
> Key: HBASE-19174
> URL: https://issues.apache.org/jira/browse/HBASE-19174
> Project: HBase
> Issue Type: Improvement
> Components: documentation
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
> Attachments: HBASE-19174.master.001.patch
>
>
> old_news.adoc references to the [Hadoop
> wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past
> presentations. The page itself states that it will be decommissioned in the
> future. The link should go to the book instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238705#comment-16238705 ] stack commented on HBASE-19176: --- [~elserj] yes sir (patch has branch-2 in it). Would love to have a native client. > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238702#comment-16238702 ] Josh Elser commented on HBASE-19176: You're still leaving it in master, right [~stack]? > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19035) Miss metrics when coprocessor use region scanner to read data
[ https://issues.apache.org/jira/browse/HBASE-19035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238700#comment-16238700 ] Guanghao Zhang commented on HBASE-19035: Ping [~stack] [~anoop.hbase] [~Apache9] for reviewing. > Miss metrics when coprocessor use region scanner to read data > - > > Key: HBASE-19035 > URL: https://issues.apache.org/jira/browse/HBASE-19035 > Project: HBase > Issue Type: Bug >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19035.master.001.patch, > HBASE-19035.master.002.patch > > > Region interface is exposed to coprocessor. So coprocessor use getScanner to > get a region scanner to read data. But the scan metrics was only updated in > region server level. So we will miss some scan metrics for the read from > coprocessor. > || Region Operation || When to update requests metric || > | get | update read metric in nextRaw() | > | put | update write metric in batchMutate() | > | delete | update write metric in batchMutate() | > | increment | update read metric by get() and update write metric in > doDelta() | > | append | update read metric by get() and update write metric in doDelta() | > | mutateRow | update write metric in processRowsWithLocks() | > | mutateRowsWithLocks | update write metric in processRowsWithLocks() | > | batchMutate | update write metric in batchMutate() | > | checkAndMutate | update read metric by get() and update write metric by > mutateRow() | > | checkAndRowMutate | update read metric by get() and update write metric by > doBatchMutate() | > | processRowsWithLocks | update write metric in processRowsWithLocks() | > Meanwhile, remove requestRowActionCount in RSRpcServices. This metric can be > computed by region's readRequestsCount and writeRequestsCount. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238699#comment-16238699 ] Hudson commented on HBASE-19097: FAILURE: Integrated in Jenkins build HBase-1.4 #991 (See [https://builds.apache.org/job/HBase-1.4/991/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev 7a9e1dd1b8a4545a813c4b64bddebcacc4db9b64) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19177) Determine if custom maven-fluido-skin jar is still necessary
[ https://issues.apache.org/jira/browse/HBASE-19177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238697#comment-16238697 ] Josh Elser commented on HBASE-19177: Some folks who may be interested, sorry if you're not! [~busbey], [~stack], [~misty] > Determine if custom maven-fluido-skin jar is still necessary > > > Key: HBASE-19177 > URL: https://issues.apache.org/jira/browse/HBASE-19177 > Project: HBase > Issue Type: Task > Components: site >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Major > Fix For: 2.0.0-beta-1 > > > To get a fancy, mobile-friendly website, HBASE-14785 introduced a patched > version of the maven-fluido-skin and committed the pre-built jar into our > release. > A few folks have noticed this jar lurking around the 2.0.0 alpha releases. By > version number, it doesn't seem like we'd need to have this anymore (and can > use the newest version). > Let's check it out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19177) Determine if custom maven-fluido-skin jar is still necessary
Josh Elser created HBASE-19177: -- Summary: Determine if custom maven-fluido-skin jar is still necessary Key: HBASE-19177 URL: https://issues.apache.org/jira/browse/HBASE-19177 Project: HBase Issue Type: Task Components: site Reporter: Josh Elser Assignee: Josh Elser Priority: Major Fix For: 2.0.0-beta-1 To get a fancy, mobile-friendly website, HBASE-14785 introduced a patched version of the maven-fluido-skin and committed the pre-built jar into our release. A few folks have noticed this jar lurking around the 2.0.0 alpha releases. By version number, it doesn't seem like we'd need to have this anymore (and can use the newest version). Let's check it out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook
[
https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238696#comment-16238696
]
Guanghao Zhang commented on HBASE-19131:
+1
> Add the ClusterStatus hook and cleanup other hooks which can be replaced by
> ClusterStatus hook
> --
>
> Key: HBASE-19131
> URL: https://issues.apache.org/jira/browse/HBASE-19131
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 1.4.0, 1.5.0, 2.0.0-beta-1
>
> Attachments: HBASE-19131.v0.patch, HBASE-19131.v1.patch,
> HBASE-19131.v2.patch, HBASE-19131.v3.patch, HBASE-19131.v4.patch
>
>
> This issue will add the hook for {{ClusterStatus}} and cleanup other hooks
> which can be replaced by {{ClusterStatus}} hook.
> # {{ListDeadServers}} - introduced by HBASE-18131
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18961) doMiniBatchMutate() is big, split it into smaller methods
[ https://issues.apache.org/jira/browse/HBASE-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18961: - Attachment: hbase-18961.master.005.patch Fixed checkstyle error + build retry for a flaky failure > doMiniBatchMutate() is big, split it into smaller methods > - > > Key: HBASE-18961 > URL: https://issues.apache.org/jira/browse/HBASE-18961 > Project: HBase > Issue Type: Sub-task > Components: regionserver >Affects Versions: 2.0.0-alpha-3 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: hbase-18961.master.001.patch, > hbase-18961.master.002.patch, hbase-18961.master.003.patch, > hbase-18961.master.004.patch, hbase-18961.master.005.patch > > > Split doMiniBatchMutate() and improve readability. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19173) Configure IntegrationTestRSGroup automatically for minicluster mode
[ https://issues.apache.org/jira/browse/HBASE-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238693#comment-16238693 ] Josh Elser commented on HBASE-19173: LGTM! > Configure IntegrationTestRSGroup automatically for minicluster mode > --- > > Key: HBASE-19173 > URL: https://issues.apache.org/jira/browse/HBASE-19173 > Project: HBase > Issue Type: Bug > Components: rsgroup, test >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0 > > Attachments: HBASE-19173.patch > > > IntegrationTestRSGroup fails if run in minicluster mode. Configuration should > be handled automatically. > FAILURE! - in org.apache.hadoop.hbase.rsgroup.IntegrationTestRSGroup > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered > master coprocessor service found for name RSGroupAdminService > at > org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:702) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:64515) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2352) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:297) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:277) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18624) Added support for clearing BlockCache based on table name
[
https://issues.apache.org/jira/browse/HBASE-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238691#comment-16238691
]
Hadoop QA commented on HBASE-18624:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m
23s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
1s{color} | {color:blue} Findbugs executables are 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 3 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
13s{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} javadoc {color} | {color:green} 1m
18s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
6s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
41s{color} | {color:red} hbase-client: The patch generated 7 new + 893
unchanged - 0 fixed = 900 total (was 893) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
11s{color} | {color:red} hbase-server: The patch generated 6 new + 300
unchanged - 7 fixed = 306 total (was 307) {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
11s{color} | {color:red} The patch generated 6 new + 359 unchanged - 1 fixed =
365 total (was 360) {color} |
| {color:red}-1{color} | {color:red} ruby-lint {color} | {color:red} 0m
4s{color} | {color:red} The patch generated 4 new + 740 unchanged - 0 fixed =
744 total (was 740) {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} 5m
1s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
50m 15s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {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:green}+1{color} | {color:green} unit {color} | {color:green} 3m
1s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 97m
39s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m
23s{color} | {color:green} hbase-shell
[jira] [Commented] (HBASE-19165) TODO Handle stuck in transition: rit=OPENING, location=ve0538....
[
https://issues.apache.org/jira/browse/HBASE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238686#comment-16238686
]
Hadoop QA commented on HBASE-19165:
---
| (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:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are 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:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
26s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
0s{color} | {color:red} hbase-server: The patch generated 1 new + 39 unchanged
- 1 fixed = 40 total (was 40) {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
24s{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 20s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}101m 28s{color}
| {color:red} hbase-server 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}163m 56s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestRestoreSnapshotProcedure |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19165 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12895989/HBASE-19165.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux c5d95cb0c3d0 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 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 / 3e4b86d4d6 |
| maven | version: Apache Maven 3.5.2
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_141 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HBASE-Build/9599/artifact/patchprocess/diff-checkstyle-hbase-server.txt
|
| unit |
[jira] [Commented] (HBASE-19102) TestZooKeeperMainServer fails with KeeperException$ConnectionLossException
[ https://issues.apache.org/jira/browse/HBASE-19102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238684#comment-16238684 ] Hudson commented on HBASE-19102: FAILURE: Integrated in Jenkins build HBase-2.0 #792 (See [https://builds.apache.org/job/HBase-2.0/792/]) HBASE-19102 TestZooKeeperMainServer fails with KeeperException (stack: rev 0fb3bd2e3c3b5bcce2f1c374bd07e4811ebfae0b) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperMainServer.java > TestZooKeeperMainServer fails with KeeperException$ConnectionLossException > -- > > Key: HBASE-19102 > URL: https://issues.apache.org/jira/browse/HBASE-19102 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19102.master.001.patch, > HBASE-19102.master.002.patch, HBASE-19102.master.002.patch > > > I'm trying to run test suite on a local machine. I never get to the second > part because I fail on below test with below exception near every time (and > an ipv6 test... will do that next). > 1 > --- > 2 Test set: org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer > 3 > --- > 4 Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.161 s > <<< FAILURE! - in org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer > 5 > testCommandLineWorks(org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer) > Time elapsed: 15.848 s <<< ERROR! > 6 org.apache.zookeeper.KeeperException$ConnectionLossException: > KeeperErrorCode = ConnectionLoss for /testCommandLineWorks > 7 at > org.apache.hadoop.hbase.zookeeper.TestZooKeeperMainServer.testCommandLineWorks(TestZooKeeperMainServer.java:81) > Looks like running the command before we are connected causes the above -- we > pause 15 seconds and then throw the above. If I wait until connected before > proceding, stuff seems to work reliably. I don't have access to the watcher > on connections since we override the zk main class... so this seems only > avenue available at mo (This zk main thing is all a hack around zk main > because it had bugs ... but I think we have to keep the hack because folks > use different versions of zk. My $workplace defaults to something that is > years old, 3.4.5 for instance). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238685#comment-16238685 ] Hudson commented on HBASE-19097: FAILURE: Integrated in Jenkins build HBase-2.0 #792 (See [https://builds.apache.org/job/HBase-2.0/792/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev b9b0f15cdbad14620eebf5769c0a3b664ab5afe8) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18233) We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
[ https://issues.apache.org/jira/browse/HBASE-18233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allan Yang updated HBASE-18233: --- Attachment: HBASE-18233-branch-1.2.v5.patch V5 patch uploaded, added a timeout on the UT newly added. Still not understand why the build will timeout. If this patch failed too, I will add a trial patch to test the branch-1.2. Sorry for so much trouble, everyone. > We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock > - > > Key: HBASE-18233 > URL: https://issues.apache.org/jira/browse/HBASE-18233 > Project: HBase > Issue Type: Bug >Affects Versions: 1.2.7 >Reporter: Allan Yang >Assignee: Allan Yang >Priority: Blocker > Fix For: 1.3.2, 1.2.7 > > Attachments: HBASE-18233-branch-1.2.patch, > HBASE-18233-branch-1.2.v2.patch, HBASE-18233-branch-1.2.v3.patch, > HBASE-18233-branch-1.2.v4 (1).patch, HBASE-18233-branch-1.2.v4 (1).patch, > HBASE-18233-branch-1.2.v4 (2).patch, HBASE-18233-branch-1.2.v4.patch, > HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, > HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, > HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, > HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v5.patch > > > Please refer to the discuss in HBASE-18144 > https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238672#comment-16238672 ] Hudson commented on HBASE-19097: FAILURE: Integrated in Jenkins build HBase-1.5 #134 (See [https://builds.apache.org/job/HBase-1.5/134/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev e61f6ff0ecf4fcd07ca20abcbfd5ec6f6fc60f52) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Status: Patch Available (was: In Progress) > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Status: In Progress (was: Patch Available) > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Attachment: HBASE-18775.HBASE-18477.007.patch > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch, HBASE-18775.HBASE-18477.007.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19176: -- Status: Patch Available (was: Open) > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19176) Remove hbase-native-client from branch-2
[ https://issues.apache.org/jira/browse/HBASE-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19176: -- Attachment: HBASE-19716-branch-2.patch Remove module and references in dev-support script. > Remove hbase-native-client from branch-2 > > > Key: HBASE-19176 > URL: https://issues.apache.org/jira/browse/HBASE-19176 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19716-branch-2.patch > > > As per discussion over in "[DISCUSSION] Items to purge from branch-2 before > we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19176) Remove hbase-native-client from branch-2
stack created HBASE-19176: - Summary: Remove hbase-native-client from branch-2 Key: HBASE-19176 URL: https://issues.apache.org/jira/browse/HBASE-19176 Project: HBase Issue Type: Task Reporter: stack Assignee: stack Priority: Major Fix For: 2.0.0-beta-1 As per discussion over in "[DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.", purge hbase-native-client from hbase2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13622) document upgrade rollback
[ https://issues.apache.org/jira/browse/HBASE-13622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-13622: Resolution: Fixed Fix Version/s: (was: 2.0.0) 2.0.0-beta-1 3.0.0 Status: Resolved (was: Patch Available) > document upgrade rollback > - > > Key: HBASE-13622 > URL: https://issues.apache.org/jira/browse/HBASE-13622 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 0.98.0, 1.0.0, 1.1.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Labels: operability, upgrade > Fix For: 3.0.0, 2.0.0-beta-1 > > Attachments: HBASE-13622.1.patch > > > I have some docs on doing a rollback of an hbase upgrade that are currently > vendor specific. polish them up, make them suitable for HBase generally, and > add them to the ref guide. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19173) Configure IntegrationTestRSGroup automatically for minicluster mode
[ https://issues.apache.org/jira/browse/HBASE-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-19173: --- Attachment: HBASE-19173.patch > Configure IntegrationTestRSGroup automatically for minicluster mode > --- > > Key: HBASE-19173 > URL: https://issues.apache.org/jira/browse/HBASE-19173 > Project: HBase > Issue Type: Bug > Components: rsgroup, test >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0 > > Attachments: HBASE-19173.patch > > > IntegrationTestRSGroup fails if run in minicluster mode. Configuration should > be handled automatically. > FAILURE! - in org.apache.hadoop.hbase.rsgroup.IntegrationTestRSGroup > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered > master coprocessor service found for name RSGroupAdminService > at > org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:702) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:64515) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2352) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:297) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:277) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19173) Configure IntegrationTestRSGroup automatically for minicluster mode
[ https://issues.apache.org/jira/browse/HBASE-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-19173: --- Status: Patch Available (was: Open) > Configure IntegrationTestRSGroup automatically for minicluster mode > --- > > Key: HBASE-19173 > URL: https://issues.apache.org/jira/browse/HBASE-19173 > Project: HBase > Issue Type: Bug > Components: rsgroup, test >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0 > > Attachments: HBASE-19173.patch > > > IntegrationTestRSGroup fails if run in minicluster mode. Configuration should > be handled automatically. > FAILURE! - in org.apache.hadoop.hbase.rsgroup.IntegrationTestRSGroup > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: > org.apache.hadoop.hbase.exceptions.UnknownProtocolException: No registered > master coprocessor service found for name RSGroupAdminService > at > org.apache.hadoop.hbase.master.MasterRpcServices.execMasterService(MasterRpcServices.java:702) > at > org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:64515) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2352) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:124) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:297) > at > org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:277) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[
https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238648#comment-16238648
]
Hadoop QA commented on HBASE-18775:
---
| (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} docker {color} | {color:red} 20m
8s{color} | {color:red} Docker failed to build yetus/hbase:5d60123. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18775 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12895996/HBASE-18775.HBASE-18477.006.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9600/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> Add a Global Read-Only property to turn off all writes for the cluster
> --
>
> Key: HBASE-18775
> URL: https://issues.apache.org/jira/browse/HBASE-18775
> Project: HBase
> Issue Type: Sub-task
> Components: master, regionserver
>Affects Versions: HBASE-18477
>Reporter: Zach York
>Assignee: Zach York
>Priority: Major
> Attachments: HBASE-18775.HBASE-18477.001.patch,
> HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch,
> HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch,
> HBASE-18775.HBASE-18477.006.patch
>
>
> As part of HBASE-18477, we need a way to turn off all modification for a
> cluster. This patch extends the read only mode used by replication to disable
> all data and metadata operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-13428) Migration to hbase-2.0.0
[ https://issues.apache.org/jira/browse/HBASE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238646#comment-16238646 ] stack commented on HBASE-13428: --- TEST: Test migrating an ACL table from hbase1 to hbase2 to ensure we can continue to read its content. > Migration to hbase-2.0.0 > > > Key: HBASE-13428 > URL: https://issues.apache.org/jira/browse/HBASE-13428 > Project: HBase > Issue Type: Umbrella > Components: migration >Reporter: stack >Priority: Blocker > Fix For: 2.0.0-beta-1 > > > Opening a 2.0 umbrella migration issue. Lets hang off this one any tools and > expectations migrating from 1.0 (or earlier) to 2.0. So far there are none > that I know of though there is an expectation in HBASE-13373 that hfiles are > at least major version 2 and minor version 3. Lets list all such > expectations, etc., here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13631) Migration from 0.94 to 2.0.0
[ https://issues.apache.org/jira/browse/HBASE-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238645#comment-16238645 ] stack commented on HBASE-13631: --- Started "DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)" on dev list to get closure on this. > Migration from 0.94 to 2.0.0 > > > Key: HBASE-13631 > URL: https://issues.apache.org/jira/browse/HBASE-13631 > Project: HBase > Issue Type: Sub-task > Components: migration >Reporter: Anoop Sam John >Priority: Blocker > Fix For: 2.0.0-beta-1 > > > We have HFile V2 (minor version-2) only in 0.94 and 2.0 needs HFile V3 with > minor version 3 atleast. We can test and document clearly the path of upgrade > from 94.x to 2.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19175) Add linklint files to gitignore
[ https://issues.apache.org/jira/browse/HBASE-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-19175: -- Status: Patch Available (was: In Progress) > Add linklint files to gitignore > --- > > Key: HBASE-19175 > URL: https://issues.apache.org/jira/browse/HBASE-19175 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel > Attachments: HBASE-19175.master.001.patch > > > When running the check-website-links scripts locally instead of Jenkins > several files and directories are created. To prevent accidental addition to > the repository they should be added to the gitignore file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (HBASE-19175) Add linklint files to gitignore
[ https://issues.apache.org/jira/browse/HBASE-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-19175 started by Jan Hentschel. - > Add linklint files to gitignore > --- > > Key: HBASE-19175 > URL: https://issues.apache.org/jira/browse/HBASE-19175 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel > Attachments: HBASE-19175.master.001.patch > > > When running the check-website-links scripts locally instead of Jenkins > several files and directories are created. To prevent accidental addition to > the repository they should be added to the gitignore file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19175) Add linklint files to gitignore
[ https://issues.apache.org/jira/browse/HBASE-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-19175: -- Attachment: HBASE-19175.master.001.patch > Add linklint files to gitignore > --- > > Key: HBASE-19175 > URL: https://issues.apache.org/jira/browse/HBASE-19175 > Project: HBase > Issue Type: Improvement >Reporter: Jan Hentschel >Assignee: Jan Hentschel > Attachments: HBASE-19175.master.001.patch > > > When running the check-website-links scripts locally instead of Jenkins > several files and directories are created. To prevent accidental addition to > the repository they should be added to the gitignore file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19175) Add linklint files to gitignore
Jan Hentschel created HBASE-19175: - Summary: Add linklint files to gitignore Key: HBASE-19175 URL: https://issues.apache.org/jira/browse/HBASE-19175 Project: HBase Issue Type: Improvement Reporter: Jan Hentschel Assignee: Jan Hentschel When running the check-website-links scripts locally instead of Jenkins several files and directories are created. To prevent accidental addition to the repository they should be added to the gitignore file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[ https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238618#comment-16238618 ] stack edited comment on HBASE-19152 at 11/4/17 12:04 AM: - 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch [~busbey] This seems to work. I tried the nightly script and seems to do right thing... was (Author: stack): [~busbey] This seems to work. I tried the nightly script and seems to do right thing... > Update refguide 'how to build an RC' and the make_rc.sh script > -- > > Key: HBASE-19152 > URL: https://issues.apache.org/jira/browse/HBASE-19152 > Project: HBase > Issue Type: Sub-task > Components: build >Reporter: stack >Assignee: stack > Fix For: 2.0.0-beta-1 > > Attachments: > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > HBASE-19152.master.001.patch, HBASE-19152.master.002.patch, > HBASE-19152.master.003.patch, HBASE-19152.master.004.patch, > HBASE-19152.master.005.patch, HBASE-19152.master.006.patch, > HBASE-19152.master.007.patch, HBASE-19152.master.008.patch > > > Update the section on how to build an RC. In particular, note that tags > should be signed and talk up the new way of building the src tgz (after a > Sean suggestion) including removal of old means src.xml from hbase-assembly. > Update the make_rc.sh script so it works for branch-2 builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script
[ https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-19152: -- Attachment: 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch [~busbey] This seems to work. I tried the nightly script and seems to do right thing... > Update refguide 'how to build an RC' and the make_rc.sh script > -- > > Key: HBASE-19152 > URL: https://issues.apache.org/jira/browse/HBASE-19152 > Project: HBase > Issue Type: Sub-task > Components: build >Reporter: stack >Assignee: stack > Fix For: 2.0.0-beta-1 > > Attachments: > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > 0001-HBASE-19152-Update-refguide-how-to-build-an-RC-and-t.patch, > HBASE-19152.master.001.patch, HBASE-19152.master.002.patch, > HBASE-19152.master.003.patch, HBASE-19152.master.004.patch, > HBASE-19152.master.005.patch, HBASE-19152.master.006.patch, > HBASE-19152.master.007.patch, HBASE-19152.master.008.patch > > > Update the section on how to build an RC. In particular, note that tags > should be signed and talk up the new way of building the src tgz (after a > Sean suggestion) including removal of old means src.xml from hbase-assembly. > Update the make_rc.sh script so it works for branch-2 builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17819) Reduce the heap overhead for BucketCache
[ https://issues.apache.org/jira/browse/HBASE-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238582#comment-16238582 ] Ted Yu commented on HBASE-17819: bq. eviction of blocks on HFile close is default off only (We have a config to turn this off). State off is mentioned twice above. Can you clarify ? > Reduce the heap overhead for BucketCache > > > Key: HBASE-17819 > URL: https://issues.apache.org/jira/browse/HBASE-17819 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-17819_V1.patch, HBASE-17819_V2.patch, > HBASE-17819_V3.patch > > > We keep Bucket entry map in BucketCache. Below is the math for heapSize for > the key , value into this map. > BlockCacheKey > --- > String hfileName - Ref - 4 > long offset - 8 > BlockType blockType - Ref - 4 > boolean isPrimaryReplicaBlock - 1 > Total = 12 (Object) + 17 = 29 > BucketEntry > > int offsetBase - 4 > int length - 4 > byte offset1 - 1 > byte deserialiserIndex - 1 > long accessCounter - 8 > BlockPriority priority - Ref - 4 > volatile boolean markedForEvict - 1 > AtomicInteger refCount - 16 + 4 > long cachedTime - 8 > Total = 12 (Object) + 51 = 63 > ConcurrentHashMap Map.Entry - 40 > blocksByHFile ConcurrentSkipListSet Entry - 40 > Total = 29 + 63 + 80 = 172 > For 10 million blocks we will end up having 1.6GB of heap size. > This jira aims to reduce this as much as possible -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19174) Update link to HBase presentations
[ https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-19174: -- Status: Patch Available (was: In Progress) > Update link to HBase presentations > -- > > Key: HBASE-19174 > URL: https://issues.apache.org/jira/browse/HBASE-19174 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Jan Hentschel >Assignee: Jan Hentschel > Attachments: HBASE-19174.master.001.patch > > > old_news.adoc references to the [Hadoop > wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past > presentations. The page itself states that it will be decommissioned in the > future. The link should go to the book instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238549#comment-16238549 ] Hudson commented on HBASE-19097: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #2022 (See [https://builds.apache.org/job/HBase-1.1-JDK8/2022/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev 51f06c742cb1c26b0fc345a1130b3849980a5c0c) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19174) Update link to HBase presentations
[ https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-19174: -- Attachment: HBASE-19174.master.001.patch > Update link to HBase presentations > -- > > Key: HBASE-19174 > URL: https://issues.apache.org/jira/browse/HBASE-19174 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Jan Hentschel >Assignee: Jan Hentschel > Attachments: HBASE-19174.master.001.patch > > > old_news.adoc references to the [Hadoop > wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past > presentations. The page itself states that it will be decommissioned in the > future. The link should go to the book instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (HBASE-19174) Update link to HBase presentations
[ https://issues.apache.org/jira/browse/HBASE-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-19174 started by Jan Hentschel. - > Update link to HBase presentations > -- > > Key: HBASE-19174 > URL: https://issues.apache.org/jira/browse/HBASE-19174 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Jan Hentschel >Assignee: Jan Hentschel > > old_news.adoc references to the [Hadoop > wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past > presentations. The page itself states that it will be decommissioned in the > future. The link should go to the book instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19174) Update link to HBase presentations
Jan Hentschel created HBASE-19174: - Summary: Update link to HBase presentations Key: HBASE-19174 URL: https://issues.apache.org/jira/browse/HBASE-19174 Project: HBase Issue Type: Improvement Components: documentation Reporter: Jan Hentschel Assignee: Jan Hentschel old_news.adoc references to the [Hadoop wiki|https://wiki.apache.org/hadoop/HBase/HBasePresentations] for past presentations. The page itself states that it will be decommissioned in the future. The link should go to the book instead. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19068) Change all url of apache.org from HTTP to HTTPS in HBase book
[ https://issues.apache.org/jira/browse/HBASE-19068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel updated HBASE-19068: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: (was: 2.0.0) 3.0.0 Status: Resolved (was: Patch Available) +1. Committed to master. [~stana] Thanks for the patch. > Change all url of apache.org from HTTP to HTTPS in HBase book > - > > Key: HBASE-19068 > URL: https://issues.apache.org/jira/browse/HBASE-19068 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Yung-An He >Assignee: Yung-An He >Priority: Major > Fix For: 3.0.0 > > Attachments: HBASE-19068-master.patch > > > We should change all the links of apache.org from HTTP to HTTPS in our hbase > book due to the security issue. Also, fix the broken link in the package > summary to org.apache.hadoop.metrics. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19097) update testing to use Apache Yetus Test Patch version 0.6.0
[ https://issues.apache.org/jira/browse/HBASE-19097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238539#comment-16238539 ] Hudson commented on HBASE-19097: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1938 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1938/]) HBASE-19097 update nightly tests to use Apache Yetus 0.6.0 (busbey: rev 51f06c742cb1c26b0fc345a1130b3849980a5c0c) * (edit) dev-support/Jenkinsfile > update testing to use Apache Yetus Test Patch version 0.6.0 > --- > > Key: HBASE-19097 > URL: https://issues.apache.org/jira/browse/HBASE-19097 > Project: HBase > Issue Type: Task > Components: build >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-1, 1.1.13 > > Attachments: HBASE-19097.0.patch > > > once Yetus does their 0.6.0 release, we should update our nightly and > precommit tests to use it. They've added diagnostic info about maven version > in use that would help troubleshoot some of our failures. > Also the 0.5.0 release removed the maven eclipse plugin tests, since that > plugin is EOL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18840) Add functionality to refresh meta table at master startup
[ https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238538#comment-16238538 ] Zach York commented on HBASE-18840: --- [~stack] I know you are pretty heads-down on the 2.x release, but can you review when you get a chance? Thanks! > Add functionality to refresh meta table at master startup > - > > Key: HBASE-18840 > URL: https://issues.apache.org/jira/browse/HBASE-18840 > Project: HBase > Issue Type: Sub-task >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18840.HBASE-18477.001.patch, > HBASE-18840.HBASE-18477.002.patch, HBASE-18840.HBASE-18477.003.patch > > > If a HBase cluster’s hbase:meta table is deleted or a cluster is started with > a new meta table, HBase needs the functionality to synchronize it’s metadata > from Storage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12125) Add Hbck option to check and fix WAL's from replication queue
[ https://issues.apache.org/jira/browse/HBASE-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated HBASE-12125: - Attachment: HBASE-12125.v4.master.patch Test was environment dependent since WAL files in the replication queue are sorted by name, which is why it was passing locally for me but failing on jenkins. Changed the test to remove that dependency. Also added some test cleanup. > Add Hbck option to check and fix WAL's from replication queue > - > > Key: HBASE-12125 > URL: https://issues.apache.org/jira/browse/HBASE-12125 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 3.0.0 >Reporter: Virag Kothari >Assignee: Vincent Poon >Priority: Major > Attachments: HBASE-12125.v1.master.patch, > HBASE-12125.v2.master.patch, HBASE-12125.v3.master.patch, > HBASE-12125.v4.master.patch > > > The replication source will discard the WAL file in many cases when it > encounters an exception reading it . This can cause data loss > and the underlying reason of failed read remains hidden. Only in certain > scenarios, the replication source should dump the current WAL and move to the > next one. > This JIRA aims to have an hbck option to check the WAL files of replication > queues for any inconsistencies and also provide an option to fix it. > The fix can be to remove the file from replication queue in zk and from the > memory of replication source manager and replication sources. > A region server endpoint call from the hbck client to region server can be > used to achieve this. > Hbck can be configured with the following options: > -softCheckReplicationWAL : Tries to open only the oldest WAL (the WAL > currently read by replication source) from replication queue. If there is a > position associated, it also seeks to that position and reads an entry from > there > -hardCheckReplicationWAL: Check all WAL paths from replication queues by > reading them completely to make sure they are ok. > -fixMissingReplicationWAL: Remove the WAL's from replication queues which are > not present on hdfs > -fixCorruptedReplicationWAL: Remove the WAL's from replication queues which > are corrupted (based on the findings from softCheck/hardCheck). Also the > WAL's are moved to a quarantine dir > -rollAndFixCorruptedReplicationWAL - If the current WAL is corrupted, it is > first rolled over and then deals with it in the same way as > -fixCorruptedReplicationWAL option -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Status: Patch Available (was: In Progress) > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Status: In Progress (was: Patch Available) > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19144) [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the cluster
[
https://issues.apache.org/jira/browse/HBASE-19144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-19144:
---
Resolution: Fixed
Hadoop Flags: Reviewed
Release Note: When regionserver placement groups (RSGroups) is active, as
servers join the cluster the Master will attempt to reassign regions in
FAILED_OPEN state.
Status: Resolved (was: Patch Available)
Pushed to branch-1.4 and up
> [RSgroups] Retry assignments in FAILED_OPEN state when servers (re)join the
> cluster
> ---
>
> Key: HBASE-19144
> URL: https://issues.apache.org/jira/browse/HBASE-19144
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.5.0
>
> Attachments: HBASE-19144-branch-1.patch, HBASE-19144-branch-1.patch,
> HBASE-19144.patch, HBASE-19144.patch, HBASE-19144.patch
>
>
> After all servers in the RSgroup are down the regions cannot be opened
> anywhere and transition rapidly into FAILED_OPEN state.
>
> 2017-10-31 21:06:25,449 INFO [ProcedureExecutor-13] master.RegionStates:
> Transition {c6c8150c9f4b8df25ba32073f25a5143 state=OFFLINE, ts=1509483985448,
> server=node-5.cluster,16020,1509482700768} to
> {c6c8150c9f4b8df25ba32073f25a5143 state=FAILED_OPEN, ts=1509483985449,
> server=node-5.cluster,16020,1509482700768}
> 2017-10-31 21:06:25,449 WARN [ProcedureExecutor-13] master.RegionStates:
> Failed to open/close d4e2f173e31ffad6aac140f4bd7b02bc on
> node-5.cluster,16020,1509482700768, set to FAILED_OPEN
>
> Any region in FAILED_OPEN state has to be manually reassigned, or the master
> can be restarted and this will also cause reattempt of assignment of any
> regions in FAILED_OPEN state. This is not unexpected but is an operational
> headache. It would be better if the RSGroupInfoManager could automatically
> kick reassignments of regions in FAILED_OPEN state when servers rejoin the
> cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18775) Add a Global Read-Only property to turn off all writes for the cluster
[ https://issues.apache.org/jira/browse/HBASE-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zach York updated HBASE-18775: -- Attachment: HBASE-18775.HBASE-18477.006.patch > Add a Global Read-Only property to turn off all writes for the cluster > -- > > Key: HBASE-18775 > URL: https://issues.apache.org/jira/browse/HBASE-18775 > Project: HBase > Issue Type: Sub-task > Components: master, regionserver >Affects Versions: HBASE-18477 >Reporter: Zach York >Assignee: Zach York >Priority: Major > Attachments: HBASE-18775.HBASE-18477.001.patch, > HBASE-18775.HBASE-18477.002.patch, HBASE-18775.HBASE-18477.003.patch, > HBASE-18775.HBASE-18477.004.patch, HBASE-18775.HBASE-18477.005.patch, > HBASE-18775.HBASE-18477.006.patch > > > As part of HBASE-18477, we need a way to turn off all modification for a > cluster. This patch extends the read only mode used by replication to disable > all data and metadata operations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
