[jira] [Commented] (HBASE-18412) [Shell] Support unset of list of configuration for a table
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095852#comment-16095852 ] Hudson commented on HBASE-18412: FAILURE: Integrated in Jenkins build HBase-2.0 #209 (See [https://builds.apache.org/job/HBase-2.0/209/]) HBASE-18412 [Shell] Support unset of list of configuration for a table (tedyu: rev b81fed7f885bc6396251707f8ad07023c7df0c8a) * (edit) hbase-shell/src/main/ruby/hbase/admin.rb * (edit) hbase-shell/src/main/ruby/shell/commands/alter.rb * (edit) hbase-shell/src/test/ruby/hbase/admin_test.rb > [Shell] Support unset of list of configuration for a table > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18424) Fix TestAsyncTableGetMultiThreaded
[
https://issues.apache.org/jira/browse/HBASE-18424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095838#comment-16095838
]
Hadoop QA commented on HBASE-18424:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
1s{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
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
48s{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} 2m
56s{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
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
38s{color} | {color:green} the patch passed {color} |
| {color: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}
29m 33s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
49s{color} | {color:green} the patch passed {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} 83m 34s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
30s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}128m 33s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.master.procedure.TestDisableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestModifyTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestCreateTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestEnableTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestDeleteTableProcedure |
| | org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface |
| | org.apache.hadoop.hbase.client.TestSnapshotCloneIndependence |
| | org.apache.hadoop.hbase.coprocessor.TestHTableWrapper |
| | org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy
|
| | org.apache.hadoop.hbase.master.TestGetLastFlushedSequenceId |
| | org.apache.hadoop.hbase.client.TestFromClientSide |
| | org.apache.hadoop.hbase.client.TestMultipleTimestamps |
| | org.apache.hadoop.hbase.client.TestAsyncTableScanAll |
| | org.apache.hadoop.hbase.regionserver.TestCompaction |
| | org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2 |
| | org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
| | org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics |
| | org.apache.hadoop.hbase.master.assignment.TestAssignmentManager |
| | org.apache.hadoop.hbase.quotas.TestSnapshotQuotaObserverChore |
| | org.apache.hadoop.hbase.namespace.TestNamespaceAuditor |
| | org.apache.
[jira] [Commented] (HBASE-17908) Upgrade guava
[
https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095836#comment-16095836
]
Hadoop QA commented on HBASE-17908:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 13m
40s{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 210 new or modified
test files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 2m
13s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 7m
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
59s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-testing-util hbase-spark-it hbase-assembly . {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
32s{color} | {color:red} hbase-rest in master has 3 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 6m
11s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
21s{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
36s{color} | {color:red} hbase-spark in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 8m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 7m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 5m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
26s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 47s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hbase-testing-util hbase-spark-it hbase-assembly . {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 13m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 7m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
16s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
11s{color} | {color:green} hbase-metrics-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
1s{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
17s{color} | {color:green} hbase-metrics in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
26s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {c
[jira] [Commented] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095833#comment-16095833
]
Hadoop QA commented on HBASE-18420:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s{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}
37m 40s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
33s{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 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
3s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 51m 29s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18420 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878302/HBASE-18420.v1.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 76b713809bb6 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 / af534ac |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7745/testReport/ |
| modules | C: hbase-client U: hbase-client |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7745/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Some methods of Admin don't use ColumnFamilyDescriptor
> --
>
> Key: HBASE-18420
> URL: https://issues.apache.org/jira/browse/HBASE-18420
> Project: HBase
> Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: C
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Status: Open (was: Patch Available) > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch, HBASE-18420.v1.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Status: Patch Available (was: Open) > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch, HBASE-18420.v1.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Attachment: HBASE-18420.v1.patch v1 patch for master # fix javadoc errors > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch, HBASE-18420.v1.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095791#comment-16095791
]
Chia-Ping Tsai commented on HBASE-18419:
LGTM
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Critical
> Attachments: HBASE-18419.patch
>
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18412) [Shell] Support unset of list of configuration for a table
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095783#comment-16095783 ] Hudson commented on HBASE-18412: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3410 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3410/]) HBASE-18412 [Shell] Support unset of list of configuration for a table (tedyu: rev af534acabb3e0d03e804ff409a09f3b77e17e779) * (edit) hbase-shell/src/main/ruby/shell/commands/alter.rb * (edit) hbase-shell/src/test/ruby/hbase/admin_test.rb * (edit) hbase-shell/src/main/ruby/hbase/admin.rb > [Shell] Support unset of list of configuration for a table > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18412) [Shell] Support unset of list of configuration for a table
[ https://issues.apache.org/jira/browse/HBASE-18412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18412: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0-alpha-2 3.0.0 Status: Resolved (was: Patch Available) > [Shell] Support unset of list of configuration for a table > -- > > Key: HBASE-18412 > URL: https://issues.apache.org/jira/browse/HBASE-18412 > Project: HBase > Issue Type: Improvement >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Minor > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18412.master.001.patch > > > Add a method 'table_conf_unset' in admin.rb to reset the configuration as the > system default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18424) Fix TestAsyncTableGetMultiThreaded
[ https://issues.apache.org/jira/browse/HBASE-18424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-18424: -- Status: Patch Available (was: Open) > Fix TestAsyncTableGetMultiThreaded > -- > > Key: HBASE-18424 > URL: https://issues.apache.org/jira/browse/HBASE-18424 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-18424-v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095738#comment-16095738
]
Shibin Zhang edited comment on HBASE-18323 at 7/21/17 3:58 AM:
---
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
{code:java}
String hbaseUser = null;
try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}
}
}
if (!groups.isEmpty()) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
{code}
was (Author: zhangshibin):
{code:java}
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
{code:java}
String hbaseUser = null;
{color:#d04437} try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}{color}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
{color:#d04437} if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}{color}
}
}
if (!groups.isEmpty()) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
{code}
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095738#comment-16095738
]
Shibin Zhang edited comment on HBASE-18323 at 7/21/17 3:58 AM:
---
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
{code:java}
String hbaseUser = null;
try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}
}
}
if (!groups.isEmpty()) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
{code}
was (Author: zhangshibin):
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
{code:java}
String hbaseUser = null;
try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}
}
}
if (!groups.isEmpty()) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
{code}
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095738#comment-16095738
]
Shibin Zhang edited comment on HBASE-18323 at 7/21/17 3:57 AM:
---
{code:java}
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
{code:java}
String hbaseUser = null;
{color:#d04437} try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}{color}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
{color:#d04437} if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}{color}
}
}
if (!groups.isEmpty()) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
{code}
was (Author: zhangshibin):
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
String hbaseUser = null;
{color:#d04437} try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}{color}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
{color:#d04437} if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}{color}
}
}
if (!groups.isEmpty(){color:#d04437}colored text{color}) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18323) Remove multiple ACLs for the same user in kerberos
[
https://issues.apache.org/jira/browse/HBASE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095738#comment-16095738
]
Shibin Zhang commented on HBASE-18323:
--
[~elserj] sorry to feedback so late, could you help me codereview , how about
this way :
String hbaseUser = null;
{color:#d04437} try {
hbaseUser =
UserGroupInformation.getCurrentUser().getShortUserName();
} catch (IOException e) {
LOG.warn("Current Service User could not get.", e);
}{color}
if (superUsers != null) {
List groups = new ArrayList<>();
for (String user : superUsers) {
if (AuthUtil.isGroupPrincipal(user)) {
// TODO: Set node ACL for groups when ZK supports this feature
groups.add(user);
} else {
{color:#d04437} if(!user.equals(hbaseUser)) {
acls.add(new ACL(Perms.ALL, new Id("sasl", user)));
}{color}
}
}
if (!groups.isEmpty(){color:#d04437}colored text{color}) {
LOG.warn("Znode ACL setting for group " + groups
+ " is skipped, ZooKeeper doesn't support this feature
presently.");
}
}
> Remove multiple ACLs for the same user in kerberos
> --
>
> Key: HBASE-18323
> URL: https://issues.apache.org/jira/browse/HBASE-18323
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.2.0, 3.0.0
>Reporter: Shibin Zhang
>Priority: Minor
> Attachments: HBASE-18323.patch, HBASE-18323-V2.patch,
> HBASE-18323-V3.patch
>
>
> When deploy hbase in kerberos way ,there will be multiple acls in znode :
> 'world,'anyone
> : r
> 'sasl,'hbase
> : cdrwa
> 'sasl,'hbase
> : cdrwa
> I also see the related issue and apply the patch, like
> https://issues.apache.org/jira/browse/HBASE-17717
> but in my environment ,this situation still appear,
> After dig into the code , i found the reason in source code ZKUtil.createAcl
> is
> if (zkw.isClientReadable(node)) {
> LOG.error("isSecureZooKeeper user: clientReadable");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> acls.addAll(Ids.READ_ACL_UNSAFE);
> } else {
> LOG.error("isSecureZooKeeper user: clientReadable no");
> acls.addAll(Ids.CREATOR_ALL_ACL);
> }
> acls.addAll(Ids.CREATOR_ALL_ACL);
>
> Id AUTH_IDS = new Id("auth", "");
> ArrayList CREATOR_ALL_ACL = new ArrayList(Collections.singletonList(new
> ACL(31, AUTH_IDS)));
> AUTH_IDS with "auth " will result current connection auth user add to
> znode acl ,
> so it will appear multiple acls for same users.
> I think this line of code we can remove :
> acls.addAll(Ids.CREATOR_ALL_ACL);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095714#comment-16095714 ] Hudson commented on HBASE-18147: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3409 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3409/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev bdc94b1d6b836479b308fb0e7e4952c85b37a550) * (edit) dev-support/docker/Dockerfile * (add) dev-support/Jenkinsfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18427) minor cleanup around AssignmentManager
[
https://issues.apache.org/jira/browse/HBASE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095666#comment-16095666
]
Hadoop QA commented on HBASE-18427:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
49s{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}
31m 48s{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
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}120m
24s{color} | {color:green} hbase-server in the patch passed. {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}168m 18s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:bdc94b1 |
| JIRA Issue | HBASE-18427 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878271/hbase-18427.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 8f196bf3f6f6 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 / bdc94b1 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7742/testReport/ |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7742/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> minor cleanup around AssignmentManager
> --
>
> Key: HBASE-18427
> URL: https://issues.apache.org/jira/browse/HBASE-18427
> Project: HBase
> Issue Type: Bug
> Components: amv2
>Reporter: Umesh Agashe
>Assignee:
[jira] [Commented] (HBASE-18418) Remove apache_hbase_topology from dev-support
[
https://issues.apache.org/jira/browse/HBASE-18418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095646#comment-16095646
]
Andrew Purtell commented on HBASE-18418:
+1
> Remove apache_hbase_topology from dev-support
> -
>
> Key: HBASE-18418
> URL: https://issues.apache.org/jira/browse/HBASE-18418
> Project: HBase
> Issue Type: Task
>Reporter: Dima Spivak
>Assignee: Dima Spivak
>Priority: Minor
> Attachments: HBASE-18418_v1.patch
>
>
> As [~misty] noted on dev@, we still keep a folder containing the Apache HBase
> topology for [clusterdock|https://github.com/clusterdock/framework] in
> dev-support. Since the {{clusterdock}} org on GitHub will likely always have
> a more up-to-date iteration of this code (and since I plan on showing it some
> love there in the next few weeks), we'd probably be better off removing it
> from HBase. Any objections?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18238) Address ruby static analysis for bin directory
[
https://issues.apache.org/jira/browse/HBASE-18238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095633#comment-16095633
]
Hadoop QA commented on HBASE-18238:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HBASE-18238 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-18238 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878018/HBASE-18238.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7743/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Address ruby static analysis for bin directory
> --
>
> Key: HBASE-18238
> URL: https://issues.apache.org/jira/browse/HBASE-18238
> Project: HBase
> Issue Type: Sub-task
>Reporter: Mike Drob
>Assignee: Mike Drob
> Fix For: 2.0.0
>
> Attachments: HBASE-18238.patch, report.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095629#comment-16095629 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #219 (See [https://builds.apache.org/job/HBase-1.3-JDK8/219/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev b3a2a00aff1591bdec9b7c67691e1fce0ba0b4e3) * (edit) dev-support/docker/Dockerfile * (add) dev-support/Jenkinsfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095624#comment-16095624 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #166 (See [https://builds.apache.org/job/HBase-1.2-JDK8/166/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 933f4b33dc7102b5db99aea2fb05a9c9b0f70686) * (add) dev-support/Jenkinsfile * (edit) dev-support/docker/Dockerfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095621#comment-16095621 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1976 (See [https://builds.apache.org/job/HBase-1.1-JDK8/1976/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 5316580dc65840ca9acef852476ba4b794571ba0) * (add) dev-support/Jenkinsfile * (edit) dev-support/docker/Dockerfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095619#comment-16095619 ] Hudson commented on HBASE-18147: FAILURE: Integrated in Jenkins build HBase-1.4 #815 (See [https://builds.apache.org/job/HBase-1.4/815/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 6f1cc2c89ff44a0e59d292a5f05c20ae99e4d9b8) * (edit) dev-support/docker/Dockerfile * (add) dev-support/Jenkinsfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095618#comment-16095618 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1893 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1893/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 5316580dc65840ca9acef852476ba4b794571ba0) * (edit) dev-support/docker/Dockerfile * (add) dev-support/Jenkinsfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18424) Fix TestAsyncTableGetMultiThreaded
[ https://issues.apache.org/jira/browse/HBASE-18424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-18424: -- Attachment: HBASE-18424-v1.patch Patch v1. cc:[~syuanjiang] > Fix TestAsyncTableGetMultiThreaded > -- > > Key: HBASE-18424 > URL: https://issues.apache.org/jira/browse/HBASE-18424 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov > Attachments: HBASE-18424-v1.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18371) [C++] Update folly and wangle dependencies
[
https://issues.apache.org/jira/browse/HBASE-18371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095598#comment-16095598
]
Xiaobing Zhou commented on HBASE-18371:
---
v3 LGTM, had a run of dock build, but there are many compile issues when the
following is tried:
{noformat}
buck test --no-cache --no-results-cache //core:retry-test
{noformat}
Could you double check it? Thanks.
> [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] [Assigned] (HBASE-18350) Enable RSGroups UT that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang reassigned HBASE-18350: -- Assignee: Stephen Yuan Jiang > Enable RSGroups UT that were disabled by Proc-V2 AM in HBASE-14614 > -- > > Key: HBASE-18350 > URL: https://issues.apache.org/jira/browse/HBASE-18350 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Stephen Yuan Jiang > > The following RSGroups tests were disabled by Core Proc-V2 AM in HBASE-14614: > - Disabled/Ignore TestRSGroupsOfflineMode#testOffline; need to dig in on what > offline is. > - Disabled/Ignore TestRSGroups. > This JIRA tracks the work to enable them (or remove/modify if not applicable). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-18419:
--
Attachment: HBASE-18419.patch
Attached. Built on top of HBASE-18420 patch. Will wait for that to land before
triggering QA.
Verified locally against single node hbase.
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Critical
> Attachments: HBASE-18419.patch
>
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
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&focusedCommentId=16095583#comment-16095583 ] Xiaobing Zhou commented on HBASE-18078: --- Posted v4: # removed RPC test related pieces. # did some clean work. > [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 > > > 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] [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.004.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 > > > 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-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095576#comment-16095576 ] Hudson commented on HBASE-17738: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3408 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3408/]) HBASE-17738 BucketCache startup is slow - addendum (Ram) (ramkrishna: rev 0c49185c3e95cc91ba6455a404ca4e89f2c2fc20) * (edit) hbase-common/src/test/java/org/apache/hadoop/hbase/util/TestByteBufferArray.java * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferArray.java > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-17738_10.patch, HBASE-17738_11.patch, > HBASE-17738_2.patch, HBASE-17738_2.patch, HBASE-17738_3.patch, > HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738_6_withoutUnsafe.patch, HBASE-17738_8.patch, HBASE-17738_9.patch, > HBASE-17738_log.patch, HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16993) BucketCache throw java.io.IOException: Invalid HFile block magic when configuring hbase.bucketcache.bucket.sizes
[
https://issues.apache.org/jira/browse/HBASE-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095577#comment-16095577
]
Hudson commented on HBASE-16993:
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3408 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3408/])
HBASE-16993 BucketCache throw java.io.IOException: Invalid HFile block
(anoopsamjohn: rev bc93b6610b349d38502290af27da0ae0b5fd4936)
* (edit) hbase-common/src/main/resources/hbase-default.xml
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestCacheConfig.java
> BucketCache throw java.io.IOException: Invalid HFile block magic when
> configuring hbase.bucketcache.bucket.sizes
>
>
> Key: HBASE-16993
> URL: https://issues.apache.org/jira/browse/HBASE-16993
> Project: HBase
> Issue Type: Bug
> Components: BucketCache
>Affects Versions: 1.1.3
> Environment: hbase version 1.1.3
>Reporter: liubangchen
>Assignee: Anoop Sam John
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-16993.000.patch, HBASE-16993.001.patch,
> HBASE-16993_branch-1.patch, HBASE-16993.master.001.patch,
> HBASE-16993.master.002.patch, HBASE-16993.master.003.patch,
> HBASE-16993.master.004.patch, HBASE-16993.master.005.patch,
> HBASE-16993_V2.patch, HBASE-16993_V6.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> hbase-site.xml setting
>
> hbase.bucketcache.bucket.sizes
> 16384,32768,40960,
> 46000,49152,51200,65536,131072,524288
>
>
> hbase.bucketcache.size
> 16384
>
>
> hbase.bucketcache.ioengine
> offheap
>
>
> hfile.block.cache.size
> 0.3
>
>
> hfile.block.bloom.cacheonwrite
> true
>
>
> hbase.rs.cacheblocksonwrite
> true
>
>
> hfile.block.index.cacheonwrite
> true
> n_splits = 200
> create 'usertable',{NAME =>'family', COMPRESSION => 'snappy', VERSIONS =>
> 1,DATA_BLOCK_ENCODING => 'DIFF',CONFIGURATION =>
> {'hbase.hregion.memstore.block.multiplier' => 5}},{DURABILITY =>
> 'SKIP_WAL'},{SPLITS => (1..n_splits).map {|i|
> "user#{1000+i*(-1000)/n_splits}"}}
> load data
> bin/ycsb load hbase10 -P workloads/workloada -p table=usertable -p
> columnfamily=family -p fieldcount=10 -p fieldlength=100 -p
> recordcount=2 -p insertorder=hashed -p insertstart=0 -p
> clientbuffering=true -p durability=SKIP_WAL -threads 20 -s
> run
> bin/ycsb run hbase10 -P workloads/workloadb -p table=usertable -p
> columnfamily=family -p fieldcount=10 -p fieldlength=100 -p
> operationcount=2000 -p readallfields=true -p clientbuffering=true -p
> requestdistribution=zipfian -threads 10 -s
> log info
> 2016-11-02 20:20:20,261 ERROR
> [RW.default.readRpcServer.handler=36,queue=21,port=6020] bucket.BucketCache:
> Failed reading block fdcc7ed6f3b2498b9ef316cc8206c233_44819759 from bucket
> cache
> java.io.IOException: Invalid HFile block magic:
> \x00\x00\x00\x00\x00\x00\x00\x00
> at
> org.apache.hadoop.hbase.io.hfile.BlockType.parse(BlockType.java:154)
> at org.apache.hadoop.hbase.io.hfile.BlockType.read(BlockType.java:167)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock.(HFileBlock.java:273)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock$1.deserialize(HFileBlock.java:134)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock$1.deserialize(HFileBlock.java:121)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getBlock(BucketCache.java:427)
> at
> org.apache.hadoop.hbase.io.hfile.CombinedBlockCache.getBlock(CombinedBlockCache.java:85)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.getCachedBlock(HFileReaderV2.java:266)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:403)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:269)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:634)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:584)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:247)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:156)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:363)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:217)
> at
> org.apache.h
[jira] [Updated] (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 updated HBASE-18371: -- Attachment: hbase-18371_v3.patch Here is the rebased patch. > [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] [Commented] (HBASE-18371) [C++] Update folly and wangle dependencies
[ https://issues.apache.org/jira/browse/HBASE-18371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095524#comment-16095524 ] Xiaobing Zhou commented on HBASE-18371: --- Thanks [~enis] for the work. The patch v2 fails to be applied due to conflict, could you please have a rebase? > [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 > > > 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] [Commented] (HBASE-17738) BucketCache startup is slow
[ https://issues.apache.org/jira/browse/HBASE-17738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095514#comment-16095514 ] Hudson commented on HBASE-17738: FAILURE: Integrated in Jenkins build HBase-2.0 #207 (See [https://builds.apache.org/job/HBase-2.0/207/]) HBASE-17738 BucketCache startup is slow - addendum (Ram) (ramkrishna: rev e095d3964b6f8cb67d15f8fe2d7924cbc7c801ca) * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferArray.java * (edit) hbase-common/src/test/java/org/apache/hadoop/hbase/util/TestByteBufferArray.java > BucketCache startup is slow > --- > > Key: HBASE-17738 > URL: https://issues.apache.org/jira/browse/HBASE-17738 > Project: HBase > Issue Type: Sub-task > Components: BucketCache >Affects Versions: 2.0.0 >Reporter: stack >Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-17738_10.patch, HBASE-17738_11.patch, > HBASE-17738_2.patch, HBASE-17738_2.patch, HBASE-17738_3.patch, > HBASE-17738_4.patch, HBASE-17738_5_withoutUnsafe.patch, > HBASE-17738_6_withoutUnsafe.patch, HBASE-17738_8.patch, HBASE-17738_9.patch, > HBASE-17738_log.patch, HBASE-17738.patch > > > If you set bucketcache size at 64G say and then start hbase, it takes a long > time. Can we do the allocations in parallel and not inline with the server > startup? > Related, prefetching on a bucketcache is slow. Speed it up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-16993) BucketCache throw java.io.IOException: Invalid HFile block magic when configuring hbase.bucketcache.bucket.sizes
[
https://issues.apache.org/jira/browse/HBASE-16993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095515#comment-16095515
]
Hudson commented on HBASE-16993:
FAILURE: Integrated in Jenkins build HBase-2.0 #207 (See
[https://builds.apache.org/job/HBase-2.0/207/])
HBASE-16993 BucketCache throw java.io.IOException: Invalid HFile block
(anoopsamjohn: rev 8606cda3577542f1ce56de7af3671a61a12322a9)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestCacheConfig.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* (edit) hbase-common/src/main/resources/hbase-default.xml
> BucketCache throw java.io.IOException: Invalid HFile block magic when
> configuring hbase.bucketcache.bucket.sizes
>
>
> Key: HBASE-16993
> URL: https://issues.apache.org/jira/browse/HBASE-16993
> Project: HBase
> Issue Type: Bug
> Components: BucketCache
>Affects Versions: 1.1.3
> Environment: hbase version 1.1.3
>Reporter: liubangchen
>Assignee: Anoop Sam John
> Fix For: 3.0.0, 1.4.0, 1.5.0, 2.0.0-alpha-2
>
> Attachments: HBASE-16993.000.patch, HBASE-16993.001.patch,
> HBASE-16993_branch-1.patch, HBASE-16993.master.001.patch,
> HBASE-16993.master.002.patch, HBASE-16993.master.003.patch,
> HBASE-16993.master.004.patch, HBASE-16993.master.005.patch,
> HBASE-16993_V2.patch, HBASE-16993_V6.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> hbase-site.xml setting
>
> hbase.bucketcache.bucket.sizes
> 16384,32768,40960,
> 46000,49152,51200,65536,131072,524288
>
>
> hbase.bucketcache.size
> 16384
>
>
> hbase.bucketcache.ioengine
> offheap
>
>
> hfile.block.cache.size
> 0.3
>
>
> hfile.block.bloom.cacheonwrite
> true
>
>
> hbase.rs.cacheblocksonwrite
> true
>
>
> hfile.block.index.cacheonwrite
> true
> n_splits = 200
> create 'usertable',{NAME =>'family', COMPRESSION => 'snappy', VERSIONS =>
> 1,DATA_BLOCK_ENCODING => 'DIFF',CONFIGURATION =>
> {'hbase.hregion.memstore.block.multiplier' => 5}},{DURABILITY =>
> 'SKIP_WAL'},{SPLITS => (1..n_splits).map {|i|
> "user#{1000+i*(-1000)/n_splits}"}}
> load data
> bin/ycsb load hbase10 -P workloads/workloada -p table=usertable -p
> columnfamily=family -p fieldcount=10 -p fieldlength=100 -p
> recordcount=2 -p insertorder=hashed -p insertstart=0 -p
> clientbuffering=true -p durability=SKIP_WAL -threads 20 -s
> run
> bin/ycsb run hbase10 -P workloads/workloadb -p table=usertable -p
> columnfamily=family -p fieldcount=10 -p fieldlength=100 -p
> operationcount=2000 -p readallfields=true -p clientbuffering=true -p
> requestdistribution=zipfian -threads 10 -s
> log info
> 2016-11-02 20:20:20,261 ERROR
> [RW.default.readRpcServer.handler=36,queue=21,port=6020] bucket.BucketCache:
> Failed reading block fdcc7ed6f3b2498b9ef316cc8206c233_44819759 from bucket
> cache
> java.io.IOException: Invalid HFile block magic:
> \x00\x00\x00\x00\x00\x00\x00\x00
> at
> org.apache.hadoop.hbase.io.hfile.BlockType.parse(BlockType.java:154)
> at org.apache.hadoop.hbase.io.hfile.BlockType.read(BlockType.java:167)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock.(HFileBlock.java:273)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock$1.deserialize(HFileBlock.java:134)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlock$1.deserialize(HFileBlock.java:121)
> at
> org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getBlock(BucketCache.java:427)
> at
> org.apache.hadoop.hbase.io.hfile.CombinedBlockCache.getBlock(CombinedBlockCache.java:85)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.getCachedBlock(HFileReaderV2.java:266)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:403)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:269)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:634)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:584)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:247)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:156)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:363)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:217)
> at
> org.apache.hadoop.hbase.regionse
[jira] [Commented] (HBASE-18404) Small typo on ACID documentation page
[
https://issues.apache.org/jira/browse/HBASE-18404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095512#comment-16095512
]
Hadoop QA commented on HBASE-18404:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
41s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 32s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}153m
3s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}201m 28s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18404 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878235/HBASE-18404.patch |
| Optional Tests | asflicense javac javadoc unit xml |
| uname | Linux 26fd9e73e8a1 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 / bc93b66 |
| Default Java | 1.8.0_131 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7736/testReport/ |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7736/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Small typo on ACID documentation page
> -
>
> Key: HBASE-18404
> URL: https://issues.apache.org/jira/browse/HBASE-18404
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.3.1
>Reporter: Michael Crutcher
>Assignee: Coral
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-18404.patch
>
>
> I noticed a couple of occurrences of the "word" wholely on the ACID semantics
> doc page (https://hbase.apache.org/acid-semantics.html)
> This should be "wholly".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095508#comment-16095508 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.2-IT #903 (See [https://builds.apache.org/job/HBase-1.2-IT/903/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 933f4b33dc7102b5db99aea2fb05a9c9b0f70686) * (add) dev-support/Jenkinsfile * (edit) dev-support/docker/Dockerfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095504#comment-16095504 ] Hudson commented on HBASE-18147: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #142 (See [https://builds.apache.org/job/HBase-1.3-IT/142/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev b3a2a00aff1591bdec9b7c67691e1fce0ba0b4e3) * (add) dev-support/Jenkinsfile * (edit) dev-support/docker/Dockerfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- 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&focusedCommentId=16095502#comment-16095502
]
Hadoop QA commented on HBASE-18338:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-18338 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-18338 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878265/HBASE-18338.006.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7740/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> [C++] Implement RpcTestServer
> -
>
> Key: HBASE-18338
> URL: https://issues.apache.org/jira/browse/HBASE-18338
> Project: HBase
> Issue Type: Sub-task
>Reporter: Xiaobing Zhou
>Assignee: Xiaobing Zhou
> Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch,
> HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch,
> HBASE-18338.005.patch, HBASE-18338.006.patch
>
>
> This is a spin-off from HBASE-18078. We need RpcTestServer to simulate
> various communication scenarios, e.g. timeout, connection aborted, long
> running services and so on.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18427) minor cleanup around AssignmentManager
[ https://issues.apache.org/jira/browse/HBASE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18427: - Status: Patch Available (was: In Progress) > minor cleanup around AssignmentManager > -- > > Key: HBASE-18427 > URL: https://issues.apache.org/jira/browse/HBASE-18427 > Project: HBase > Issue Type: Bug > Components: amv2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Minor > Attachments: hbase-18427.master.001.patch > > > Minor cleanup around AssignmentManager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18427) minor cleanup around AssignmentManager
[ https://issues.apache.org/jira/browse/HBASE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18427: - Attachment: hbase-18427.master.001.patch > minor cleanup around AssignmentManager > -- > > Key: HBASE-18427 > URL: https://issues.apache.org/jira/browse/HBASE-18427 > Project: HBase > Issue Type: Bug > Components: amv2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Minor > Attachments: hbase-18427.master.001.patch > > > Minor cleanup around AssignmentManager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18163) rubocop and ruby-lint are not available
[
https://issues.apache.org/jira/browse/HBASE-18163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-18163.
-
Resolution: Duplicate
> rubocop and ruby-lint are not available
> ---
>
> Key: HBASE-18163
> URL: https://issues.apache.org/jira/browse/HBASE-18163
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Mike Drob
> Labels: beginner
>
> From the yetus output:
> {noformat}
> executable for 'rubocop' was not specified.
> executable for 'Ruby-lint' was not specified.
> {noformat}
> which results in this during the build
> | {color:blue}0{color} | {color:blue} rubocop {color} | {color:blue} 0m 11s
> {color} | {color:blue} rubocop was not available. {color} |
> | {color:blue}0{color} | {color:blue} ruby-lint {color} | {color:blue} 0m 11s
> {color} | {color:blue} Ruby-lint was not available. {color} |
> We should make those available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-18147: Resolution: Fixed Fix Version/s: 1.1.12 2.0.0-alpha-2 1.2.7 1.3.2 1.4.0 3.0.0 Status: Resolved (was: Patch Available) Pushed to all active branches. Thanks for the reviews! > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 3.0.0, 1.4.0, 1.3.2, 1.2.7, 2.0.0-alpha-2, 1.1.12 > > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095487#comment-16095487 ] Hudson commented on HBASE-18147: FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #204 (See [https://builds.apache.org/job/HBase-1.3-JDK7/204/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev b3a2a00aff1591bdec9b7c67691e1fce0ba0b4e3) * (edit) dev-support/docker/Dockerfile * (add) dev-support/Jenkinsfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095488#comment-16095488 ] Hudson commented on HBASE-18147: FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #170 (See [https://builds.apache.org/job/HBase-1.2-JDK7/170/]) HBASE-18147 POC jenkinsfile for nightly checks. (busbey: rev 933f4b33dc7102b5db99aea2fb05a9c9b0f70686) * (add) dev-support/Jenkinsfile * (edit) dev-support/docker/Dockerfile > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (HBASE-18427) minor cleanup around AssignmentManager
[ https://issues.apache.org/jira/browse/HBASE-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-18427 started by Umesh Agashe. > minor cleanup around AssignmentManager > -- > > Key: HBASE-18427 > URL: https://issues.apache.org/jira/browse/HBASE-18427 > Project: HBase > Issue Type: Bug > Components: amv2 >Reporter: Umesh Agashe >Assignee: Umesh Agashe >Priority: Minor > > Minor cleanup around AssignmentManager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18427) minor cleanup around AssignmentManager
Umesh Agashe created HBASE-18427: Summary: minor cleanup around AssignmentManager Key: HBASE-18427 URL: https://issues.apache.org/jira/browse/HBASE-18427 Project: HBase Issue Type: Bug Components: amv2 Reporter: Umesh Agashe Assignee: Umesh Agashe Priority: Minor Minor cleanup around AssignmentManager. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17908) Upgrade guava
[ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095478#comment-16095478 ] stack commented on HBASE-17908: --- .028 rebase and retry. Tests seem to pass locally. Remote JVMs went away. > Upgrade guava > - > > Key: HBASE-17908 > URL: https://issues.apache.org/jira/browse/HBASE-17908 > Project: HBase > Issue Type: Sub-task > Components: dependencies >Reporter: Balazs Meszaros >Assignee: stack >Priority: Critical > Fix For: 2.0.0 > > Attachments: 0001-HBASE-17908-Upgrade-guava.022.patch, > HBASE-17908.master.001.patch, HBASE-17908.master.002.patch, > HBASE-17908.master.003.patch, HBASE-17908.master.004.patch, > HBASE-17908.master.005.patch, HBASE-17908.master.006.patch, > HBASE-17908.master.007.patch, HBASE-17908.master.008.patch, > HBASE-17908.master.009.patch, HBASE-17908.master.010.patch, > HBASE-17908.master.011.patch, HBASE-17908.master.012.patch, > HBASE-17908.master.013.patch, HBASE-17908.master.013.patch, > HBASE-17908.master.014.patch, HBASE-17908.master.015.patch, > HBASE-17908.master.015.patch, HBASE-17908.master.016.patch, > HBASE-17908.master.017.patch, HBASE-17908.master.018.patch, > HBASE-17908.master.019.patch, HBASE-17908.master.020.patch, > HBASE-17908.master.021.patch, HBASE-17908.master.021.patch, > HBASE-17908.master.022.patch, HBASE-17908.master.023.patch, > HBASE-17908.master.024.patch, HBASE-17908.master.025.patch, > HBASE-17908.master.026.patch, HBASE-17908.master.027.patch, > HBASE-17908.master.028.patch > > > Currently we are using guava 12.0.1, but the latest version is 21.0. > Upgrading guava is always a hassle because it is not always backward > compatible with itself. > Currently I think there are to approaches: > 1. Upgrade guava to the newest version (21.0) and shade it. > 2. Upgrade guava to a version which does not break or builds (15.0). > If we can update it, some dependencies should be removed: > commons-collections, commons-codec, ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095476#comment-16095476 ] Sean Busbey commented on HBASE-18147: - filed HBASE-18426 to continue the handling of multiple jdks > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18426) nightly job should use independent stages to check supported jdks
Sean Busbey created HBASE-18426: --- Summary: nightly job should use independent stages to check supported jdks Key: HBASE-18426 URL: https://issues.apache.org/jira/browse/HBASE-18426 Project: HBase Issue Type: Improvement Components: community, test Reporter: Sean Busbey Assignee: Sean Busbey Priority: Critical follow on from HBASE-18147 to handle the lack of multijdk support for unit tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17908) Upgrade guava
[ https://issues.apache.org/jira/browse/HBASE-17908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-17908: -- Attachment: HBASE-17908.master.028.patch > Upgrade guava > - > > Key: HBASE-17908 > URL: https://issues.apache.org/jira/browse/HBASE-17908 > Project: HBase > Issue Type: Sub-task > Components: dependencies >Reporter: Balazs Meszaros >Assignee: stack >Priority: Critical > Fix For: 2.0.0 > > Attachments: 0001-HBASE-17908-Upgrade-guava.022.patch, > HBASE-17908.master.001.patch, HBASE-17908.master.002.patch, > HBASE-17908.master.003.patch, HBASE-17908.master.004.patch, > HBASE-17908.master.005.patch, HBASE-17908.master.006.patch, > HBASE-17908.master.007.patch, HBASE-17908.master.008.patch, > HBASE-17908.master.009.patch, HBASE-17908.master.010.patch, > HBASE-17908.master.011.patch, HBASE-17908.master.012.patch, > HBASE-17908.master.013.patch, HBASE-17908.master.013.patch, > HBASE-17908.master.014.patch, HBASE-17908.master.015.patch, > HBASE-17908.master.015.patch, HBASE-17908.master.016.patch, > HBASE-17908.master.017.patch, HBASE-17908.master.018.patch, > HBASE-17908.master.019.patch, HBASE-17908.master.020.patch, > HBASE-17908.master.021.patch, HBASE-17908.master.021.patch, > HBASE-17908.master.022.patch, HBASE-17908.master.023.patch, > HBASE-17908.master.024.patch, HBASE-17908.master.025.patch, > HBASE-17908.master.026.patch, HBASE-17908.master.027.patch, > HBASE-17908.master.028.patch > > > Currently we are using guava 12.0.1, but the latest version is 21.0. > Upgrading guava is always a hassle because it is not always backward > compatible with itself. > Currently I think there are to approaches: > 1. Upgrade guava to the newest version (21.0) and shade it. > 2. Upgrade guava to a version which does not break or builds (15.0). > If we can update it, some dependencies should be removed: > commons-collections, commons-codec, ... -- 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&focusedCommentId=16095472#comment-16095472 ] Xiaobing Zhou commented on HBASE-18338: --- Posted v6: # moved HBASE_CLIENT_RPC_TEST_MODE as suggested # did some code formatting. Simply passing IOBuf in and out in SaslHandler is tried, but RpcTestServer is not able to get any request. I'd debug this in follow up patch. Right now keep it as v5 is. Thanks for review [~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 > 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 > > > 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-18247) Hbck to fix the case that replica region shows as key in the meta table
[
https://issues.apache.org/jira/browse/HBASE-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095470#comment-16095470
]
Ted Yu commented on HBASE-18247:
lgtm
nit:
{code}
+locations.add(getRegionLocation(r, regionInfo, regionInfo.getReplicaId()));
+//locations.add(getRegionLocation(r, regionInfo, 0));
{code}
Drop the commented out line.
> Hbck to fix the case that replica region shows as key in the meta table
> ---
>
> Key: HBASE-18247
> URL: https://issues.apache.org/jira/browse/HBASE-18247
> Project: HBase
> Issue Type: Bug
> Components: hbck, Operability
>Affects Versions: 2.0.0-alpha-1
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0-alpha-2
>
> Attachments: HBASE-18247-branch-1.2-v001.patch
>
>
> Recently, we run into one case with read replica, the replica region shows up
> as key in meta table (it is not supposed to happen, we are still working on
> why it showed up in the meta table).
> However, hbck always reported the error about the primary region. Please see
> the error attached.
> {code}
> The entry in meta table
> test,92b0201b,1492546349354_0001.c3e6f235fe7caef75f8b0fb92a012da3.
> column=info:regioninfo, timestamp=1494958820573, value={ENCODED =>
> c3e6f235fe7caef75f8b0fb92a012da3, NAME =>
> 'test,92b0201b,1492546349354_0001.c3e6f235fe7caef75f8b0fb92a012da3.',
> STARTKEY => '92b0201b', ENDKEY => '92f1a952', REPLICA_ID => 1}
> ERROR: Region { meta =>
> test,92b0201b,1492546349354.d2c637715f31a072f174e70d407fb458., hdfs => null,
> deployed => , replicaId => 0 } found in META, but not in HDFS or deployed on
> any region server.
> {code}
> Traced the code, in the following line, it does not consider the case that
> replicaId in regionInfo could be non-default.
> https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L985
> If it is changed to get replicaId from regionInfo, then hbck should be able
> to fix this by "-fixMeta".
> {code}
> diff --git
> a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> index 9eb5111..1649e53 100644
> ---
> a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> +++
> b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
> @@ -982,7 +982,7 @@ public class MetaTableAccessor {
> List locations = new ArrayList<>(1);
> NavigableMap> familyMap =
> r.getNoVersionMap();
>
> -locations.add(getRegionLocation(r, regionInfo, 0));
> +locations.add(getRegionLocation(r, regionInfo,
> regionInfo.getReplicaId()));
>
> NavigableMap infoMap = familyMap.get(getCatalogFamily());
> if (infoMap == null) return new RegionLocations(locations);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18425) Fix TestMasterFailover
Vladimir Rodionov created HBASE-18425: - Summary: Fix TestMasterFailover Key: HBASE-18425 URL: https://issues.apache.org/jira/browse/HBASE-18425 Project: HBase Issue Type: Sub-task Reporter: Vladimir Rodionov Assignee: Vladimir Rodionov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18424) Fix TestAsyncTableGetMultiThreaded
Vladimir Rodionov created HBASE-18424: - Summary: Fix TestAsyncTableGetMultiThreaded Key: HBASE-18424 URL: https://issues.apache.org/jira/browse/HBASE-18424 Project: HBase Issue Type: Sub-task Reporter: Vladimir Rodionov Assignee: Vladimir Rodionov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-18338: -- Attachment: (was: HBASE-18338.006.patch) > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch, > HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch, > HBASE-18338.005.patch, HBASE-18338.006.patch > > > This is a spin-off from HBASE-18078. We need RpcTestServer to simulate > various communication scenarios, e.g. timeout, connection aborted, long > running services and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-18338: -- Attachment: HBASE-18338.006.patch > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch, > HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch, > HBASE-18338.005.patch, HBASE-18338.006.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-18338) [C++] Implement RpcTestServer
[
https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095469#comment-16095469
]
Hadoop QA commented on HBASE-18338:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-18338 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-18338 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878263/HBASE-18338.006.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7739/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> [C++] Implement RpcTestServer
> -
>
> Key: HBASE-18338
> URL: https://issues.apache.org/jira/browse/HBASE-18338
> Project: HBase
> Issue Type: Sub-task
>Reporter: Xiaobing Zhou
>Assignee: Xiaobing Zhou
> Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch,
> HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch,
> HBASE-18338.005.patch, HBASE-18338.006.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] [Created] (HBASE-18423) Fix TestMetaWithReplicas
Vladimir Rodionov created HBASE-18423: - Summary: Fix TestMetaWithReplicas Key: HBASE-18423 URL: https://issues.apache.org/jira/browse/HBASE-18423 Project: HBase Issue Type: Sub-task Reporter: Vladimir Rodionov Assignee: Vladimir Rodionov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18338) [C++] Implement RpcTestServer
[ https://issues.apache.org/jira/browse/HBASE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaobing Zhou updated HBASE-18338: -- Attachment: HBASE-18338.006.patch > [C++] Implement RpcTestServer > - > > Key: HBASE-18338 > URL: https://issues.apache.org/jira/browse/HBASE-18338 > Project: HBase > Issue Type: Sub-task >Reporter: Xiaobing Zhou >Assignee: Xiaobing Zhou > Attachments: HBASE-18338.000.patch, HBASE-18338.001.patch, > HBASE-18338.002.patch, HBASE-18338.003.patch, HBASE-18338.004.patch, > HBASE-18338.005.patch, HBASE-18338.006.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-18354) Fix TestMasterMetrics that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095467#comment-16095467 ] Vladimir Rodionov commented on HBASE-18354: --- Then ship it :) > Fix TestMasterMetrics that were disabled by Proc-V2 AM in HBASE-14614 > - > > Key: HBASE-18354 > URL: https://issues.apache.org/jira/browse/HBASE-18354 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > Attachments: HBASE-18354-v1.patch, HBASE-18354-v2.patch > > > With Core Proc-V2 AM change in HBASE-14614, stuff is different now around > startup which messes up the TestMasterMetrics test. HBASE-14614 disabled two > of three tests. > This JIRA tracks work to fix the disabled tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18422) Fix TestRegionRebalancing
Vladimir Rodionov created HBASE-18422: - Summary: Fix TestRegionRebalancing Key: HBASE-18422 URL: https://issues.apache.org/jira/browse/HBASE-18422 Project: HBase Issue Type: Sub-task Reporter: Vladimir Rodionov Assignee: Vladimir Rodionov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-18351) Fix tests that carry meta in Master that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reassigned HBASE-18351: - Assignee: Vladimir Rodionov > Fix tests that carry meta in Master that were disabled by Proc-V2 AM in > HBASE-14614 > --- > > Key: HBASE-18351 > URL: https://issues.apache.org/jira/browse/HBASE-18351 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > > The following tests were disabled as part of Core Proc-V2 AM in HBASE-14614 > - TestRegionRebalancing is disabled because doesn't consider the fact that > Master carries system tables only (fix of average in RegionStates brought out > the issue). > - Disabled testMetaAddressChange in TestMetaWithReplicas because presumes can > move meta... you can't > - TestAsyncTableGetMultiThreaded wants to move hbase:meta...Balancer does > NPEs. AMv2 won't let you move hbase:meta off Master. > - TestMasterFailover needs to be rewritten for AMv2. It uses tricks not > ordained when up on AMv2. The test is also hobbled by fact that we > religiously enforce that only master can carry meta, something we are lose > about in old AM > This JIRA is tracking the work to enable/modify them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18406) In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op
[ https://issues.apache.org/jira/browse/HBASE-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095461#comment-16095461 ] Umesh Agashe commented on HBASE-18406: -- ship it! [~syuanjiang], can you push this? > In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op > - > > Key: HBASE-18406 > URL: https://issues.apache.org/jira/browse/HBASE-18406 > Project: HBase > Issue Type: Bug >Reporter: Alex Leblang >Assignee: Alex Leblang > Attachments: HBASE-18406.master.001.patch, > HBASE-18406.master.002.patch > > > The comments above this method explain that it exists to set configs and > return, however, no configs are set in the method. > As you can see here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L210-L214 > > It is only ever called here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L142 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18357) Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-18357: -- Attachment: HBASE-18357-v1.patch > Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in > HBASE-14614 > > > Key: HBASE-18357 > URL: https://issues.apache.org/jira/browse/HBASE-18357 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > Attachments: HBASE-18357-v1.patch > > > The Core Proc-V2 AM change in HBASE-14614 disabled two tests inTestHCM: > testMulti and testRegionCaching > This JIRA tracks the work to enable them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095455#comment-16095455 ] Mike Drob commented on HBASE-18420: --- Oooh, was not expecting javadoc errors. Yea, let's take care of those. > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[
https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095446#comment-16095446
]
Hadoop QA commented on HBASE-18420:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
36m 21s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
12s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
22s{color} | {color:red} hbase-client generated 4 new + 0 unchanged - 0 fixed =
4 total (was 0) {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
54s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
7s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 49m 46s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-18420 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878247/HBASE-18420.v0.patch |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux 2a1642691f7c 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 / bc93b66 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC3 |
| javadoc |
https://builds.apache.org/job/PreCommit-HBASE-Build/7738/artifact/patchprocess/diff-javadoc-javadoc-hbase-client.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/7738/testReport/ |
| modules | C: hbase-client U: hbase-client |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7738/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Some methods of Admin don't use ColumnFamilyDescriptor
> --
>
> Key: HBASE-18420
>
[jira] [Commented] (HBASE-18354) Fix TestMasterMetrics that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095427#comment-16095427 ] Stephen Yuan Jiang commented on HBASE-18354: +1. Looks good to me. > Fix TestMasterMetrics that were disabled by Proc-V2 AM in HBASE-14614 > - > > Key: HBASE-18354 > URL: https://issues.apache.org/jira/browse/HBASE-18354 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > Attachments: HBASE-18354-v1.patch, HBASE-18354-v2.patch > > > With Core Proc-V2 AM change in HBASE-14614, stuff is different now around > startup which messes up the TestMasterMetrics test. HBASE-14614 disabled two > of three tests. > This JIRA tracks work to fix the disabled tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18086) Create native client which creates load on selected cluster
[ https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18086: --- Attachment: 18086.v18.txt w.r.t. total_rows parameter, since indices start with 0, passing FLAGS_num_rows-1 is fine. I have renamed the parameter to make it more readable. Streamlined the options for puts / appends / scans / gets where default value is true. The tool does puts, appends, scans and gets in separate rounds. > Create native client which creates load on selected cluster > --- > > Key: HBASE-18086 > URL: https://issues.apache.org/jira/browse/HBASE-18086 > Project: HBase > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: 18086.v11.txt, 18086.v12.txt, 18086.v14.txt, > 18086.v17.txt, 18086.v18.txt, 18086.v1.txt, 18086.v3.txt, 18086.v4.txt, > 18086.v5.txt, 18086.v6.txt, 18086.v7.txt, 18086.v8.txt > > > This task is to create a client which uses multiple threads to conduct Puts > followed by Gets against selected cluster. > Default is to run the tool against local cluster. > This would give us some idea on the characteristics of native client in terms > of handling high load. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18406) In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op
[ https://issues.apache.org/jira/browse/HBASE-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095406#comment-16095406 ] Alex Leblang commented on HBASE-18406: -- Ok, the latest patch keeps that logging line > In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op > - > > Key: HBASE-18406 > URL: https://issues.apache.org/jira/browse/HBASE-18406 > Project: HBase > Issue Type: Bug >Reporter: Alex Leblang >Assignee: Alex Leblang > Attachments: HBASE-18406.master.001.patch, > HBASE-18406.master.002.patch > > > The comments above this method explain that it exists to set configs and > return, however, no configs are set in the method. > As you can see here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L210-L214 > > It is only ever called here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L142 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18406) In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op
[ https://issues.apache.org/jira/browse/HBASE-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Leblang updated HBASE-18406: - Attachment: HBASE-18406.master.002.patch > In ServerCrashProcedure.java start(MasterProcedureEnv) is a no-op > - > > Key: HBASE-18406 > URL: https://issues.apache.org/jira/browse/HBASE-18406 > Project: HBase > Issue Type: Bug >Reporter: Alex Leblang >Assignee: Alex Leblang > Attachments: HBASE-18406.master.001.patch, > HBASE-18406.master.002.patch > > > The comments above this method explain that it exists to set configs and > return, however, no configs are set in the method. > As you can see here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L210-L214 > > It is only ever called here: > https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/ServerCrashProcedure.java#L142 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095397#comment-16095397 ] Chia-Ping Tsai commented on HBASE-18420: bq. How do we check for folks adding the wrong method signature going forward? The HTableDescriptor and HColumnDescriptor are declared as @Deprecated so the committers should be extra vigilant before committing. :( > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
[ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095373#comment-16095373 ] Alex Leblang commented on HBASE-18020: -- ping [~dimaspivak], would you mind taking a look to ensure that I've properly responded to your review? > Update API Compliance Checker to Incorporate Improvements Done in Hadoop > > > Key: HBASE-18020 > URL: https://issues.apache.org/jira/browse/HBASE-18020 > Project: HBase > Issue Type: Improvement > Components: API, community >Reporter: Alex Leblang >Assignee: Alex Leblang > Fix For: 2.0.0 > > Attachments: HBASE-18020.0.patch, HBASE-18020.branch-1.2.001.patch, > HBASE-18020.branch-1.2.002.patch, HBASE-18020.branch-1.2.003.patch, > HBASE-18020.branch-1.2.004.patch > > > Recently the Hadoop community has made a number of improvements in their api > compliance checker based on feedback from the hbase and kudu community. We > should adopt these changes ourselves. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095370#comment-16095370 ] Mike Drob commented on HBASE-18420: --- +1 assuming no QA issues. How do we check for folks adding the wrong method signature going forward? > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18357) Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095368#comment-16095368 ] Vladimir Rodionov edited comment on HBASE-18357 at 7/20/17 9:07 PM: Three tests fails: h5. TestClusterStatus The reason is described above: client connection is not getting periodic ClusterStatus notifications. This functionality is totally missing in 2.0. We can leave this test disabled or modify it to remove code which relied on this functionality h5. TestMulti Gets deadlocked in Admin.move because test configures RPC_HANDLER_COUNT to be equals to 1. One handler to Master is taken by test client and when RS tries to report Master Region state change it is get blocked. What we can do is to make all calls from RS to Master are HIGH priority calls or to change test case and set RPC_HANDLER_COUNT to a default value (one test in test suite relies on value of 1 though) h5. TestRegionCaching Fixed. Different semantics in 2.0 when call to a region fails due to stale info in a region cache and there is only one attempt. In pre-2.0 HBase did not do anything, in 2.0 HBase clears stale cache entry [~syuanjiang], [~devaraj] what do you think? was (Author: vrodionov): Three tests fails: h5. TestClusterStatus The reason is described above: client connection is not getting periodic ClusterStatus notifications. This functionality is totally missing in 2.0. We can leave this test disabled or modify it to remove code which relied on this functionality h5. TestMulti Gets deadlocked in Admin.move because test configures RPC_HANDLER_COUNT to be equals to 1. One handler to Master is taken by test client and when RS tries to report Master Region state change it is get blocked. What we can do is to make all calls from RS to Master are HIGH priority calls or to change test case and set RPC_HANDLER_COUNT to a default value (one test in test suite relies on vale of 1 though) h5. TestRegionCaching Fixed. Different semantics in 2.0 when call to a region fails due to stale info in a region cache and there is only one attempt. In pre-2.0 HBase did not do anything, in 2.0 HBase clears stale cache entry [~syuanjiang], [~devaraj] what do you think? > Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in > HBASE-14614 > > > Key: HBASE-18357 > URL: https://issues.apache.org/jira/browse/HBASE-18357 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > > The Core Proc-V2 AM change in HBASE-14614 disabled two tests inTestHCM: > testMulti and testRegionCaching > This JIRA tracks the work to enable them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18357) Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in HBASE-14614
[ https://issues.apache.org/jira/browse/HBASE-18357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095368#comment-16095368 ] Vladimir Rodionov commented on HBASE-18357: --- Three tests fails: h5. TestClusterStatus The reason is described above: client connection is not getting periodic ClusterStatus notifications. This functionality is totally missing in 2.0. We can leave this test disabled or modify it to remove code which relied on this functionality h5. TestMulti Gets deadlocked in Admin.move because test configures RPC_HANDLER_COUNT to be equals to 1. One handler to Master is taken by test client and when RS tries to report Master Region state change it is get blocked. What we can do is to make all calls from RS to Master are HIGH priority calls or to change test case and set RPC_HANDLER_COUNT to a default value (one test in test suite relies on vale of 1 though) h5. TestRegionCaching Fixed. Different semantics in 2.0 when call to a region fails due to stale info in a region cache and there is only one attempt. In pre-2.0 HBase did not do anything, in 2.0 HBase clears stale cache entry [~syuanjiang], [~devaraj] what do you think? > Enable disabled tests in TestHCM that were disabled by Proc-V2 AM in > HBASE-14614 > > > Key: HBASE-18357 > URL: https://issues.apache.org/jira/browse/HBASE-18357 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0-alpha-1 >Reporter: Stephen Yuan Jiang >Assignee: Vladimir Rodionov > > The Core Proc-V2 AM change in HBASE-14614 disabled two tests inTestHCM: > testMulti and testRegionCaching > This JIRA tracks the work to enable them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Attachment: HBASE-18420.v0.patch > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Status: Patch Available (was: Open) > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18420.v0.patch > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Fix Version/s: 2.0.0-alpha-2 3.0.0 > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Description: I overlooked them when committing HBASE-18241. Admin class ||Removed API||New API|| |modifyColumnFamily(TableName, HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| |modifyColumnFamilyAsync(TableName, HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, ColumnFamilyDescriptor)| |addColumnFamilyAsync(TableName, HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| These methods are introduced by HBASE-16519 and HBASE-1989. Both of them belong to 2.0 so we can change the input arguments without worrying about any compatibility issue. was: I overlooked them when committing HBASE-18241. Admin class ||Removed API||New API|| |modifyColumnFamily(TableName, HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| |modifyColumnFamilyAsync(TableName, HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, ColumnFamilyDescriptor)| |addColumnFamilyAsync(TableName, HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 3.0.0, 2.0.0-alpha-2 > > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > These methods are introduced by HBASE-16519 and HBASE-1989. Both of them > belong to 2.0 so we can change the input arguments without worrying about any > compatibility issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095361#comment-16095361 ] Josh Elser commented on HBASE-18147: bq. I'll presume you're fine with me fixing these on commit? shout if not. +1 > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18147) nightly job to check health of active branches
[ https://issues.apache.org/jira/browse/HBASE-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095356#comment-16095356 ] Sean Busbey commented on HBASE-18147: - I don't know if one is more stable than the other, but if ASF git goes down the rest of the job will fail, so no sense including a different thing that can break us. I'll presume you're fine with me fixing these on commit? shout if not. > nightly job to check health of active branches > -- > > Key: HBASE-18147 > URL: https://issues.apache.org/jira/browse/HBASE-18147 > Project: HBase > Issue Type: Test > Components: community, test >Reporter: Sean Busbey >Assignee: Sean Busbey > Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, > HBASE-18147.v1.patch > > > We should set up a job that runs Apache Yetus Test Patch's nightly mode. > Essentially, it produces a report that considers how the branch measures up > against the things we check in our precommit checks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18421) update hadoop prerequisites docs to call out 2.8.1
[ https://issues.apache.org/jira/browse/HBASE-18421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095350#comment-16095350 ] Sean Busbey commented on HBASE-18421: - I added a short link similar to the ones we've used for prior releases: https://s.apache.org/hadoop-2.8.1-announcement > update hadoop prerequisites docs to call out 2.8.1 > -- > > Key: HBASE-18421 > URL: https://issues.apache.org/jira/browse/HBASE-18421 > Project: HBase > Issue Type: Task > Components: community, dependencies, documentation >Reporter: Sean Busbey > > The Hadoop PMC has release 2.8.1 with the same "not ready for production" > caveat as 2.8.0 ([ref announce > email|https://lists.apache.org/thread.html/06609e491325c16debbdef4fbe8cecc6160b8909c06683c4805ad4af@%3Cgeneral.hadoop.apache.org%3E]) > We should update our docs proactively. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18421) update hadoop prerequisites docs to call out 2.8.1
Sean Busbey created HBASE-18421: --- Summary: update hadoop prerequisites docs to call out 2.8.1 Key: HBASE-18421 URL: https://issues.apache.org/jira/browse/HBASE-18421 Project: HBase Issue Type: Task Components: community, dependencies, documentation Reporter: Sean Busbey The Hadoop PMC has release 2.8.1 with the same "not ready for production" caveat as 2.8.0 ([ref announce email|https://lists.apache.org/thread.html/06609e491325c16debbdef4fbe8cecc6160b8909c06683c4805ad4af@%3Cgeneral.hadoop.apache.org%3E]) We should update our docs proactively. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18086) Create native client which creates load on selected cluster
[
https://issues.apache.org/jira/browse/HBASE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095266#comment-16095266
]
Ted Yu edited comment on HBASE-18086 at 7/20/17 8:47 PM:
-
bq. Why are we doing Deletes before Append / Increment?
Since Append / Increment is not idempotent, the delete calls were intended to
make successive runs quicker.
Otherwise, truncate_preserve command is involved which takes some time.
I will drop this in the next patch since append would write to the same row.
The table is created with the following clause:
{code}
SPLITS => ['0', '1', '2', '3', '4', '5', '6', '7', '8', '9']
{code}
With shifted region (along with unshifted region), more than one region is
involved for the multi-get requests.
w.r.t. simplifying verification logic, since integer written thru Increment has
unique format (e.g. \x00\x00\x00\x00\x00\x00\x00\x01), I want to see if there
is suggestion on how to detect that value of a Cell should be interpreted as
integer.
We may rely on the length of value since the value, being the column number,
wouldn't reach 8 bytes long (bounded by num_cols parameter).
was (Author: yuzhih...@gmail.com):
bq. Why are we doing Deletes before Append / Increment?
Since Append / Increment is not idempotent, the delete calls were intended to
make successive runs quicker.
Otherwise, truncate_preserve command is involved which takes some time.
I can drop this in the next patch.
The table is created with the following clause:
{code}
SPLITS => ['0', '1', '2', '3', '4', '5', '6', '7', '8', '9']
{code}
With shifted region (along with unshifted region), more than one region is
involved for the multi-get requests.
w.r.t. simplifying verification logic, since integer written thru Increment has
unique format (e.g. \x00\x00\x00\x00\x00\x00\x00\x01), I want to see if there
is suggestion on how to detect that value of a Cell should be interpreted as
integer.
We may rely on the length of value since the value, being the column number,
wouldn't reach 8 bytes long (bounded by num_cols parameter).
> Create native client which creates load on selected cluster
> ---
>
> Key: HBASE-18086
> URL: https://issues.apache.org/jira/browse/HBASE-18086
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 18086.v11.txt, 18086.v12.txt, 18086.v14.txt,
> 18086.v17.txt, 18086.v1.txt, 18086.v3.txt, 18086.v4.txt, 18086.v5.txt,
> 18086.v6.txt, 18086.v7.txt, 18086.v8.txt
>
>
> This task is to create a client which uses multiple threads to conduct Puts
> followed by Gets against selected cluster.
> Default is to run the tool against local cluster.
> This would give us some idea on the characteristics of native client in terms
> of handling high load.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Description: I overlooked them when committing HBASE-18241. Admin class ||Removed API||New API|| |modifyColumnFamily(TableName, HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| |modifyColumnFamilyAsync(TableName, HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, ColumnFamilyDescriptor)| |addColumnFamilyAsync(TableName, HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| was: I overlooked them when committing HBASE-18241. Admin class ||Removed APIs||New APIs|| |modifyColumnFamily(TableName, HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| |modifyColumnFamilyAsync(TableName, HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, ColumnFamilyDescriptor)| |addColumnFamilyAsync(TableName, HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed API||New API|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Description: I overlooked them when committing HBASE-18241. Admin class ||Removed APIs||New APIs|| |modifyColumnFamily(TableName, HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| |modifyColumnFamilyAsync(TableName, HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, ColumnFamilyDescriptor)| |addColumnFamilyAsync(TableName, HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| was: I overlooked them when committing HBASE-18241. Admin#modifyColumnFamily modifyColumnFamilyAsync > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > > I overlooked them when committing HBASE-18241. > Admin class > ||Removed APIs||New APIs|| > |modifyColumnFamily(TableName, > HColumnDescriptor)|modifyColumnFamily(TableName, ColumnFamilyDescriptor)| > |modifyColumnFamilyAsync(TableName, > HColumnDescriptor)|modifyColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| > |addColumnFamily(TableName, HColumnDescriptor)|addColumnFamily(TableName, > ColumnFamilyDescriptor)| > |addColumnFamilyAsync(TableName, > HColumnDescriptor)|addColumnFamilyAsync(TableName, ColumnFamilyDescriptor)| -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Description: I overlooked them when committing HBASE-18241. Admin#modifyColumnFamily modifyColumnFamilyAsync was:I overlooked them when committing HBASE-18241. > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > > I overlooked them when committing HBASE-18241. > Admin#modifyColumnFamily > modifyColumnFamilyAsync -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095337#comment-16095337
]
Chia-Ping Tsai commented on HBASE-18419:
see HBASE-18420
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
[ https://issues.apache.org/jira/browse/HBASE-18420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18420: --- Description: I overlooked them when committing HBASE-18241. > Some methods of Admin don't use ColumnFamilyDescriptor > -- > > Key: HBASE-18420 > URL: https://issues.apache.org/jira/browse/HBASE-18420 > Project: HBase > Issue Type: Bug >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > > I overlooked them when committing HBASE-18241. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-7386) Investigate providing some supervisor support for znode deletion
[
https://issues.apache.org/jira/browse/HBASE-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095330#comment-16095330
]
Hadoop QA commented on HBASE-7386:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
4s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} pylint {color} | {color:red} 0m
1s{color} | {color:red} The patch generated 6 new + 0 unchanged - 0 fixed = 6
total (was 0) {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m
7s{color} | {color:red} The patch generated 153 new + 489 unchanged - 9 fixed =
642 total (was 498) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 3 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
31m 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:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m
12s{color} | {color:red} The patch generated 2 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 32m 32s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:757bf37 |
| JIRA Issue | HBASE-7386 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12878238/HBASE-7386-master-00.patch
|
| Optional Tests | asflicense shellcheck shelldocs pylint |
| uname | Linux 1c2618903bc3 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 / bc93b66 |
| shellcheck | v0.4.6 |
| pylint | v1.7.2 |
| pylint |
https://builds.apache.org/job/PreCommit-HBASE-Build/7737/artifact/patchprocess/diff-patch-pylint.txt
|
| shellcheck |
https://builds.apache.org/job/PreCommit-HBASE-Build/7737/artifact/patchprocess/diff-patch-shellcheck.txt
|
| whitespace |
https://builds.apache.org/job/PreCommit-HBASE-Build/7737/artifact/patchprocess/whitespace-tabs.txt
|
| asflicense |
https://builds.apache.org/job/PreCommit-HBASE-Build/7737/artifact/patchprocess/patch-asflicense-problems.txt
|
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/7737/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Investigate providing some supervisor support for znode deletion
>
>
> Key: HBASE-7386
> URL: https://issues.apache.org/jira/browse/HBASE-7386
> Project: HBase
> Issue Type: Task
> Components: master, regionserver, scripts
>Reporter: Gregory Chanan
>Assignee: stack
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HBASE-7386-bin.patch, HBASE-7386-bin-v2.patch,
> HBASE-7386-bin-v3.patch, HBASE-7386-conf.patch, HBASE-7386-conf-v2.patch,
> HBASE-7386-conf-v3.patch, HBASE-7386-master-00.patch, HBASE-7386-src.patch,
> HBASE-7386-v0.patch, supervisordconfigs-v0.patch
>
>
> There a couple of JIRAs for deleting the znode on a process failure:
> HBASE-5844 (RS)
> HBASE-5926 (Master)
> which are pretty neat; on process failure, they delete the znode of the
> underlying process so HBase can recover faster.
> These JIRAs were implemented via the startup scripts; i.e. the script hangs
> around and waits for the process to exit, then deletes the znode.
> There are a few problems associated with this approach, as listed in the
> below JIRAs:
> 1) Hides startup output in script
> https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463401&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463401
> 2) two hbase processes listed per launched daemon
> https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409
> 3) Not run by a real supervisor
> https://issues.apache.org/jira/browse/HBASE-5844?focusedCommentId=13463409&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13463409
> 4) Weird output aft
[jira] [Created] (HBASE-18420) Some methods of Admin don't use ColumnFamilyDescriptor
Chia-Ping Tsai created HBASE-18420: -- Summary: Some methods of Admin don't use ColumnFamilyDescriptor Key: HBASE-18420 URL: https://issues.apache.org/jira/browse/HBASE-18420 Project: HBase Issue Type: Bug Reporter: Chia-Ping Tsai Assignee: Chia-Ping Tsai -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095327#comment-16095327
]
Chia-Ping Tsai commented on HBASE-18419:
bq. I think I can make the patch for this
okay. Thank you.
bq. but want to double check that the proper way to do this now would be:
You are right. But some methods of Admin don't use
ColumnFamilyDescriptor...That is my bad. I overlooked them when committing
HBASE-18241. Let me fix them first. Will create another jira.
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Chia-Ping Tsai
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reassigned HBASE-18419:
--
Assignee: Mike Drob (was: Chia-Ping Tsai)
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Mike Drob
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18403) [Shell]Truncate permission required
[ https://issues.apache.org/jira/browse/HBASE-18403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095315#comment-16095315 ] Sean Busbey commented on HBASE-18403: - If the current test framework won't let us make a non-superuser for the truncate command, then we could add this to the things we need to test with atleast a standalone instance ala HBASE-18417 > [Shell]Truncate permission required > --- > > Key: HBASE-18403 > URL: https://issues.apache.org/jira/browse/HBASE-18403 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Yun Zhao >Assignee: Yun Zhao >Priority: Trivial > Attachments: HBASE-18403.patch > > > When a user has only (Create) permission to execute truncate, the table will > be deleted and not re-created -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095314#comment-16095314
]
Mike Drob commented on HBASE-18419:
---
I think I can make the patch for this, but want to double check that the proper
way to do this now would be:
{code}
ColumnFamilyDescriptor cfd =
ColumnFamilyDescriptorBuilder.newBuilder(columnDescriptor)
.setMobEnabled(true)
.setMobThreshold((long) threshold)
.build();
admin.modifyColumnFamily(tableName, columnDescriptor);
{code}
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Chia-Ping Tsai
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reassigned HBASE-18419:
--
Assignee: Chia-Ping Tsai
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Assignee: Chia-Ping Tsai
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095284#comment-16095284
]
Mike Drob commented on HBASE-18419:
---
Ping [~chia7712] FYI
> IntegrationTestIngestWithMob fails in standalone mode
> -
>
> Key: HBASE-18419
> URL: https://issues.apache.org/jira/browse/HBASE-18419
> Project: HBase
> Issue Type: Bug
> Components: integration tests
>Affects Versions: 2.0.0-alpha-1
>Reporter: Mike Drob
>Priority: Critical
>
> When attempting to run ITIWM against a cluster I get the following error:
> {noformat}
> java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
> at
> org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
> at
> org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
> at
> org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18419) IntegrationTestIngestWithMob fails in standalone mode
Mike Drob created HBASE-18419:
-
Summary: IntegrationTestIngestWithMob fails in standalone mode
Key: HBASE-18419
URL: https://issues.apache.org/jira/browse/HBASE-18419
Project: HBase
Issue Type: Bug
Components: integration tests
Affects Versions: 2.0.0-alpha-1
Reporter: Mike Drob
Priority: Critical
When attempting to run ITIWM against a cluster I get the following error:
{noformat}
java.lang.UnsupportedOperationException: HColumnDescriptor is read-only
at
org.apache.hadoop.hbase.client.ImmutableHColumnDescriptor.getDelegateeForModification(ImmutableHColumnDescriptor.java:44)
at
org.apache.hadoop.hbase.HColumnDescriptor.setMobEnabled(HColumnDescriptor.java:735)
at
org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.initTable(IntegrationTestIngestWithMOB.java:122)
at
org.apache.hadoop.hbase.IntegrationTestIngest.setUpCluster(IntegrationTestIngest.java:92)
at
org.apache.hadoop.hbase.IntegrationTestBase.setUp(IntegrationTestBase.java:148)
at
org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:131)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at
org.apache.hadoop.hbase.IntegrationTestIngestWithMOB.main(IntegrationTestIngestWithMOB.java:153)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
