[jira] [Updated] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18736: --- Labels: (was: incompatibleChange) > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18736: --- Hadoop Flags: Incompatible change > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18736: --- Labels: incompatibleChange (was: ) > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Labels: incompatibleChange > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18674) upgrade hbase to commons-lang3
[ https://issues.apache.org/jira/browse/HBASE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151402#comment-16151402 ] Hadoop QA commented on HBASE-18674: --- (!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://builds.apache.org/job/PreCommit-HBASE-Build/8436/console in case of problems. > upgrade hbase to commons-lang3 > -- > > Key: HBASE-18674 > URL: https://issues.apache.org/jira/browse/HBASE-18674 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0-alpha-2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18674.master.001.patch, > hbase-18674.master.002.patch, hbase-18674.master.002.patch, > hbase-18674.master.003.patch, hbase-18674.master.004.patch, > hbase-18674.master.004.patch, hbase-18674.master.005.patch, > hbase-18674.master.006.patch, hbase-18674.master.007.patch, > hbase-18674.master.008.patch > > > upgrade hbase to use commons-lang 3.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18674) upgrade hbase to commons-lang3
[ https://issues.apache.org/jira/browse/HBASE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18674: - Attachment: hbase-18674.master.008.patch Added dependencies in pom.xml based on latest build failures. > upgrade hbase to commons-lang3 > -- > > Key: HBASE-18674 > URL: https://issues.apache.org/jira/browse/HBASE-18674 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0-alpha-2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18674.master.001.patch, > hbase-18674.master.002.patch, hbase-18674.master.002.patch, > hbase-18674.master.003.patch, hbase-18674.master.004.patch, > hbase-18674.master.004.patch, hbase-18674.master.005.patch, > hbase-18674.master.006.patch, hbase-18674.master.007.patch, > hbase-18674.master.008.patch > > > upgrade hbase to use commons-lang 3.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17980) Any HRegionInfo we give out should be immutable
[ https://issues.apache.org/jira/browse/HBASE-17980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151388#comment-16151388 ] stack commented on HBASE-17980: --- That sounds good any other places.we.let out his. > Any HRegionInfo we give out should be immutable > --- > > Key: HBASE-17980 > URL: https://issues.apache.org/jira/browse/HBASE-17980 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.0.0 >Reporter: Chia-Ping Tsai >Assignee: Kuan-Po Tseng > Labels: beginner > Fix For: 2.0.0 > > > This is similar to HBASE-15583. > # Introduce RegionInfo class. HRegionInfo will extend RegionInfo. > # Deprecate HRegionInfo to be removed in 3.0 > # RegionInfo contain all of the read-only methods of HRegionInfo > # Add "RegionInfo Builder" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151385#comment-16151385
]
Hadoop QA commented on HBASE-18444:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
41s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
26s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 41s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
31s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 95m
15s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}152m 24s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:47a5614 |
| JIRA Issue | HBASE-18444 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12885038/HBASE-18444.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 15bec6230317 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / e1eb532 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/8435/testReport/ |
| modules | C: hbase-common hbase-server U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8435/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Add support for specifying custom
[jira] [Commented] (HBASE-18674) upgrade hbase to commons-lang3
[
https://issues.apache.org/jira/browse/HBASE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151355#comment-16151355
]
Hadoop QA commented on HBASE-18674:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 11m
33s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
6s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 51 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
21s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 4m
59s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source: .
hbase-resource-bundle hbase-shaded hbase-spark-it {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
57s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
12s{color} | {color:red} hbase-mapreduce in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
12s{color} | {color:red} hbase-backup in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
14s{color} | {color:red} hbase-it in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
7s{color} | {color:red} hbase-rest in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 5m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
5s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
19s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
30m 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:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-resource-bundle hbase-spark-it hbase-shaded . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 8m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
19s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
9s{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} |
[jira] [Commented] (HBASE-17980) Any HRegionInfo we give out should be immutable
[ https://issues.apache.org/jira/browse/HBASE-17980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151339#comment-16151339 ] Kuan-Po Tseng commented on HBASE-17980: --- Almost done. Now I am adding some tests. But I have a question, I am not quite sure which place should I replace HRegionInfo with ImmutableHRegionInfo. What I pretty sure is that in HBaseAdmin List getOnlineRegions(ServerName sn) this methods should return ImmutableHRegionInfo. > Any HRegionInfo we give out should be immutable > --- > > Key: HBASE-17980 > URL: https://issues.apache.org/jira/browse/HBASE-17980 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.0.0 >Reporter: Chia-Ping Tsai >Assignee: Kuan-Po Tseng > Labels: beginner > Fix For: 2.0.0 > > > This is similar to HBASE-15583. > # Introduce RegionInfo class. HRegionInfo will extend RegionInfo. > # Deprecate HRegionInfo to be removed in 3.0 > # RegionInfo contain all of the read-only methods of HRegionInfo > # Add "RegionInfo Builder" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151332#comment-16151332 ] Hudson commented on HBASE-18739: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3639 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3639/]) HBASE-18739 Make all TimeRange Constructors InterfaceAudience Private (stack: rev e1eb53296d984ea34cb5c2db5289412062b0c753) * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/io/TimeRange.java > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Jadhav updated HBASE-18444:
Attachment: HBASE-18444.master.001.patch
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
> Labels: patch
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch,
> HBASE-18444.master.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Jadhav updated HBASE-18444:
Fix Version/s: 2.0.0
Status: Patch Available (was: Open)
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 1.3.1, 2.0.0
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
> Labels: patch
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch,
> HBASE-18444.master.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151328#comment-16151328
]
Ajay Jadhav commented on HBASE-18444:
-
Attached patch for master.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
> Labels: patch
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch,
> HBASE-18444.master.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Jadhav updated HBASE-18444:
Status: Open (was: Patch Available)
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 1.3.1, 2.0.0
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch,
> HBASE-18444.master.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16060) 1.x clients cannot access table state talking to 2.0 cluster
[
https://issues.apache.org/jira/browse/HBASE-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151327#comment-16151327
]
stack commented on HBASE-16060:
---
Running 1.0.1 shell against hbase2 HEAD list works but stuff like create, while
they have desired effect, they hang up waiting on state of table to show up in
zk. Let me work on echo'ing out to zk table states so hbase1 basic admin keeps
working.
> 1.x clients cannot access table state talking to 2.0 cluster
>
>
> Key: HBASE-16060
> URL: https://issues.apache.org/jira/browse/HBASE-16060
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
>Priority: Blocker
> Fix For: 2.0.0-alpha-3
>
>
> Since table state is migrated to meta instead of zk in 2.0, 1.x clients
> talking to 2.0 cluster cannot access the table state. This causes some weird
> behavior since from a client perspective, {{Admin.isTableEnabled()}} and
> {{Admin.isTableDisabled()}} both return false.
> One option we can do is to add code in 1.x clients so that they can access
> the table state in meta if needed. Otherwise, we can mirror the table state
> in zk (while keeping meta as the source of truth) during 2.x lifecycle so
> that any 1.x client can still work correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151323#comment-16151323 ] Hudson commented on HBASE-18739: FAILURE: Integrated in Jenkins build HBase-2.0 #438 (See [https://builds.apache.org/job/HBase-2.0/438/]) HBASE-18739 Make all TimeRange Constructors InterfaceAudience Private (stack: rev 9dd458a8c79e341510cf4e983e5b88ae4e0ed8be) * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/io/TimeRange.java > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[ https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151322#comment-16151322 ] Ted Yu commented on HBASE-18652: +1 > Expose individual cache stats in a CombinedCache through JMX > > > Key: HBASE-18652 > URL: https://issues.apache.org/jira/browse/HBASE-18652 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Biju Nair >Assignee: Biju Nair > Attachments: HBASE-18652.PATCH, HBASE-18652-V1.0.PATCH, > HBASE-18652-V2.0.PATCH, HBASE-18652-WIP.PATCH > > > With offHeap cache being used to store data blocks and on-heap for index and > bloom filters, exposing the stats from the individual caches through JMX will > help understand the cache usage trend. Currently the combined cache stats is > available through JMX which may not provide insight into the individual cache > usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151319#comment-16151319
]
Hadoop QA commented on HBASE-18652:
---
| (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:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
2s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 29 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 40s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
24s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
30s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}136m
54s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
56s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}191m 24s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:47a5614 |
| JIRA Issue | HBASE-18652 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12885017/HBASE-18652-V2.0.PATCH
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 47c37542202d 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Updated] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Jadhav updated HBASE-18444:
Priority: Major (was: Minor)
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18741) Remove cancel command from backup code
Ted Yu created HBASE-18741: -- Summary: Remove cancel command from backup code Key: HBASE-18741 URL: https://issues.apache.org/jira/browse/HBASE-18741 Project: HBase Issue Type: Bug Reporter: Ted Yu After recent refactoring of backup code, cancel command is no longer applicable since there is no server procedure performing backup / restore. This issue is to remove cancel command from BackupCommands.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151285#comment-16151285
]
Ajay Jadhav commented on HBASE-18444:
-
[~yuzhih...@gmail.com]: Yes, that was intentional to separate the default meta
table name (meta) from the metaTableSuffix that user provides. The user can
have a metaTableSuffix with "_" as prefix.
I'll attach the patch for master soon.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
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=16151282#comment-16151282 ] Ajay Jadhav commented on HBASE-18477: - [~busbey]: I'll take a look at the ClusterStatus to expose this flag. > 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 > Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase > Read-Replica Clusters Scope doc.pdf, HBase Read-Replica Clusters Scope > doc_v2.docx > > > 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-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[
https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151258#comment-16151258
]
Hadoop QA commented on HBASE-18740:
---
| (x) *{color:red}-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:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 2m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 42s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}145m
49s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}204m 46s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.13.1 Server=1.13.1 Image:yetus/hbase:47a5614 |
| JIRA Issue | HBASE-18740 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12885004/HBASE-18740-master.patch
|
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux 36209156d6ff 3.13.0-117-generic #164-Ubuntu SMP Fri Apr 7
11:05:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 19bb4ef |
| Default Java | 1.8.0_144 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/8433/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8433/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Upgrade Zookeeper version in branch 1.4 and branch-1
>
>
> Key: HBASE-18740
> URL: https://issues.apache.org/jira/browse/HBASE-18740
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 1.4.0, 1.5.0
>Reporter: Jerry He
>Assignee: Jerry He
> Attachments: HBASE-18740-branch-1.patch, HBASE-18740-branch-1.patch,
> HBASE-18740-master.patch
>
>
> Branch 1.4 and branch 1 are still on Zookeeper 3.4.6.
> Branch 2 and master branch have upgraded to 3.4.9.
> There are some important fixes we'd like to have. See the linked JIRAs.
> Another critical fix is ZOOKEEPER-2146, which can be explored maliciously.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151249#comment-16151249
]
Ted Yu commented on HBASE-18444:
{code}
539 if(isValidMetaTableSuffix(metaTableSuffix)) {
540 metaTableName = DEFAULT_META_TABLE_NAME_STR + "_" +
metaTableSuffix;
{code}
isValidMetaTableSuffix() gives the impression that metaTableSuffix should be
the whole suffix.
But line 540 adds underscore.
Suggest consolidating with variable holding the whole suffix.
Please attach patch for master branch.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151240#comment-16151240
]
Ajay Jadhav commented on HBASE-18444:
-
ping [~ndimiduk] [~anoop.hbase] [~yuzhih...@gmail.com]
Can you guys take a look at the patch?
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16060) 1.x clients cannot access table state talking to 2.0 cluster
[
https://issues.apache.org/jira/browse/HBASE-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151190#comment-16151190
]
stack commented on HBASE-16060:
---
I think we need to do this suggestion of [~enis]
bq. One option we can do is to add code in 1.x clients so that they can access
the table state in meta if needed. Otherwise, we can mirror the table state in
zk (while keeping meta as the source of truth) during 2.x lifecycle so that any
1.x client can still work correctly.
Basic read-only ops like list and exists would help here.
> 1.x clients cannot access table state talking to 2.0 cluster
>
>
> Key: HBASE-16060
> URL: https://issues.apache.org/jira/browse/HBASE-16060
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
>Priority: Blocker
> Fix For: 2.0.0-alpha-3
>
>
> Since table state is migrated to meta instead of zk in 2.0, 1.x clients
> talking to 2.0 cluster cannot access the table state. This causes some weird
> behavior since from a client perspective, {{Admin.isTableEnabled()}} and
> {{Admin.isTableDisabled()}} both return false.
> One option we can do is to add code in 1.x clients so that they can access
> the table state in meta if needed. Otherwise, we can mirror the table state
> in zk (while keeping meta as the source of truth) during 2.x lifecycle so
> that any 1.x client can still work correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151180#comment-16151180
]
Hadoop QA commented on HBASE-18652:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
1s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
50s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 29 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
33m 26s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
11s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
26s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}115m 35s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
45s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}169m 6s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | Possible null pointer dereference of cacheConfig in
org.apache.hadoop.hbase.regionserver.MetricsRegionServerWrapperImpl.initBlockCache()
Dereferenced at MetricsRegionServerWrapperImpl.java:cacheConfig in
org.apache.hadoop.hbase.regionserver.MetricsRegionServerWrapperImpl.initBlockCache()
Dereferenced at MetricsRegionServerWrapperImpl.java:[line 161] |
| Failed junit tests |
hadoop.hbase.security.access.TestCoprocessorWhitelistMasterObserver |
\\
\\
||
[jira] [Commented] (HBASE-17826) Backup: submit M/R job to a particular Yarn queue
[ https://issues.apache.org/jira/browse/HBASE-17826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151178#comment-16151178 ] Hudson commented on HBASE-17826: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3638 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3638/]) HBASE-17826 Backup: submit M/R job to a particular Yarn queue - addendum (tedyu: rev 7a1c1216782d534efa409d2c5b3c1dc69b19160b) * (edit) hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/impl/BackupCommands.java > Backup: submit M/R job to a particular Yarn queue > - > > Key: HBASE-17826 > URL: https://issues.apache.org/jira/browse/HBASE-17826 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-17826-add.patch, HBASE-17826-v1.patch, > HBASE-17826-v2.patch > > > We need this to be configurable. Currently, all M/R jobs are submitted to a > default queue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18646) [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool size configurable
[ https://issues.apache.org/jira/browse/HBASE-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151179#comment-16151179 ] Hudson commented on HBASE-18646: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3638 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3638/]) HBASE-18646 [Backup] LogRollMasterProcedureManager: make procedure (tedyu: rev 19bb4ef487407cdf59a3f3c5bbef6dd8b917b682) * (edit) hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/master/LogRollMasterProcedureManager.java > [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool > size configurable > - > > Key: HBASE-18646 > URL: https://issues.apache.org/jira/browse/HBASE-18646 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-18646-v1.patch, HBASE-18646-v2.patch, > HBASE-18646-v3.patch, HBASE-18646-v4.patch > > > The default procedure timeout of 60 sec and pool size (1) may be not optimal > for large deployements -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18478) Allow users to remove RegionFinder from LoadBalancer calculations if no locality possible
[ https://issues.apache.org/jira/browse/HBASE-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151170#comment-16151170 ] Zach York commented on HBASE-18478: --- [~stack] [~apurtell] Any chance we can get traction on this? It's a fairly simple change. > Allow users to remove RegionFinder from LoadBalancer calculations if no > locality possible > - > > Key: HBASE-18478 > URL: https://issues.apache.org/jira/browse/HBASE-18478 > Project: HBase > Issue Type: Improvement > Components: Balancer >Reporter: Zach York >Assignee: Zach York > Attachments: HBASE-18478.branch-1.001.patch, > HBASE-18478.master.001.patch > > > BaseLoadBalancer should have the option to remove RegionFinder from load > balancing. This provides significant cluster start time reduction for > FileSystems that do not surface locality such as Amazon S3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16060) 1.x clients cannot access table state talking to 2.0 cluster
[
https://issues.apache.org/jira/browse/HBASE-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151159#comment-16151159
]
stack commented on HBASE-16060:
---
Given Admin will be incompatible in hbase2, looking into the suggestion by
[~enis] above that even mainline Table needs Admin internally. Searching, I've
turned up this list so far:
LoadIncrementalHFiles does Admin#tableExists, createTables.
Creating Snapshots.
Canary does Admin#listTables, #getTableDescriptor
ACC does listTables, isTableAvailable.
MapReduce makes use of Admin doing following admin.getClusterStatus() to
calcluate Splits. Wants to createTables too (ImportTsv)
h2. Thrift usage of Admin API
{noformat}
compact(ByteBuffer)
createTable(ByteBuffer, List)
deleteTable(ByteBuffer)
disableTable(ByteBuffer)
enableTable(ByteBuffer)
getTableNames()
majorCompact(ByteBuffer)
{noformat}
h2. REST usage of Admin API
{noformat}
RootResource
getTableList()
TableName[] tableNames = servlet.getAdmin().listTableNames();
SchemaResource
delete(UriInfo)
Admin admin = servlet.getAdmin();
update(TableSchemaModel, boolean, UriInfo)
Admin admin = servlet.getAdmin();
StorageClusterStatusResource
get(UriInfo)
ClusterStatus status = servlet.getAdmin().getClusterStatus();
StorageClusterVersionResource
get(UriInfo)
model.setVersion(servlet.getAdmin().getClusterStatus().getHBaseVersion());
TableResource
exists()
return servlet.getAdmin().tableExists(TableName.valueOf(table));
{noformat}
> 1.x clients cannot access table state talking to 2.0 cluster
>
>
> Key: HBASE-16060
> URL: https://issues.apache.org/jira/browse/HBASE-16060
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
>Priority: Blocker
> Fix For: 2.0.0-alpha-3
>
>
> Since table state is migrated to meta instead of zk in 2.0, 1.x clients
> talking to 2.0 cluster cannot access the table state. This causes some weird
> behavior since from a client perspective, {{Admin.isTableEnabled()}} and
> {{Admin.isTableDisabled()}} both return false.
> One option we can do is to add code in 1.x clients so that they can access
> the table state in meta if needed. Otherwise, we can mirror the table state
> in zk (while keeping meta as the source of truth) during 2.x lifecycle so
> that any 1.x client can still work correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[ https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair updated HBASE-18652: -- Attachment: HBASE-18652-V2.0.PATCH Updated patch to resolve the UT failure. > Expose individual cache stats in a CombinedCache through JMX > > > Key: HBASE-18652 > URL: https://issues.apache.org/jira/browse/HBASE-18652 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Biju Nair >Assignee: Biju Nair > Attachments: HBASE-18652.PATCH, HBASE-18652-V1.0.PATCH, > HBASE-18652-V2.0.PATCH, HBASE-18652-WIP.PATCH > > > With offHeap cache being used to store data blocks and on-heap for index and > bloom filters, exposing the stats from the individual caches through JMX will > help understand the cache usage trend. Currently the combined cache stats is > available through JMX which may not provide insight into the individual cache > usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17980) Any HRegionInfo we give out should be immutable
[ https://issues.apache.org/jira/browse/HBASE-17980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151107#comment-16151107 ] stack commented on HBASE-17980: --- Any luck w/ this one lads? Thanks. > Any HRegionInfo we give out should be immutable > --- > > Key: HBASE-17980 > URL: https://issues.apache.org/jira/browse/HBASE-17980 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.0.0 >Reporter: Chia-Ping Tsai >Assignee: Kuan-Po Tseng > Labels: beginner > Fix For: 2.0.0 > > > This is similar to HBASE-15583. > # Introduce RegionInfo class. HRegionInfo will extend RegionInfo. > # Deprecate HRegionInfo to be removed in 3.0 > # RegionInfo contain all of the read-only methods of HRegionInfo > # Add "RegionInfo Builder" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15762) Consider hbase-client to be shaded by default in 2.0
[ https://issues.apache.org/jira/browse/HBASE-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15762: -- Issue Type: Task (was: Sub-task) Parent: (was: HBASE-14996) > Consider hbase-client to be shaded by default in 2.0 > - > > Key: HBASE-15762 > URL: https://issues.apache.org/jira/browse/HBASE-15762 > Project: HBase > Issue Type: Task >Reporter: Enis Soztutar > Fix For: 2.0.0 > > > We have hbase-client and hbase-shaded-client for branch-1. For 2.0, I think > we should just get rid of the hbase-shaded-client and only have hbase-client > which is shaded by default. No need to have un-shaded client thus preventing > applications to shoot themselves in the foot. > One caveat though is that hbase-client is used in the server side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15762) Consider hbase-client to be shaded by default in 2.0
[ https://issues.apache.org/jira/browse/HBASE-15762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15762: -- Priority: Critical (was: Major) > Consider hbase-client to be shaded by default in 2.0 > - > > Key: HBASE-15762 > URL: https://issues.apache.org/jira/browse/HBASE-15762 > Project: HBase > Issue Type: Task >Reporter: Enis Soztutar >Priority: Critical > Fix For: 2.0.0 > > > We have hbase-client and hbase-shaded-client for branch-1. For 2.0, I think > we should just get rid of the hbase-shaded-client and only have hbase-client > which is shaded by default. No need to have un-shaded client thus preventing > applications to shoot themselves in the foot. > One caveat though is that hbase-client is used in the server side. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151067#comment-16151067 ] stack commented on HBASE-18736: --- This looks like it will cause damage but given that HTD implements TD and HCD implements CFD, if client code is recompiled against new HBase 2 Admin, it should 'work' w/o code mods. Any other opinions on this? (I'm +1) > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[
https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151066#comment-16151066
]
Hadoop QA commented on HBASE-18740:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 27m
25s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
12s{color} | {color:red} root in master failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
59s{color} | {color:green} master passed with JDK v1.8.0_144 {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
13s{color} | {color:red} root in master failed with JDK v1.7.0_151. {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m
15s{color} | {color:red} root in master failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
44s{color} | {color:green} master passed with JDK v1.8.0_144 {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
11s{color} | {color:red} root in master failed with JDK v1.7.0_151. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
9s{color} | {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
48s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
48s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
12s{color} | {color:red} root in the patch failed with JDK v1.7.0_151. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 12s{color}
| {color:red} root in the patch failed with JDK v1.7.0_151. {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m
14s{color} | {color:red} root in the patch failed. {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
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
12s{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
24s{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
37s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
48s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
0s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
12s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
23s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
35s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
48s{color} | {color:red} The patch causes 7 errors with Hadoop v2.7.1. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
19s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
11s{color} | {color:red} root in the patch failed with JDK v1.7.0_151. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 9s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} |
[jira] [Commented] (HBASE-18736) Cleanup the HTD/HCD for Admin
[
https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151065#comment-16151065
]
Hadoop QA commented on HBASE-18736:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
2s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
18s{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} mvneclipse {color} | {color:green} 0m
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
21s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 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} findbugs {color} | {color:green} 3m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
42s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}138m 44s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
54s{color} | {color:green} hbase-client-project in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
41s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}201m 46s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.security.access.TestCoprocessorWhitelistMasterObserver |
| | hadoop.hbase.tool.TestCanaryTool |
| Timed out junit tests |
org.apache.hadoop.hbase.replication.TestReplicationStateHBaseImpl |
| | org.apache.hadoop.hbase.replication.TestReplicationTableBase |
| | org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles |
| |
org.apache.hadoop.hbase.replication.regionserver.TestTableBasedReplicationSourceManagerImpl
|
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:47a5614 |
| JIRA Issue | HBASE-18736 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12884971/HBASE-18736.v0.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed small patch to master and branch-2. > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17826) Backup: submit M/R job to a particular Yarn queue
[ https://issues.apache.org/jira/browse/HBASE-17826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151054#comment-16151054 ] Hudson commented on HBASE-17826: FAILURE: Integrated in Jenkins build HBase-2.0 #437 (See [https://builds.apache.org/job/HBase-2.0/437/]) HBASE-17826 Backup: submit M/R job to a particular Yarn queue - addendum (tedyu: rev 45470e72f8e63b9cd36ed12ee88a981b13ef4d1d) * (edit) hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/impl/BackupCommands.java > Backup: submit M/R job to a particular Yarn queue > - > > Key: HBASE-17826 > URL: https://issues.apache.org/jira/browse/HBASE-17826 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-17826-add.patch, HBASE-17826-v1.patch, > HBASE-17826-v2.patch > > > We need this to be configurable. Currently, all M/R jobs are submitted to a > default queue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18646) [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool size configurable
[ https://issues.apache.org/jira/browse/HBASE-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151055#comment-16151055 ] Hudson commented on HBASE-18646: FAILURE: Integrated in Jenkins build HBase-2.0 #437 (See [https://builds.apache.org/job/HBase-2.0/437/]) HBASE-18646 [Backup] LogRollMasterProcedureManager: make procedure (tedyu: rev a253e87704b34ce12c4a17919465980ea62e2687) * (edit) hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/master/LogRollMasterProcedureManager.java > [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool > size configurable > - > > Key: HBASE-18646 > URL: https://issues.apache.org/jira/browse/HBASE-18646 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-18646-v1.patch, HBASE-18646-v2.patch, > HBASE-18646-v3.patch, HBASE-18646-v4.patch > > > The default procedure timeout of 60 sec and pool size (1) may be not optimal > for large deployements -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18723) [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity list the dependencies we exploit
[ https://issues.apache.org/jira/browse/HBASE-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151053#comment-16151053 ] Hudson commented on HBASE-18723: FAILURE: Integrated in Jenkins build HBase-2.0 #437 (See [https://builds.apache.org/job/HBase-2.0/437/]) HBASE-18723 [pom cleanup] Do a pass with dependency:analyze; remove (stack: rev 43c4bc57618e3ede14f4964704ad753c27253e61) * (edit) hbase-it/pom.xml * (edit) hbase-resource-bundle/pom.xml * (edit) hbase-thrift/pom.xml * (edit) hbase-endpoint/pom.xml * (edit) pom.xml * (edit) hbase-hadoop-compat/pom.xml * (edit) hbase-external-blockcache/pom.xml * (edit) hbase-archetypes/hbase-client-project/pom.xml * (edit) hbase-protocol-shaded/pom.xml * (edit) hbase-examples/pom.xml * (edit) hbase-rest/pom.xml * (edit) hbase-spark-it/pom.xml * (edit) hbase-metrics/pom.xml * (edit) hbase-server/pom.xml * (edit) hbase-hadoop2-compat/pom.xml * (edit) hbase-backup/pom.xml * (edit) hbase-prefix-tree/pom.xml * (edit) hbase-common/pom.xml * (edit) hbase-rsgroup/pom.xml * (edit) hbase-spark/pom.xml * (edit) hbase-procedure/pom.xml * (edit) hbase-shaded/pom.xml * (edit) hbase-replication/pom.xml * (edit) hbase-mapreduce/pom.xml * (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml * (edit) hbase-metrics-api/pom.xml * (edit) hbase-shell/pom.xml > [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity > list the dependencies we exploit > - > > Key: HBASE-18723 > URL: https://issues.apache.org/jira/browse/HBASE-18723 > Project: HBase > Issue Type: Bug > Components: pom >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18723.master.001.patch, > HBASE-18723.master.002.patch, HBASE-18723.master.003.patch > > > Do a pass over our poms. They are sloppy including unused jars and not > listing actually used dependencies. Undo 'required' dependencies like junit > and mockito; not all modules need these anymore. > This cleanup motivated by failures up on jenkins where a build step is not > finding transitive includes; explicit mention is needed (See failures in > HBASE-18674). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[
https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151049#comment-16151049
]
Hadoop QA commented on HBASE-18739:
---
| (x) *{color:red}-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:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
35s{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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
34m 38s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
17s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
7s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 45m 29s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.13.1 Server=1.13.1 Image:yetus/hbase:47a5614 |
| JIRA Issue | HBASE-18739 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12884993/HBASE-18739.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux e9352152240e 3.13.0-117-generic #164-Ubuntu SMP Fri Apr 7
11:05:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 19bb4ef |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/8430/testReport/ |
| modules | C: hbase-common U: hbase-common |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8430/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Make all TimeRange Constructors InterfaceAudience Private.
> --
>
> Key: HBASE-18739
> URL: https://issues.apache.org/jira/browse/HBASE-18739
> Project: HBase
> Issue Type: Sub-task
> Components: API
>Reporter: stack
>
[jira] [Commented] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[ https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151044#comment-16151044 ] Ted Yu commented on HBASE-18740: lgtm > Upgrade Zookeeper version in branch 1.4 and branch-1 > > > Key: HBASE-18740 > URL: https://issues.apache.org/jira/browse/HBASE-18740 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.4.0, 1.5.0 >Reporter: Jerry He >Assignee: Jerry He > Attachments: HBASE-18740-branch-1.patch, HBASE-18740-branch-1.patch, > HBASE-18740-master.patch > > > Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. > Branch 2 and master branch have upgraded to 3.4.9. > There are some important fixes we'd like to have. See the linked JIRAs. > Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[ https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-18740: - Attachment: HBASE-18740-master.patch HBASE-18740-branch-1.patch > Upgrade Zookeeper version in branch 1.4 and branch-1 > > > Key: HBASE-18740 > URL: https://issues.apache.org/jira/browse/HBASE-18740 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.4.0, 1.5.0 >Reporter: Jerry He >Assignee: Jerry He > Attachments: HBASE-18740-branch-1.patch, HBASE-18740-branch-1.patch, > HBASE-18740-master.patch > > > Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. > Branch 2 and master branch have upgraded to 3.4.9. > There are some important fixes we'd like to have. See the linked JIRAs. > Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18727) [C++] Don't link JNI/JVM stuff into libHbaseClient
[
https://issues.apache.org/jira/browse/HBASE-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-18727:
--
Attachment: hbase-18727-v2.patch
This v2 is an attempt to also remove {{-ljvm}} and the includes from the main
libHBaseClient build.
I think BUCK is not affected with this.
> [C++] Don't link JNI/JVM stuff into libHbaseClient
> --
>
> Key: HBASE-18727
> URL: https://issues.apache.org/jira/browse/HBASE-18727
> Project: HBase
> Issue Type: Sub-task
>Reporter: Scott Hunt
>Priority: Minor
> Fix For: HBASE-14850
>
> Attachments: hbase-18727-v2.patch, Makefile_HBASE_18727.patch
>
>
> It doesn't seem like we should be linking the objects from the test-util
> directory into the library, as those [I believe] are just for testing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151030#comment-16151030
]
Hadoop QA commented on HBASE-18652:
---
| (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:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
4s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 29 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 45s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
36s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
24s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
31s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}131m 11s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
52s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}186m 56s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | Possible null pointer dereference of cacheConfig in
org.apache.hadoop.hbase.regionserver.MetricsRegionServerWrapperImpl.initBlockCache()
Dereferenced at MetricsRegionServerWrapperImpl.java:cacheConfig in
org.apache.hadoop.hbase.regionserver.MetricsRegionServerWrapperImpl.initBlockCache()
Dereferenced at MetricsRegionServerWrapperImpl.java:[line 161] |
| Failed junit tests | hadoop.hbase.client.TestAsyncQuotaAdminApi |
\\
\\
|| Subsystem || Report/Notes ||
[jira] [Commented] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[ https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151008#comment-16151008 ] Ted Yu commented on HBASE-18740: How about upgrading to 3.4.10 release ? > Upgrade Zookeeper version in branch 1.4 and branch-1 > > > Key: HBASE-18740 > URL: https://issues.apache.org/jira/browse/HBASE-18740 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.4.0, 1.5.0 >Reporter: Jerry He >Assignee: Jerry He > Attachments: HBASE-18740-branch-1.patch > > > Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. > Branch 2 and master branch have upgraded to 3.4.9. > There are some important fixes we'd like to have. See the linked JIRAs. > Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18674) upgrade hbase to commons-lang3
[ https://issues.apache.org/jira/browse/HBASE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150998#comment-16150998 ] Hadoop QA commented on HBASE-18674: --- (!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://builds.apache.org/job/PreCommit-HBASE-Build/8431/console in case of problems. > upgrade hbase to commons-lang3 > -- > > Key: HBASE-18674 > URL: https://issues.apache.org/jira/browse/HBASE-18674 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0-alpha-2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18674.master.001.patch, > hbase-18674.master.002.patch, hbase-18674.master.002.patch, > hbase-18674.master.003.patch, hbase-18674.master.004.patch, > hbase-18674.master.004.patch, hbase-18674.master.005.patch, > hbase-18674.master.006.patch, hbase-18674.master.007.patch > > > upgrade hbase to use commons-lang 3.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-13740) Stop using Hadoop private interfaces
[ https://issues.apache.org/jira/browse/HBASE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13740: -- Fix Version/s: (was: 2.0.0-alpha-3) 2.0.0 > Stop using Hadoop private interfaces > > > Key: HBASE-13740 > URL: https://issues.apache.org/jira/browse/HBASE-13740 > Project: HBase > Issue Type: Umbrella >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Priority: Blocker > Fix For: 2.0.0 > > > Now that we are push downstream folks to stay off of our private interfaces, > we should provide a good example by doing the same with Hadoop. > Things to do in this umbrella > * We need a good way to check; manual inspection is untenable > * For anything where Hadoop isn't maintaining an isolated API (i.e. they > include a non-org.apache.hadoop or jvm class), we should just rip things out > * For the rest we'll need to determine if we ask for upgrading things to > LimitedPrivate(HBase) or Public -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[ https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-18740: - Affects Version/s: 1.5.0 1.4.0 Status: Patch Available (was: Open) > Upgrade Zookeeper version in branch 1.4 and branch-1 > > > Key: HBASE-18740 > URL: https://issues.apache.org/jira/browse/HBASE-18740 > Project: HBase > Issue Type: Improvement >Affects Versions: 1.4.0, 1.5.0 >Reporter: Jerry He >Assignee: Jerry He > Attachments: HBASE-18740-branch-1.patch > > > Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. > Branch 2 and master branch have upgraded to 3.4.9. > There are some important fixes we'd like to have. See the linked JIRAs. > Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13740) Stop using Hadoop private interfaces
[ https://issues.apache.org/jira/browse/HBASE-13740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150996#comment-16150996 ] stack commented on HBASE-13740: --- Moving out of alpha3. No movement. > Stop using Hadoop private interfaces > > > Key: HBASE-13740 > URL: https://issues.apache.org/jira/browse/HBASE-13740 > Project: HBase > Issue Type: Umbrella >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Priority: Blocker > Fix For: 2.0.0 > > > Now that we are push downstream folks to stay off of our private interfaces, > we should provide a good example by doing the same with Hadoop. > Things to do in this umbrella > * We need a good way to check; manual inspection is untenable > * For anything where Hadoop isn't maintaining an isolated API (i.e. they > include a non-org.apache.hadoop or jvm class), we should just rip things out > * For the rest we'll need to determine if we ask for upgrading things to > LimitedPrivate(HBase) or Public -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
[ https://issues.apache.org/jira/browse/HBASE-18740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-18740: - Attachment: HBASE-18740-branch-1.patch > Upgrade Zookeeper version in branch 1.4 and branch-1 > > > Key: HBASE-18740 > URL: https://issues.apache.org/jira/browse/HBASE-18740 > Project: HBase > Issue Type: Improvement >Reporter: Jerry He >Assignee: Jerry He > Attachments: HBASE-18740-branch-1.patch > > > Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. > Branch 2 and master branch have upgraded to 3.4.9. > There are some important fixes we'd like to have. See the linked JIRAs. > Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[ https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair updated HBASE-18652: -- Attachment: HBASE-18652-V1.0.PATCH Updated patch for review comments from [~tedyu] > Expose individual cache stats in a CombinedCache through JMX > > > Key: HBASE-18652 > URL: https://issues.apache.org/jira/browse/HBASE-18652 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Biju Nair >Assignee: Biju Nair > Attachments: HBASE-18652.PATCH, HBASE-18652-V1.0.PATCH, > HBASE-18652-WIP.PATCH > > > With offHeap cache being used to store data blocks and on-heap for index and > bloom filters, exposing the stats from the individual caches through JMX will > help understand the cache usage trend. Currently the combined cache stats is > available through JMX which may not provide insight into the individual cache > usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Release Note: All constructors have already been deprecated. This change makes them InterfaceAudience Private. > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Status: Patch Available (was: Open) > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15284) Make TimeRange constructors IA.Private and remove unused TimeRange constructors
[ https://issues.apache.org/jira/browse/HBASE-15284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150985#comment-16150985 ] stack commented on HBASE-15284: --- Moved this out. It removes constructors and changes a signature to not throw an IOE. Lets not have these changes in 2.0. I moved this issue to 3.0. Meantime, in a subtask, I took on the comments from this patch putting them at head of the TimeRange class, annotated all Constructors Private with warning that Constructor -- which has been deprecated already -- maybe removed or made private in 3.0. > Make TimeRange constructors IA.Private and remove unused TimeRange > constructors > --- > > Key: HBASE-15284 > URL: https://issues.apache.org/jira/browse/HBASE-15284 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 3.0.0 > > Attachments: hbase-15284.patch, hbase-15284.v2.patch, > hbase-15284.v3.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18674) upgrade hbase to commons-lang3
[ https://issues.apache.org/jira/browse/HBASE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18674: - Attachment: hbase-18674.master.007.patch Rebased on latest master that has patch for HBASE-18723. Lets see if we get a clean build. > upgrade hbase to commons-lang3 > -- > > Key: HBASE-18674 > URL: https://issues.apache.org/jira/browse/HBASE-18674 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0-alpha-2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0 > > Attachments: hbase-18674.master.001.patch, > hbase-18674.master.002.patch, hbase-18674.master.002.patch, > hbase-18674.master.003.patch, hbase-18674.master.004.patch, > hbase-18674.master.004.patch, hbase-18674.master.005.patch, > hbase-18674.master.006.patch, hbase-18674.master.007.patch > > > upgrade hbase to use commons-lang 3.6 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Attachment: HBASE-18739.master.001.patch > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-15284) Make TimeRange constructors IA.Private and remove unused TimeRange constructors
[ https://issues.apache.org/jira/browse/HBASE-15284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-15284: -- Fix Version/s: (was: 2.0.0-alpha-3) 3.0.0 > Make TimeRange constructors IA.Private and remove unused TimeRange > constructors > --- > > Key: HBASE-15284 > URL: https://issues.apache.org/jira/browse/HBASE-15284 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 3.0.0 > > Attachments: hbase-15284.patch, hbase-15284.v2.patch, > hbase-15284.v3.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Fix Version/s: (was: 2.0.0-alpha-3) 3.0.0 > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
[ https://issues.apache.org/jira/browse/HBASE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18739: -- Fix Version/s: (was: 3.0.0) 2.0.0-alpha-3 > Make all TimeRange Constructors InterfaceAudience Private. > -- > > Key: HBASE-18739 > URL: https://issues.apache.org/jira/browse/HBASE-18739 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18739.master.001.patch > > > Make all constructors InterfaceAudience Private. Add comments from parent > issue on how to use this class -- no construction but may be passed about > Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18740) Upgrade Zookeeper version in branch 1.4 and branch-1
Jerry He created HBASE-18740: Summary: Upgrade Zookeeper version in branch 1.4 and branch-1 Key: HBASE-18740 URL: https://issues.apache.org/jira/browse/HBASE-18740 Project: HBase Issue Type: Improvement Reporter: Jerry He Assignee: Jerry He Branch 1.4 and branch 1 are still on Zookeeper 3.4.6. Branch 2 and master branch have upgraded to 3.4.9. There are some important fixes we'd like to have. See the linked JIRAs. Another critical fix is ZOOKEEPER-2146, which can be explored maliciously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18739) Make all TimeRange Constructors InterfaceAudience Private.
stack created HBASE-18739: - Summary: Make all TimeRange Constructors InterfaceAudience Private. Key: HBASE-18739 URL: https://issues.apache.org/jira/browse/HBASE-18739 Project: HBase Issue Type: Sub-task Components: API Reporter: stack Assignee: stack Make all constructors InterfaceAudience Private. Add comments from parent issue on how to use this class -- no construction but may be passed about Client-side -- and update the deprecate note that action will happen in 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18699) Copy LoadIncrementalHFiles to another package and mark the old one as deprecated
[
https://issues.apache.org/jira/browse/HBASE-18699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150970#comment-16150970
]
Hadoop QA commented on HBASE-18699:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
23s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 27 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
52s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-spark-it . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 2m
57s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
18s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scalac {color} | {color:green} 6m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 3m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
32m 42s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-spark-it . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 4m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} scaladoc {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
20s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}118m
30s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m
17s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
30s{color} | {color:green} hbase-endpoint in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m
56s{color} | {color:green} hbase-backup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
26s{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} |
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[
https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18106:
--
Hadoop Flags: Incompatible change,Reviewed
Release Note:
Admin.listProcedures and Admin.listLocks were renamed to getProcedures and
getLocks (listProcedures was added to hbase 1.2). This change was done in an
incompatible way -- we just yanked listProcedures (Because Admin Interface is
not compatible with hbase1).
Main changes:
- ProcedureInfo and LockInfo were removed, we use JSON instead of them
- Procedure and LockedResource are their server side equivalent
- Procedure protobuf state_data became obsolate, it is only kept for
reading previously written WAL
- Procedure protobuf contains a state_message field, which stores the
internal
state messages (Any type instead of bytes)
- Procedure.serializeStateData and deserializeStateData were changed
slightly
- Procedures internal states are available on client side
- Procedures are displayed on web UI and in shell in the following jruby
format:
{ ID => '1', PARENT_ID = '-1', PARAMETERS => [ ..extra state
information.. ] }
was:
Admin.listProcedures and Admin.listLocks were renamed to getProcedures and
getLocks.
listProcedures permission has been renamed to getProcedures and getLocks
permission was introduced.
Marked as an incompat change.
> Redo ProcedureInfo and LockInfo
> ---
>
> Key: HBASE-18106
> URL: https://issues.apache.org/jira/browse/HBASE-18106
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
>Affects Versions: 2.0.0
>Reporter: stack
>Assignee: Balazs Meszaros
>Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-3
>
> Attachments: HBASE-18106.master.001.patch,
> HBASE-18106.master.002.patch, HBASE-18106.master.003.patch,
> HBASE-18106.master.004.patch, HBASE-18106.master.005.patch,
> HBASE-18106.master.006.patch, HBASE-18106.master.007.patch
>
>
> ProcedureInfo was introduced as a lowest-common-denominator POJO that could
> be used as a facade on PB Procedures. It was good for showing state of
> Procedure framework in shell and UI.
> Its a bit weird though. Its up in hbase-common rather than in Procedure and
> it can only ever show a subset of the Procedure info.
> I was thinking we could use the pb3.1 pb->JSON utility instead and emit a
> JSON String wherever we need to export a view on procedure internals.
> This issue is about exploring this possibility. Would depend on our having an
> upgraded guava (so probably depends on the 'pre-build' project).
> From ProcedureInfo and LockInfo need fixing in
> https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.kid1jzo114xw
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated HBASE-18737:
--
Attachment: HBASE-18737-WIP.PATCH
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: HBASE-18737-WIP.PATCH, RS_UI_AFTER-1.PNG,
> RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-18737 started by Biju Nair.
-
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: HBASE-18737-WIP.PATCH, RS_UI_AFTER-1.PNG,
> RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated HBASE-18737:
--
Attachment: RS_UI_AFTER-1.PNG
Thanks [~tedyu] & [~chia7712] for taking at a look. Attached is the updated UI
and a patch for review and comments.
Also if you haven't noticed, moved the Block Cache stats section which is
static data above the Tasks section which is dynamic for ease of navigation.
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: RS_UI_AFTER-1.PNG, RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-18507) [C++] Support for MultiPuts in AsyncBatchRpcRetryingCaller class
[ https://issues.apache.org/jira/browse/HBASE-18507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-18507. --- Resolution: Fixed Fix Version/s: HBASE-14850 Thanks Sudeep. I have committed the code after running the tests. We can address the only remaining review item in a follow up jira. > [C++] Support for MultiPuts in AsyncBatchRpcRetryingCaller class > > > Key: HBASE-18507 > URL: https://issues.apache.org/jira/browse/HBASE-18507 > Project: HBase > Issue Type: Sub-task >Reporter: Sudeep Sunthankar >Assignee: Sudeep Sunthankar > Fix For: HBASE-14850 > > Attachments: HBASE-18507.HBASE-14850.v1.patch, > HBASE-18507.HBASE-14850.v2.patch, HBASE-18507.HBASE-14850.v3.patch, > HBASE-18507.HBASE-14850.v4.patch > > > We will be addressing Multi Puts changes to AsyncBatchRpcRetryingCaller class > here -- 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=16150875#comment-16150875
]
Sean Busbey commented on HBASE-18477:
-
{quote}
2 & 3. To make a cluster read-only, we added this config flag-
hbase.global.readonly.enabled=true which can be set through hbase-site.xml
This is how a user can determine if the cluster is read-only.
But apart from that, doing this programmatically involves catching the readonly
exception.
IMO I think since the client always know which cluster they are talking too,
providing a programmatic way seems unnecessary.
Let me know what is your concern here.
{quote}
I'd like to see the read-only status exposed via ClusterStatus
> 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
> Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase
> Read-Replica Clusters Scope doc.pdf, HBase Read-Replica Clusters Scope
> doc_v2.docx
>
>
> 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-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=16150874#comment-16150874 ] Sean Busbey commented on HBASE-18477: - Can someone include a pdf version of the current scope doc? > 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 > Attachments: HBase Read-Replica Clusters Scope doc.docx, HBase > Read-Replica Clusters Scope doc.pdf, HBase Read-Replica Clusters Scope > doc_v2.docx > > > 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] [Comment Edited] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150869#comment-16150869
]
Sean Busbey edited comment on HBASE-18444 at 9/1/17 5:26 PM:
-
sorry, I got a bit snowed under. Let me go take a look over at HBASE-18477 for
the up to date scope doc.
we could always start landing these things in a branch if you want a place to
keep coherent development moving forward.
was (Author: busbey):
sorry, I got a bit snowed under. Let me go take a look over at HBASE-18478 for
the up to date scope doc.
we could always start landing these things in a branch if you want a place to
keep coherent development moving forward.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150869#comment-16150869
]
Sean Busbey commented on HBASE-18444:
-
sorry, I got a bit snowed under. Let me go take a look over at HBASE-18478 for
the up to date scope doc.
we could always start landing these things in a branch if you want a place to
keep coherent development moving forward.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18646) [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool size configurable
[ https://issues.apache.org/jira/browse/HBASE-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18646: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: (was: 2.0.0) 2.0.0-alpha-3 3.0.0 Status: Resolved (was: Patch Available) > [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool > size configurable > - > > Key: HBASE-18646 > URL: https://issues.apache.org/jira/browse/HBASE-18646 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-18646-v1.patch, HBASE-18646-v2.patch, > HBASE-18646-v3.patch, HBASE-18646-v4.patch > > > The default procedure timeout of 60 sec and pool size (1) may be not optimal > for large deployements -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150838#comment-16150838
]
Zach York commented on HBASE-18444:
---
I would like to get this JIRA going again as there are more dependent changes.
I'll try to rework them, but the reworking won't make much sense and will have
to be undone afterwards.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Sub-task
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15607) Remove PB references from Admin for 2.0
[ https://issues.apache.org/jira/browse/HBASE-15607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150842#comment-16150842 ] stack commented on HBASE-15607: --- The '[DISCUSS] hbase-2.0.0 compatibility expectations' thread has been hanging out there a while now with no comment. I just made a call that hbase1 and hbase2 Admins will be incompatible (You cannot admin an hbase2 cluster with an hbase1 client). So, I think all that is left here [~ram_krish] is the planned deprecations for branch-1 (to be 'nice') and a release note. Thanks. > Remove PB references from Admin for 2.0 > --- > > Key: HBASE-15607 > URL: https://issues.apache.org/jira/browse/HBASE-15607 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan >Priority: Blocker > Fix For: 2.0.0, 1.3.0, 2.0.0-alpha-3 > > Attachments: HBASE-15607_1.patch, HBASE-15607_2.patch, > HBASE-15607_3.patch, HBASE-15607_3.patch, HBASE-15607_4.patch, > HBASE-15607_4.patch, HBASE-15607_branch-1.patch, HBASE-15607.patch > > > This is a sub-task for HBASE-15174. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18704) Upgrade hbase to commons-collections 4
[ https://issues.apache.org/jira/browse/HBASE-18704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150817#comment-16150817 ] Sean Busbey commented on HBASE-18704: - unfortunately the patch has gone stale. could you rebase it onto the current master branch? > Upgrade hbase to commons-collections 4 > -- > > Key: HBASE-18704 > URL: https://issues.apache.org/jira/browse/HBASE-18704 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0-alpha-2 >Reporter: Peter Somogyi >Assignee: Peter Somogyi > Fix For: 2.0.0 > > Attachments: HBASE-18704.master.001.patch > > > Upgrade hbase to use commons-collections 4.1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18683) Upgrade hbase to commons-math 3
[
https://issues.apache.org/jira/browse/HBASE-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150808#comment-16150808
]
Sean Busbey commented on HBASE-18683:
-
I suspect our generated LICENSE file is incomplete for commons-math3 3.6.1.
For example, in [the project LICENS.txt for derivative
works|https://github.com/apache/commons-math/blob/3.6.1-release/LICENSE.txt#L419]:
{code}
The BracketFinder (package org.apache.commons.math3.optimization.univariate)
and PowellOptimizer (package org.apache.commons.math3.optimization.general)
classes are based on the Python code in module "optimize.py" (version 0.5)
developed by Travis E. Oliphant for the SciPy library (http://www.scipy.org/)
Copyright © 2003-2009 SciPy Developers.
SciPy license
Copyright © 2001, 2002 Enthought, Inc.
All rights reserved.
Copyright © 2003-2013 SciPy Developers.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of Enthought nor the names of the SciPy Developers may
be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND
ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
{code}
This bit doesn't appear in the generated LICENSE file attached. Do we somehow
filter our the BracketFinder and PowellOptimizer classes?
> Upgrade hbase to commons-math 3
> ---
>
> Key: HBASE-18683
> URL: https://issues.apache.org/jira/browse/HBASE-18683
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0-alpha-2
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
> Fix For: 2.0.0
>
> Attachments: HBASE-18683.master.001.patch,
> HBASE-18683.master.001.patch, HBASE-18683.master.002.patch, LICENSE.txt,
> NOTICE.txt
>
>
> Upgrade hbase to use commons-math 3.6.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18724) Close stale github PRs
[ https://issues.apache.org/jira/browse/HBASE-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18724: Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) thanks for the reviews! > Close stale github PRs > -- > > Key: HBASE-18724 > URL: https://issues.apache.org/jira/browse/HBASE-18724 > Project: HBase > Issue Type: Task > Components: community >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0 > > > Time to prune again > * [#55|https://github.com/apache/hbase/pull/55] looks like an error > * [#54|https://github.com/apache/hbase/pull/54] looks like an error > * [#53|https://github.com/apache/hbase/pull/53] looks like an error > * [#48|https://github.com/apache/hbase/pull/48] looks like a dup of #49 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reassigned HBASE-18737:
--
Assignee: Biju Nair
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Assignee: Biju Nair
>Priority: Minor
> Attachments: RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150793#comment-16150793
]
Chia-Ping Tsai commented on HBASE-18737:
Could you add the unit for *cache size*?
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Priority: Minor
> Attachments: RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18699) Copy LoadIncrementalHFiles to another package and mark the old one as deprecated
[ https://issues.apache.org/jira/browse/HBASE-18699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150785#comment-16150785 ] Chia-Ping Tsai commented on HBASE-18699: +1 > Copy LoadIncrementalHFiles to another package and mark the old one as > deprecated > > > Key: HBASE-18699 > URL: https://issues.apache.org/jira/browse/HBASE-18699 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Affects Versions: 3.0.0, 2.0.0-alpha-2 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-18699.patch, HBASE-18699-v1.patch, > HBASE-18699-v2.patch, HBASE-18699-v3.patch > > > LoadIncrementalHFiles does not depend on map reduce. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18736: --- Status: Patch Available (was: Open) > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18736) Cleanup the HTD/HCD for Admin
[ https://issues.apache.org/jira/browse/HBASE-18736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18736: --- Attachment: HBASE-18736.v0.patch > Cleanup the HTD/HCD for Admin > - > > Key: HBASE-18736 > URL: https://issues.apache.org/jira/browse/HBASE-18736 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18736.v0.patch > > > see the > [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] > in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150781#comment-16150781
]
Ted Yu commented on HBASE-18737:
Looks good.
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Priority: Minor
> Attachments: RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150776#comment-16150776
]
Ted Yu commented on HBASE-18652:
Looks good overall.
{code}
+if (GLOBAL_L1_CACHE_INSTANCE != null)
+ return GLOBAL_L1_CACHE_INSTANCE.getStats();
{code}
Either wrap the return in curly braces or move it to the same line as if.
> Expose individual cache stats in a CombinedCache through JMX
>
>
> Key: HBASE-18652
> URL: https://issues.apache.org/jira/browse/HBASE-18652
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Reporter: Biju Nair
>Assignee: Biju Nair
> Attachments: HBASE-18652.PATCH, HBASE-18652-WIP.PATCH
>
>
> With offHeap cache being used to store data blocks and on-heap for index and
> bloom filters, exposing the stats from the individual caches through JMX will
> help understand the cache usage trend. Currently the combined cache stats is
> available through JMX which may not provide insight into the individual cache
> usage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18738) Ride over HDFS 'safe mode' post-launch
stack created HBASE-18738: - Summary: Ride over HDFS 'safe mode' post-launch Key: HBASE-18738 URL: https://issues.apache.org/jira/browse/HBASE-18738 Project: HBase Issue Type: Bug Reporter: stack A coworker has an integration test that includes setting HDFS into 'safe mode' post-launch of the cluster. He finds that HBase just falls over. We should do better. We should be able to recognize the switch and going into stasis recovering once 'safe mode' has expired. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[ https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair updated HBASE-18652: -- Attachment: HBASE-18652.PATCH Attaching patch for master. > Expose individual cache stats in a CombinedCache through JMX > > > Key: HBASE-18652 > URL: https://issues.apache.org/jira/browse/HBASE-18652 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Biju Nair >Assignee: Biju Nair > Attachments: HBASE-18652.PATCH, HBASE-18652-WIP.PATCH > > > With offHeap cache being used to store data blocks and on-heap for index and > bloom filters, exposing the stats from the individual caches through JMX will > help understand the cache usage trend. Currently the combined cache stats is > available through JMX which may not provide insight into the individual cache > usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18652) Expose individual cache stats in a CombinedCache through JMX
[ https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair updated HBASE-18652: -- Status: Patch Available (was: In Progress) > Expose individual cache stats in a CombinedCache through JMX > > > Key: HBASE-18652 > URL: https://issues.apache.org/jira/browse/HBASE-18652 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Biju Nair >Assignee: Biju Nair > Attachments: HBASE-18652.PATCH, HBASE-18652-WIP.PATCH > > > With offHeap cache being used to store data blocks and on-heap for index and > bloom filters, exposing the stats from the individual caches through JMX will > help understand the cache usage trend. Currently the combined cache stats is > available through JMX which may not provide insight into the individual cache > usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18737) Display configured max size of memstore and cache on RS UI
Biju Nair created HBASE-18737:
-
Summary: Display configured max size of memstore and cache on RS UI
Key: HBASE-18737
URL: https://issues.apache.org/jira/browse/HBASE-18737
Project: HBase
Issue Type: Improvement
Reporter: Biju Nair
Priority: Minor
Displaying the configured size of {{memstore}} and {{cache}} will help
non-admin users understand the cluster capacity. Attached screenshot with
proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18737) Display configured max size of memstore and cache on RS UI
[
https://issues.apache.org/jira/browse/HBASE-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated HBASE-18737:
--
Attachment: RS_UI.PNG
RS_UI_AFTER.PNG
> Display configured max size of memstore and cache on RS UI
> --
>
> Key: HBASE-18737
> URL: https://issues.apache.org/jira/browse/HBASE-18737
> Project: HBase
> Issue Type: Improvement
>Reporter: Biju Nair
>Priority: Minor
> Attachments: RS_UI_AFTER.PNG, RS_UI.PNG
>
>
> Displaying the configured size of {{memstore}} and {{cache}} will help
> non-admin users understand the cluster capacity. Attached screenshot with
> proposed usability related changes and the current RS UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17826) Backup: submit M/R job to a particular Yarn queue
[ https://issues.apache.org/jira/browse/HBASE-17826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150746#comment-16150746 ] Ted Yu commented on HBASE-17826: Integrated the addendum. > Backup: submit M/R job to a particular Yarn queue > - > > Key: HBASE-17826 > URL: https://issues.apache.org/jira/browse/HBASE-17826 > Project: HBase > Issue Type: Improvement >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Labels: backup > Fix For: 3.0.0, 2.0.0-alpha-3 > > Attachments: HBASE-17826-add.patch, HBASE-17826-v1.patch, > HBASE-17826-v2.patch > > > We need this to be configurable. Currently, all M/R jobs are submitted to a > default queue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18729) [compat 1-2] The input type of Result#createCompleteResult is changed
[ https://issues.apache.org/jira/browse/HBASE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150733#comment-16150733 ] Chia-Ping Tsai commented on HBASE-18729: see HBASE-18736 > [compat 1-2] The input type of Result#createCompleteResult is changed > - > > Key: HBASE-18729 > URL: https://issues.apache.org/jira/browse/HBASE-18729 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > > HBASE-11544 introduce the Result#createCompleteResult in branch-1.1, and > HBASE-17740 changes its input type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18106) Redo ProcedureInfo and LockInfo
[
https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150724#comment-16150724
]
Hadoop QA commented on HBASE-18106:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 26 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
22s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
46s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
19s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
25s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
15s{color} | {color:red} The patch generated 164 new + 331 unchanged - 67 fixed
= 495 total (was 398) {color} |
| {color:red}-1{color} | {color:red} ruby-lint {color} | {color:red} 0m
7s{color} | {color:red} The patch generated 79 new + 755 unchanged - 80 fixed =
834 total (was 835) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
40m 34s{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}
2m 32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 9m
1s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
22s{color} | {color:red} hbase-client generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
38s{color} | {color:red} hbase-server generated 3 new + 0 unchanged - 0 fixed =
3 total (was 0) {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} 2m
36s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
39s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
26s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}121m
49s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} |
[jira] [Created] (HBASE-18736) Cleanup the HTD/HCD for Admin
Chia-Ping Tsai created HBASE-18736: -- Summary: Cleanup the HTD/HCD for Admin Key: HBASE-18736 URL: https://issues.apache.org/jira/browse/HBASE-18736 Project: HBase Issue Type: Sub-task Reporter: Chia-Ping Tsai Assignee: Chia-Ping Tsai see the [discussion|https://issues.apache.org/jira/browse/HBASE-18729?focusedCommentId=16150675=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16150675] in HBASE-18729. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18724) Close stale github PRs
[ https://issues.apache.org/jira/browse/HBASE-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150707#comment-16150707 ] Chia-Ping Tsai commented on HBASE-18724: +1 > Close stale github PRs > -- > > Key: HBASE-18724 > URL: https://issues.apache.org/jira/browse/HBASE-18724 > Project: HBase > Issue Type: Task > Components: community >Reporter: Sean Busbey >Assignee: Sean Busbey > > Time to prune again > * [#55|https://github.com/apache/hbase/pull/55] looks like an error > * [#54|https://github.com/apache/hbase/pull/54] looks like an error > * [#53|https://github.com/apache/hbase/pull/53] looks like an error > * [#48|https://github.com/apache/hbase/pull/48] looks like a dup of #49 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18723) [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity list the dependencies we exploit
[ https://issues.apache.org/jira/browse/HBASE-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150684#comment-16150684 ] stack commented on HBASE-18723: --- Pushed to branch-2. Thanks [~Apache9] > [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity > list the dependencies we exploit > - > > Key: HBASE-18723 > URL: https://issues.apache.org/jira/browse/HBASE-18723 > Project: HBase > Issue Type: Bug > Components: pom >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18723.master.001.patch, > HBASE-18723.master.002.patch, HBASE-18723.master.003.patch > > > Do a pass over our poms. They are sloppy including unused jars and not > listing actually used dependencies. Undo 'required' dependencies like junit > and mockito; not all modules need these anymore. > This cleanup motivated by failures up on jenkins where a build step is not > finding transitive includes; explicit mention is needed (See failures in > HBASE-18674). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18729) [compat 1-2] The input type of Result#createCompleteResult is changed
[ https://issues.apache.org/jira/browse/HBASE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150675#comment-16150675 ] stack commented on HBASE-18729: --- hbase1 and hbase2 are incompatible. So much has changed (I gleaned more evidence doing this JACC exercise -- changed return types from void to Future, purge of PB from Admin interface returning POJOs instead, etc.). It is broke. So go ahead w/ cleanup I'd say. Let me update the compatibility expectation thread on dev list. > [compat 1-2] The input type of Result#createCompleteResult is changed > - > > Key: HBASE-18729 > URL: https://issues.apache.org/jira/browse/HBASE-18729 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Chia-Ping Tsai > Fix For: 2.0.0-alpha-3 > > > HBASE-11544 introduce the Result#createCompleteResult in branch-1.1, and > HBASE-17740 changes its input type. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18723) [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity list the dependencies we exploit
[ https://issues.apache.org/jira/browse/HBASE-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16150665#comment-16150665 ] stack commented on HBASE-18723: --- bq. stack No branch-2 sir? I forgot! Thanks for the kick. > [pom cleanup] Do a pass with dependency:analyze; remove unused and explicity > list the dependencies we exploit > - > > Key: HBASE-18723 > URL: https://issues.apache.org/jira/browse/HBASE-18723 > Project: HBase > Issue Type: Bug > Components: pom >Reporter: stack >Assignee: stack > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-18723.master.001.patch, > HBASE-18723.master.002.patch, HBASE-18723.master.003.patch > > > Do a pass over our poms. They are sloppy including unused jars and not > listing actually used dependencies. Undo 'required' dependencies like junit > and mockito; not all modules need these anymore. > This cleanup motivated by failures up on jenkins where a build step is not > finding transitive includes; explicit mention is needed (See failures in > HBASE-18674). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
