[jira] [Commented] (HBASE-18448) Added support for refreshing HFiles through API and shell
[ https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102738#comment-16102738 ] ramkrishna.s.vasudevan commented on HBASE-18448: Thanks for this info. So I think you will be periodically refreshing using this refresh files. Just asking, can the region server in replica have a periodic scheduler thread per store to do this refresh rather than having it in the admin and using it through shell? do you have some constraints in using that way? > Added support for refreshing HFiles through API and shell > - > > Key: HBASE-18448 > URL: https://issues.apache.org/jira/browse/HBASE-18448 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0, 1.3.1 >Reporter: Ajay Jadhav >Assignee: Ajay Jadhav >Priority: Minor > Fix For: 1.4.0 > > Attachments: HBASE-18448.branch-1.001.patch, > HBASE-18448.branch-1.002.patch > > > In the case where multiple HBase clusters are sharing a common rootDir, even > after flushing the data from > one cluster doesn't mean that other clusters (replicas) will automatically > pick the new HFile. Through this patch, > we are exposing the refresh HFiles API which when issued from a replica will > update the in-memory file handle list > with the newly added file. > This allows replicas to be consistent with the data written through the > primary cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18445) Upgrading Guava broke hadoop-3.0 profile
[
https://issues.apache.org/jira/browse/HBASE-18445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102673#comment-16102673
]
Hudson commented on HBASE-18445:
FAILURE: Integrated in Jenkins build HBase-2.0 #240 (See
[https://builds.apache.org/job/HBase-2.0/240/])
HBASE-18445 exclude guava from hadoop-auth (busbey: rev
10573c6c99c6df77117da3dc9539d90b2678b7c3)
* (edit) pom.xml
> Upgrading Guava broke hadoop-3.0 profile
>
>
> Key: HBASE-18445
> URL: https://issues.apache.org/jira/browse/HBASE-18445
> Project: HBase
> Issue Type: Bug
> Components: build, dependencies, hadoop3
>Affects Versions: 2.0.0-alpha-2
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18445.patch
>
>
> After HBASE-17908 upgrade guava, we have failures with the hadoop-3.0 profile.
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (banned-jsr305) @ hbase-client
> ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
> {noformat}
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ hbase-client ---
> [INFO] org.apache.hbase:hbase-client:jar:2.0.0-alpha-2-SNAPSHOT
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.0.0-alpha4:compile
> [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5.3:compile
> [INFO] | | \- org.apache.httpcomponents:httpcore:jar:4.4.6:compile
> [INFO] | +- com.nimbusds:nimbus-jose-jwt:jar:3.9:compile
> [INFO] | | +- net.jcip:jcip-annotations:jar:1.0:compile
> [INFO] | | \- net.minidev:json-smart:jar:1.1.1:compile
> [INFO] | +- org.apache.kerby:kerb-simplekdc:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerby-config:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-core:jar:1.0.0-RC2:compile
> [INFO] | | | +- org.apache.kerby:kerby-asn1:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-pkix:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-util:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-client:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-common:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-util:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-crypto:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-server:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-identity:jar:1.0.0-RC2:compile
> [INFO] | | \- org.apache.kerby:kerb-admin:jar:1.0.0-RC2:compile
> [INFO] | \- com.google.guava:guava:jar:11.0.2:compile
> [INFO] | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102672#comment-16102672
]
Hudson commented on HBASE-18402:
FAILURE: Integrated in Jenkins build HBase-2.0 #240 (See
[https://builds.apache.org/job/HBase-2.0/240/])
HBASE-18402 Thrift2 should support DeleteFamilyVersion - revert due to (busbey:
rev b7045d4fcfc89551dd6a02de65747fbe440f8107)
* (edit)
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/generated/TDeleteType.java
* (edit)
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftUtilities.java
* (edit)
hbase-thrift/src/main/resources/org/apache/hadoop/hbase/thrift2/hbase.thrift
* (edit)
hbase-thrift/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java
HBASE-18402 Thrift2 should support DeleteFamilyVersion type (busbey: rev
311ca34aec53147f1d62b70679321573830614e1)
* (edit)
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/generated/TDeleteType.java
* (edit)
hbase-thrift/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java
* (edit)
hbase-thrift/src/main/resources/org/apache/hadoop/hbase/thrift2/hbase.thrift
* (edit)
hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftUtilities.java
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[
https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102662#comment-16102662
]
Hadoop QA commented on HBASE-18261:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 4m
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 4 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
32s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 12m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
10s{color} | {color:red} hbase-protocol-shaded in master has 27 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 12m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
33s{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}
32m 40s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
30s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
2s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}115m
54s{color} | {color:green} hbase-server in the patch passed. {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}206m 22s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18261 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12879082/hbase-18261.master.004.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile cc hbaseprotoc |
| uname | Linux 81f06248a8d4 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-17922) TestRegionServerHostname always fails against hadoop 3.0.0-alpha2
[
https://issues.apache.org/jira/browse/HBASE-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102652#comment-16102652
]
Hudson commented on HBASE-17922:
FAILURE: Integrated in Jenkins build HBase-1.4 #823 (See
[https://builds.apache.org/job/HBase-1.4/823/])
HBASE-17922 Clean TestRegionServerHostname for hadoop3. (syuanjiangdev: rev
aca8a124c0e335896cc92b9718f01136e654eb81)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerHostname.java
> TestRegionServerHostname always fails against hadoop 3.0.0-alpha2
> -
>
> Key: HBASE-17922
> URL: https://issues.apache.org/jira/browse/HBASE-17922
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 2.0.0
>Reporter: Jonathan Hsieh
>Assignee: Mike Drob
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-17922.patch
>
>
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 126.363 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostname(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 120.029 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 12
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:405)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1123)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1077)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:948)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:942)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostname(TestRegionServerHostname.java:88)
> Results :
> Tests in error:
> TestRegionServerHostname.testRegionServerHostname:88 ยป TestTimedOut test
> timed...
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18459) [C++] Fix Segfault in location-cache
[ https://issues.apache.org/jira/browse/HBASE-18459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-18459: -- Attachment: hbase-18459-v1.patch v1 patch. Formatting is off (but I'll fix it in commit). I've tested this manually with load-client with 10 threads, and shutting down the zookeeper before the client starts. > [C++] Fix Segfault in location-cache > > > Key: HBASE-18459 > URL: https://issues.apache.org/jira/browse/HBASE-18459 > Project: HBase > Issue Type: Sub-task >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: HBASE-14850 > > Attachments: hbase-18459-v1.patch > > > When testing with the new multi-threaded load-client (implemented in > HBASE-18086), I've noticed that sometimes we get a segfault when zookeeper or > master connection gets an exception. > It seems to be from the way the we invalidate meta and refresh the meta. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18459) [C++] Fix Segfault in location-cache
Enis Soztutar created HBASE-18459: - Summary: [C++] Fix Segfault in location-cache Key: HBASE-18459 URL: https://issues.apache.org/jira/browse/HBASE-18459 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: HBASE-14850 When testing with the new multi-threaded load-client (implemented in HBASE-18086), I've noticed that sometimes we get a segfault when zookeeper or master connection gets an exception. It seems to be from the way the we invalidate meta and refresh the meta. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Attachment: (was: HBASE-18248.patch) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Attachment: (was: HBASE-18248-branch-1.patch) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Attachment: (was: HBASE-18248-branch-1.3.patch) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Attachment: (was: HBASE-18248-branch-2.patch) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.3.patch, HBASE-18248-branch-1.patch, > HBASE-18248-branch-1.patch, HBASE-18248.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18248) Warn if monitored task has been tied up beyond a configurable threshold
[ https://issues.apache.org/jira/browse/HBASE-18248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-18248: --- Attachment: (was: HBASE-18248-branch-2.patch) > Warn if monitored task has been tied up beyond a configurable threshold > --- > > Key: HBASE-18248 > URL: https://issues.apache.org/jira/browse/HBASE-18248 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18248-branch-1.3.patch, > HBASE-18248-branch-1.3.patch, HBASE-18248-branch-1.patch, > HBASE-18248-branch-1.patch, HBASE-18248.patch, HBASE-18248.patch > > > Warn if monitored task has been tied up beyond a configurable threshold. We > especially want to do this for RPC tasks. Use a separate threshold for > warning about stuck RPC tasks versus other types of tasks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.4.0
Status: Resolved (was: Patch Available)
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Fix For: 1.4.0
>
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102546#comment-16102546
]
Stephen Yuan Jiang commented on HBASE-18458:
[~mdrob], almost straightforward, only slight difference in
testRegionServerHostnameReportedToMaster due to branch-1 and branch-2 different
checking.
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102547#comment-16102547
]
Stephen Yuan Jiang commented on HBASE-18458:
This is test only change (one test suite affected), the failed UTs are
unrelated to this change.
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102538#comment-16102538
]
Hadoop QA commented on HBASE-18458:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
24s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
4s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
36s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
4s{color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} branch-1 passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} branch-1 passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
36s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
16m 3s{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} 2m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} the patch passed with JDK v1.7.0_131 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 96m 32s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}127m 46s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestClientScannerRPCTimeout |
| | hadoop.hbase.master.TestAssignmentListener |
| | hadoop.hbase.client.TestReplicasClient |
| | hadoop.hbase.regionserver.TestRSKilledWhenInitializing |
| | hadoop.hbase.coprocessor.TestRowProcessorEndpoint |
| | hadoop.hbase.master.TestMasterFailover |
| | hadoop.hbase.TestZooKeeper |
| | hadoop.hbase.security.access.TestAccessControlFilter |
| Timed out junit tests |
org.apache.hadoop.hbase.security.visibility.TestVisibilityWithCheckAuths |
| | org.apache.hadoop.hbase.security.access.TestCellACLs |
| | org.apache.hadoop.hbase.security.access.TestScanEarlyTermination |
\\
\\
||
[jira] [Updated] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[ https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18261: - Attachment: hbase-18261.master.004.patch Fixed findbugs error. > [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure > and HMaster.finishActiveMasterInitialization() > -- > > Key: HBASE-18261 > URL: https://issues.apache.org/jira/browse/HBASE-18261 > Project: HBase > Issue Type: Improvement > Components: amv2 >Affects Versions: 2.0.0-alpha-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0-alpha-2 > > Attachments: hbase-18261.master.001.patch, > HBASE-18261.master.001.patch, hbase-18261.master.002.patch, > hbase-18261.master.003.patch, hbase-18261.master.004.patch > > > When unit test > hbase.master.procedure.TestServerCrashProcedure#testRecoveryAndDoubleExecutionOnRsWithMeta() > is enabled and run several times, it fails intermittently. Cause is meta > recovery is done at two different places: > * ServerCrashProcedure.processMeta() > * HMaster.finishActiveMasterInitialization() > and its not coordinated. > When HMaster.finishActiveMasterInitialization() gets to submit splitMetaLog() > first and while its running call from ServerCrashProcedure.processMeta() > fails causing step to be retried again in a loop. > When ServerCrashProcedure.processMeta() submits splitMetaLog after > splitMetaLog from HMaster.finishActiveMasterInitialization() is finished, > success is returned without doing any work. > But if ServerCrashProcedure.processMeta() submits splitMetaLog request and > while its going HMaster.finishActiveMasterInitialization() submits it test > fails with exception. > [~stack] and I discussed the possible solution: > Create RecoverMetaProcedure and call it where required. Procedure framework > provides mutual exclusion and requires idempotence, which should fix the > problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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=16102511#comment-16102511 ] Xiaobing Zhou commented on HBASE-18078: --- Posted v5: # added two functions (i.e. ping and addr) implementation in test_rpc_service.proto # rebased HBASE-18338 # did some refactoring v6 will come with error implementation that triggers ConnectionException. > [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, HBASE-18078.004.patch, > HBASE-18078.005.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-18445) Upgrading Guava broke hadoop-3.0 profile
[
https://issues.apache.org/jira/browse/HBASE-18445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102510#comment-16102510
]
Hudson commented on HBASE-18445:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3440 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3440/])
HBASE-18445 exclude guava from hadoop-auth (busbey: rev
a649afebbac08964fa4221ddf78bc89a3342801d)
* (edit) pom.xml
> Upgrading Guava broke hadoop-3.0 profile
>
>
> Key: HBASE-18445
> URL: https://issues.apache.org/jira/browse/HBASE-18445
> Project: HBase
> Issue Type: Bug
> Components: build, dependencies, hadoop3
>Affects Versions: 2.0.0-alpha-2
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18445.patch
>
>
> After HBASE-17908 upgrade guava, we have failures with the hadoop-3.0 profile.
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (banned-jsr305) @ hbase-client
> ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
> {noformat}
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ hbase-client ---
> [INFO] org.apache.hbase:hbase-client:jar:2.0.0-alpha-2-SNAPSHOT
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.0.0-alpha4:compile
> [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5.3:compile
> [INFO] | | \- org.apache.httpcomponents:httpcore:jar:4.4.6:compile
> [INFO] | +- com.nimbusds:nimbus-jose-jwt:jar:3.9:compile
> [INFO] | | +- net.jcip:jcip-annotations:jar:1.0:compile
> [INFO] | | \- net.minidev:json-smart:jar:1.1.1:compile
> [INFO] | +- org.apache.kerby:kerb-simplekdc:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerby-config:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-core:jar:1.0.0-RC2:compile
> [INFO] | | | +- org.apache.kerby:kerby-asn1:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-pkix:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-util:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-client:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-common:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-util:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-crypto:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-server:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-identity:jar:1.0.0-RC2:compile
> [INFO] | | \- org.apache.kerby:kerb-admin:jar:1.0.0-RC2:compile
> [INFO] | \- com.google.guava:guava:jar:11.0.2:compile
> [INFO] | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (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:all-tabpanel ] Xiaobing Zhou updated HBASE-18078: -- Attachment: HBASE-18078.005.patch > [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, HBASE-18078.004.patch, > HBASE-18078.005.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-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102493#comment-16102493
]
Sean Busbey commented on HBASE-18402:
-
so you did. pretty sure that's a sign that I'm done for the day. Sorry for the
noise folks!
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[
https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102494#comment-16102494
]
Hadoop QA commented on HBASE-18261:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 4m
29s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 4 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 11m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
31s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
0s{color} | {color:red} hbase-protocol-shaded in master has 27 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
47s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 12m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
39s{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}
31m 50s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 11s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
54s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
29s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
57s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}135m
25s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
50s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}224m 11s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | Exception is caught when Exception is not thrown in
org.apache.hadoop.hbase.master.procedure.RecoverMetaProcedure.executeFromState(MasterProcedureEnv,
MasterProcedureProtos$RecoverMetaState) At RecoverMetaProcedure.java:is not
thrown in
org.apache.hadoop.hbase.master.procedure.RecoverMetaProcedure.executeFromState(MasterProcedureEnv,
MasterProcedureProtos$RecoverMetaState) At RecoverMetaProcedure.java:[line
144] |
\\
[jira] [Commented] (HBASE-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102488#comment-16102488
]
Ted Yu commented on HBASE-18402:
I reverted and re-applied for branch-2 yesterday.
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102489#comment-16102489
]
Mike Drob commented on HBASE-18458:
---
Is this a straight backport? Haven't tested it but patch LGTM.
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18422) Fix TestRegionRebalancing
[ https://issues.apache.org/jira/browse/HBASE-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102486#comment-16102486 ] Vladimir Rodionov commented on HBASE-18422: --- Interesting. The test TestRegionRebalancing constantly PASSES in my Eclipse and fails in command-line. Digging into this. > Fix TestRegionRebalancing > - > > Key: HBASE-18422 > URL: https://issues.apache.org/jira/browse/HBASE-18422 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-18422-v1.patch, HBASE-18422-v2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102475#comment-16102475
]
Ajay Jadhav commented on HBASE-18444:
-
Thanks [~zyork] Let me know the umbrella JIRA id, I'll relate this(HBASE-18444)
and HBASE-18448 to it.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18445) Upgrading Guava broke hadoop-3.0 profile
[
https://issues.apache.org/jira/browse/HBASE-18445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-18445:
Resolution: Fixed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
Checked build locally. Pushed to branch-2 and master. thanks for the fix up
Mike!
> Upgrading Guava broke hadoop-3.0 profile
>
>
> Key: HBASE-18445
> URL: https://issues.apache.org/jira/browse/HBASE-18445
> Project: HBase
> Issue Type: Bug
> Components: build, dependencies, hadoop3
>Affects Versions: 2.0.0-alpha-2
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18445.patch
>
>
> After HBASE-17908 upgrade guava, we have failures with the hadoop-3.0 profile.
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (banned-jsr305) @ hbase-client
> ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
> {noformat}
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ hbase-client ---
> [INFO] org.apache.hbase:hbase-client:jar:2.0.0-alpha-2-SNAPSHOT
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.0.0-alpha4:compile
> [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5.3:compile
> [INFO] | | \- org.apache.httpcomponents:httpcore:jar:4.4.6:compile
> [INFO] | +- com.nimbusds:nimbus-jose-jwt:jar:3.9:compile
> [INFO] | | +- net.jcip:jcip-annotations:jar:1.0:compile
> [INFO] | | \- net.minidev:json-smart:jar:1.1.1:compile
> [INFO] | +- org.apache.kerby:kerb-simplekdc:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerby-config:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-core:jar:1.0.0-RC2:compile
> [INFO] | | | +- org.apache.kerby:kerby-asn1:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-pkix:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-util:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-client:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-common:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-util:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-crypto:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-server:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-identity:jar:1.0.0-RC2:compile
> [INFO] | | \- org.apache.kerby:kerb-admin:jar:1.0.0-RC2:compile
> [INFO] | \- com.google.guava:guava:jar:11.0.2:compile
> [INFO] | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-18402.
-
Resolution: Fixed
cherry-picked the revert and reapply to branch-2
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-18402:
Issue Type: Improvement (was: Bug)
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18023) Log multi-* requests for more than threshold number of rows
[ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102454#comment-16102454 ] Andrew Purtell edited comment on HBASE-18023 at 7/26/17 11:31 PM: -- I've noticed that replication can trigger this quite a bit as the sink applies the shipped edits. Should we make a distinction between normal clients and replication clients and apply two separate thresholds? was (Author: apurtell): I've noticed that replication will trigger this quite a bit. Should we make a distinction between normal clients and replication clients and apply two separate thresholds? > Log multi-* requests for more than threshold number of rows > --- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Clay B. >Assignee: David Harju >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18023.addendum.patch, > HBASE-18023-branch-1.3.patch, HBASE-18023-branch-1.patch, > HBASE-18023.master.001.patch, HBASE-18023.master.002.patch, > HBASE-18023.master.003.patch, HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get > through request throttling (e.g. it is one request) but still crash a region > server with a garbage storm. We have seen regionservers hit this issue and it > is silent and deadly. The RS will report nothing more than a mysterious > garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case > it happens to be deadly. Knowing the client, user and how many rows are > affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102461#comment-16102461
]
Sean Busbey commented on HBASE-18444:
-
excellent. other committers please consider this blocked on the umbrella.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18023) Log multi-* requests for more than threshold number of rows
[ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102454#comment-16102454 ] Andrew Purtell commented on HBASE-18023: I've noticed that replication will trigger this quite a bit. Should we make a distinction between normal clients and replication clients and apply two separate thresholds? > Log multi-* requests for more than threshold number of rows > --- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Clay B. >Assignee: David Harju >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18023.addendum.patch, > HBASE-18023-branch-1.3.patch, HBASE-18023-branch-1.patch, > HBASE-18023.master.001.patch, HBASE-18023.master.002.patch, > HBASE-18023.master.003.patch, HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get > through request throttling (e.g. it is one request) but still crash a region > server with a garbage storm. We have seen regionservers hit this issue and it > is silent and deadly. The RS will report nothing more than a mysterious > garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case > it happens to be deadly. Knowing the client, user and how many rows are > affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102445#comment-16102445
]
Andrew Purtell commented on HBASE-18431:
PB compat is fine. I set up bidirectional replication from a 1.3.1 cluster to a
1.4.0-SNAPSHOT cluster with this patch applied and used the 1.3.1 binaries to
drive a replication scenario with LoadTestTool writing to the 1.4.0-SNAPSHOT
cluster with that replicating rows back to the 1.3.1 one. No issues.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor )
[jira] [Commented] (HBASE-9272) A parallel, unordered scanner
[
https://issues.apache.org/jira/browse/HBASE-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102422#comment-16102422
]
Hadoop QA commented on HBASE-9272:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
3s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HBASE-9272 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-9272 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12610225/9272-trunk-v4.txt |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7807/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> A parallel, unordered scanner
> -
>
> Key: HBASE-9272
> URL: https://issues.apache.org/jira/browse/HBASE-9272
> Project: HBase
> Issue Type: New Feature
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Minor
> Attachments: 9272-0.94.txt, 9272-0.94-v2.txt, 9272-0.94-v3.txt,
> 9272-0.94-v4.txt, 9272-trunk.txt, 9272-trunk-v2.txt, 9272-trunk-v3.txt,
> 9272-trunk-v3.txt, 9272-trunk-v4.txt, ParallelClientScanner.java,
> ParallelClientScanner.java
>
>
> The contract of ClientScanner is to return rows in sort order. That limits
> the order in which region can be scanned.
> I propose a simple ParallelScanner that does not have this requirement and
> queries regions in parallel, return whatever gets returned first.
> This is generally useful for scans that filter a lot of data on the server,
> or in cases where the client can very quickly react to the returned data.
> I have a simple prototype (doesn't do error handling right, and might be a
> bit heavy on the synchronization side - it used a BlockingQueue to hand data
> between the client using the scanner and the threads doing the scanning, it
> also could potentially starve some scanners long enugh to time out at the
> server).
> On the plus side, it's only a 130 lines of code. :)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102421#comment-16102421
]
Ted Yu commented on HBASE-18458:
lgtm, pending QA run.
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-9272) A parallel, unordered scanner
[ https://issues.apache.org/jira/browse/HBASE-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102414#comment-16102414 ] Jean-Marc Spaggiari commented on HBASE-9272: Guys, Is there still any work on that? JMS > A parallel, unordered scanner > - > > Key: HBASE-9272 > URL: https://issues.apache.org/jira/browse/HBASE-9272 > Project: HBase > Issue Type: New Feature >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Minor > Attachments: 9272-0.94.txt, 9272-0.94-v2.txt, 9272-0.94-v3.txt, > 9272-0.94-v4.txt, 9272-trunk.txt, 9272-trunk-v2.txt, 9272-trunk-v3.txt, > 9272-trunk-v3.txt, 9272-trunk-v4.txt, ParallelClientScanner.java, > ParallelClientScanner.java > > > The contract of ClientScanner is to return rows in sort order. That limits > the order in which region can be scanned. > I propose a simple ParallelScanner that does not have this requirement and > queries regions in parallel, return whatever gets returned first. > This is generally useful for scans that filter a lot of data on the server, > or in cases where the client can very quickly react to the returned data. > I have a simple prototype (doesn't do error handling right, and might be a > bit heavy on the synchronization side - it used a BlockingQueue to hand data > between the client using the scanner and the threads doing the scanning, it > also could potentially starve some scanners long enugh to time out at the > server). > On the plus side, it's only a 130 lines of code. :) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (HBASE-18402) Thrift2 should support DeleteFamilyVersion type
[
https://issues.apache.org/jira/browse/HBASE-18402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-18402:
-
reopening to fix branch-2
> Thrift2 should support DeleteFamilyVersion type
>
>
> Key: HBASE-18402
> URL: https://issues.apache.org/jira/browse/HBASE-18402
> Project: HBase
> Issue Type: Bug
> Components: Thrift
>Affects Versions: 2.0.0-alpha-1
>Reporter: Zheng Hu
>Assignee: Zheng Hu
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18402.v1.patch
>
>
> Currently, our thrift2 only support two delete types, Actually, there are
> four delete types.and we should support the other delete type: DeleteFamily
> and DeleteFamilyVersion.
> {code}
> /**
> * Specify type of delete:
> * - DELETE_COLUMN means exactly one version will be removed,
> * - DELETE_COLUMNS means previous versions will also be removed.
> */
> enum TDeleteType {
> DELETE_COLUMN = 0,
> DELETE_COLUMNS = 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Status: Patch Available (was: Open)
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to branch-1)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Summary: Refactor TestRegionServerHostname to make it robust (Port
HBASE-17922 to branch-1) (was: Refactor TestRegionServerHostname to make it
robust (Port HBASE-17922))
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922 to
> branch-1)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Attachment: HBASE-17922.v1-branch-1.patch
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Affects Version/s: (was: 2.0.0)
1.4.0
Priority: Minor (was: Major)
Fix Version/s: (was: 2.0.0-alpha-2)
(was: 3.0.0)
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 1.4.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
>Priority: Minor
> Attachments: HBASE-17922.v1-branch-1.patch
>
>
> The TestRegionServerHostname is passing in branch-1; however, it always fails
> locally. Running tests individually always pass. Failing to start RS in
> some combination of test run indicates some resource leak.
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
> When running the testRegionServerHostnameReportedToMaster alone or with
> another newly added test, the test passed without problem.
> When running the {{testRegionServerHostnameReportedToMaster}} test with
> {{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
> {{TestRegionServerHostname}}, the region server failed to start:
> {noformat}
> 2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
> regionserver.HRegionServer(2182): ABORTING region server
> 192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
> hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> java.lang.RuntimeException: Failed suppression of fs shutdown hook:
> org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
> at
> org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
> robust than the one in branch-1 right now. Porting the change to branch-1
> (with small modification due to code difference between branch-1 and
> branch-2) is a good idea.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Description:
The TestRegionServerHostname is passing in branch-1; however, it always fails
locally. Running tests individually always pass. Failing to start RS in some
combination of test run indicates some resource leak.
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 30.095 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
{code}
When running the testRegionServerHostnameReportedToMaster alone or with another
newly added test, the test passed without problem.
When running the {{testRegionServerHostnameReportedToMaster}} test with
{{testInvalidRegionServerHostnameAbortsServer}} in the same test suite
{{TestRegionServerHostname}}, the region server failed to start:
{noformat}
2017-07-25 15:34:24,132 FATAL [RS:0;192.168.1.7:64317]
regionserver.HRegionServer(2182): ABORTING region server
192.168.1.7,64317,1501022063917: Unhandled: Failed suppression of fs shutdown
hook: org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
java.lang.RuntimeException: Failed suppression of fs shutdown hook:
org.apache.hadoop.fs.FileSystem$Cache$ClientFinalizer@668e0f60
at
org.apache.hadoop.hbase.regionserver.ShutdownHook.suppressHdfsShutdownHook(ShutdownHook.java:204)
at
org.apache.hadoop.hbase.regionserver.ShutdownHook.install(ShutdownHook.java:84)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:940)
at
org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.runRegionServer(MiniHBaseCluster.java:156)
at
org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.access$000(MiniHBaseCluster.java:108)
at
org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer$1.run(MiniHBaseCluster.java:140)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1846)
at
org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:307)
at
org.apache.hadoop.hbase.MiniHBaseCluster$MiniHBaseClusterRegionServer.run(MiniHBaseCluster.java:138)
at java.lang.Thread.run(Thread.java:745)
{noformat}
HBASE-17922 addressed similar issue in Hadoop 3. I think this change is more
robust than the one in branch-1 right now. Porting the change to branch-1
(with small modification due to code difference between branch-1 and branch-2)
is a good idea.
was:
The
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 30.095 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Description:
The
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 30.095 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
{code}
was:
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 30.095 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
{code}
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
> Fix For: 3.0.0, 2.0.0-alpha-2
>
>
> The
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
>
[jira] [Assigned] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang reassigned HBASE-18458:
--
Assignee: Stephen Yuan Jiang (was: Mike Drob)
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
> Fix For: 3.0.0, 2.0.0-alpha-2
>
>
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
> at
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
[
https://issues.apache.org/jira/browse/HBASE-18458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Yuan Jiang updated HBASE-18458:
---
Description:
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 30.095 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 3
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:894)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostnameReportedToMaster(TestRegionServerHostname.java:158)
{code}
was:
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 126.363 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostname(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 120.029 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 12
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:405)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1123)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1077)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:948)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:942)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostname(TestRegionServerHostname.java:88)
Results :
Tests in error:
TestRegionServerHostname.testRegionServerHostname:88 ยป TestTimedOut test
timed...
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
{code}
> Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
> --
>
> Key: HBASE-18458
> URL: https://issues.apache.org/jira/browse/HBASE-18458
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Mike Drob
> Fix For: 3.0.0, 2.0.0-alpha-2
>
>
> {code}
> Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 46.042 sec
> <<< FAILURE! - in
> org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
> testRegionServerHostnameReportedToMaster(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
> Time elapsed: 30.095 sec <<< ERROR!
> org.junit.runners.model.TestTimedOutException: test timed out after 3
> milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1072)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1028)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:900)
> at
>
[jira] [Created] (HBASE-18458) Refactor TestRegionServerHostname to make it robust (Port HBASE-17922)
Stephen Yuan Jiang created HBASE-18458:
--
Summary: Refactor TestRegionServerHostname to make it robust (Port
HBASE-17922)
Key: HBASE-18458
URL: https://issues.apache.org/jira/browse/HBASE-18458
Project: HBase
Issue Type: Sub-task
Components: hadoop3
Affects Versions: 2.0.0
Reporter: Stephen Yuan Jiang
Assignee: Mike Drob
Fix For: 3.0.0, 2.0.0-alpha-2
{code}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 126.363 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testRegionServerHostname(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 120.029 sec <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 12
milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:221)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:405)
at
org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:225)
at
org.apache.hadoop.hbase.MiniHBaseCluster.(MiniHBaseCluster.java:94)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1123)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:1077)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:948)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:942)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testRegionServerHostname(TestRegionServerHostname.java:88)
Results :
Tests in error:
TestRegionServerHostname.testRegionServerHostname:88 ยป TestTimedOut test
timed...
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18422) Fix TestRegionRebalancing
[
https://issues.apache.org/jira/browse/HBASE-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102390#comment-16102390
]
Hadoop QA commented on HBASE-18422:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
24s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s{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}
36m 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-alpha4. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 3m
8s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}117m 37s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}171m 49s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | org.apache.hadoop.hbase.master.HMaster.augmentAssignments(Map) makes
inefficient use of keySet iterator instead of entrySet iterator At
HMaster.java:keySet iterator instead of entrySet iterator At
HMaster.java:[line 1479] |
| Failed junit tests | hadoop.hbase.TestRegionRebalancing |
| | hadoop.hbase.master.TestMasterMetrics |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18422 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12879030/HBASE-18422-v2.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 490e3392e4b9 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 3d81f7b |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| findbugs |
https://builds.apache.org/job/PreCommit-HBASE-Build/7803/artifact/patchprocess/new-findbugs-hbase-server.html
|
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/7803/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7803/testReport/ |
| modules | C: hbase-server U:
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102388#comment-16102388
]
Zach York commented on HBASE-18444:
---
I am working on an Umbrella JIRA that will explain these questions.
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18376) Flaky exclusion doesn't appear to work in precommit
[
https://issues.apache.org/jira/browse/HBASE-18376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102386#comment-16102386
]
Sean Busbey commented on HBASE-18376:
-
I don't think it's working, though the parameter is definitely getting
propogated into the personality running in the container.
{code}
21:41:55
21:41:55
21:41:55 Running unit tests
21:41:55
21:41:55
21:41:55
21:41:55
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: MultiJDK not configured.
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Personality: patch unit
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Personality: clear queue
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: EXCLUDE_TESTS_URL =
"https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/;
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: INCLUDE_TESTS_URL =
21:41:55
"https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/":
Scheme missing.
21:41:55 Wget error 1 in fetching excludes file from url
"https://builds.apache.org/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/excludes/;.
Ignoring and proceeding.
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Personality: enqueue
hbase-protocol-shaded -DHBasePatchProcess -PrunAllTests
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Personality: enqueue
hbase-procedure -DHBasePatchProcess -PrunAllTests
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Personality: enqueue
hbase-server -DHBasePatchProcess -PrunAllTests
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: MultiJDK not configured.
21:41:55 [Wed Jul 26 21:41:55 UTC 2017 DEBUG]: Start clock
21:41:58 cd /testptch/hbase/hbase-protocol-shaded
21:41:58 mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hbase-master-patch-0
-DHBasePatchProcess -PrunAllTests clean test -fae >
/testptch/patchprocess/patch-unit-hbase-protocol-shaded.txt 2>&1
21:42:24 [Wed Jul 26 21:42:24 UTC 2017 DEBUG]: Stop clock
21:42:24 Elapsed: 0m 29s
21:42:24 [Wed Jul 26 21:42:24 UTC 2017 DEBUG]: Start clock
21:42:27 cd /testptch/hbase/hbase-procedure
21:42:27 mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hbase-master-patch-0
-DHBasePatchProcess -PrunAllTests clean test -fae >
/testptch/patchprocess/patch-unit-hbase-procedure.txt 2>&1
21:45:21 [Wed Jul 26 21:45:21 UTC 2017 DEBUG]: Stop clock
21:45:21 Elapsed: 2m 57s
21:45:21 [Wed Jul 26 21:45:21 UTC 2017 DEBUG]: Start clock
21:45:24 cd /testptch/hbase/hbase-server
21:45:24 mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hbase-master-patch-0
-DHBasePatchProcess -PrunAllTests clean test -fae >
/testptch/patchprocess/patch-unit-hbase-server.txt 2>&1
{code}
> Flaky exclusion doesn't appear to work in precommit
> ---
>
> Key: HBASE-18376
> URL: https://issues.apache.org/jira/browse/HBASE-18376
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Priority: Critical
> Attachments: HBASE-18376.master.001.patch
>
>
> Yesterday we started defaulting the precommit parameter for the flaky test
> list to point to the job on builds.a.o. Looks like the personality is
> ignoring it.
> example build that's marked to keep:
> https://builds.apache.org/job/PreCommit-HBASE-Build/7646/
> (search for 'Running unit tests' to skip to the right part of the console')
> should add some more debug output in there too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
[
https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102382#comment-16102382
]
Sean Busbey commented on HBASE-18444:
-
Can we get a scope document here?
1) use case motivation. normally our deployment guidance for multiple clusters
sharing an underlying storage source would be to set different root dirs. It
sounds like your proposition is sharing table data. How do the read only
clusters properly see updates to that data if they have their own meta?
2) How are we flagging a cluster as read-only?
3) How do we handle upgrade? Can I turn this on for an existing cluster?
4) How do we explain this for downstream use via documentation?
> Add support for specifying custom meta table suffix
> ---
>
> Key: HBASE-18444
> URL: https://issues.apache.org/jira/browse/HBASE-18444
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0, 1.3.1
>Reporter: Ajay Jadhav
>Assignee: Ajay Jadhav
>Priority: Minor
> Labels: patch
> Fix For: 1.4.0
>
> Attachments: HBASE-18444.branch-1.001.patch
>
>
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need
> separate meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of
> meta_{suffix} making it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18395) Update clock on region open and close
[
https://issues.apache.org/jira/browse/HBASE-18395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102350#comment-16102350
]
Appy commented on HBASE-18395:
--
[~amit.patel] has addressed most of the comments on review board and the patch
looks in a great shape.
Filed HBASE-18457 for follow up work since it'll require some prior discussion.
Let me push this one to {{HBASE-14070.HLC}} branch.
fyi :[~stack], [~enis]
> Update clock on region open and close
> -
>
> Key: HBASE-18395
> URL: https://issues.apache.org/jira/browse/HBASE-18395
> Project: HBase
> Issue Type: Sub-task
>Reporter: Amit Patel
>Assignee: Amit Patel
>Priority: Minor
> Attachments: HBASE-18395.HBASE-14070.HLC.001.patch,
> HBASE-18395.HBASE-14070.HLC.002.patch, HBASE-18395.HBASE-14070.HLC.003.patch
>
>
> This task covers the patch for updating the clock on region opening and
> closing.
> The patch would include the following:
> * Addition of a new protobuf message type that contains a field for a
> timestamp
> * Setting of timestamp field in building region open/close request and
> response messages
> * Updating the clock upon receiving message
> The patch for this task will be going against the
> [HBASE-14070.HLC|https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=shortlog;h=refs/heads/HBASE-14070.HLC]
> branch with the intent that it would be added as a commit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-18455) TestClientScannerRPCTimeout is flaky
[ https://issues.apache.org/jira/browse/HBASE-18455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-18455. Resolution: Duplicate > TestClientScannerRPCTimeout is flaky > > > Key: HBASE-18455 > URL: https://issues.apache.org/jira/browse/HBASE-18455 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: Andrew Purtell > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18455) TestClientScannerRPCTimeout is flaky
[ https://issues.apache.org/jira/browse/HBASE-18455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102345#comment-16102345 ] Chia-Ping Tsai commented on HBASE-18455: Yes, we can close this IMHO. > TestClientScannerRPCTimeout is flaky > > > Key: HBASE-18455 > URL: https://issues.apache.org/jira/browse/HBASE-18455 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: Andrew Purtell > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18457) [HLC] Follow up work of updating clocks (from HBASE-18395)
Appy created HBASE-18457: Summary: [HLC] Follow up work of updating clocks (from HBASE-18395) Key: HBASE-18457 URL: https://issues.apache.org/jira/browse/HBASE-18457 Project: HBase Issue Type: Sub-task Reporter: Appy So list of things that need to be considered in future - Mocking clocks in HMaster/RegionServer to test that clocks get updated on assign/unassign - Discuss the idea of adding timestamp type to NodeTime proto --> Get rid of isLikelyOfType() fn - In assign/unassign RPCs, either update the clock which matches table's clock type OR all clocks. Updating only meta clock every time looks kind of weird right now (and this called out explicitly in comments too). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-10643) Failure in RS when using large size bucketcache
[ https://issues.apache.org/jira/browse/HBASE-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair resolved HBASE-10643. --- Resolution: Won't Fix Resolving. Please refer to the superceding ticket in the latest version of HBase. > Failure in RS when using large size bucketcache > --- > > Key: HBASE-10643 > URL: https://issues.apache.org/jira/browse/HBASE-10643 > Project: HBase > Issue Type: Bug > Components: BlockCache, regionserver >Affects Versions: 0.98.0, 0.96.0 >Reporter: Biju Nair > Labels: beginner > > When RS is brought up with XX:MaxDirectMemorySize of 22GB or higher, RS fails > after a successful start. From the RS logs it looks like the bucketCache > memory allocation is taking more time makes the RS considered dead by ZK. One > option to fix the problem would be to allocate the bucketCache before > registering with ZK. > 2014-02-28 18:54:42,967 WARN [regionserver60020.compactionChecker] > util.Sleeper: We slept 33496ms instead of 1ms, this is likely due to a > long garbage collecting pause and it's usually bad, see > http://hbase.apache.org/book.html#trouble.rs.runtime.zkexpired > 2014-02-28 18:54:42,967 WARN [regionserver60020.periodicFlusher] > util.Sleeper: We slept 33496ms instead of 1ms, this is likely due to a > long garbage collecting pause and it's usually bad, see > http://hbase.apache.org/book.html#trouble.rs.runtime.zkexpired > 2014-02-28 18:54:42,967 WARN [JvmPauseMonitor] util.JvmPauseMonitor: > Detected pause in JVM or host machine (eg GC): pause of approximately 23988ms > GC pool 'ParNew' had collection(s): count=1 time=24432ms > 2014-02-28 18:54:43,006 FATAL [regionserver60020] regionserver.HRegionServer: > ABORTING region server bbg-master2.bbg-test.hdp,60020,1393628951236: > org.apache.hadoop.hbase.YouAreDeadException: Server REPORT rejected; > currently processing bbg-master2.bbg-test.hdp,60020,1393628951236 as dead > server > at > org.apache.hadoop.hbase.master.ServerManager.checkIsDead(ServerManager.java:341) > at > org.apache.hadoop.hbase.master.ServerManager.regionServerReport(ServerManager.java:254) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18456) Add ChaosMonkey that skews clocks
Sean Busbey created HBASE-18456: --- Summary: Add ChaosMonkey that skews clocks Key: HBASE-18456 URL: https://issues.apache.org/jira/browse/HBASE-18456 Project: HBase Issue Type: New Feature Components: integration tests Reporter: Sean Busbey We should add a monkey that skews clocks around the cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18455) TestClientScannerRPCTimeout is flaky
[ https://issues.apache.org/jira/browse/HBASE-18455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102310#comment-16102310 ] Andrew Purtell commented on HBASE-18455: [~chia7712] , you said this is a dup of HBASE-18415? > TestClientScannerRPCTimeout is flaky > > > Key: HBASE-18455 > URL: https://issues.apache.org/jira/browse/HBASE-18455 > Project: HBase > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: Andrew Purtell > -- 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=16102285#comment-16102285 ] Xiaobing Zhou commented on HBASE-18338: --- Nice to have this, thanks [~enis]. > [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 > Fix For: HBASE-14850 > > Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch, > HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch, > HBASE-18338.005.patch, HBASE-18338.006.patch, hbase-18338-addendum.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-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102288#comment-16102288
]
Chia-Ping Tsai commented on HBASE-18431:
TestClientScannerRPCTimeout is traced by HBASE-18415.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> Here, maybe DeleteTracker moved packages?
> \\
>
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-18338: -- Attachment: hbase-18338-addendum.patch I've pushed this small addendum for the new .proto file so that it does not get deleted from rsync. > [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 > Fix For: HBASE-14850 > > Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch, > HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch, > HBASE-18338.005.patch, HBASE-18338.006.patch, hbase-18338-addendum.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-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[ https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102281#comment-16102281 ] Sean Busbey commented on HBASE-18261: - FYI, [~appy] and I have been trying to fix handling of the flaky test list in precommit and this JIRA happens to be the one mentioned in our test runs. > [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure > and HMaster.finishActiveMasterInitialization() > -- > > Key: HBASE-18261 > URL: https://issues.apache.org/jira/browse/HBASE-18261 > Project: HBase > Issue Type: Improvement > Components: amv2 >Affects Versions: 2.0.0-alpha-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0-alpha-2 > > Attachments: hbase-18261.master.001.patch, > HBASE-18261.master.001.patch, hbase-18261.master.002.patch, > hbase-18261.master.003.patch > > > When unit test > hbase.master.procedure.TestServerCrashProcedure#testRecoveryAndDoubleExecutionOnRsWithMeta() > is enabled and run several times, it fails intermittently. Cause is meta > recovery is done at two different places: > * ServerCrashProcedure.processMeta() > * HMaster.finishActiveMasterInitialization() > and its not coordinated. > When HMaster.finishActiveMasterInitialization() gets to submit splitMetaLog() > first and while its running call from ServerCrashProcedure.processMeta() > fails causing step to be retried again in a loop. > When ServerCrashProcedure.processMeta() submits splitMetaLog after > splitMetaLog from HMaster.finishActiveMasterInitialization() is finished, > success is returned without doing any work. > But if ServerCrashProcedure.processMeta() submits splitMetaLog request and > while its going HMaster.finishActiveMasterInitialization() submits it test > fails with exception. > [~stack] and I discussed the possible solution: > Create RecoverMetaProcedure and call it where required. Procedure framework > provides mutual exclusion and requires idempotence, which should fix the > problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[
https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102233#comment-16102233
]
Hadoop QA commented on HBASE-18261:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color: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} 0m
16s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 11m
49s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 2m
13s{color} | {color:red} hbase-protocol-shaded in master has 27 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
45s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 11m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s{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}
29m 46s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 4s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 3m
0s{color} | {color:red} hbase-server generated 1 new + 0 unchanged - 0 fixed =
1 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
30s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
53s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}120m
14s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
46s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}203m 2s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hbase-server |
| | Exception is caught when Exception is not thrown in
org.apache.hadoop.hbase.master.procedure.RecoverMetaProcedure.executeFromState(MasterProcedureEnv,
MasterProcedureProtos$RecoverMetaState) At RecoverMetaProcedure.java:is not
thrown in
org.apache.hadoop.hbase.master.procedure.RecoverMetaProcedure.executeFromState(MasterProcedureEnv,
MasterProcedureProtos$RecoverMetaState) At RecoverMetaProcedure.java:[line
144] |
\\
[jira] [Commented] (HBASE-18376) Flaky exclusion doesn't appear to work in precommit
[
https://issues.apache.org/jira/browse/HBASE-18376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102232#comment-16102232
]
Appy commented on HBASE-18376:
--
So me and [~busbey] tried to fix precommit job using DOCKER_EXTRAARGS. Let's
see if this build
(https://builds.apache.org/job/PreCommit-HBASE-Build/7804/console) shows the
maven command with excluded tests.
Btw, following is what worked.
DOCKER_EXTRAARGS=--env=EXCLUDE_TESTS_URL="$\{EXCLUDE_TESTS_URL}"
And these are what didn't work :-/
DOCKER_EXTRAARGS=--env EXCLUDE_TESTS_URL="$\{EXCLUDE_TESTS_URL}"
DOCKER_EXTRAARGS=-env EXCLUDE_TESTS_URL="$\{EXCLUDE_TESTS_URL}"
> Flaky exclusion doesn't appear to work in precommit
> ---
>
> Key: HBASE-18376
> URL: https://issues.apache.org/jira/browse/HBASE-18376
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Priority: Critical
> Attachments: HBASE-18376.master.001.patch
>
>
> Yesterday we started defaulting the precommit parameter for the flaky test
> list to point to the job on builds.a.o. Looks like the personality is
> ignoring it.
> example build that's marked to keep:
> https://builds.apache.org/job/PreCommit-HBASE-Build/7646/
> (search for 'Running unit tests' to skip to the right part of the console')
> should add some more debug output in there too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18422) Fix TestRegionRebalancing
[ https://issues.apache.org/jira/browse/HBASE-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-18422: -- Attachment: HBASE-18422-v2.patch Patch v2. > Fix TestRegionRebalancing > - > > Key: HBASE-18422 > URL: https://issues.apache.org/jira/browse/HBASE-18422 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-18422-v1.patch, HBASE-18422-v2.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18371) [C++] Update folly and wangle dependencies
[ https://issues.apache.org/jira/browse/HBASE-18371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-18371. --- Resolution: Fixed Hadoop Flags: Reviewed Thanks [~xiaobingo] for the review. I've pushed this. > [C++] Update folly and wangle dependencies > -- > > Key: HBASE-18371 > URL: https://issues.apache.org/jira/browse/HBASE-18371 > Project: HBase > Issue Type: Sub-task >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: HBASE-14850 > > Attachments: hbase-18371_v1.patch, hbase-18371_v2.patch, > hbase-18371_v3.patch > > > We need to update folly and wangle dependency versions. Debugging an issue, I > realized that we may need a couple of recent patches from wangle. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18455) TestClientScannerRPCTimeout is flaky
Andrew Purtell created HBASE-18455: -- Summary: TestClientScannerRPCTimeout is flaky Key: HBASE-18455 URL: https://issues.apache.org/jira/browse/HBASE-18455 Project: HBase Issue Type: Bug Affects Versions: 1.4.0, 1.5.0 Reporter: Andrew Purtell -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102116#comment-16102116
]
Andrew Purtell commented on HBASE-18431:
TestClientScannerRPCTimeout is flaky independent of this change.
TestRSKilledWhenInitializing is a known flake being tracked by another JIRA.
All other tests called out in the precommit report pass for me repeatedly 25 of
25 times.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method
[jira] [Commented] (HBASE-18405) Track scope for HBase-Spark module
[ https://issues.apache.org/jira/browse/HBASE-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102056#comment-16102056 ] Sean Busbey commented on HBASE-18405: - excellent. Let's go ahead and call this scope set. I'll get the relevant JIRAs for our gaps linked later this week. > Track scope for HBase-Spark module > -- > > Key: HBASE-18405 > URL: https://issues.apache.org/jira/browse/HBASE-18405 > Project: HBase > Issue Type: Task > Components: spark >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 1.4.0, 2.0.0-beta-1 > > Attachments: Apache HBase - Apache Spark Integration Scope.pdf, > Apache HBase - Apache Spark Integration Scope - update 1.pdf > > > Start with [\[DISCUSS\] status of and plans for our hbase-spark integration > |https://lists.apache.org/thread.html/fd74ef9b9da77abf794664f06ea19c839fb3d543647fb29115081683@%3Cdev.hbase.apache.org%3E] > and formalize into a scope document for bringing this feature into a release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18448) Added support for refreshing HFiles through API and shell
[ https://issues.apache.org/jira/browse/HBASE-18448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102052#comment-16102052 ] Ajay Jadhav commented on HBASE-18448: - [~ram_krish]: Exposing the refresh hfiles API is useful in the following scenario: Assuming we have 2 HBase clusters pointing to same rootDir (S3 bucket) out of which one is in read-only mode (replica) and the other one accepts writes (primary) 1. We issue a "put" on primary cluster and do a flush immediately. 2. This will create an HFile on storage (S3). 3. Replica will not be aware of this newly created HFile as the write didn't go through it. 4. The only way for replica to be consistent with primary is to issue a refresh HFiles on replica which will update the in-memory file handle list for replica. This is why we need the refresh HFiles API to keep all the clusters consistent with writes on the primary cluster. More information about this feature is available here too- https://aws.amazon.com/blogs/big-data/setting-up-read-replica-clusters-with-hbase-on-amazon-s3/ > Added support for refreshing HFiles through API and shell > - > > Key: HBASE-18448 > URL: https://issues.apache.org/jira/browse/HBASE-18448 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0, 1.3.1 >Reporter: Ajay Jadhav >Assignee: Ajay Jadhav >Priority: Minor > Fix For: 1.4.0 > > Attachments: HBASE-18448.branch-1.001.patch, > HBASE-18448.branch-1.002.patch > > > In the case where multiple HBase clusters are sharing a common rootDir, even > after flushing the data from > one cluster doesn't mean that other clusters (replicas) will automatically > pick the new HFile. Through this patch, > we are exposing the refresh HFiles API which when issued from a replica will > update the in-memory file handle list > with the newly added file. > This allows replicas to be consistent with the data written through the > primary cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101996#comment-16101996
]
Andrew Purtell commented on HBASE-18431:
bq. Break a cycle with proto definitions by moving TableName into its own proto
module and fixing up users
Haven't seen comment if this is a reasonable way to break the cycle between
HBase.proto and AccessControl.proto after moving SnapshotDescription back.
Assuming so, let me make sure protobuf allows this kind of change by checking
if 1.3 and 1.4 with this change applied can still communicate.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method
[jira] [Commented] (HBASE-18445) Upgrading Guava broke hadoop-3.0 profile
[
https://issues.apache.org/jira/browse/HBASE-18445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101985#comment-16101985
]
Mike Drob commented on HBASE-18445:
---
Ran unit test suite locally, everything seemed to work still.
> Upgrading Guava broke hadoop-3.0 profile
>
>
> Key: HBASE-18445
> URL: https://issues.apache.org/jira/browse/HBASE-18445
> Project: HBase
> Issue Type: Bug
> Components: build, dependencies, hadoop3
>Affects Versions: 2.0.0-alpha-2
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18445.patch
>
>
> After HBASE-17908 upgrade guava, we have failures with the hadoop-3.0 profile.
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (banned-jsr305) @ hbase-client
> ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {noformat}
> {noformat}
> [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ hbase-client ---
> [INFO] org.apache.hbase:hbase-client:jar:2.0.0-alpha-2-SNAPSHOT
> [INFO] +- org.apache.hadoop:hadoop-auth:jar:3.0.0-alpha4:compile
> [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5.3:compile
> [INFO] | | \- org.apache.httpcomponents:httpcore:jar:4.4.6:compile
> [INFO] | +- com.nimbusds:nimbus-jose-jwt:jar:3.9:compile
> [INFO] | | +- net.jcip:jcip-annotations:jar:1.0:compile
> [INFO] | | \- net.minidev:json-smart:jar:1.1.1:compile
> [INFO] | +- org.apache.kerby:kerb-simplekdc:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerby-config:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-core:jar:1.0.0-RC2:compile
> [INFO] | | | +- org.apache.kerby:kerby-asn1:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-pkix:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerby-util:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-client:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-common:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-util:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-crypto:jar:1.0.0-RC2:compile
> [INFO] | | +- org.apache.kerby:kerb-server:jar:1.0.0-RC2:compile
> [INFO] | | | \- org.apache.kerby:kerb-identity:jar:1.0.0-RC2:compile
> [INFO] | | \- org.apache.kerby:kerb-admin:jar:1.0.0-RC2:compile
> [INFO] | \- com.google.guava:guava:jar:11.0.2:compile
> [INFO] | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101955#comment-16101955
]
Andrew Purtell commented on HBASE-18431:
[~anoop.hbase]
Adding back FastLongHistogram is harmless and fixes a disallowed change in
minor releases .
Moving DeleteTracker from one package to another does not change function at
all and restores binary compatibility to a coprocessor interface.
Moving SnapshotDescription back into HBase.proto fixes disallowed changes to
the public Admin interface and also fixes compatibility problems with the core
CP interfaces.
I see some noise from precommit. Let me check that.
It doesn't matter the intent of the JIRAs where the changes were made because
the compat breaks are disallowed. This is a release blocker for branch-1.4 and
any future 1.x release.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
>
[jira] [Commented] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[ https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101927#comment-16101927 ] Umesh Agashe commented on HBASE-18261: -- Fixed unit tests. trying with new patch. > [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure > and HMaster.finishActiveMasterInitialization() > -- > > Key: HBASE-18261 > URL: https://issues.apache.org/jira/browse/HBASE-18261 > Project: HBase > Issue Type: Improvement > Components: amv2 >Affects Versions: 2.0.0-alpha-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0-alpha-2 > > Attachments: hbase-18261.master.001.patch, > HBASE-18261.master.001.patch, hbase-18261.master.002.patch, > hbase-18261.master.003.patch > > > When unit test > hbase.master.procedure.TestServerCrashProcedure#testRecoveryAndDoubleExecutionOnRsWithMeta() > is enabled and run several times, it fails intermittently. Cause is meta > recovery is done at two different places: > * ServerCrashProcedure.processMeta() > * HMaster.finishActiveMasterInitialization() > and its not coordinated. > When HMaster.finishActiveMasterInitialization() gets to submit splitMetaLog() > first and while its running call from ServerCrashProcedure.processMeta() > fails causing step to be retried again in a loop. > When ServerCrashProcedure.processMeta() submits splitMetaLog after > splitMetaLog from HMaster.finishActiveMasterInitialization() is finished, > success is returned without doing any work. > But if ServerCrashProcedure.processMeta() submits splitMetaLog request and > while its going HMaster.finishActiveMasterInitialization() submits it test > fails with exception. > [~stack] and I discussed the possible solution: > Create RecoverMetaProcedure and call it where required. Procedure framework > provides mutual exclusion and requires idempotence, which should fix the > problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18261) [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure and HMaster.finishActiveMasterInitialization()
[ https://issues.apache.org/jira/browse/HBASE-18261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18261: - Attachment: hbase-18261.master.003.patch > [AMv2] Create new RecoverMetaProcedure and use it from ServerCrashProcedure > and HMaster.finishActiveMasterInitialization() > -- > > Key: HBASE-18261 > URL: https://issues.apache.org/jira/browse/HBASE-18261 > Project: HBase > Issue Type: Improvement > Components: amv2 >Affects Versions: 2.0.0-alpha-1 >Reporter: Umesh Agashe >Assignee: Umesh Agashe > Fix For: 2.0.0-alpha-2 > > Attachments: hbase-18261.master.001.patch, > HBASE-18261.master.001.patch, hbase-18261.master.002.patch, > hbase-18261.master.003.patch > > > When unit test > hbase.master.procedure.TestServerCrashProcedure#testRecoveryAndDoubleExecutionOnRsWithMeta() > is enabled and run several times, it fails intermittently. Cause is meta > recovery is done at two different places: > * ServerCrashProcedure.processMeta() > * HMaster.finishActiveMasterInitialization() > and its not coordinated. > When HMaster.finishActiveMasterInitialization() gets to submit splitMetaLog() > first and while its running call from ServerCrashProcedure.processMeta() > fails causing step to be retried again in a loop. > When ServerCrashProcedure.processMeta() submits splitMetaLog after > splitMetaLog from HMaster.finishActiveMasterInitialization() is finished, > success is returned without doing any work. > But if ServerCrashProcedure.processMeta() submits splitMetaLog request and > while its going HMaster.finishActiveMasterInitialization() submits it test > fails with exception. > [~stack] and I discussed the possible solution: > Create RecoverMetaProcedure and call it where required. Procedure framework > provides mutual exclusion and requires idempotence, which should fix the > problem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18449) Fix client.locking.TestEntityLocks
[
https://issues.apache.org/jira/browse/HBASE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101914#comment-16101914
]
Hudson commented on HBASE-18449:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3438 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3438/])
HBASE-18449 Fix client.locking.TestEntityLocks (chia7712: rev
3d81f7b9e7b3c15fbe7b987901e521ba01e3e3cf)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/client/locking/TestEntityLocks.java
> Fix client.locking.TestEntityLocks
> --
>
> Key: HBASE-18449
> URL: https://issues.apache.org/jira/browse/HBASE-18449
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18449.v0.patch
>
>
> {noformat}
> Wanted but not invoked:
> abortable.abort(
> ,
> isA(org.apache.hadoop.hbase.HBaseIOException)
> );
> -> at
> org.apache.hadoop.hbase.client.locking.TestEntityLocks.testHeartbeatException(TestEntityLocks.java:195)
> Actually, there were zero interactions with this mock.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-8009) Fix and reenable the hbase-example unit tests.
[ https://issues.apache.org/jira/browse/HBASE-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101911#comment-16101911 ] Sean Busbey commented on HBASE-8009: I think they failed to even compile during the HBASE-15638 migration, which is why they got killed instead of ignored. I'd agree that we need to figure out a way to have an equivalent to the coverage they provided. > Fix and reenable the hbase-example unit tests. > -- > > Key: HBASE-8009 > URL: https://issues.apache.org/jira/browse/HBASE-8009 > Project: HBase > Issue Type: Task > Components: test >Reporter: stack >Priority: Critical > > The unit tests pass locally for me repeatedly but fail from time to time up > on jenkins. HBASE-7994 disabled them. This issue is about spending the time > to make sure they pass up on jenkins again. They have been disabled because > unit tests have been failing way more often than they have been passing over > the last few months and we want to establish passing tests as the precedent > again. Once that is in place, we can work on bringing back examples. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18449) Fix client.locking.TestEntityLocks
[
https://issues.apache.org/jira/browse/HBASE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101832#comment-16101832
]
Hudson commented on HBASE-18449:
FAILURE: Integrated in Jenkins build HBase-2.0 #237 (See
[https://builds.apache.org/job/HBase-2.0/237/])
HBASE-18449 Fix client.locking.TestEntityLocks (chia7712: rev
164df6bdd975b8daae064135aa579f3caecc1ab1)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/client/locking/TestEntityLocks.java
> Fix client.locking.TestEntityLocks
> --
>
> Key: HBASE-18449
> URL: https://issues.apache.org/jira/browse/HBASE-18449
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18449.v0.patch
>
>
> {noformat}
> Wanted but not invoked:
> abortable.abort(
> ,
> isA(org.apache.hadoop.hbase.HBaseIOException)
> );
> -> at
> org.apache.hadoop.hbase.client.locking.TestEntityLocks.testHeartbeatException(TestEntityLocks.java:195)
> Actually, there were zero interactions with this mock.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Work started] (HBASE-18304) Start enforcing upperbounds on dependencies
[ https://issues.apache.org/jira/browse/HBASE-18304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-18304 started by Tamas Penzes. > Start enforcing upperbounds on dependencies > --- > > Key: HBASE-18304 > URL: https://issues.apache.org/jira/browse/HBASE-18304 > Project: HBase > Issue Type: Task > Components: build, dependencies >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > > would be nice to get this going before our next major version. > http://maven.apache.org/enforcer/enforcer-rules/requireUpperBoundDeps.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-8009) Fix and reenable the hbase-example unit tests.
[ https://issues.apache.org/jira/browse/HBASE-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101689#comment-16101689 ] Mike Drob commented on HBASE-8009: -- Looks like these tests were killed in HBASE-15638 so there's nothing to unignore. Should they have been migrated at that time to somewhere else instead of being deleted? > Fix and reenable the hbase-example unit tests. > -- > > Key: HBASE-8009 > URL: https://issues.apache.org/jira/browse/HBASE-8009 > Project: HBase > Issue Type: Task > Components: test >Reporter: stack >Priority: Critical > > The unit tests pass locally for me repeatedly but fail from time to time up > on jenkins. HBASE-7994 disabled them. This issue is about spending the time > to make sure they pass up on jenkins again. They have been disabled because > unit tests have been failing way more often than they have been passing over > the last few months and we want to establish passing tests as the precedent > again. Once that is in place, we can work on bringing back examples. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-2739) Master should fail to start if it cannot successfully split logs
[ https://issues.apache.org/jira/browse/HBASE-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101679#comment-16101679 ] Mike Drob commented on HBASE-2739: -- This moved out of MasterFileSystem in HBASE-15763 - the code looks pretty different now as well. I'm not sure if this is still an issue anymore. > Master should fail to start if it cannot successfully split logs > > > Key: HBASE-2739 > URL: https://issues.apache.org/jira/browse/HBASE-2739 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.20.4, 0.90.0 >Reporter: Todd Lipcon >Priority: Critical > > In trunk, in splitLogAfterStartup(), we log the error splitting, but don't > shut down. Depending on configuration, we should probably shut down here > rather than continue with dataloss. > In 0.20, we print the stacktrace to stdout in verifyClusterState, but > continue through and often fail to start up -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-18304) Start enforcing upperbounds on dependencies
[ https://issues.apache.org/jira/browse/HBASE-18304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Penzes reassigned HBASE-18304: Assignee: Tamas Penzes > Start enforcing upperbounds on dependencies > --- > > Key: HBASE-18304 > URL: https://issues.apache.org/jira/browse/HBASE-18304 > Project: HBase > Issue Type: Task > Components: build, dependencies >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Tamas Penzes > Labels: beginner > Fix For: 2.0.0 > > > would be nice to get this going before our next major version. > http://maven.apache.org/enforcer/enforcer-rules/requireUpperBoundDeps.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18431) Mitigate compatibility concerns between branch-1.3 and branch-1.4
[
https://issues.apache.org/jira/browse/HBASE-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101612#comment-16101612
]
Anoop Sam John commented on HBASE-18431:
Do you know which jira(s) made above BC breaks? Just to make sure that the
current changes wont break the original intent of those jiras.
> Mitigate compatibility concerns between branch-1.3 and branch-1.4
> -
>
> Key: HBASE-18431
> URL: https://issues.apache.org/jira/browse/HBASE-18431
> Project: HBase
> Issue Type: Bug
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Blocker
> Fix For: 1.4.0, 1.5.0
>
> Attachments: HBASE-18431-branch-1.4.patch
>
>
> There are compatibility concerns with branch-1.4.
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Binary Compatibility
> Compatibility - 89.9%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 23
> Medium - 9
> Low - 21
> {noformat}
> {noformat}
> Library Name HBase
> Version #11.3.1
> Version #21.4.0-SNAPSHOT
> Subject Source Compatibility
> Compatibility- 86.5%
> Added Methods - 305
> Removed Methods - 105
> Problems with Data Types
> High - 88
> Medium - 0
> Low - 0
> Other Changes in Data Types- 25
> {noformat}
> This report includes HBASE-15816 which hasn't been committed yet. Otherwise
> it's current.
> I'm not generally concerned with added methods.
> The following methods have been added to Public/Evolving interface Table.
> Pointing them out in case it merits review.
> \\
> * Abstract method Table.getReadRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.getWriteRpcTimeout ( ) has been added to this
> interface. No effect.
> * Abstract method Table.setReadRpcTimeout ( int ) has been added to this
> interface. No effect.
> * Abstract method Table.setWriteRpcTimeout ( int ) has been added to this
> interface.
> The Public/Evolving interface Admin has some signature changes equating to
> removed methods. I don't think this is allowed in a minor release.
> \\
> * Abstract method Admin.isSnapshotFinished ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> * Abstract method Admin.snapshot ( String, TableName,
> HBaseProtos.SnapshotDescription.Type ) has been removed from Admin.
> * Abstract method Admin.snapshot ( HBaseProtos.SnapshotDescription ) has been
> removed from Admin.
> * Abstract method Admin.takeSnapshotAsync ( HBaseProtos.SnapshotDescription
> ) has been removed from Admin.
> The LimitedPrivate(CONFIG) interface AsyncRpcClient has been removed. This
> change is debatable but I think we can allow it.
> \\
> * AsyncRpcClient has been removed
> The Public/Evolving class FastLongHistogram has been removed. I don't believe
> this change is allowed in a minor release.
> \\
> * FastLongHistogram has been removed
> Method signatures in LimitedPrivate(COPROC) interfaces MasterObserver and
> RegionObserver have changed, equating to removed methods. The first set of
> changes is due to move of SnapshotDescription from HBaseProtos to
> SnapshotProtos:
> \\
> * Abstract method MasterObserver.postCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.postRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.postSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preCloneSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preDeleteSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preListSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription ) has been removed from MasterObserver.
> * Abstract method MasterObserver.preRestoreSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has been removed from
> MasterObserver.
> * Abstract method MasterObserver.preSnapshot (
> ObserverContext,
> HBaseProtos.SnapshotDescription, HTableDescriptor ) has
[jira] [Commented] (HBASE-18441) ZookeeperWatcher#interruptedException should throw exception
[
https://issues.apache.org/jira/browse/HBASE-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101610#comment-16101610
]
Hudson commented on HBASE-18441:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3437 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3437/])
HBASE-18441 ZookeeperWatcher#interruptedException should throw exception (liyu:
rev 1e49decfa2bc72c039ed559055d41b1c2c2b3a61)
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/zookeeper/TestZKUtil.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java
> ZookeeperWatcher#interruptedException should throw exception
>
>
> Key: HBASE-18441
> URL: https://issues.apache.org/jira/browse/HBASE-18441
> Project: HBase
> Issue Type: Bug
>Reporter: Yu Li
>Assignee: Yu Li
> Fix For: 2.0.0, 3.0.0, 1.4.0
>
> Attachments: HBASE-18441.patch, HBASE-18441.trivial.patch
>
>
> Currently Zookeeper#interruptedException will swallow the
> InterruptedException and only log, which might cause unexpected behavior,
> such as when invoking {{ZKUtil#checkExists}} and the watcher thread somehow
> interrupted, the method will return -1 which means the checked znode doesn't
> exist, while actually the znode exists.
> We could also see a TODO tag in the javadoc, which indicates we need some
> fix/improvement here:
> {code}
> /**
>* Handles InterruptedExceptions in client calls.
>*
>* This may be temporary but for now this gives one place to deal with
> these.
>*
>* TODO: Currently, this method does nothing.
>* Is this ever expected to happen? Do we abort or can we let it run?
>* Maybe this should be logged as WARN? It shouldn't happen?
>*
>* @param ie
>*/
> {code}
> Here we propose to throw a {{KeeperException$SystemErrorException}} in
> {{ZookeeperWatcher#interruptedException}}, and will add a UT case to cover
> the interruption scenario.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18447) MetricRegistryInfo#hashCode uses hashCode instead of toHashCode
[ https://issues.apache.org/jira/browse/HBASE-18447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101611#comment-16101611 ] Hudson commented on HBASE-18447: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3437 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3437/]) HBASE-18447 MetricRegistryInfo#hashCode uses hashCode instead of (chia7712: rev 6dec2b3aa6736450b3ae429a60159a77bb0d576e) * (edit) hbase-metrics-api/src/main/java/org/apache/hadoop/hbase/metrics/MetricRegistryInfo.java > MetricRegistryInfo#hashCode uses hashCode instead of toHashCode > --- > > Key: HBASE-18447 > URL: https://issues.apache.org/jira/browse/HBASE-18447 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0.0, 3.0.0, 1.4.0 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Minor > Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2 > > Attachments: HBASE-18447.master.001.patch > > > With commons-lang 2.6 .hashCode and .toHashCode gives back the same result > but with version 2.4 the hashCode gives back the HashCodeBuilder's hash. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18454) RegionServer Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Summary: RegionServer Do not close file descriptor when using shortcircuit (was: Hbase Do not close file descriptor when using shortcircuit) > RegionServer Do not close file descriptor when using shortcircuit > - > > Key: HBASE-18454 > URL: https://issues.apache.org/jira/browse/HBASE-18454 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 1.2.6 > Environment: HDFS 2.7.3, HBASE 1.2.6, centOS 6.8 >Reporter: HanRyong,Jung > > I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. > The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. > At this time, when one disk fails in HDFS, I found a phenomenon that I did a > hotswap but did not close file descriptor in hbase. > And the fd path on the umount disk is changed to an incorrect path. > If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted > data1, the path changed to /volumn. > And many file descriptors used in shortcircuit are in the delete state. > example ) > ls -al /proc/regionserver_pid/fd > lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> > /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 > (deleted) > lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> > /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta > (deleted) > lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> > /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 > (deleted) > lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> > /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta > (deleted) > lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> > */volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 > (deleted)* > . > . > . > . > > when data4 fails, execute fuser) > /sbin/fuser -cu /data4 > Cannot stat file /proc/regionserver_pid/fd/*192*: input/output error > Cannot stat file /proc/regionserver_pid/fd/1282: input/output error > Cannot stat file /proc/regionserver_pid/fd/1283: input/output error > . > . > . > . > . > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18449) Fix client.locking.TestEntityLocks
[
https://issues.apache.org/jira/browse/HBASE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18449:
---
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Push this to branch-2 and master.
[~ram_krish] Thanks for the reviews.
> Fix client.locking.TestEntityLocks
> --
>
> Key: HBASE-18449
> URL: https://issues.apache.org/jira/browse/HBASE-18449
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18449.v0.patch
>
>
> {noformat}
> Wanted but not invoked:
> abortable.abort(
> ,
> isA(org.apache.hadoop.hbase.HBaseIOException)
> );
> -> at
> org.apache.hadoop.hbase.client.locking.TestEntityLocks.testHeartbeatException(TestEntityLocks.java:195)
> Actually, there were zero interactions with this mock.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Description: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> */volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted)* . . . . when data4 fails, execute fuser) /sbin/fuser -cu /data4 Cannot stat file /proc/regionserver_pid/fd/*192*: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error . . . . . was: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> */volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted)* when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344:
[jira] [Updated] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Description: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> */volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted)* when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344: input/output error Cannot stat file /proc/regionserver_pid/fd/1381: input/output error Cannot stat file /proc/regionserver_pid/fd/1382: input/output error Cannot stat file /proc/regionserver_pid/fd/1383: input/output error Cannot stat file /proc/regionserver_pid/fd/1384: input/output error Cannot stat file /proc/regionserver_pid/fd/1394: input/output error Cannot stat file /proc/regionserver_pid/fd/1395: input/output error Cannot stat file /proc/regionserver_pid/fd/1410: input/output error Cannot stat file /proc/regionserver_pid/fd/1430: input/output error Cannot stat file /proc/regionserver_pid/fd/1477: input/output error Cannot stat file /proc/regionserver_pid/fd/1672: input/output error Cannot stat file /proc/regionserver_pid/fd/1673: input/output error Cannot stat file /proc/regionserver_pid/fd/2006: input/output error Cannot stat file /proc/regionserver_pid/fd/2021: input/output error Cannot stat file /proc/regionserver_pid/fd/2083: input/output error Cannot stat file /proc/regionserver_pid/fd/2309: input/output error Cannot stat file /proc/regionserver_pid/fd/2416: input/output error Cannot stat file /proc/regionserver_pid/fd/2428: input/output error Cannot stat file /proc/regionserver_pid/fd/2540: input/output error Cannot stat file /proc/regionserver_pid/fd/2555: input/output error Cannot stat file /proc/regionserver_pid/fd/2621: input/output error Cannot stat file /proc/regionserver_pid/fd/2624: input/output error Cannot stat file /proc/regionserver_pid/fd/2756: input/output error Cannot stat file /proc/regionserver_pid/fd/2803: input/output error Cannot stat file /proc/regionserver_pid/fd/2927: input/output error Cannot stat file /proc/regionserver_pid/fd/3456: input/output error Cannot stat file /proc/regionserver_pid/fd/3534: input/output error Cannot stat file /proc/regionserver_pid/fd/3814: input/output error Cannot stat file /proc/regionserver_pid/fd/3891: input/output error Cannot stat file /proc/regionserver_pid/fd/4034: input/output error Cannot stat file /proc/regionserver_pid/fd/4337: input/output error Cannot stat file /proc/regionserver_pid/fd/5272: input/output error Cannot stat file /proc/regionserver_pid/fd/5864: input/output error Cannot stat file /proc/regionserver_pid/fd/7419: input/output error Cannot stat file /proc/regionserver_pid/fd/7422: input/output error was: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit.
[jira] [Updated] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Description: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 ->* /volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted)* when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344: input/output error Cannot stat file /proc/regionserver_pid/fd/1381: input/output error Cannot stat file /proc/regionserver_pid/fd/1382: input/output error Cannot stat file /proc/regionserver_pid/fd/1383: input/output error Cannot stat file /proc/regionserver_pid/fd/1384: input/output error Cannot stat file /proc/regionserver_pid/fd/1394: input/output error Cannot stat file /proc/regionserver_pid/fd/1395: input/output error Cannot stat file /proc/regionserver_pid/fd/1410: input/output error Cannot stat file /proc/regionserver_pid/fd/1430: input/output error Cannot stat file /proc/regionserver_pid/fd/1477: input/output error Cannot stat file /proc/regionserver_pid/fd/1672: input/output error Cannot stat file /proc/regionserver_pid/fd/1673: input/output error Cannot stat file /proc/regionserver_pid/fd/2006: input/output error Cannot stat file /proc/regionserver_pid/fd/2021: input/output error Cannot stat file /proc/regionserver_pid/fd/2083: input/output error Cannot stat file /proc/regionserver_pid/fd/2309: input/output error Cannot stat file /proc/regionserver_pid/fd/2416: input/output error Cannot stat file /proc/regionserver_pid/fd/2428: input/output error Cannot stat file /proc/regionserver_pid/fd/2540: input/output error Cannot stat file /proc/regionserver_pid/fd/2555: input/output error Cannot stat file /proc/regionserver_pid/fd/2621: input/output error Cannot stat file /proc/regionserver_pid/fd/2624: input/output error Cannot stat file /proc/regionserver_pid/fd/2756: input/output error Cannot stat file /proc/regionserver_pid/fd/2803: input/output error Cannot stat file /proc/regionserver_pid/fd/2927: input/output error Cannot stat file /proc/regionserver_pid/fd/3456: input/output error Cannot stat file /proc/regionserver_pid/fd/3534: input/output error Cannot stat file /proc/regionserver_pid/fd/3814: input/output error Cannot stat file /proc/regionserver_pid/fd/3891: input/output error Cannot stat file /proc/regionserver_pid/fd/4034: input/output error Cannot stat file /proc/regionserver_pid/fd/4337: input/output error Cannot stat file /proc/regionserver_pid/fd/5272: input/output error Cannot stat file /proc/regionserver_pid/fd/5864: input/output error Cannot stat file /proc/regionserver_pid/fd/7419: input/output error Cannot stat file /proc/regionserver_pid/fd/7422: input/output error was: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit.
[jira] [Updated] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Description: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> /volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted) <-- change path when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344: input/output error Cannot stat file /proc/regionserver_pid/fd/1381: input/output error Cannot stat file /proc/regionserver_pid/fd/1382: input/output error Cannot stat file /proc/regionserver_pid/fd/1383: input/output error Cannot stat file /proc/regionserver_pid/fd/1384: input/output error Cannot stat file /proc/regionserver_pid/fd/1394: input/output error Cannot stat file /proc/regionserver_pid/fd/1395: input/output error Cannot stat file /proc/regionserver_pid/fd/1410: input/output error Cannot stat file /proc/regionserver_pid/fd/1430: input/output error Cannot stat file /proc/regionserver_pid/fd/1477: input/output error Cannot stat file /proc/regionserver_pid/fd/1672: input/output error Cannot stat file /proc/regionserver_pid/fd/1673: input/output error Cannot stat file /proc/regionserver_pid/fd/2006: input/output error Cannot stat file /proc/regionserver_pid/fd/2021: input/output error Cannot stat file /proc/regionserver_pid/fd/2083: input/output error Cannot stat file /proc/regionserver_pid/fd/2309: input/output error Cannot stat file /proc/regionserver_pid/fd/2416: input/output error Cannot stat file /proc/regionserver_pid/fd/2428: input/output error Cannot stat file /proc/regionserver_pid/fd/2540: input/output error Cannot stat file /proc/regionserver_pid/fd/2555: input/output error Cannot stat file /proc/regionserver_pid/fd/2621: input/output error Cannot stat file /proc/regionserver_pid/fd/2624: input/output error Cannot stat file /proc/regionserver_pid/fd/2756: input/output error Cannot stat file /proc/regionserver_pid/fd/2803: input/output error Cannot stat file /proc/regionserver_pid/fd/2927: input/output error Cannot stat file /proc/regionserver_pid/fd/3456: input/output error Cannot stat file /proc/regionserver_pid/fd/3534: input/output error Cannot stat file /proc/regionserver_pid/fd/3814: input/output error Cannot stat file /proc/regionserver_pid/fd/3891: input/output error Cannot stat file /proc/regionserver_pid/fd/4034: input/output error Cannot stat file /proc/regionserver_pid/fd/4337: input/output error Cannot stat file /proc/regionserver_pid/fd/5272: input/output error Cannot stat file /proc/regionserver_pid/fd/5864: input/output error Cannot stat file /proc/regionserver_pid/fd/7419: input/output error Cannot stat file /proc/regionserver_pid/fd/7422: input/output error was: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase
[jira] [Updated] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
[ https://issues.apache.org/jira/browse/HBASE-18454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HanRyong,Jung updated HBASE-18454: -- Description: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> /volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted) <- change path when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344: input/output error Cannot stat file /proc/regionserver_pid/fd/1381: input/output error Cannot stat file /proc/regionserver_pid/fd/1382: input/output error Cannot stat file /proc/regionserver_pid/fd/1383: input/output error Cannot stat file /proc/regionserver_pid/fd/1384: input/output error Cannot stat file /proc/regionserver_pid/fd/1394: input/output error Cannot stat file /proc/regionserver_pid/fd/1395: input/output error Cannot stat file /proc/regionserver_pid/fd/1410: input/output error Cannot stat file /proc/regionserver_pid/fd/1430: input/output error Cannot stat file /proc/regionserver_pid/fd/1477: input/output error Cannot stat file /proc/regionserver_pid/fd/1672: input/output error Cannot stat file /proc/regionserver_pid/fd/1673: input/output error Cannot stat file /proc/regionserver_pid/fd/2006: input/output error Cannot stat file /proc/regionserver_pid/fd/2021: input/output error Cannot stat file /proc/regionserver_pid/fd/2083: input/output error Cannot stat file /proc/regionserver_pid/fd/2309: input/output error Cannot stat file /proc/regionserver_pid/fd/2416: input/output error Cannot stat file /proc/regionserver_pid/fd/2428: input/output error Cannot stat file /proc/regionserver_pid/fd/2540: input/output error Cannot stat file /proc/regionserver_pid/fd/2555: input/output error Cannot stat file /proc/regionserver_pid/fd/2621: input/output error Cannot stat file /proc/regionserver_pid/fd/2624: input/output error Cannot stat file /proc/regionserver_pid/fd/2756: input/output error Cannot stat file /proc/regionserver_pid/fd/2803: input/output error Cannot stat file /proc/regionserver_pid/fd/2927: input/output error Cannot stat file /proc/regionserver_pid/fd/3456: input/output error Cannot stat file /proc/regionserver_pid/fd/3534: input/output error Cannot stat file /proc/regionserver_pid/fd/3814: input/output error Cannot stat file /proc/regionserver_pid/fd/3891: input/output error Cannot stat file /proc/regionserver_pid/fd/4034: input/output error Cannot stat file /proc/regionserver_pid/fd/4337: input/output error Cannot stat file /proc/regionserver_pid/fd/5272: input/output error Cannot stat file /proc/regionserver_pid/fd/5864: input/output error Cannot stat file /proc/regionserver_pid/fd/7419: input/output error Cannot stat file /proc/regionserver_pid/fd/7422: input/output error was: I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase
[jira] [Created] (HBASE-18454) Hbase Do not close file descriptor when using shortcircuit
HanRyong,Jung created HBASE-18454: - Summary: Hbase Do not close file descriptor when using shortcircuit Key: HBASE-18454 URL: https://issues.apache.org/jira/browse/HBASE-18454 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.2.6 Environment: HDFS 2.7.3, HBASE 1.2.6, centOS 6.8 Reporter: HanRyong,Jung I am a user using HDFS 2.7.3, HBASE 1.2.6, centOS 6.8. The regionserver uses 11 hard disks(jbod) and uses the hbase short circuit. At this time, when one disk fails in HDFS, I found a phenomenon that I did a hotswap but did not close file descriptor in hbase. And the fd path on the umount disk is changed to an incorrect path. If I check /proc/regionserver_pid/fd, if I used /data1/volumn and umounted data1, the path changed to /volumn. And many file descriptors used in shortcircuit are in the delete state. example ) ls -al /proc/regionserver_pid/fd lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 946 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 947 -> /data8/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir21/blk_1215239490_141511919.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 948 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080 (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 949 -> /data7/volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir111/subdir27/blk_1215241080_141513509.meta (deleted) lr-x-- 1 dragonboy dragonboy 64 2017-07-26 20:54 902 -> /volumn/hdfs/datanode/current/BP-199986352-10.114.243.73-1490077615453/current/finalized/subdir244/subdir160/blk_1257545757 (deleted) when data4 fails, execute fuser) /sbin/fuser -cu data4 Cannot stat file /proc/regionserver_pid/fd/1275: input/output error Cannot stat file /proc/regionserver_pid/fd/1282: input/output error Cannot stat file /proc/regionserver_pid/fd/1283: input/output error Cannot stat file /proc/regionserver_pid/fd/1297: input/output error Cannot stat file /proc/regionserver_pid/fd/1298: input/output error Cannot stat file /proc/regionserver_pid/fd/1306: input/output error Cannot stat file /proc/regionserver_pid/fd/1335: input/output error Cannot stat file /proc/regionserver_pid/fd/1336: input/output error Cannot stat file /proc/regionserver_pid/fd/1343: input/output error Cannot stat file /proc/regionserver_pid/fd/1344: input/output error Cannot stat file /proc/regionserver_pid/fd/1381: input/output error Cannot stat file /proc/regionserver_pid/fd/1382: input/output error Cannot stat file /proc/regionserver_pid/fd/1383: input/output error Cannot stat file /proc/regionserver_pid/fd/1384: input/output error Cannot stat file /proc/regionserver_pid/fd/1394: input/output error Cannot stat file /proc/regionserver_pid/fd/1395: input/output error Cannot stat file /proc/regionserver_pid/fd/1410: input/output error Cannot stat file /proc/regionserver_pid/fd/1430: input/output error Cannot stat file /proc/regionserver_pid/fd/1477: input/output error Cannot stat file /proc/regionserver_pid/fd/1672: input/output error Cannot stat file /proc/regionserver_pid/fd/1673: input/output error Cannot stat file /proc/regionserver_pid/fd/2006: input/output error Cannot stat file /proc/regionserver_pid/fd/2021: input/output error Cannot stat file /proc/regionserver_pid/fd/2083: input/output error Cannot stat file /proc/regionserver_pid/fd/2309: input/output error Cannot stat file /proc/regionserver_pid/fd/2416: input/output error Cannot stat file /proc/regionserver_pid/fd/2428: input/output error Cannot stat file /proc/regionserver_pid/fd/2540: input/output error Cannot stat file /proc/regionserver_pid/fd/2555: input/output error Cannot stat file /proc/regionserver_pid/fd/2621: input/output error Cannot stat file /proc/regionserver_pid/fd/2624: input/output error Cannot stat file /proc/regionserver_pid/fd/2756: input/output error Cannot stat file /proc/regionserver_pid/fd/2803: input/output error Cannot stat file /proc/regionserver_pid/fd/2927: input/output error Cannot stat file /proc/regionserver_pid/fd/3456: input/output error Cannot stat file /proc/regionserver_pid/fd/3534: input/output error Cannot stat file /proc/regionserver_pid/fd/3814: input/output error Cannot stat file /proc/regionserver_pid/fd/3891: input/output error Cannot stat file /proc/regionserver_pid/fd/4034: input/output error Cannot stat file /proc/regionserver_pid/fd/4337: input/output error Cannot stat file /proc/regionserver_pid/fd/5272: input/output error Cannot stat file /proc/regionserver_pid/fd/5864: input/output error Cannot stat file
[jira] [Commented] (HBASE-18449) Fix client.locking.TestEntityLocks
[
https://issues.apache.org/jira/browse/HBASE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101568#comment-16101568
]
Chia-Ping Tsai commented on HBASE-18449:
Will commit it soon
> Fix client.locking.TestEntityLocks
> --
>
> Key: HBASE-18449
> URL: https://issues.apache.org/jira/browse/HBASE-18449
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18449.v0.patch
>
>
> {noformat}
> Wanted but not invoked:
> abortable.abort(
> ,
> isA(org.apache.hadoop.hbase.HBaseIOException)
> );
> -> at
> org.apache.hadoop.hbase.client.locking.TestEntityLocks.testHeartbeatException(TestEntityLocks.java:195)
> Actually, there were zero interactions with this mock.
> {noformat}
--
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=16101561#comment-16101561
]
Hadoop QA commented on HBASE-18185:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{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
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
30m 59s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{color} | {color:green} the patch passed {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-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 38m 13s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.03.0-ce Server=17.03.0-ce Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18185 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878975/HBASE-18185.v5.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 8430f296eef7 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 / 6dec2b3 |
| Default Java | 1.8.0_131 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7794/testReport/ |
| modules | C: hbase-it U: hbase-it |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7794/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> 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
>
[jira] [Commented] (HBASE-18449) Fix client.locking.TestEntityLocks
[
https://issues.apache.org/jira/browse/HBASE-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101544#comment-16101544
]
Hadoop QA commented on HBASE-18449:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
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}
30m 32s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}120m 5s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}166m 18s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18449 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878958/HBASE-18449.v0.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 513c6339a125 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 6dec2b3 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| unit |
https://builds.apache.org/job/PreCommit-HBASE-Build/7792/artifact/patchprocess/patch-unit-hbase-server.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7792/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7792/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Fix client.locking.TestEntityLocks
> --
>
> Key: HBASE-18449
> URL: https://issues.apache.org/jira/browse/HBASE-18449
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 3.0.0, 2.0.0-alpha-1
>Reporter: Chia-Ping Tsai
>Assignee:
[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=16101539#comment-16101539
]
Hadoop QA commented on HBASE-18185:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m
1s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
9s{color} | {color:red} root in master failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
19s{color} | {color:green} master passed with JDK v1.8.0_131 {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
10s{color} | {color:red} hbase-it in master failed with JDK v1.7.0_131. {color}
|
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m
10s{color} | {color:red} hbase-it in master failed. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} master passed with JDK v1.8.0_131 {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
11s{color} | {color:red} hbase-it in master failed with JDK v1.7.0_131. {color}
|
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
10s{color} | {color:red} hbase-it in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
19s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m
10s{color} | {color:red} hbase-it in the patch failed with JDK v1.7.0_131.
{color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 10s{color}
| {color:red} hbase-it in the patch failed with JDK v1.7.0_131. {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} mvneclipse {color} | {color:red} 0m
11s{color} | {color:red} hbase-it in the patch failed. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
7s{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
15s{color} | {color:red} The patch causes 7 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
22s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
29s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
36s{color} | {color:red} The patch causes 7 errors with Hadoop v2.5.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
44s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
51s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m
58s{color} | {color:red} The patch causes 7 errors with Hadoop v2.6.3. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m
5s{color} | {color:red} The patch causes 7 errors with Hadoop v2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
9s{color} | {color:green} the patch passed with JDK v1.8.0_131 {color} |
| {color:red}-1{color} | {color:red} javadoc
[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.v5.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-branch-1.v5.patch, > HBASE-18185.v3.patch, HBASE-18185.v4.patch, HBASE-18185.v5.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.v5.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-branch-1.v5.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-branch-1.v5.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-branch-1.v5.patch, > HBASE-18185.v3.patch, HBASE-18185.v4.patch, HBASE-18185.v5.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.v5.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-branch-1.v5.patch, > HBASE-18185.v3.patch, HBASE-18185.v4.patch, HBASE-18185.v5.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)
