[jira] [Comment Edited] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078960#comment-16078960
]
Shibin Zhang edited comment on HBASE-18323 at 7/8/17 5:34 AM:
--
[~elserj] " always use CREATOR_ALL_ACL, just avoid setting the explicit
ACL for the same user"
sorry , i don't know what's your meaning in above ,how to
avoid setting ?
" we definitely need some unit test additions for this
change "
could you give me some advice? what kind of unit test for
change? some logic maybe confused me.
was (Author: zhangshibin):
[~elserj] " always use CREATOR_ALL_ACL, just avoid setting the explicit
ACL for the same user"
sorry , i don't know what's your meaning in above ,how to avoid
setting ?
" we definitely need some unit test additions for this
change "
could you give me some advice? what kind of unit test for change?
some logic maybe confused me.
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078960#comment-16078960
]
Shibin Zhang commented on HBASE-18323:
--
[~elserj] " always use CREATOR_ALL_ACL, just avoid setting the explicit
ACL for the same user"
sorry , i don't know what's your meaning in above ,how to avoid
setting ?
" we definitely need some unit test additions for this
change "
could you give me some advice? what kind of unit test for change?
some logic maybe confused to me.
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078960#comment-16078960
]
Shibin Zhang edited comment on HBASE-18323 at 7/8/17 5:33 AM:
--
[~elserj] " always use CREATOR_ALL_ACL, just avoid setting the explicit
ACL for the same user"
sorry , i don't know what's your meaning in above ,how to avoid
setting ?
" we definitely need some unit test additions for this
change "
could you give me some advice? what kind of unit test for change?
some logic maybe confused me.
was (Author: zhangshibin):
[~elserj] " always use CREATOR_ALL_ACL, just avoid setting the explicit
ACL for the same user"
sorry , i don't know what's your meaning in above ,how to avoid
setting ?
" we definitely need some unit test additions for this
change "
could you give me some advice? what kind of unit test for change?
some logic maybe confused to me.
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18335) clean up configuration guide
[ https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078946#comment-16078946 ] Hudson commented on HBASE-18335: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3335 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3335/]) HBASE-18335 configuration guide fixes (tedyu: rev 48d28c7a248d0f8c19b18c20d4484864ac67b549) * (edit) src/main/asciidoc/_chapters/configuration.adoc * (edit) src/main/asciidoc/_chapters/hbase-default.adoc > clean up configuration guide > > > Key: HBASE-18335 > URL: https://issues.apache.org/jira/browse/HBASE-18335 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18335-0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17705) Procedure execution must fail fast if procedure is not registered
[ https://issues.apache.org/jira/browse/HBASE-17705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078935#comment-16078935 ] Vladimir Rodionov commented on HBASE-17705: --- These test failures are not related to the patch. I think patch is ready. > Procedure execution must fail fast if procedure is not registered > - > > Key: HBASE-17705 > URL: https://issues.apache.org/jira/browse/HBASE-17705 > Project: HBase > Issue Type: Bug >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-17705.v2.patch, HBASE-17705.v3.patch > > > The issue was discovered during backup testing and described here: > https://issues.apache.org/jira/browse/HBASE-14123?focusedCommentId=15886712=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15886712 > If procedure is not registered, client will be retrying until max attempts > reached. The Master should throw DoNotRetryIOException and client RPC should > handle this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18316) Implement async admin operations for draining region servers
[ https://issues.apache.org/jira/browse/HBASE-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18316: --- Attachment: HBASE-18316.master.001.patch > Implement async admin operations for draining region servers > > > Key: HBASE-18316 > URL: https://issues.apache.org/jira/browse/HBASE-18316 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-18316.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18316) Implement async admin operations for draining region servers
[ https://issues.apache.org/jira/browse/HBASE-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18316: --- Status: Patch Available (was: Open) > Implement async admin operations for draining region servers > > > Key: HBASE-18316 > URL: https://issues.apache.org/jira/browse/HBASE-18316 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > Attachments: HBASE-18316.master.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18339) Update test-patch to use hadoop 3.0.0-alpha4
[ https://issues.apache.org/jira/browse/HBASE-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18339: Issue Type: Improvement (was: Bug) > Update test-patch to use hadoop 3.0.0-alpha4 > > > Key: HBASE-18339 > URL: https://issues.apache.org/jira/browse/HBASE-18339 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: Mike Drob >Assignee: Mike Drob > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18339) Update test-patch to use hadoop 3.0.0-alpha4
[ https://issues.apache.org/jira/browse/HBASE-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18339: Component/s: test > Update test-patch to use hadoop 3.0.0-alpha4 > > > Key: HBASE-18339 > URL: https://issues.apache.org/jira/browse/HBASE-18339 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: Mike Drob >Assignee: Mike Drob > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18327) redo test-patch personality 'hadoopcheck' to better account for feature branches
[
https://issues.apache.org/jira/browse/HBASE-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-18327:
Resolution: Fixed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
> redo test-patch personality 'hadoopcheck' to better account for feature
> branches
>
>
> Key: HBASE-18327
> URL: https://issues.apache.org/jira/browse/HBASE-18327
> Project: HBase
> Issue Type: Improvement
> Components: build, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-18327.0.patch, HBASE-18327.1.patch,
> HBASE-18327.2.patch
>
>
> right now our 'which hadoop checks do we need' check looks like this:
> {code}
> if [[ "${PATCH_BRANCH}" = "master" ]]; then
> hbase_hadoop2_versions=${HBASE_MASTER_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_MASTER_HADOOP3_VERSIONS}
> elif [[ ${PATCH_BRANCH} = branch-2* ]]; then
> hbase_hadoop2_versions=${HBASE_BRANCH2_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_BRANCH2_HADOOP3_VERSIONS}
> else
> hbase_hadoop2_versions=${HBASE_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_HADOOP3_VERSIONS}
> fi
> {code}
> the check is basically "if master do this, if like branch-2 do that,
> otherwise behave like branch-1".
> we often have feature branches that thus end up being treated like branch-1,
> even though those branches should all be based off of master. (since we
> follow a master-first development approach.)
> we should redo this check so it's "if branch-1 do this, if branch-2 do that,
> otherwise behave like master"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[
https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078923#comment-16078923
]
Hadoop QA commented on HBASE-16148:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 31m
35s{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 22 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 2m
56s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
3s{color} | {color:red} hbase-common in master has 2 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
45s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 5m
35s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
54s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
30s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
62m 35s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 9m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
10s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
15s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}308m 22s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}459m 3s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.replication.multiwal.TestReplicationEndpointWithMultipleWAL |
| | hadoop.hbase.quotas.TestSnapshotQuotaObserverChore |
| | hadoop.hbase.client.TestMobSnapshotCloneIndependence |
| | hadoop.hbase.client.TestBlockEvictionFromClient |
| | hadoop.hbase.regionserver.TestPerColumnFamilyFlush |
| | hadoop.hbase.coprocessor.TestRegionObserverInterface |
| | hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce
[jira] [Updated] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18317: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master and branch-2. Thanks [~Apache9] for reviewing. > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch, HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078919#comment-16078919 ] Guanghao Zhang commented on HBASE-18317: The findbugs warning is not introduced by this. Let me commit it shortly. > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch, HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[
https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078917#comment-16078917
]
Hadoop QA commented on HBASE-18317:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
9s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
52s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
17s{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
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
47s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
22s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 31s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
47s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}117m
50s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
39s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}165m 53s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18317 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12876160/HBASE-18317.master.002.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 062a133de86d 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 48d28c7 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7572/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html
|
| findbugs |
[jira] [Assigned] (HBASE-18318) Implement updateConfiguration/stopMaster/stopRegionServer/shutdown methods
[ https://issues.apache.org/jira/browse/HBASE-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-18318: -- Assignee: Guanghao Zhang > Implement updateConfiguration/stopMaster/stopRegionServer/shutdown methods > -- > > Key: HBASE-18318 > URL: https://issues.apache.org/jira/browse/HBASE-18318 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17056) Remove checked in PB generated files
[ https://issues.apache.org/jira/browse/HBASE-17056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078896#comment-16078896 ] stack commented on HBASE-17056: --- Is that in a pom [~chia7712]? Thanks. > Remove checked in PB generated files > - > > Key: HBASE-17056 > URL: https://issues.apache.org/jira/browse/HBASE-17056 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Enis Soztutar >Assignee: stack >Priority: Critical > Fix For: 2.0.0 > > Attachments: > 0002-HBASE-17056-Remove-checked-in-PB-generated-files.patch, > HBASE-17056.master.001.patch, HBASE-17056.master.002.patch, > HBASE-17056.master.003.patch > > > Now that we have the new PB maven plugin, there is no need to have the PB > files checked in to the repo. The reason we did that was to ease up developer > env setup. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16488) Starting namespace and quota services in master startup asynchronizely
[
https://issues.apache.org/jira/browse/HBASE-16488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078887#comment-16078887
]
Hadoop QA commented on HBASE-16488:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
36s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 10 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
48s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
29s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
32s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
52s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} branch-1 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
48s{color} | {color:red} hbase-server in branch-1 has 2 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
29s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
32s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{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}
14m 47s{color} | {color:green} The patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
24s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
32s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}103m 31s{color}
| {color:red} hbase-server in the patch failed. {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}132m 3s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.master.procedure.TestCreateNamespaceProcedure |
| | hadoop.hbase.regionserver.TestScannerHeartbeatMessages |
| | hadoop.hbase.security.access.TestAccessControlFilter |
| |
hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint |
| | hadoop.hbase.wal.TestWALOpenAfterDNRollingStart |
| | hadoop.hbase.master.procedure.TestCreateTableProcedure |
| | hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure |
| | hadoop.hbase.replication.regionserver.TestReplicator |
| | hadoop.hbase.master.procedure.TestDisableTableProcedure |
| |
[jira] [Commented] (HBASE-18229) create new Async Split API to embrace AM v2
[
https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078866#comment-16078866
]
Hadoop QA commented on HBASE-18229:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} rubocop {color} | {color:blue} 0m
1s{color} | {color:blue} rubocop was not available. {color} |
| {color:blue}0{color} | {color:blue} ruby-lint {color} | {color:blue} 0m
1s{color} | {color:blue} Ruby-lint 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 4 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 2m
20s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 13m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
1s{color} | {color:red} hbase-protocol-shaded in master has 27 extant Findbugs
warnings. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
45s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
27s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
1s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 13m
7s{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:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 2 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}
26m 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-alpha3. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
56s{color} | {color:green} the patch passed {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
26s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
45s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}110m 20s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 7m
15s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
[jira] [Commented] (HBASE-18340) TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4)
[ https://issues.apache.org/jira/browse/HBASE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078852#comment-16078852 ] Andrew Purtell commented on HBASE-18340: Given this level of carnage it should be straightforward to find the breaking commit and revert it - on branch-1.4 anyway. Let me come back to this next week. > TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4) > -- > > Key: HBASE-18340 > URL: https://issues.apache.org/jira/browse/HBASE-18340 > Project: HBase > Issue Type: Bug >Reporter: Andrew Purtell >Priority: Blocker > Fix For: 1.4.0, 1.5.0 > > > TestAddColumnFamilyProcedure - hanging > TestCreateNamespaceProcedure - failing > TestDeleteNamespaceProcedure - failing > TestDisableTableProcedure - hanging > TestModifyColumnFamilyProcedure - hanging > TestModifyTableProcedure - hanging > TestTruncateTableProcedure - hanging > Tests are still running so this is not a complete list of all of them, but I > think they are all going to broken. Just tried TestEnableTableProcedure and > that is hanging too. > Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< > FAILURE! - in > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) > Time elapsed: 2.053 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure.testRollbackAndDoubleExecution(TestCreateNamespaceProcedure.java:219) > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 525.635 sec - > in org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure > Running org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure > Tests run: 6, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.331 sec <<< > FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestDeleteNamespacePr > ocedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure) > Time elapsed: 3.528 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure.testRollbackAndDoubleExecution(TestDeleteNamespaceProcedure.java:198) > Tests seem to be hanging in tearDown > "main" #1 prio=5 os_prio=31 tid=0x7fcdbd806000 nid=0x1703 in > Object.wait() [0x70218000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:186) > - locked <0x000716820ae0> (a > java.util.concurrent.atomic.AtomicBoolean) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4443) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4435) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTableAsyncV2(HBaseAdmin.java:1370) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1329) > at > org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingUtility.java:1966) > at > org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure.tearDown(TestDisableTableProcedure.java:79) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18340) TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4)
[ https://issues.apache.org/jira/browse/HBASE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18340: --- Description: TestAddColumnFamilyProcedure - hanging TestCreateNamespaceProcedure - failing TestDeleteNamespaceProcedure - failing TestDisableTableProcedure - hanging TestModifyColumnFamilyProcedure - hanging TestModifyTableProcedure - hanging TestTruncateTableProcedure - hanging Tests are still running so this is not a complete list of all of them, but I think they are all going to broken. Just tried TestEnableTableProcedure and that is hanging too. Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) Time elapsed: 2.053 sec <<< FAILURE! java.lang.AssertionError: expected a running proc at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) at org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure.testRollbackAndDoubleExecution(TestCreateNamespaceProcedure.java:219) Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 525.635 sec - in org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure Running org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure Tests run: 6, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.331 sec <<< FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestDeleteNamespacePr ocedure testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure) Time elapsed: 3.528 sec <<< FAILURE! java.lang.AssertionError: expected a running proc at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) at org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure.testRollbackAndDoubleExecution(TestDeleteNamespaceProcedure.java:198) Tests seem to be hanging in tearDown "main" #1 prio=5 os_prio=31 tid=0x7fcdbd806000 nid=0x1703 in Object.wait() [0x70218000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:186) - locked <0x000716820ae0> (a java.util.concurrent.atomic.AtomicBoolean) at org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4443) at org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4435) at org.apache.hadoop.hbase.client.HBaseAdmin.disableTableAsyncV2(HBaseAdmin.java:1370) at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1329) at org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingUtility.java:1966) at org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure.tearDown(TestDisableTableProcedure.java:79) was: TestAddColumnFamilyProcedure - hanging TestCreateNamespaceProcedure - failing TestDeleteNamespaceProcedure - failing TestDisableTableProcedure - hanging TestModifyColumnFamilyProcedure - hanging TestModifyTableProcedure - hanging TestTruncateTableProcedure - hanging Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) Time elapsed: 2.053 sec <<< FAILURE! java.lang.AssertionError: expected a running proc at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) at
[jira] [Updated] (HBASE-18340) TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4)
[ https://issues.apache.org/jira/browse/HBASE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18340: --- Fix Version/s: 1.5.0 1.4.0 > TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4) > -- > > Key: HBASE-18340 > URL: https://issues.apache.org/jira/browse/HBASE-18340 > Project: HBase > Issue Type: Bug >Reporter: Andrew Purtell >Priority: Blocker > Fix For: 1.4.0, 1.5.0 > > > TestAddColumnFamilyProcedure - hanging > TestCreateNamespaceProcedure - failing > TestDeleteNamespaceProcedure - failing > TestDisableTableProcedure - hanging > TestModifyColumnFamilyProcedure - hanging > TestModifyTableProcedure - hanging > TestTruncateTableProcedure - hanging > Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< > FAILURE! - in > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) > Time elapsed: 2.053 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure.testRollbackAndDoubleExecution(TestCreateNamespaceProcedure.java:219) > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 525.635 sec - > in org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure > Running org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure > Tests run: 6, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.331 sec <<< > FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestDeleteNamespacePr > ocedure > testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure) > Time elapsed: 3.528 sec <<< FAILURE! > java.lang.AssertionError: expected a running proc > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at > org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) > at > org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) > at > org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure.testRollbackAndDoubleExecution(TestDeleteNamespaceProcedure.java:198) > Tests seem to be hanging in tearDown > "main" #1 prio=5 os_prio=31 tid=0x7fcdbd806000 nid=0x1703 in > Object.wait() [0x70218000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:186) > - locked <0x000716820ae0> (a > java.util.concurrent.atomic.AtomicBoolean) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4443) > at > org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4435) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTableAsyncV2(HBaseAdmin.java:1370) > at > org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1329) > at > org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingUtility.java:1966) > at > org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure.tearDown(TestDisableTableProcedure.java:79) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18340) TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4)
Andrew Purtell created HBASE-18340: -- Summary: TestXXXProcedure tests hanging or failing on branch-1 (branch-1.4) Key: HBASE-18340 URL: https://issues.apache.org/jira/browse/HBASE-18340 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Priority: Blocker TestAddColumnFamilyProcedure - hanging TestCreateNamespaceProcedure - failing TestDeleteNamespaceProcedure - failing TestDisableTableProcedure - hanging TestModifyColumnFamilyProcedure - hanging TestModifyTableProcedure - hanging TestTruncateTableProcedure - hanging Tests run: 7, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.63 sec <<< FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure) Time elapsed: 2.053 sec <<< FAILURE! java.lang.AssertionError: expected a running proc at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) at org.apache.hadoop.hbase.master.procedure.TestCreateNamespaceProcedure.testRollbackAndDoubleExecution(TestCreateNamespaceProcedure.java:219) Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 525.635 sec - in org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure Running org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure Tests run: 6, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 9.331 sec <<< FAILURE! - in org.apache.hadoop.hbase.master.procedure.TestDeleteNamespacePr ocedure testRollbackAndDoubleExecution(org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure) Time elapsed: 3.528 sec <<< FAILURE! java.lang.AssertionError: expected a running proc at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.apache.hadoop.hbase.procedure2.ProcedureTestingUtility.assertProcNotYetCompleted(ProcedureTestingUtility.java:204) at org.apache.hadoop.hbase.master.procedure.MasterProcedureTestingUtility.testRollbackAndDoubleExecution(MasterProcedureTestingUtility.java:279) at org.apache.hadoop.hbase.master.procedure.TestDeleteNamespaceProcedure.testRollbackAndDoubleExecution(TestDeleteNamespaceProcedure.java:198) Tests seem to be hanging in tearDown "main" #1 prio=5 os_prio=31 tid=0x7fcdbd806000 nid=0x1703 in Object.wait() [0x70218000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:186) - locked <0x000716820ae0> (a java.util.concurrent.atomic.AtomicBoolean) at org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4443) at org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:4435) at org.apache.hadoop.hbase.client.HBaseAdmin.disableTableAsyncV2(HBaseAdmin.java:1370) at org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:1329) at org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingUtility.java:1966) at org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure.tearDown(TestDisableTableProcedure.java:79) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18317: --- Status: Patch Available (was: Open) > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch, HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18317: --- Status: Open (was: Patch Available) > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch, HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18317: --- Attachment: HBASE-18317.master.002.patch Try to trigger hadoop QA. > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch, HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18260) Address new license dependencies from hadoop3-alpha4
[
https://issues.apache.org/jira/browse/HBASE-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078841#comment-16078841
]
Hadoop QA commented on HBASE-18260:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color: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}
28m 31s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
8s{color} | {color:green} hbase-resource-bundle in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
6s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 33m 6s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18260 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12874092/HBASE-18260.patch |
| Optional Tests | asflicense javac javadoc unit xml |
| uname | Linux d84237ef09f1 3.13.0-116-generic #163-Ubuntu SMP Fri Mar 31
14:13:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 48d28c7 |
| Default Java | 1.8.0_131 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7570/testReport/ |
| modules | C: hbase-resource-bundle U: hbase-resource-bundle |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7570/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Address new license dependencies from hadoop3-alpha4
>
>
> Key: HBASE-18260
> URL: https://issues.apache.org/jira/browse/HBASE-18260
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Reporter: Mike Drob
>Assignee: Mike Drob
> Attachments: HBASE-18260.patch
>
>
> hadoop3-alpha4 adds at least one new dependency that requires an update to
> our supplemental-models.xml
> use this jira to track the changes for after that is released.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18260) Address new license dependencies from hadoop3-alpha4
[ https://issues.apache.org/jira/browse/HBASE-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-18260: -- Status: Patch Available (was: Open) > Address new license dependencies from hadoop3-alpha4 > > > Key: HBASE-18260 > URL: https://issues.apache.org/jira/browse/HBASE-18260 > Project: HBase > Issue Type: Bug > Components: dependencies >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18260.patch > > > hadoop3-alpha4 adds at least one new dependency that requires an update to > our supplemental-models.xml > use this jira to track the changes for after that is released. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-16488) Starting namespace and quota services in master startup asynchronizely
[ https://issues.apache.org/jira/browse/HBASE-16488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang updated HBASE-16488: --- Attachment: HBASE-16488.v9-branch-1.patch > Starting namespace and quota services in master startup asynchronizely > -- > > Key: HBASE-16488 > URL: https://issues.apache.org/jira/browse/HBASE-16488 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 2.0.0, 1.3.0, 1.0.3, 1.4.0, 1.1.5, 1.2.2 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > Attachments: HBASE-16488.v1-branch-1.patch, > HBASE-16488.v1-master.patch, HBASE-16488.v2-branch-1.patch, > HBASE-16488.v2-branch-1.patch, HBASE-16488.v3-branch-1.patch, > HBASE-16488.v3-branch-1.patch, HBASE-16488.v4-branch-1.patch, > HBASE-16488.v5-branch-1.patch, HBASE-16488.v6-branch-1.patch, > HBASE-16488.v7-branch-1.patch, HBASE-16488.v8-branch-1.patch, > HBASE-16488.v9-branch-1.patch > > > From time to time, during internal IT test and from customer, we often see > master initialization failed due to namespace table region takes long time to > assign (eg. sometimes split log takes long time or hanging; or sometimes RS > is temporarily not available; sometimes due to some unknown assignment > issue). In the past, there was some proposal to improve this situation, eg. > HBASE-13556 / HBASE-14190 (Assign system tables ahead of user region > assignment) or HBASE-13557 (Special WAL handling for system tables) or > HBASE-14623 (Implement dedicated WAL for system tables). > This JIRA proposes another way to solve this master initialization fail > issue: namespace service is only used by a handful operations (eg. create > table / namespace DDL / get namespace API / some RS group DDL). Only quota > manager depends on it and quota management is off by default. Therefore, > namespace service is not really needed for master to be functional. So we > could start namespace service asynchronizely without blocking master startup. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18339) Update test-patch to use hadoop 3.0.0-alpha4
Mike Drob created HBASE-18339: - Summary: Update test-patch to use hadoop 3.0.0-alpha4 Key: HBASE-18339 URL: https://issues.apache.org/jira/browse/HBASE-18339 Project: HBase Issue Type: Bug Reporter: Mike Drob Assignee: Mike Drob -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (HBASE-16051) TestScannerHeartbeatMessages fails on some machines
[ https://issues.apache.org/jira/browse/HBASE-16051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-16051: Still seeing this in branch-1.4 testScannerHeartbeatMessages(org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages) Time elapsed: 2.237 sec <<< FAILURE! java.lang.AssertionError: Heartbeats messages are disabled, an exception should be thrown. If an exception is not thrown, the test case is not testing the importance of heartbeat messages at org.junit.Assert.fail(Assert.java:88) at org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages.testImportanceOfHeartbeats(TestScannerHeartbeatMessages.java:237) at org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages.testScannerHeartbeatMessages(TestScannerHeartbeatMessages.java:207) > TestScannerHeartbeatMessages fails on some machines > --- > > Key: HBASE-16051 > URL: https://issues.apache.org/jira/browse/HBASE-16051 > Project: HBase > Issue Type: Test > Components: test >Affects Versions: 1.3.0 >Reporter: Mikhail Antonov >Assignee: Phil Yang > Fix For: 2.0.0, 1.3.0, 1.4.0 > > Attachments: HBASE-16051-v1.patch > > > I can see below on my Linux box (reproduces consistently). It passes on OSX > laptop. > T E S T S > --- > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; > support was removed in 8.0 > Running org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 27.907 sec > <<< FAILURE! - in > org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages > testScannerHeartbeatMessages(org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages) > Time elapsed: 12.95 sec <<< FAILURE! > java.lang.AssertionError: Heartbeats messages are disabled, an exception > should be thrown. If an exception is not thrown, the test case is not > testing the importance of heartbeat messages > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages.testImportanceOfHeartbeats(TestScannerHeartbeatMessages.java:233) > at > org.apache.hadoop.hbase.regionserver.TestScannerHeartbeatMessages.testScannerHeartbeatMessages(TestScannerHeartbeatMessages.java:204) > Results : > Failed tests: > > TestScannerHeartbeatMessages.testScannerHeartbeatMessages:204->testImportanceOfHeartbeats:233 > Heartbeats messages are disabled, an exception should be thrown. If an > exception is not thrown, the test case is not testing the importance of > heartbeat messages > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078768#comment-16078768
]
Hadoop QA commented on HBASE-18337:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
35m 5s{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-alpha3. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
16s{color} | {color:green} hbase-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 43m 35s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18337 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12876139/HBASE-18337.patch |
| Optional Tests | asflicense javac javadoc unit xml compile |
| uname | Linux 10a9e2d085c5 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b0a5fa0 |
| Default Java | 1.8.0_131 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7568/testReport/ |
| modules | C: hbase-shaded U: hbase-shaded |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7568/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
>
[jira] [Commented] (HBASE-18078) [C++] Harden RPC by handling various communication abnormalities
[ https://issues.apache.org/jira/browse/HBASE-18078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078760#comment-16078760 ] Xiaobing Zhou commented on HBASE-18078: --- This ticket will not contain anything related to TestRpcServer, it will be in HBASE-18338. > [C++] Harden RPC by handling various communication abnormalities > > > Key: HBASE-18078 > URL: https://issues.apache.org/jira/browse/HBASE-18078 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18078.000.patch, HBASE-18078.001.patch, > HBASE-18078.002.patch, HBASE-18078.003.patch > > > RPC layer should handle various communication abnormalities (e.g. connection > timeout, server aborted connection, and so on). Ideally, the corresponding > exceptions should be raised and propagated through handlers of pipeline in > client. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078753#comment-16078753 ] Xiaobing Zhou commented on HBASE-18338: --- Posted v0. # simplified the implementation a lot. # added RpcTestServerHandler and RpcTestServerPipelineFactory # added test.proto and test_rpc_service.proto from Java side in order to implement server stubs like echo/ping Will add implementation of server stubs to hook protobuf engine into RpcTestServerHandler in next patch. > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18338.000.patch > > > This is a spin-off from HBASE-18078. We need RpcTestServer to simulate > various communication scenarios, e.g. timeout, connection aborted, long > running services and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-18338: -- Attachment: HBASE-18338.000.patch > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18338.000.patch > > > This is a spin-off from HBASE-18078. We need RpcTestServer to simulate > various communication scenarios, e.g. timeout, connection aborted, long > running services and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[
https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078737#comment-16078737
]
Hadoop QA commented on HBASE-16148:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 22 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
50s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{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:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
32s{color} | {color:red} hbase-common in master has 2 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
49s{color} | {color:red} hbase-client in master has 4 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
46s{color} | {color:red} hbase-server in master has 10 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s{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: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}
28m 29s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
12s{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:red}-1{color} | {color:red} unit {color} | {color:red}115m 11s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
48s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}171m 52s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAsyncClusterAdminApi |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-16148 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12876121/HBASE-16148.master.011.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 087624692c2e 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
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-18338: -- Description: This is a spin-off from HBASE-18078. We need RpcTestServer to simulate various communication scenarios, e.g. timeout, connection aborted, long running services and so on. > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > > This is a spin-off from HBASE-18078. We need RpcTestServer to simulate > various communication scenarios, e.g. timeout, connection aborted, long > running services and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17544) Expose metrics for the CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-17544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078734#comment-16078734 ] Andrew Purtell commented on HBASE-17544: [~esteban] Bump. We can do it if you're busy. > Expose metrics for the CatalogJanitor > - > > Key: HBASE-17544 > URL: https://issues.apache.org/jira/browse/HBASE-17544 > Project: HBase > Issue Type: Improvement >Reporter: Esteban Gutierrez >Assignee: Esteban Gutierrez > > Currently there is other way to know what the CatalogJanitor is doing except > in the logs. We should have better visibility of when it was the last time > the CatalogJanitor ran, how long it took to scan meta, the number of merged > and parent regions cleaned on the last run, and if in maintenance mode (see > HBASE-16008). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18338) [C++] Implement RpcTestServer
Xiaobing Zhou created HBASE-18338: - Summary: [C++] Implement RpcTestServer Key: HBASE-18338 URL: https://issues.apache.org/jira/browse/HBASE-18338 Project: HBase Issue Type: Sub-task Reporter: Xiaobing Zhou Assignee: Xiaobing Zhou -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18335) clean up configuration guide
[ https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18335: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the patch, Artem. Thanks for the review, Enis. > clean up configuration guide > > > Key: HBASE-18335 > URL: https://issues.apache.org/jira/browse/HBASE-18335 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18335-0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078720#comment-16078720
]
Mike Drob edited comment on HBASE-18337 at 7/7/17 9:27 PM:
---
i haven't had a chance to test these with crunch yet, only verified that the
signatures are removed locally. let's not push until i can get some
cross-project testing done.
was (Author: mdrob):
i haven't had a chance to test these with crunch yet, only verified that the
signatures are removed locally. let's not push until i can get some
cross-component testing done.
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
> at java.util.jar.JarVerifier.update(JarVerifier.java:228)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
> at java.util.jar.JarFile.getInputStream(JarFile.java:450)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at
> java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
> at
> org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078720#comment-16078720
]
Mike Drob commented on HBASE-18337:
---
i haven't had a chance to test these with crunch yet, only verified that the
signatures are removed locally. let's not push until i can get some
cross-component testing done.
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
> at java.util.jar.JarVerifier.update(JarVerifier.java:228)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
> at java.util.jar.JarFile.getInputStream(JarFile.java:450)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at
> java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
> at
> org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18327) redo test-patch personality 'hadoopcheck' to better account for feature branches
[
https://issues.apache.org/jira/browse/HBASE-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078703#comment-16078703
]
Sean Busbey commented on HBASE-18327:
-
(pushing in a bit, presuming the above "1"s are the result of the jira issue
that's stripping the "+" from "+1")
> redo test-patch personality 'hadoopcheck' to better account for feature
> branches
>
>
> Key: HBASE-18327
> URL: https://issues.apache.org/jira/browse/HBASE-18327
> Project: HBase
> Issue Type: Improvement
> Components: build, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Attachments: HBASE-18327.0.patch, HBASE-18327.1.patch,
> HBASE-18327.2.patch
>
>
> right now our 'which hadoop checks do we need' check looks like this:
> {code}
> if [[ "${PATCH_BRANCH}" = "master" ]]; then
> hbase_hadoop2_versions=${HBASE_MASTER_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_MASTER_HADOOP3_VERSIONS}
> elif [[ ${PATCH_BRANCH} = branch-2* ]]; then
> hbase_hadoop2_versions=${HBASE_BRANCH2_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_BRANCH2_HADOOP3_VERSIONS}
> else
> hbase_hadoop2_versions=${HBASE_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_HADOOP3_VERSIONS}
> fi
> {code}
> the check is basically "if master do this, if like branch-2 do that,
> otherwise behave like branch-1".
> we often have feature branches that thus end up being treated like branch-1,
> even though those branches should all be based off of master. (since we
> follow a master-first development approach.)
> we should redo this check so it's "if branch-1 do this, if branch-2 do that,
> otherwise behave like master"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18327) redo test-patch personality 'hadoopcheck' to better account for feature branches
[
https://issues.apache.org/jira/browse/HBASE-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078701#comment-16078701
]
Sean Busbey commented on HBASE-18327:
-
0.98 is already EOL. It's true that after this patch 0.98 checks will be
treated the same as master rather than like branch-1. Both of those are
incorrect though, so I don't think that's an issue.
> redo test-patch personality 'hadoopcheck' to better account for feature
> branches
>
>
> Key: HBASE-18327
> URL: https://issues.apache.org/jira/browse/HBASE-18327
> Project: HBase
> Issue Type: Improvement
> Components: build, test
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Minor
> Attachments: HBASE-18327.0.patch, HBASE-18327.1.patch,
> HBASE-18327.2.patch
>
>
> right now our 'which hadoop checks do we need' check looks like this:
> {code}
> if [[ "${PATCH_BRANCH}" = "master" ]]; then
> hbase_hadoop2_versions=${HBASE_MASTER_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_MASTER_HADOOP3_VERSIONS}
> elif [[ ${PATCH_BRANCH} = branch-2* ]]; then
> hbase_hadoop2_versions=${HBASE_BRANCH2_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_BRANCH2_HADOOP3_VERSIONS}
> else
> hbase_hadoop2_versions=${HBASE_HADOOP2_VERSIONS}
> hbase_hadoop3_versions=${HBASE_HADOOP3_VERSIONS}
> fi
> {code}
> the check is basically "if master do this, if like branch-2 do that,
> otherwise behave like branch-1".
> we often have feature branches that thus end up being treated like branch-1,
> even though those branches should all be based off of master. (since we
> follow a master-first development approach.)
> we should redo this check so it's "if branch-1 do this, if branch-2 do that,
> otherwise behave like master"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Status: Patch Available (was: Open) > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch, hbase-18229-master-v7.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078697#comment-16078697
]
Sean Busbey commented on HBASE-18337:
-
+1 presuming no surprises from QA.
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
> at java.util.jar.JarVerifier.update(JarVerifier.java:228)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
> at java.util.jar.JarFile.getInputStream(JarFile.java:450)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at
> java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
> at
> org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-18337:
--
Status: Patch Available (was: Open)
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
> at java.util.jar.JarVerifier.update(JarVerifier.java:228)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
> at java.util.jar.JarFile.getInputStream(JarFile.java:450)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at
> java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
> at
> org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18337) hbase-shaded-server brings in signed jars
[
https://issues.apache.org/jira/browse/HBASE-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-18337:
--
Attachment: HBASE-18337.patch
Patch to exclude signature files
> hbase-shaded-server brings in signed jars
> -
>
> Key: HBASE-18337
> URL: https://issues.apache.org/jira/browse/HBASE-18337
> Project: HBase
> Issue Type: Bug
> Components: shading
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18337.patch
>
>
> hbase-shaded-server brings in some digital signatures which causes problems
> to our friends that need to use them at least in crunch and a few other
> places as well.
> they get errors like:
> {noformat}
> java.lang.SecurityException: Invalid signature file digest for Manifest main
> attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
> at java.util.jar.JarVerifier.update(JarVerifier.java:228)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
> at java.util.jar.JarFile.getInputStream(JarFile.java:450)
> at
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
> at java.net.URL.openStream(URL.java:1045)
> at java.util.ServiceLoader.parse(ServiceLoader.java:304)
> at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
> at
> java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
> at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
> at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
> at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
> at
> org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18337) hbase-shaded-server brings in signed jars
Mike Drob created HBASE-18337:
-
Summary: hbase-shaded-server brings in signed jars
Key: HBASE-18337
URL: https://issues.apache.org/jira/browse/HBASE-18337
Project: HBase
Issue Type: Bug
Components: shading
Affects Versions: 2.0.0-alpha-1
Reporter: Mike Drob
Assignee: Mike Drob
Fix For: 2.0.0-alpha-2
hbase-shaded-server brings in some digital signatures which causes problems to
our friends that need to use them at least in crunch and a few other places as
well.
they get errors like:
{noformat}
java.lang.SecurityException: Invalid signature file digest for Manifest main
attributes
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:314)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:268)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:162)
at java.net.URL.openStream(URL.java:1045)
at java.util.ServiceLoader.parse(ServiceLoader.java:304)
at java.util.ServiceLoader.access$200(ServiceLoader.java:185)
at
java.util.ServiceLoader$LazyIterator.hasNextService(ServiceLoader.java:357)
at java.util.ServiceLoader$LazyIterator.hasNext(ServiceLoader.java:393)
at java.util.ServiceLoader$1.hasNext(ServiceLoader.java:474)
at org.apache.hadoop.fs.FileSystem.loadFileSystems(FileSystem.java:3169)
at
org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3217)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3256)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:123)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3307)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3275)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:476)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:225)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createRootDir(HBaseTestingUtility.java:1282)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1107)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1085)
at
org.apache.crunch.io.hbase.WordCountHBaseIT.setUp(WordCountHBaseIT.java:130)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18335) clean up configuration guide
[
https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078691#comment-16078691
]
Hadoop QA commented on HBASE-18335:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
11s{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} 6m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
23s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
26m 23s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha3. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
59s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}135m 34s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}179m 36s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | hadoop.hbase.coprocessor.TestRegionObserverInterface |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18335 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12876094/HBASE-18335-0.patch |
| Optional Tests | asflicense javac javadoc unit |
| uname | Linux 2d6f9db1c0a1 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / b0a5fa0 |
| Default Java | 1.8.0_131 |
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/7565/artifact/patchprocess/whitespace-eol.txt
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/7565/artifact/patchprocess/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7565/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7565/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> clean up configuration guide
>
>
> Key: HBASE-18335
> URL: https://issues.apache.org/jira/browse/HBASE-18335
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1
>Reporter: Artem Ervits
>Assignee: Artem Ervits
> Fix For: 3.0.0
>
> Attachments: HBASE-18335-0.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078604#comment-16078604 ] Alex Leblang edited comment on HBASE-18020 at 7/7/17 8:04 PM: -- I posted an updated version to rb. Thanks for the thorough review [~dspivak] was (Author: awleblang): I posted an updated version to rb. Thanks for the through review [~dspivak] > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078604#comment-16078604 ] Alex Leblang commented on HBASE-18020: -- I posted an updated version to rb. Thanks for the through review [~dspivak] > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Leblang updated HBASE-18020: - Attachment: HBASE-18020.branch-1.2.003.patch > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18260) Address new license dependencies from hadoop3-alpha4
[ https://issues.apache.org/jira/browse/HBASE-18260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078587#comment-16078587 ] Mike Drob commented on HBASE-18260: --- 3.0.0-alpha4 is live now, you should be clear to push, [~busbey] > Address new license dependencies from hadoop3-alpha4 > > > Key: HBASE-18260 > URL: https://issues.apache.org/jira/browse/HBASE-18260 > Project: HBase > Issue Type: Bug > Components: dependencies >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18260.patch > > > hadoop3-alpha4 adds at least one new dependency that requires an update to > our supplemental-models.xml > use this jira to track the changes for after that is released. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18177) FanOutOneBlockAsyncDFSOutputHelper fails to compile against Hadoop 3
[
https://issues.apache.org/jira/browse/HBASE-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078586#comment-16078586
]
Mike Drob commented on HBASE-18177:
---
Thanks for the review. hadoop 3-alpha4 is live now, tests passed against it for
me so I think you're clear to push.
{noformat}
mvn clean package -Dhadoop.profile=3.0 -Dhadoop-three.version=3.0.0-alpha4
-Dtest=TestFanOutOneBlockAsyncDFSOutput -pl hbase-server -am
{noformat}
> FanOutOneBlockAsyncDFSOutputHelper fails to compile against Hadoop 3
>
>
> Key: HBASE-18177
> URL: https://issues.apache.org/jira/browse/HBASE-18177
> Project: HBase
> Issue Type: Bug
> Components: wal
>Reporter: Esteban Gutierrez
>Assignee: Mike Drob
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18177.patch, HBASE-18177.v2.patch
>
>
> After HDFS-10996 ClientProtocol#create() needs to specify the erasure code
> policy to use. In the meantime we should add a workaround to
> FanOutOneBlockAsyncDFSOutputHelper to be able to compile against Hadoop 3 and
> Hadoop 2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Patel updated HBASE-16148: --- Attachment: HBASE-16148.master.012.patch > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.012.patch, HBASE-16148.master.6.patch, > HBASE-16148.master.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch, HBASE-16148.master.test.4.patch, > HBASE-16148.master.test.5.patch, HLC.10.1.patch, HLC.10.2.patch, > HLC.10.3.patch, HLC.10.4.patch, HLC.10.5.patch, HLC.10.6.patch, > HLC.10.7.patch, HLC.10.patch, HLC.1.patch, HLC.2.patch, HLC.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078560#comment-16078560 ] Amit Patel edited comment on HBASE-16148 at 7/7/17 7:25 PM: vv Core HLC + Undo use of master's timestamp for meta updates + Enable HLC for just meta table. Just making sure that tests pass. [^HBASE-16148.master.012.patch] was (Author: amit.patel): vv Core HLC + Undo use of master's timestamp for meta updates + Enable HLC for just meta table. Just making sure that tests pass. > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.012.patch, HBASE-16148.master.6.patch, > HBASE-16148.master.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch, HBASE-16148.master.test.4.patch, > HBASE-16148.master.test.5.patch, HLC.10.1.patch, HLC.10.2.patch, > HLC.10.3.patch, HLC.10.4.patch, HLC.10.5.patch, HLC.10.6.patch, > HLC.10.7.patch, HLC.10.patch, HLC.1.patch, HLC.2.patch, HLC.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078560#comment-16078560 ] Amit Patel commented on HBASE-16148: vv Core HLC + Undo use of master's timestamp for meta updates + Enable HLC for just meta table. Just making sure that tests pass. > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.6.patch, HBASE-16148.master.test.1.patch, > HBASE-16148.master.test.2.patch, HBASE-16148.master.test.3.patch, > HBASE-16148.master.test.4.patch, HBASE-16148.master.test.5.patch, > HLC.10.1.patch, HLC.10.2.patch, HLC.10.3.patch, HLC.10.4.patch, > HLC.10.5.patch, HLC.10.6.patch, HLC.10.7.patch, HLC.10.patch, HLC.1.patch, > HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, > HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078515#comment-16078515 ] Amit Patel edited comment on HBASE-16148 at 7/7/17 6:50 PM: v Core HLC (same as above) + Undo use of master's timestamp for meta updates. Just making sure that tests pass. [^HBASE-16148.master.011.patch] was (Author: amit.patel): v Core HLC (same as above) + Undo use of master's timestamp for meta updates. Just making sure that tests pass. > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.6.patch, HBASE-16148.master.test.1.patch, > HBASE-16148.master.test.2.patch, HBASE-16148.master.test.3.patch, > HBASE-16148.master.test.4.patch, HBASE-16148.master.test.5.patch, > HLC.10.1.patch, HLC.10.2.patch, HLC.10.3.patch, HLC.10.4.patch, > HLC.10.5.patch, HLC.10.6.patch, HLC.10.7.patch, HLC.10.patch, HLC.1.patch, > HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, > HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078515#comment-16078515 ] Amit Patel commented on HBASE-16148: v Core HLC (same as above) + Undo use of master's timestamp for meta updates. Just making sure that tests pass. > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.6.patch, HBASE-16148.master.test.1.patch, > HBASE-16148.master.test.2.patch, HBASE-16148.master.test.3.patch, > HBASE-16148.master.test.4.patch, HBASE-16148.master.test.5.patch, > HLC.10.1.patch, HLC.10.2.patch, HLC.10.3.patch, HLC.10.4.patch, > HLC.10.5.patch, HLC.10.6.patch, HLC.10.7.patch, HLC.10.patch, HLC.1.patch, > HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, > HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Patel updated HBASE-16148: --- Attachment: HBASE-16148.master.011.patch > Hybrid Logical Clocks(placeholder for running tests) > > > Key: HBASE-16148 > URL: https://issues.apache.org/jira/browse/HBASE-16148 > Project: HBase > Issue Type: Sub-task > Components: API >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: test-patch > Attachments: HBASE-16148.master.001.patch, > HBASE-16148.master.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.patch, HBASE-16148.master.005.patch, > HBASE-16148.master.006.patch, HBASE-16148.master.007.patch, > HBASE-16148.master.008.patch, HBASE-16148.master.009.patch, > HBASE-16148.master.010.patch, HBASE-16148.master.011.patch, > HBASE-16148.master.6.patch, HBASE-16148.master.test.1.patch, > HBASE-16148.master.test.2.patch, HBASE-16148.master.test.3.patch, > HBASE-16148.master.test.4.patch, HBASE-16148.master.test.5.patch, > HLC.10.1.patch, HLC.10.2.patch, HLC.10.3.patch, HLC.10.4.patch, > HLC.10.5.patch, HLC.10.6.patch, HLC.10.7.patch, HLC.10.patch, HLC.1.patch, > HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, > HLC.9.patch, HLC.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18255) Time-Delayed HBase Performance Degradation with Java 7
[ https://issues.apache.org/jira/browse/HBASE-18255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-18255: --- Release Note: This change sets the JVM property ReservedCodeCacheSize to 256MB in the provided hbase-env.sh example file. The specific value for this property attempts to prevent performance issues seen when HBase using Java 7. The value set is the same as the default when using Java8. Just added a sentence or two for the release notes. > Time-Delayed HBase Performance Degradation with Java 7 > -- > > Key: HBASE-18255 > URL: https://issues.apache.org/jira/browse/HBASE-18255 > Project: HBase > Issue Type: Bug > Components: Performance >Affects Versions: 1.3.1, 1.2.6, 1.1.11 >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov >Priority: Critical > Labels: jdk7 > Fix For: 1.4.0, 1.3.2, 1.2.7, 1.1.12 > > Attachments: HBASE-18255-branch-1.x.v1.patch > > > The good summary of the issue and provided resolution can be found in this > article: > https://community.hortonworks.com/articles/105802/time-delayed-hbase-performance-degradation-with-ja.html > In a few words, due to internal JVM 7 bug (which has been addressed only in > Java 8), HotSpot code cache can become full and after that ALL JIT > compilations get suspended indefinitely. The default value for code cache > size in JVM 7 is quite low: 48MB. It is recommended to increase this value at > least to 256MB (default in JVM 8). > This BUG affects only 1.x -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18335) clean up configuration guide
[ https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078450#comment-16078450 ] Enis Soztutar commented on HBASE-18335: --- Nice cleanup. +1. > clean up configuration guide > > > Key: HBASE-18335 > URL: https://issues.apache.org/jira/browse/HBASE-18335 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18335-0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18335) clean up configuration guide
[ https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-18335: -- Status: Patch Available (was: Open) > clean up configuration guide > > > Key: HBASE-18335 > URL: https://issues.apache.org/jira/browse/HBASE-18335 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0-alpha-1, 1.1.11, 1.2.6, 1.3.1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18335-0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18329) update links in config guide to point to java 8 references
[ https://issues.apache.org/jira/browse/HBASE-18329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078379#comment-16078379 ] Frank Welsch edited comment on HBASE-18329 at 7/7/17 5:36 PM: -- [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA could have caused the failure. I can try to troubleshoot if something is wrong in the .adoc file. There are also some additional formatting/production issues that I can attempt to fix. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? was (Author: fwelsch): [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA and the patch in HBASE-18275 are the cause--or part of the cause--of the failure reported in yesterday's Comment in HBASE-16574. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? > update links in config guide to point to java 8 references > -- > > Key: HBASE-18329 > URL: https://issues.apache.org/jira/browse/HBASE-18329 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18329.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18275) Formatting and grammar mistakes in schemadoc chapter
[ https://issues.apache.org/jira/browse/HBASE-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078390#comment-16078390 ] Frank Welsch edited comment on HBASE-18275 at 7/7/17 5:36 PM: -- [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA could have caused the failure. I can try to troubleshoot if something is wrong in the .adoc file. There are also some additional formatting/production issues that I can attempt to fix. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? was (Author: fwelsch): [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA could have caused the failure. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. There are also some additional formatting/production issues that I can attempt to fix. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? > Formatting and grammar mistakes in schemadoc chapter > > > Key: HBASE-18275 > URL: https://issues.apache.org/jira/browse/HBASE-18275 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Trivial > Labels: newbie > Fix For: 3.0.0 > > Attachments: HBASE-18275-0.patch > > > a grammatical error and formatting error in schema design doc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18275) Formatting and grammar mistakes in schemadoc chapter
[ https://issues.apache.org/jira/browse/HBASE-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078390#comment-16078390 ] Frank Welsch edited comment on HBASE-18275 at 7/7/17 5:34 PM: -- [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA could have caused the failure. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. There are also some additional formatting/production issues that I can attempt to fix. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? was (Author: fwelsch): [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA and the patch in HBASE-18329 are the cause (or part of the cause) of the failure reported in yesterday's Comment in HBASE-16574. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? > Formatting and grammar mistakes in schemadoc chapter > > > Key: HBASE-18275 > URL: https://issues.apache.org/jira/browse/HBASE-18275 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Trivial > Labels: newbie > Fix For: 3.0.0 > > Attachments: HBASE-18275-0.patch > > > a grammatical error and formatting error in schema design doc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18329) update links in config guide to point to java 8 references
[ https://issues.apache.org/jira/browse/HBASE-18329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078391#comment-16078391 ] Ted Yu commented on HBASE-18329: There hasn't been test run for HBASE-16574 recently. Which test failure are you referring to ? > update links in config guide to point to java 8 references > -- > > Key: HBASE-18329 > URL: https://issues.apache.org/jira/browse/HBASE-18329 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18329.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18295) The result contains the cells across different rows
[ https://issues.apache.org/jira/browse/HBASE-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18295: --- Status: Patch Available (was: Open) > The result contains the cells across different rows > > > Key: HBASE-18295 > URL: https://issues.apache.org/jira/browse/HBASE-18295 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Fix For: 3.0.0, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.branch-1.v1.patch, > HBASE-18295.branch-1.v1.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch, > HBASE-18295.v2.patch, HBASE-18295.v2.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18295) The result contains the cells across different rows
[ https://issues.apache.org/jira/browse/HBASE-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18295: --- Status: Open (was: Patch Available) > The result contains the cells across different rows > > > Key: HBASE-18295 > URL: https://issues.apache.org/jira/browse/HBASE-18295 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Fix For: 3.0.0, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.branch-1.v1.patch, > HBASE-18295.branch-1.v1.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch, > HBASE-18295.v2.patch, HBASE-18295.v2.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18295) The result contains the cells across different rows
[ https://issues.apache.org/jira/browse/HBASE-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18295: --- Attachment: HBASE-18295.branch-1.v1.patch > The result contains the cells across different rows > > > Key: HBASE-18295 > URL: https://issues.apache.org/jira/browse/HBASE-18295 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Blocker > Fix For: 3.0.0, 1.4.0, 1.3.2, 2.0.0-alpha-2 > > Attachments: HBASE-18295.branch-1.3.v0.patch, > HBASE-18295.branch-1.v0.patch, HBASE-18295.branch-1.v1.patch, > HBASE-18295.branch-1.v1.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch, > HBASE-18295.v2.patch, HBASE-18295.v2.patch > > > From the [flaky > dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html] > If we use the cell which won't be flushed into disk as the top cell to reopen > the scanners, the new top cell will change. If the new top cell is in > different row, the matcher will reset, and then matcher will accept the new > top cell... > The TestStore# testFlushBeforeCompletingScan reproduces the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18275) Formatting and grammar mistakes in schemadoc chapter
[ https://issues.apache.org/jira/browse/HBASE-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078390#comment-16078390 ] Frank Welsch commented on HBASE-18275: -- [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA and the patch in HBASE-18329 are the cause (or part of the cause) of the failure reported in yesterday's Comment in HBASE-16574. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? > Formatting and grammar mistakes in schemadoc chapter > > > Key: HBASE-18275 > URL: https://issues.apache.org/jira/browse/HBASE-18275 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits >Priority: Trivial > Labels: newbie > Fix For: 3.0.0 > > Attachments: HBASE-18275-0.patch > > > a grammatical error and formatting error in schema design doc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18329) update links in config guide to point to java 8 references
[ https://issues.apache.org/jira/browse/HBASE-18329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078379#comment-16078379 ] Frank Welsch commented on HBASE-18329: -- [~dbist13] [~te...@apache.org] See the comment above about FAILURE. It seems like the patch in this JIRA and the patch in HBASE-18275 are the cause--or part of the cause--of the failure reported in yesterday's Comment in HBASE-16574. I can try to troubleshoot if something is wrong in the .adoc files for the 2 issues. In the meantime, shouldn't the STATUS of this JIRA be changed to REOPENED? > update links in config guide to point to java 8 references > -- > > Key: HBASE-18329 > URL: https://issues.apache.org/jira/browse/HBASE-18329 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18329.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078324#comment-16078324 ] Yi Liang edited comment on HBASE-18229 at 7/7/17 4:53 PM: -- retry with v7, v6 is stale was (Author: easyliangjob): retry one more time > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch, hbase-18229-master-v7.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: hbase-18229-master-v7.patch > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch, hbase-18229-master-v7.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: (was: hbase-18229-master-v7.patch) > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: hbase-18229-master-v7.patch > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Status: Open (was: Patch Available) > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: (was: hbase-18229-master-v6.patch) > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: hbase-18229-master-v6.patch retry one more time > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch, hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18229) create new Async Split API to embrace AM v2
[ https://issues.apache.org/jira/browse/HBASE-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Liang updated HBASE-18229: - Attachment: (was: hbase-18229-master-v6.patch) > create new Async Split API to embrace AM v2 > --- > > Key: HBASE-18229 > URL: https://issues.apache.org/jira/browse/HBASE-18229 > Project: HBase > Issue Type: Sub-task > Components: proc-v2 >Reporter: Yi Liang >Assignee: Yi Liang >Priority: Critical > Fix For: 2.0.0-alpha-2 > > Attachments: HBase-18229-master-v1.patch, > hbase-18229-master-v2.patch, HBASE-18229-master-v3.patch, > hbase-18229-master-v4.patch, hbase-18229-master-v5.patch, > hbase-18229-master-v6.patch > > > See HBASE-18105 for related information, this jira will change the logic of > Path 1 in splitProcedure, the execution path will be: > *HBaseAdmin.splitRegionAsync -> MasterKeepAliveConnection.splitRegion -> > MasterRpcServices.splitRegion -> HMaster.splitRegion-> > AssignmentManager.submitProcedure* > Master Will no longer ask Rs and then Rs turn around to ask master to do the > split operation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18061) [C++] Fix retry logic in multi-get calls
[ https://issues.apache.org/jira/browse/HBASE-18061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudeep Sunthankar updated HBASE-18061: -- Attachment: HBASE-18061.HBASE-14850.v5.patch V5 patch addresses the below points:- # Mocks for AsyncRpcBatchRetryingCaller class. Have run the tests for 20 reps without any issues. # Fixed a bug where we were getting deadlock issued in AsyncRpcBatchRetryingCaller. # Changed number of region servers for mini-cluster in core/client-test.cc to 2 and Gets size increased to 20K. It was increased because of incorrect behavior with requests >= 10K. the mini-cluster was freezing intermittently because of the issue mentioned above. # Fixed bug with incorrect handling of ActionsByServer map in AsyncRpcBatchRetryingCaller for tables with split regions. Added unit-tests as well for the same in core/client-test.cc Thanks. > [C++] Fix retry logic in multi-get calls > > > Key: HBASE-18061 > URL: https://issues.apache.org/jira/browse/HBASE-18061 > Project: HBase > Issue Type: Sub-task >Reporter: Enis Soztutar >Assignee: Sudeep Sunthankar > Fix For: HBASE-14850 > > Attachments: HBASE-18061.HBASE-14850.v1.patch, > HBASE-18061.HBASE-14850.v3.patch, HBASE-18061.HBASE-14850.v5.patch > > > HBASE-17576 adds multi-gets. There are a couple of todos to fix in the retry > logic, and some unit testing to be done for the multi-gets. We'll do these in > this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18335) clean up configuration guide
[ https://issues.apache.org/jira/browse/HBASE-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Ervits updated HBASE-18335: - Attachment: HBASE-18335-0.patch > clean up configuration guide > > > Key: HBASE-18335 > URL: https://issues.apache.org/jira/browse/HBASE-18335 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1 >Reporter: Artem Ervits >Assignee: Artem Ervits > Fix For: 3.0.0 > > Attachments: HBASE-18335-0.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078179#comment-16078179
]
Josh Elser commented on HBASE-18323:
I still think that's the wrong way to do it -- again, semantically, it doesn't
make sense for the reason I stated above (please ask if my explanation is not
clear to you).
Functionally, yes the end result is the same. If you leave a comment as to why
you have changed this logic in this manner, I may be swayed to doing it the way
you want to.
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18336) Operations on Table reference's does not work in hbase-shell as per help messages/documentation
Abhishek Kumar created HBASE-18336: -- Summary: Operations on Table reference's does not work in hbase-shell as per help messages/documentation Key: HBASE-18336 URL: https://issues.apache.org/jira/browse/HBASE-18336 Project: HBase Issue Type: Bug Components: documentation, shell Reporter: Abhishek Kumar Priority: Trivial Many shell command's help messages suggest that table references in shell can be kept for method calls, but it does not seem to be working. It looks like that its done on purpose (HBASE-15965) for shell 'interactive' mode, may be we can update shell command's help messages/documentation to reflect that it can work only in 'non-interactive' mode. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078074#comment-16078074 ] Duo Zhang commented on HBASE-18317: --- +1. > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18317) Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor
[ https://issues.apache.org/jira/browse/HBASE-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-18317: --- Attachment: HBASE-18317.master.002.patch > Implement async admin operations for Normalizer/CleanerChore/CatalogJanitor > --- > > Key: HBASE-18317 > URL: https://issues.apache.org/jira/browse/HBASE-18317 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18317.master.001.patch, > HBASE-18317.master.002.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18335) clean up configuration guide
Artem Ervits created HBASE-18335: Summary: clean up configuration guide Key: HBASE-18335 URL: https://issues.apache.org/jira/browse/HBASE-18335 Project: HBase Issue Type: Bug Components: documentation Affects Versions: 2.0.0-alpha-1, 1.1.11, 1.2.6, 1.3.1 Reporter: Artem Ervits Assignee: Artem Ervits Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18319) Implement getClusterStatus/getRegionLoad/getCompactionState/getLastMajorCompactionTimestamp methods
[ https://issues.apache.org/jira/browse/HBASE-18319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078003#comment-16078003 ] Hudson commented on HBASE-18319: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3331 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3331/]) HBASE-18319 Implement (zghao: rev b0a5fa0c2a119168c4272e5efba16a3ef9e9c329) * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncAdmin.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/RawAsyncHBaseAdmin.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/shaded/protobuf/RequestConverter.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncClusterAdminApi.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncRegionAdminApi.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/shaded/protobuf/ProtobufUtil.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncTableAdminApi.java * (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncHBaseAdmin.java > Implement > getClusterStatus/getRegionLoad/getCompactionState/getLastMajorCompactionTimestamp > methods > --- > > Key: HBASE-18319 > URL: https://issues.apache.org/jira/browse/HBASE-18319 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18319.master.001.patch, > HBASE-18319.master.002.patch, HBASE-18319.master.003.patch, > HBASE-18319.master.004.patch, HBASE-18319.master.004.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18083) Make large/small file clean thread number configurable in HFileCleaner
[ https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078002#comment-16078002 ] Hudson commented on HBASE-18083: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3331 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3331/]) HBASE-18083 Make large/small file clean thread number configurable in (liyu: rev 4fe73857679ecba89a7edd3c17d9f92e4c0e2164) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/cleaner/HFileCleaner.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/master/cleaner/TestHFileCleaner.java > Make large/small file clean thread number configurable in HFileCleaner > -- > > Key: HBASE-18083 > URL: https://issues.apache.org/jira/browse/HBASE-18083 > Project: HBase > Issue Type: Bug >Reporter: Yu Li >Assignee: Yu Li > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18083.patch, HBASE-18083.v2.patch, > HBASE-18083.v3.patch > > > Currently we have only one thread for both large and small file cleaning, but > when write pressure is huge we might need more cleaner threads, so we need to > make the thread number configurable. > We observed more than 1.8PB data in archive directory online due to business > access rate change, and this proposal is one of the necessary changes > required. > Default value of the configurations would still be left to 1 to keep low > pressure to NN for normal case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077992#comment-16077992
]
Peter Somogyi commented on HBASE-18332:
---
Patch 1 removes the pdfmark file generation from the build process
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated HBASE-18332:
--
Attachment: HBASE-18332.master.001.patch
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated HBASE-18332:
--
Status: Patch Available (was: In Progress)
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-18332 started by Peter Somogyi.
-
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077976#comment-16077976 ] Balazs Meszaros commented on HBASE-18185: - [~mdrob] thanks for your comment, fixed. > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-branch-1.v3.patch, > HBASE-18185-branch-1.v4.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Attachment: (was: HBASE-18185-BM-0002.patch) > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-branch-1.v3.patch, > HBASE-18185-branch-1.v4.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Attachment: HBASE-18185-branch-1.v4.patch > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-branch-1.v3.patch, > HBASE-18185-branch-1.v4.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Status: Patch Available (was: Open) > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-branch-1.v3.patch, > HBASE-18185-branch-1.v4.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Status: Open (was: Patch Available) > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-BM-0002.patch, > HBASE-18185-branch-1.v3.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Attachment: HBASE-18185.v4.patch > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-BM-0002.patch, > HBASE-18185-branch-1.v3.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError
[ https://issues.apache.org/jira/browse/HBASE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18185: Attachment: (was: HBASE-18185-BM-0001.patch) > IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails > with AssertionError > --- > > Key: HBASE-18185 > URL: https://issues.apache.org/jira/browse/HBASE-18185 > Project: HBase > Issue Type: Bug > Components: integration tests >Affects Versions: 2.0.0 >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.2.7 > > Attachments: HBASE-18185-BM-0002.patch, > HBASE-18185-branch-1.v3.patch, HBASE-18185.v3.patch, HBASE-18185.v4.patch > > > We got the following error: > Exception in thread "main" java.lang.AssertionError: Verification failed with > error code 1 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217) > at > org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123) > at > org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106) > at > org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123) > at > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362) > The reason why we got it because another assertion fails in > UnbalanceKillAndRebalanceAction: > Exception in thread "Thread-57" java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
