[jira] [Commented] (HBASE-20261) Table page (table.jsp) in Master UI does not show replicaIds for hbase meta table
[
https://issues.apache.org/jira/browse/HBASE-20261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412434#comment-16412434
]
Hudson commented on HBASE-20261:
Results for branch branch-2
[build #522 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Table page (table.jsp) in Master UI does not show replicaIds for hbase meta
> table
> -
>
> Key: HBASE-20261
> URL: https://issues.apache.org/jira/browse/HBASE-20261
> Project: HBase
> Issue Type: Bug
> Components: UI
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Minor
> Fix For: 1.5.0, 2.0.0
>
> Attachments: HBASE-20261.master.001.patch, Screen Shot 2018-03-23 at
> 12.05.27.png
>
>
> When region replication is enabled for hbase meta table, the table page
> (table.jsp) in Master UI does not show replicaIds for hbase meta table. It
> only shows the header:
> !Screen Shot 2018-03-23 at 12.05.27.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20245) HTrace commands do not work
[
https://issues.apache.org/jira/browse/HBASE-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412436#comment-16412436
]
Hudson commented on HBASE-20245:
Results for branch branch-2
[build #522 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> HTrace commands do not work
> ---
>
> Key: HBASE-20245
> URL: https://issues.apache.org/jira/browse/HBASE-20245
> Project: HBase
> Issue Type: Sub-task
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20245.master.001.patch
>
>
> When running shell-2.0 against server-2.0 we get the following error:
> {code}
> hbase(main):034:0> trace 'start'
> ERROR: undefined method `isTracing' for
> Java::OrgApacheHtraceCore::Tracer:Class
> {code}
> It is possible to manipulate tracing from shell-1.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-13300) Fix casing in getTimeStamp() and setTimestamp() for Mutations
[
https://issues.apache.org/jira/browse/HBASE-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412437#comment-16412437
]
Hudson commented on HBASE-13300:
Results for branch branch-2
[build #522 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Fix casing in getTimeStamp() and setTimestamp() for Mutations
> -
>
> Key: HBASE-13300
> URL: https://issues.apache.org/jira/browse/HBASE-13300
> Project: HBase
> Issue Type: Bug
> Components: API
>Affects Versions: 1.0.0
>Reporter: Lars George
>Assignee: Jan Hentschel
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-13300.branch-2.001.patch,
> HBASE-13300.branch-2.002.patch, HBASE-13300.branch-2.002.patch,
> HBASE-13300.master.001.patch, HBASE-13300.master.002.patch,
> HBASE-13300.master.003.patch, HBASE-13300.master.003.patch,
> HBASE-13300.master.004.patch, HBASE-13300.master.005.patch, HBASE-13300.xlsx
>
>
> For some reason we have two ways of writing this method. It should be
> consistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20135) NullPointerException during reading bloom filter when upgraded from hbase-1 to hbase-2
[
https://issues.apache.org/jira/browse/HBASE-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412435#comment-16412435
]
Hudson commented on HBASE-20135:
Results for branch branch-2
[build #522 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/522//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> NullPointerException during reading bloom filter when upgraded from hbase-1
> to hbase-2
> --
>
> Key: HBASE-20135
> URL: https://issues.apache.org/jira/browse/HBASE-20135
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Sakthi
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: hbase-20135.master.001.patch,
> hbase-20135.master.002.patch
>
>
> When upgraded from hbase-1 to hbase-2, found following exception logged
> multiple times in the log:
> {code:java}
> ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader: Error
> reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> java.io.IOException: Comparator class
> org.apache.hadoop.hbase.KeyValue$RawBytesComparator is not instantiable
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComparator(FixedFileTrailer.java:628)
> at
> org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(CompoundBloomFilter.java:79)
> at
> org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMeta(BloomFilterFactory.java:104)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBloomfilter(StoreFileReader.java:479)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreFile.java:425)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(HStoreFile.java:460)
> at
> org.apache.hadoop.hbase.regionserver.HStore.createStoreFileAndReader(HStore.java:671)
> at
> org.apache.hadoop.hbase.regionserver.HStore.lambda$openStoreFiles$0(HStore.java:537)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException{code}
>
> Analysis from [~anoop.hbase]:
> Checking the related code. There seems no issue.. We are not going
> to even fail reading the bloom. In 2.0 code base we expect the
> comparator class name to be null. But in 1.x we write old KV based
> Raw Bytes comparator class name. So reading that back, we will return
> class name as null and we get NPE it looks like.
> {code:java}
> else if
> (comparatorClassName.equals("org.apache.hadoop.hbase.KeyValue$RawBytesComparator")
> ||
> comparatorClassName.equals("org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator"))
> {
> // When the comparator to be used is Bytes.BYTES_RAWCOMPARATOR,
> we just return null from here
> // Bytes.BYTES_RAWCOMPARATOR is not a CellComparator
> comparatorKlass = null;
> }
> {code}
> We can better do a null check before trying the comparator class
> instantiation so that we can avoid this scary error logs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412429#comment-16412429
]
Hadoop QA commented on HBASE-20272:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
1s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.7.0/precommit-patchnames for
instructions. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
14s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
18m 4s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}115m
52s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
17s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}157m 6s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20272 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12916020/20272.v1.txt |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 84a8bbe736a1 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 64ccd2b295 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12116/testReport/ |
| Max. process+thread count | 4426 (vs. ulimit of 1) |
| modules |
[jira] [Commented] (HBASE-20264) Update Java prerequisite section with LTS rec and status of current GA JDKs
[ https://issues.apache.org/jira/browse/HBASE-20264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412420#comment-16412420 ] Zach York commented on HBASE-20264: --- | +|yes (but see tip about use with older Hadoop releases) I don't actually see a tip about older hadoop releases. Do you mean java releases? > Update Java prerequisite section with LTS rec and status of current GA JDKs > --- > > Key: HBASE-20264 > URL: https://issues.apache.org/jira/browse/HBASE-20264 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 1.5.0, 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Attachments: HBASE-20264.0.patch > > > Per the thread [\[DISCUSS\] strategy on Java > versions|https://lists.apache.org/thread.html/b7417aa8359e1beaa7caf47e8fa524296c499974e7467a541c6df415@%3Cdev.hbase.apache.org%3E] > * Add Java 9 and Java 10 to the support matrix as NT > * Add a NOTE to Java prereqs about "use a LTS version" > For now, leave out talk about planning for timelines on LTS additions or > dropping older JDK support. Once we get over the initial hurdle of prepping > for Java 11 we'll hopefully have enough info to know how realistic the things > talked about in the thread are and we can include a writeup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-15291) FileSystem not closed in secure bulkLoad
[ https://issues.apache.org/jira/browse/HBASE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412415#comment-16412415 ] Chia-Ping Tsai commented on HBASE-15291: Could we apply try-finally to #failedBulkLoad? Seems closeSrcFs is executed eventually > FileSystem not closed in secure bulkLoad > > > Key: HBASE-15291 > URL: https://issues.apache.org/jira/browse/HBASE-15291 > Project: HBase > Issue Type: Bug >Affects Versions: 1.0.2, 0.98.16.1 >Reporter: Yong Zhang >Assignee: Ashish Singhi >Priority: Major > Attachments: HBASE-15291-revert-master.patch, HBASE-15291.001.patch, > HBASE-15291.002.patch, HBASE-15291.003.patch, HBASE-15291.004.patch, > HBASE-15291.addendum, HBASE-15291.patch, patch > > > FileSystem not closed in secure bulkLoad after bulkLoad finish, it will > cause memory used more and more if too many bulkLoad . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19158) Ref guide needs upgrade update
[ https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412411#comment-16412411 ] Sean Busbey commented on HBASE-19158: - Okay, I think all the outstanding feedback has been captured either in new subtasks on HBASE-13428 or comments on existing subtasks. > Ref guide needs upgrade update > -- > > Key: HBASE-19158 > URL: https://issues.apache.org/jira/browse/HBASE-19158 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-beta-1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-19158.0.patch, HBASE-19158.1.patch, > HBASE-19158.2.patch > > > Our ref guide has lots of references in the upgrade section to obsolete > versions and no references to the 2.0.0-* releases. We should correct this > for beta-1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20279) [tooling] check for incompatible environment for HBase 2.0 upgrade
[
https://issues.apache.org/jira/browse/HBASE-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412410#comment-16412410
]
Sean Busbey commented on HBASE-20279:
-
maybe worth including the {{hbase upgrade}} command again? too confusing?
> [tooling] check for incompatible environment for HBase 2.0 upgrade
> --
>
> Key: HBASE-20279
> URL: https://issues.apache.org/jira/browse/HBASE-20279
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, tooling
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Critical
>
> from [~stack] on HBASE-19158:
> {quote}
> bq. Server failure. HBase can still read HFiles written in the older version
> 2 format.
> Need a script that user can run pre-upgrade.
> {quote}
> Additional commentary from [~busbey]
> In addition to the config check stack mentions, such a tool could check
> * other problematic configs, like those for master-hosts-regions
> * inconsistent configs due to changed defaults (I think we should have some
> smell-tests around the change in default for hbase.security.authorization)
> * (optionally) check for unreadable WALs
> * (optionally) check for unreadable hfiles
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20279) [tooling] check for incompatible environment for HBase 2.0 upgrade
Sean Busbey created HBASE-20279:
---
Summary: [tooling] check for incompatible environment for HBase
2.0 upgrade
Key: HBASE-20279
URL: https://issues.apache.org/jira/browse/HBASE-20279
Project: HBase
Issue Type: Sub-task
Components: documentation, tooling
Affects Versions: 2.0.0
Reporter: Sean Busbey
from [~stack] on HBASE-19158:
{quote}
bq. Server failure. HBase can still read HFiles written in the older version 2
format.
Need a script that user can run pre-upgrade.
{quote}
Additional commentary from [~busbey]
In addition to the config check stack mentions, such a tool could check
* other problematic configs, like those for master-hosts-regions
* inconsistent configs due to changed defaults (I think we should have some
smell-tests around the change in default for hbase.security.authorization)
* (optionally) check for unreadable WALs
* (optionally) check for unreadable hfiles
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412406#comment-16412406
]
Ted Yu commented on HBASE-20272:
Patch v2 removes the unnecessary table creation.
Test passes with v2 patch.
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20272:
---
Attachment: 20272.v2.txt
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt, 20272.v2.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20274) [DOC] additional metrics related changes for 2.0 upgrade section
[
https://issues.apache.org/jira/browse/HBASE-20274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412405#comment-16412405
]
Sean Busbey commented on HBASE-20274:
-
from [~stack] on HBASE-19158:
{quote}
I'm pretty sure our ops/second on master page has changed in nature. I need to
figure it and add to this metrics section.
{quote}
> [DOC] additional metrics related changes for 2.0 upgrade section
>
>
> Key: HBASE-20274
> URL: https://issues.apache.org/jira/browse/HBASE-20274
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Major
>
> Feedback on HBASE-19158 from [~md...@cloudera.com]
> {quote}
> Metrics:
> HBASE-17957
> {quote}
> If folks find others before this gets done, feel free to drop here in
> comments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20093) Replace ServerLoad by ServerMetrics for ServerManager
[
https://issues.apache.org/jira/browse/HBASE-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412404#comment-16412404
]
Chia-Ping Tsai commented on HBASE-20093:
{quote}Do you think this changed how we calculate the request per second in the
UI?
{quote}
How about using
[ServerMetrics#getRequestCountPerSecond|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/ServerMetrics.java#L38]
{quote}Just wondering. hbase2 does less requests, probably because it is
slower, but perhaps the change here made a difference too?
{quote}
All request count get smaller? I will check it later.
> Replace ServerLoad by ServerMetrics for ServerManager
> -
>
> Key: HBASE-20093
> URL: https://issues.apache.org/jira/browse/HBASE-20093
> Project: HBase
> Issue Type: Task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20093.addendum.patch, HBASE-20093.v0.patch,
> HBASE-20093.v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20278) [DOC] include ref guide updates for HBase 2.0 HBCK
Sean Busbey created HBASE-20278:
---
Summary: [DOC] include ref guide updates for HBase 2.0 HBCK
Key: HBASE-20278
URL: https://issues.apache.org/jira/browse/HBASE-20278
Project: HBase
Issue Type: Sub-task
Components: documentation, hbck
Affects Versions: 2.0.0
Reporter: Sean Busbey
Called out by [~stack] in HBASE-19158
{quote}
bq. HBCK tool from an earlier release against an HBase 2.0+ cluster will
destructively alter said cluster in unrecoverable ways.
Footnote or callout that says something like "Unfortunately we are unable to
distinguish an HBCK client so cannot put in place guards against destructive
HBCK changes." probably too much for this startup section on reread of
what I've written here.
bq. As of HBase 2.0, HBCK is a read-only tool that can report the status of
some non-public system internals. You should not rely on the format nor content
of these internals to remain consistent across HBase releases.
Ugh. We need HBCK2 and a pointer here to it. Will do in a follow-on.
{quote}
then update the upgrade section to point to the docs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-17730) [DOC] Migration to 2.0 for coprocessors
[
https://issues.apache.org/jira/browse/HBASE-17730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412403#comment-16412403
]
Sean Busbey commented on HBASE-17730:
-
notes from HBASE-19158 from [~mdrob]
{quote}
Coprocessors:
* HBASE-19408
* HBASE-19384
* HBASE-19134
* HBASE-19123
* HBASE-19077
* HBASE-19043
You already have a note about linking out to a coproc migration guide, so it's
fine to split these into a separate task, I'm just making notes here as I go
along.
{quote}
> [DOC] Migration to 2.0 for coprocessors
>
>
> Key: HBASE-17730
> URL: https://issues.apache.org/jira/browse/HBASE-17730
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, migration
>Reporter: Appy
>Priority: Blocker
> Fix For: 2.0.0
>
>
> Jiras breaking coprocessor compatibility should be marked with component '
> Coprocessor', and label 'incompatible'.
> Close to releasing 2.0, we should go through all such jiras and write down
> steps for migrating coprocessor easily.
> The idea is, it might be very hard to fix coprocessor breakages by reverse
> engineering errors, but will be easier we suggest easiest way to fix
> breakages resulting from each individual incompatible change.
> For eg. HBASE-17312 is incompatible change. It'll result in 100s of errors
> because BaseXXXObserver classes are gone and will probably result in a lot of
> confusion, but if we explicitly mention the fix which is just one line change
> - replace "Foo extends BaseXXXObserver" with "Foo implements XXXObserver" -
> it makes it very easy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20277) [DOC] appendix with guidance on updating applications for HBase 2
[
https://issues.apache.org/jira/browse/HBASE-20277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412401#comment-16412401
]
Sean Busbey commented on HBASE-20277:
-
Also this note from Mike should be incorporated here since it impacts
downstream folks who try to test stuff:
{quote}
Downstream Usage:
* HBASE-19410 using hbase-server-test-jar for starting mini cluster now also
needs hbase-zookeeper-test-jar
{quote}
> [DOC] appendix with guidance on updating applications for HBase 2
> -
>
> Key: HBASE-20277
> URL: https://issues.apache.org/jira/browse/HBASE-20277
> Project: HBase
> Issue Type: Sub-task
> Components: Client, documentation
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Major
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Classes/Methods moved:
> * HBASE-19425 (and subtasks) Put/Delete/Increment/Append
> * HBASE-19627 (and subtasks) Cell & Impl
> * HBASE-18978 (and subtasks) Async/Table
> * HBASE-18805 (and subtasks) Async/Admin
> * HBASE-14996 (and subtasks) Lots of misc changes
> * HBASE-13197 (and subtasks) Connection
> * HBASE-13844 KeyValue -> CellUtil
> * Maybe HBASE-19950 is worth calling out? Not really an upgrade issue though,
> but I know the old behavior of SCVF changed in a surprising way for the YARN
> ATS folks, when they were previously relying on what ended up being a bug.
> Could be mitigated by having a compatibility report, but would benefit from
> narrative messaging.
> Almost definitely need a blanket reminder that some deprecated APIs went away.
> {quote}
> from @busbey on HBASE-19158
> {quote}
> bq. * Classes/Methods moved:
> bq. * Almost definitely need a blanket reminder that some deprecated APIs
> went away.
> My intention was for both of these to be handled by this blurb:
> {code}
> +[[upgrade2.0.public.api]]
> +.Multiple breaking changes to source and binary compatibility for client API
> +The Java client API for HBase has a number of changes that break both source
> and binary compatibility for details see the Compatibility Check Report for
> the release you'll be upgrading to.
> +
> +
> +
> {code}
> I figure once we get an appendix that provides guidance on migrating an
> application from 1.x to 2.x we can also link to it.
> {quote}
> Get an appendix in place and then update the upgrade section as needed to
> draw attention to it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20277) [DOC] appendix with guidance on updating applications for HBase 2
[
https://issues.apache.org/jira/browse/HBASE-20277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20277:
Description:
Feedback from [~mdrob] on HBASE-19158:
{quote}
Classes/Methods moved:
* HBASE-19425 (and subtasks) Put/Delete/Increment/Append
* HBASE-19627 (and subtasks) Cell & Impl
* HBASE-18978 (and subtasks) Async/Table
* HBASE-18805 (and subtasks) Async/Admin
* HBASE-14996 (and subtasks) Lots of misc changes
* HBASE-13197 (and subtasks) Connection
* HBASE-13844 KeyValue -> CellUtil
* Maybe HBASE-19950 is worth calling out? Not really an upgrade issue though,
but I know the old behavior of SCVF changed in a surprising way for the YARN
ATS folks, when they were previously relying on what ended up being a bug.
Could be mitigated by having a compatibility report, but would benefit from
narrative messaging.
Almost definitely need a blanket reminder that some deprecated APIs went away.
{quote}
from @busbey on HBASE-19158
{quote}
bq. * Classes/Methods moved:
bq. * Almost definitely need a blanket reminder that some deprecated APIs went
away.
My intention was for both of these to be handled by this blurb:
{code}
+[[upgrade2.0.public.api]]
+.Multiple breaking changes to source and binary compatibility for client API
+The Java client API for HBase has a number of changes that break both source
and binary compatibility for details see the Compatibility Check Report for the
release you'll be upgrading to.
+
+
+
{code}
I figure once we get an appendix that provides guidance on migrating an
application from 1.x to 2.x we can also link to it.
{quote}
Get an appendix in place and then update the upgrade section as needed to draw
attention to it.
was:
Feedback from [~mdrob] on HBASE-19158:
{quote}
Classes/Methods moved:
* HBASE-19425 (and subtasks) Put/Delete/Increment/Append
* HBASE-19627 (and subtasks) Cell & Impl
* HBASE-18978 (and subtasks) Async/Table
* HBASE-18805 (and subtasks) Async/Admin
* HBASE-14996 (and subtasks) Lots of misc changes
* HBASE-13197 (and subtasks) Connection
* HBASE-13844 KeyValue -> CellUtil
* Maybe HBASE-19950 is worth calling out? Not really an upgrade issue though,
but I know the old behavior of SCVF changed in a surprising way for the YARN
ATS folks, when they were previously relying on what ended up being a bug.
Could be mitigated by having a compatibility report, but would benefit from
narrative messaging.
Almost definitely need a blanket reminder that some deprecated APIs went away.
{quote}
from @busbey on HBASE-19158
{quote}
{quote}
* Classes/Methods moved:
* Almost definitely need a blanket reminder that some deprecated APIs went away.
{quote}
My intention was for both of these to be handled by this blurb:
{quote}
+[[upgrade2.0.public.api]]
+.Multiple breaking changes to source and binary compatibility for client API
+The Java client API for HBase has a number of changes that break both source
and binary compatibility for details see the Compatibility Check Report for the
release you'll be upgrading to.
+
+
+
{quote}
I figure once we get an appendix that provides guidance on migrating an
application from 1.x to 2.x we can also link to it.
{quote}
Get an appendix in place and then update the upgrade section as needed to draw
attention to it.
> [DOC] appendix with guidance on updating applications for HBase 2
> -
>
> Key: HBASE-20277
> URL: https://issues.apache.org/jira/browse/HBASE-20277
> Project: HBase
> Issue Type: Sub-task
> Components: Client, documentation
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Major
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Classes/Methods moved:
> * HBASE-19425 (and subtasks) Put/Delete/Increment/Append
> * HBASE-19627 (and subtasks) Cell & Impl
> * HBASE-18978 (and subtasks) Async/Table
> * HBASE-18805 (and subtasks) Async/Admin
> * HBASE-14996 (and subtasks) Lots of misc changes
> * HBASE-13197 (and subtasks) Connection
> * HBASE-13844 KeyValue -> CellUtil
> * Maybe HBASE-19950 is worth calling out? Not really an upgrade issue though,
> but I know the old behavior of SCVF changed in a surprising way for the YARN
> ATS folks, when they were previously relying on what ended up being a bug.
> Could be mitigated by having a compatibility report, but would benefit from
> narrative messaging.
> Almost definitely need a blanket reminder that some deprecated APIs went away.
> {quote}
> from @busbey on HBASE-19158
> {quote}
> bq. * Classes/Methods moved:
> bq. * Almost definitely need a blanket reminder that some deprecated APIs
> went away.
> My intention was for both of these to be handled by this blurb:
> {code}
> +[[upgrade2.0.public.api]]
> +.Multiple breaking changes to source and binary compatibility for client API
> +The Java
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412400#comment-16412400
]
Duo Zhang commented on HBASE-20272:
---
Does it still pass if you just remove the creation? Seems getTable.get() will
always use the TABLE_NAME...
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20277) [DOC] appendix with guidance on updating applications for HBase 2
Sean Busbey created HBASE-20277:
---
Summary: [DOC] appendix with guidance on updating applications for
HBase 2
Key: HBASE-20277
URL: https://issues.apache.org/jira/browse/HBASE-20277
Project: HBase
Issue Type: Sub-task
Components: Client, documentation
Affects Versions: 2.0.0
Reporter: Sean Busbey
Feedback from [~mdrob] on HBASE-19158:
{quote}
Classes/Methods moved:
* HBASE-19425 (and subtasks) Put/Delete/Increment/Append
* HBASE-19627 (and subtasks) Cell & Impl
* HBASE-18978 (and subtasks) Async/Table
* HBASE-18805 (and subtasks) Async/Admin
* HBASE-14996 (and subtasks) Lots of misc changes
* HBASE-13197 (and subtasks) Connection
* HBASE-13844 KeyValue -> CellUtil
* Maybe HBASE-19950 is worth calling out? Not really an upgrade issue though,
but I know the old behavior of SCVF changed in a surprising way for the YARN
ATS folks, when they were previously relying on what ended up being a bug.
Could be mitigated by having a compatibility report, but would benefit from
narrative messaging.
Almost definitely need a blanket reminder that some deprecated APIs went away.
{quote}
from @busbey on HBASE-19158
{quote}
{quote}
* Classes/Methods moved:
* Almost definitely need a blanket reminder that some deprecated APIs went away.
{quote}
My intention was for both of these to be handled by this blurb:
{quote}
+[[upgrade2.0.public.api]]
+.Multiple breaking changes to source and binary compatibility for client API
+The Java client API for HBase has a number of changes that break both source
and binary compatibility for details see the Compatibility Check Report for the
release you'll be upgrading to.
+
+
+
{quote}
I figure once we get an appendix that provides guidance on migrating an
application from 1.x to 2.x we can also link to it.
{quote}
Get an appendix in place and then update the upgrade section as needed to draw
attention to it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20276) [shell] confirm shell REPL change and document
[
https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20276:
Fix Version/s: (was: 1.4.3)
1.4.4
> [shell] confirm shell REPL change and document
> --
>
> Key: HBASE-20276
> URL: https://issues.apache.org/jira/browse/HBASE-20276
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, shell
>Affects Versions: 1.4.0, 2.0.0
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.4.4, 2.0.0
>
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Shell:
> HBASE-19770. There was another issue opened where this was identified as a
> problem so maybe the shape will change further, but I can't find it now.
> {quote}
> New commentary from [~busbey]:
> This was a follow on to HBASE-15965. That change effectively makes it so none
> of our ruby wrappers can be used to build expressions in an interactive REPL.
> This is a pretty severe change (most of my tips on HBASE-15611 will break, I
> think).
> I think we should
> a) Have a DISCUSS thread, spanning dev@ and user@
> b) based on the outcome of that thread, either default to the new behavior or
> the old behavior
> c) if we keep the HBASE-15965 behavior as the default, flag it as
> incompatible, call it out in the hbase 2.0 upgrade section, and update docs
> (two examples: the output in the shell_exercises sections would be wrong, and
> the _table_variables section won't work)
> d) In either case document the new flag in the ref guide
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20276) [shell] confirm shell REPL change and document
[
https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20276:
Affects Version/s: 1.4.0
> [shell] confirm shell REPL change and document
> --
>
> Key: HBASE-20276
> URL: https://issues.apache.org/jira/browse/HBASE-20276
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, shell
>Affects Versions: 1.4.0, 2.0.0
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.4.3, 2.0.0
>
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Shell:
> HBASE-19770. There was another issue opened where this was identified as a
> problem so maybe the shape will change further, but I can't find it now.
> {quote}
> New commentary from [~busbey]:
> This was a follow on to HBASE-15965. That change effectively makes it so none
> of our ruby wrappers can be used to build expressions in an interactive REPL.
> This is a pretty severe change (most of my tips on HBASE-15611 will break, I
> think).
> I think we should
> a) Have a DISCUSS thread, spanning dev@ and user@
> b) based on the outcome of that thread, either default to the new behavior or
> the old behavior
> c) if we keep the HBASE-15965 behavior as the default, flag it as
> incompatible, call it out in the hbase 2.0 upgrade section, and update docs
> (two examples: the output in the shell_exercises sections would be wrong, and
> the _table_variables section won't work)
> d) In either case document the new flag in the ref guide
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20276) [shell] confirm shell REPL change and document
[
https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20276:
Fix Version/s: 1.4.3
> [shell] confirm shell REPL change and document
> --
>
> Key: HBASE-20276
> URL: https://issues.apache.org/jira/browse/HBASE-20276
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, shell
>Affects Versions: 1.4.0, 2.0.0
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 1.4.3, 2.0.0
>
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Shell:
> HBASE-19770. There was another issue opened where this was identified as a
> problem so maybe the shape will change further, but I can't find it now.
> {quote}
> New commentary from [~busbey]:
> This was a follow on to HBASE-15965. That change effectively makes it so none
> of our ruby wrappers can be used to build expressions in an interactive REPL.
> This is a pretty severe change (most of my tips on HBASE-15611 will break, I
> think).
> I think we should
> a) Have a DISCUSS thread, spanning dev@ and user@
> b) based on the outcome of that thread, either default to the new behavior or
> the old behavior
> c) if we keep the HBASE-15965 behavior as the default, flag it as
> incompatible, call it out in the hbase 2.0 upgrade section, and update docs
> (two examples: the output in the shell_exercises sections would be wrong, and
> the _table_variables section won't work)
> d) In either case document the new flag in the ref guide
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20276) [shell] confirm shell REPL change and document
[
https://issues.apache.org/jira/browse/HBASE-20276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412397#comment-16412397
]
Sean Busbey commented on HBASE-20276:
-
Additional complication, HBASE-15965 made it into release 1.4.0 and HBASE-19770
is in 1.4.2. :(
> [shell] confirm shell REPL change and document
> --
>
> Key: HBASE-20276
> URL: https://issues.apache.org/jira/browse/HBASE-20276
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0
>
>
> Feedback from [~mdrob] on HBASE-19158:
> {quote}
> Shell:
> HBASE-19770. There was another issue opened where this was identified as a
> problem so maybe the shape will change further, but I can't find it now.
> {quote}
> New commentary from [~busbey]:
> This was a follow on to HBASE-15965. That change effectively makes it so none
> of our ruby wrappers can be used to build expressions in an interactive REPL.
> This is a pretty severe change (most of my tips on HBASE-15611 will break, I
> think).
> I think we should
> a) Have a DISCUSS thread, spanning dev@ and user@
> b) based on the outcome of that thread, either default to the new behavior or
> the old behavior
> c) if we keep the HBASE-15965 behavior as the default, flag it as
> incompatible, call it out in the hbase 2.0 upgrade section, and update docs
> (two examples: the output in the shell_exercises sections would be wrong, and
> the _table_variables section won't work)
> d) In either case document the new flag in the ref guide
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20276) [shell] confirm shell REPL change and document
Sean Busbey created HBASE-20276:
---
Summary: [shell] confirm shell REPL change and document
Key: HBASE-20276
URL: https://issues.apache.org/jira/browse/HBASE-20276
Project: HBase
Issue Type: Sub-task
Components: documentation, shell
Affects Versions: 2.0.0
Reporter: Sean Busbey
Fix For: 2.0.0
Feedback from [~mdrob] on HBASE-19158:
{quote}
Shell:
HBASE-19770. There was another issue opened where this was identified as a
problem so maybe the shape will change further, but I can't find it now.
{quote}
New commentary from [~busbey]:
This was a follow on to HBASE-15965. That change effectively makes it so none
of our ruby wrappers can be used to build expressions in an interactive REPL.
This is a pretty severe change (most of my tips on HBASE-15611 will break, I
think).
I think we should
a) Have a DISCUSS thread, spanning dev@ and user@
b) based on the outcome of that thread, either default to the new behavior or
the old behavior
c) if we keep the HBASE-15965 behavior as the default, flag it as
incompatible, call it out in the hbase 2.0 upgrade section, and update docs
(two examples: the output in the shell_exercises sections would be wrong, and
the _table_variables section won't work)
d) In either case document the new flag in the ref guide
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20227) Add UT for ReplicationUtils.contains method
[
https://issues.apache.org/jira/browse/HBASE-20227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412395#comment-16412395
]
Hadoop QA commented on HBASE-20227:
---
| (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:red}-1{color} | {color:red} patch {color} | {color:red} 0m 2s{color}
| {color:red} HBASE-20227 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20227 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12916027/HBASE-20227.master.003.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12117/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Add UT for ReplicationUtils.contains method
> ---
>
> Key: HBASE-20227
> URL: https://issues.apache.org/jira/browse/HBASE-20227
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
>Reporter: Duo Zhang
>Assignee: Jingyun Tian
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20227.master.001.patch,
> HBASE-20227.master.002.patch, HBASE-20227.master.003.patch
>
>
> The method is extracted from NamespaceTableCfWALEntryFilter. But
> NamespaceTableCfWALEntryFilter is in the hbase-server module so the UTs which
> tests the function of this method are also in the hbase-server module. If
> later we modify ReplicationUtils.contains without touching any code in
> hbase-server, then we will not run the UTs for this method and may introduce
> bugs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20275) [DOC] clarify impact to hfile command from HBASE-17197
Sean Busbey created HBASE-20275:
---
Summary: [DOC] clarify impact to hfile command from HBASE-17197
Key: HBASE-20275
URL: https://issues.apache.org/jira/browse/HBASE-20275
Project: HBase
Issue Type: Sub-task
Components: documentation, tooling
Affects Versions: 2.0.0
Reporter: Sean Busbey
Feedback on HBASE-19158 from [~mdrob]
{quote}
Tools:
HBASE-17197
{quote}
It's not clear to me from the patch on HBASE-17197 if this was actually a
change that needs to be called out. So tasks:
1) Figure out if the {{hfile}} command args from HBase 1.y still works
2) Update the title of HBASE-17197 to match what the change in the jira ended
up being
3) If hfile changed in an incompatible way, add it to the upgrade section and
make sure the refguide section "hfile_tool" is up to date.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20274) [DOC] additional metrics related changes for 2.0 upgrade section
Sean Busbey created HBASE-20274:
---
Summary: [DOC] additional metrics related changes for 2.0 upgrade
section
Key: HBASE-20274
URL: https://issues.apache.org/jira/browse/HBASE-20274
Project: HBase
Issue Type: Sub-task
Components: documentation
Affects Versions: 2.0.0
Reporter: Sean Busbey
Feedback on HBASE-19158 from [~md...@cloudera.com]
{quote}
Metrics:
HBASE-17957
{quote}
If folks find others before this gets done, feel free to drop here in comments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-13631) Migration from 0.94 to 2.0.0
[ https://issues.apache.org/jira/browse/HBASE-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-13631: Fix Version/s: (was: 2.0.0-beta-1) (was: 2.0.0) > Migration from 0.94 to 2.0.0 > > > Key: HBASE-13631 > URL: https://issues.apache.org/jira/browse/HBASE-13631 > Project: HBase > Issue Type: Sub-task > Components: migration >Reporter: Anoop Sam John >Priority: Blocker > > We have HFile V2 (minor version-2) only in 0.94 and 2.0 needs HFile V3 with > minor version 3 atleast. We can test and document clearly the path of upgrade > from 94.x to 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20273) [DOC] include call out of additional changed config defaults in 2.0 upgrade
Sean Busbey created HBASE-20273:
---
Summary: [DOC] include call out of additional changed config
defaults in 2.0 upgrade
Key: HBASE-20273
URL: https://issues.apache.org/jira/browse/HBASE-20273
Project: HBase
Issue Type: Sub-task
Components: documentation
Affects Versions: 2.0.0
Reporter: Sean Busbey
Copied from feedback on HBASE-19158 from [~mdrob]:
{quote}
Default settings/configuration properties changed/renamed:
HBASE-19919
HBASE-19148
HBASE-18307
HBASE-17314
HBASE-15784
HBASE-15027
HBASE-14906
HBASE-14521
{quote}
More detail later from [~mdrob]:
{quote}
would like to see notes that:
hbase.master.cleaner.interval changed from 1 min to 10 min
MasterProcedureConstants.MASTER_PROCEDURE_THREADS defaults to CPU/4 instead of
CPU
hbase.rpc.server.nativetransport renamed to hbase.netty.nativetransport
hbase.netty.rpc.server.worker.count renamed to base.netty.worker.count
hbase.hfile.compactions.discharger.interval renamed to
hbase.hfile.compaction.discharger.interval
hbase.hregion.percolumnfamilyflush.size.lower.bound removed at site level, but
can still be applied at table level
hbase.client.reties.number now counts the total number of retries, not the
total number of tries
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20227) Add UT for ReplicationUtils.contains method
[ https://issues.apache.org/jira/browse/HBASE-20227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20227: - Attachment: HBASE-20227.master.003.patch > Add UT for ReplicationUtils.contains method > --- > > Key: HBASE-20227 > URL: https://issues.apache.org/jira/browse/HBASE-20227 > Project: HBase > Issue Type: Sub-task > Components: Replication >Reporter: Duo Zhang >Assignee: Jingyun Tian >Priority: Major > Fix For: 3.0.0 > > Attachments: HBASE-20227.master.001.patch, > HBASE-20227.master.002.patch, HBASE-20227.master.003.patch > > > The method is extracted from NamespaceTableCfWALEntryFilter. But > NamespaceTableCfWALEntryFilter is in the hbase-server module so the UTs which > tests the function of this method are also in the hbase-server module. If > later we modify ReplicationUtils.contains without touching any code in > hbase-server, then we will not run the UTs for this method and may introduce > bugs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-15291) FileSystem not closed in secure bulkLoad
[ https://issues.apache.org/jira/browse/HBASE-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412372#comment-16412372 ] Ashish Singhi commented on HBASE-15291: --- Can I get more reviews here, please... > FileSystem not closed in secure bulkLoad > > > Key: HBASE-15291 > URL: https://issues.apache.org/jira/browse/HBASE-15291 > Project: HBase > Issue Type: Bug >Affects Versions: 1.0.2, 0.98.16.1 >Reporter: Yong Zhang >Assignee: Ashish Singhi >Priority: Major > Attachments: HBASE-15291-revert-master.patch, HBASE-15291.001.patch, > HBASE-15291.002.patch, HBASE-15291.003.patch, HBASE-15291.004.patch, > HBASE-15291.addendum, HBASE-15291.patch, patch > > > FileSystem not closed in secure bulkLoad after bulkLoad finish, it will > cause memory used more and more if too many bulkLoad . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412356#comment-16412356
]
Ted Yu commented on HBASE-20272:
With the patch, the test finishes without error.
[~chia7712]:
Mind taking a look ?
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20272:
---
Attachment: 20272.v1.txt
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
[
https://issues.apache.org/jira/browse/HBASE-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20272:
---
Status: Patch Available (was: Open)
> TestAsyncTable#testCheckAndMutateWithTimeRange fails due to
> TableExistsException
>
>
> Key: HBASE-20272
> URL: https://issues.apache.org/jira/browse/HBASE-20272
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20272.v1.txt
>
>
> The following test failure is reproducible:
> {code}
> org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
> at
> org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
> at
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
> at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
> {code}
> The cause was that TestAsyncTable is parameterized while the
> testCheckAndMutateWithTimeRange uses the same table name without dropping the
> table after the first invocation finishes.
> This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20272) TestAsyncTable#testCheckAndMutateWithTimeRange fails due to TableExistsException
Ted Yu created HBASE-20272:
--
Summary: TestAsyncTable#testCheckAndMutateWithTimeRange fails due
to TableExistsException
Key: HBASE-20272
URL: https://issues.apache.org/jira/browse/HBASE-20272
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
The following test failure is reproducible:
{code}
org.apache.hadoop.hbase.TableExistsException: testCheckAndMutateWithTimeRange
at
org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.prepareCreate(CreateTableProcedure.java:233)
at
org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:87)
at
org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:51)
at
org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:184)
at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1453)
{code}
The cause was that TestAsyncTable is parameterized while the
testCheckAndMutateWithTimeRange uses the same table name without dropping the
table after the first invocation finishes.
This leads to second invocation failing with TableExistsException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412343#comment-16412343
]
Sakthi commented on HBASE-20270:
I have tested the patch manually by building a tar and testing out the shell by
trying erroneous steps like the one Sean mentioned in the description & also
tried to put value into a non-existent column family.
The 'help' message was no longer being displayed. If there could be a better
way to test this, I would be happy to try.
[~mdrob] , Could you please review it?
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: hbase-20270.master.001.patch
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20175) hbase-spark needs scala dependency convergance
[
https://issues.apache.org/jira/browse/HBASE-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412332#comment-16412332
]
Hadoop QA commented on HBASE-20175:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
25s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 9m
38s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
12s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
6s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
17m 20s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
29s{color} | {color:green} hbase-spark 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} 37m 53s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20175 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12916010/HBASE-20175.v01.patch
|
| Optional Tests | asflicense javac javadoc unit shadedjars hadoopcheck
xml compile |
| uname | Linux 1855bb5a4ff6 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20
11:50:30 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 64ccd2b295 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12115/testReport/ |
| Max. process+thread count | 935 (vs. ulimit of 1) |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12115/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> hbase-spark needs scala dependency convergance
> --
>
> Key: HBASE-20175
> URL: https://issues.apache.org/jira/browse/HBASE-20175
> Project: HBase
> Issue Type: Bug
> Components: dependencies, spark
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Attachments: HBASE-20175.v01.patch
>
>
> This is a follow-on to HBASE-16179 - I think we
[jira] [Created] (HBASE-20271) TestReplicaWithCluster.testReplicaAndReplication sometimes fails when calling setWALPosition
Duo Zhang created HBASE-20271:
-
Summary: TestReplicaWithCluster.testReplicaAndReplication
sometimes fails when calling setWALPosition
Key: HBASE-20271
URL: https://issues.apache.org/jira/browse/HBASE-20271
Project: HBase
Issue Type: Bug
Reporter: Duo Zhang
{noformat}
2018-03-24 08:29:29,965 ERROR
[RS_REFRESH_PEER-regionserver/ubuntu:0-0.replicationSource,2.replicationSource.shipperubuntu%2C35197%2C1521851267085,2]
helpers.MarkerIgnoringBase(159): * ABORTING region server
ubuntu,35197,1521851267085: Failed to operate on replication queue *
org.apache.hadoop.hbase.replication.ReplicationException: Failed to set log
position (serverName=ubuntu,35197,1521851267085, queueId=2,
fileName=ubuntu%2C35197%2C1521851267085.1521851344947, position=2533)
at
org.apache.hadoop.hbase.replication.ZKReplicationQueueStorage.setWALPosition(ZKReplicationQueueStorage.java:237)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.lambda$9(ReplicationSourceManager.java:488)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.abortWhenFail(ReplicationSourceManager.java:455)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.logPositionAndCleanOldLogs(ReplicationSourceManager.java:488)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.updateLogPosition(ReplicationSourceShipper.java:232)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.shipEdits(ReplicationSourceShipper.java:134)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:104)
Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
KeeperErrorCode = NoNode
at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
at org.apache.zookeeper.ZooKeeper.multiInternal(ZooKeeper.java:1006)
at org.apache.zookeeper.ZooKeeper.multi(ZooKeeper.java:910)
at
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.multi(RecoverableZooKeeper.java:663)
at
org.apache.hadoop.hbase.zookeeper.ZKUtil.multiOrSequential(ZKUtil.java:1670)
at
org.apache.hadoop.hbase.replication.ZKReplicationQueueStorage.setWALPosition(ZKReplicationQueueStorage.java:235)
... 6 more
2018-03-24 08:29:30,025 ERROR
[RpcServer.default.FPBQ.Fifo.handler=2,queue=0,port=37509]
master.MasterRpcServices(508): Region server ubuntu,35197,1521851267085
reported a fatal error:
* ABORTING region server ubuntu,35197,1521851267085: Failed to operate on
replication queue *
Cause:
org.apache.hadoop.hbase.replication.ReplicationException: Failed to set log
position (serverName=ubuntu,35197,1521851267085, queueId=2,
fileName=ubuntu%2C35197%2C1521851267085.1521851344947, position=2533)
at
org.apache.hadoop.hbase.replication.ZKReplicationQueueStorage.setWALPosition(ZKReplicationQueueStorage.java:237)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.lambda$9(ReplicationSourceManager.java:488)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.abortWhenFail(ReplicationSourceManager.java:455)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.logPositionAndCleanOldLogs(ReplicationSourceManager.java:488)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.updateLogPosition(ReplicationSourceShipper.java:232)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.shipEdits(ReplicationSourceShipper.java:134)
at
org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceShipper.run(ReplicationSourceShipper.java:104)
Caused by: org.apache.zookeeper.KeeperException$NoNodeException:
KeeperErrorCode = NoNode
at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
at org.apache.zookeeper.ZooKeeper.multiInternal(ZooKeeper.java:1006)
at org.apache.zookeeper.ZooKeeper.multi(ZooKeeper.java:910)
at
org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.multi(RecoverableZooKeeper.java:663)
at
org.apache.hadoop.hbase.zookeeper.ZKUtil.multiOrSequential(ZKUtil.java:1670)
at
org.apache.hadoop.hbase.replication.ZKReplicationQueueStorage.setWALPosition(ZKReplicationQueueStorage.java:235)
... 6 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18785) Blocker doc issues
[ https://issues.apache.org/jira/browse/HBASE-18785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412312#comment-16412312 ] stack commented on HBASE-18785: --- WARNING TO ADD: "Make sure Distributed Log Replay is not enabled on your hbase1 cluster; it was problematic in hbase1 and does not work at all in hbase2." > Blocker doc issues > -- > > Key: HBASE-18785 > URL: https://issues.apache.org/jira/browse/HBASE-18785 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Blocker > Fix For: 2.0.0 > > > Hang blocker documentation issues off this one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-13300) Fix casing in getTimeStamp() and setTimestamp() for Mutations
[ https://issues.apache.org/jira/browse/HBASE-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13300: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-2.0+ > Fix casing in getTimeStamp() and setTimestamp() for Mutations > - > > Key: HBASE-13300 > URL: https://issues.apache.org/jira/browse/HBASE-13300 > Project: HBase > Issue Type: Bug > Components: API >Affects Versions: 1.0.0 >Reporter: Lars George >Assignee: Jan Hentschel >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-13300.branch-2.001.patch, > HBASE-13300.branch-2.002.patch, HBASE-13300.branch-2.002.patch, > HBASE-13300.master.001.patch, HBASE-13300.master.002.patch, > HBASE-13300.master.003.patch, HBASE-13300.master.003.patch, > HBASE-13300.master.004.patch, HBASE-13300.master.005.patch, HBASE-13300.xlsx > > > For some reason we have two ways of writing this method. It should be > consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412296#comment-16412296
]
Duo Zhang commented on HBASE-20269:
---
Fine. So there must be other problem which causes the
testRegionReplicaReplicationIgnoresDroppedTables to fail.
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412295#comment-16412295
]
Ted Yu commented on HBASE-20269:
The check doesn't have to be added - without it, the ZKUtil.multiOrSequential
is a NoOp if the list is empty.
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412285#comment-16412285
]
Duo Zhang commented on HBASE-20269:
---
Why resolved?
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20093) Replace ServerLoad by ServerMetrics for ServerManager
[ https://issues.apache.org/jira/browse/HBASE-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412287#comment-16412287 ] stack commented on HBASE-20093: --- [~chia7712] Do you think this changed how we calculate the request per second in the UI? Just wondering. hbase2 does less requests, probably because it is slower, but perhaps the change here made a difference too? Just asking. Thanks. > Replace ServerLoad by ServerMetrics for ServerManager > - > > Key: HBASE-20093 > URL: https://issues.apache.org/jira/browse/HBASE-20093 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai >Priority: Major > Fix For: 2.0.0 > > Attachments: HBASE-20093.addendum.patch, HBASE-20093.v0.patch, > HBASE-20093.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412280#comment-16412280
]
Hadoop QA commented on HBASE-20270:
---
| (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:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
33s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} rubocop {color} | {color:red} 0m
4s{color} | {color:red} The patch generated 2 new + 27 unchanged - 2 fixed = 29
total (was 29) {color} |
| {color:green}+1{color} | {color:green} ruby-lint {color} | {color:green} 0m
0s{color} | {color:green} The patch generated 0 new + 13 unchanged - 1 fixed =
13 total (was 14) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 12m
34s{color} | {color:green} hbase-shell in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
9s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 0s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20270 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915999/hbase-20270.master.001.patch
|
| Optional Tests | asflicense javac javadoc unit rubocop ruby_lint |
| uname | Linux 7a37000c4324 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12
21:23:04 UTC 2018 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 / b8f999bf33 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| rubocop | v0.54.0 |
| rubocop |
https://builds.apache.org/job/PreCommit-HBASE-Build/12114/artifact/patchprocess/diff-patch-rubocop.txt
|
| ruby-lint | v2.3.1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12114/testReport/ |
| Max. process+thread count | 2375 (vs. ulimit of 1) |
| modules | C: hbase-shell U: hbase-shell |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12114/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: hbase-20270.master.001.patch
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of
[jira] [Commented] (HBASE-13300) Fix casing in getTimeStamp() and setTimestamp() for Mutations
[
https://issues.apache.org/jira/browse/HBASE-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412277#comment-16412277
]
Hadoop QA commented on HBASE-13300:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color: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 12 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
28s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
5s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
15s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 4m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 4m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
32s{color} | {color:green} hbase-client: The patch generated 0 new + 418
unchanged - 1 fixed = 418 total (was 419) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
11s{color} | {color:green} hbase-server: The patch generated 0 new + 426
unchanged - 17 fixed = 426 total (was 443) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
16s{color} | {color:green} The patch hbase-mapreduce passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s{color} | {color:green} The patch hbase-thrift passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} The patch hbase-examples passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
15s{color} | {color:green} The patch hbase-rest passed checkstyle {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
42s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
19m 30s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 6m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
1s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
5s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}109m
25s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 11m
32s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
|
[jira] [Updated] (HBASE-20245) HTrace commands do not work
[
https://issues.apache.org/jira/browse/HBASE-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20245:
--
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
Status: Resolved (was: Patch Available)
Pushed to branch-2.0.+
> HTrace commands do not work
> ---
>
> Key: HBASE-20245
> URL: https://issues.apache.org/jira/browse/HBASE-20245
> Project: HBase
> Issue Type: Sub-task
>Reporter: Balazs Meszaros
>Assignee: Balazs Meszaros
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20245.master.001.patch
>
>
> When running shell-2.0 against server-2.0 we get the following error:
> {code}
> hbase(main):034:0> trace 'start'
> ERROR: undefined method `isTracing' for
> Java::OrgApacheHtraceCore::Tracer:Class
> {code}
> It is possible to manipulate tracing from shell-1.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18269) Jython docs out of date
[
https://issues.apache.org/jira/browse/HBASE-18269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412264#comment-16412264
]
Artem Ervits commented on HBASE-18269:
--
[~mdrob] ping
> Jython docs out of date
> ---
>
> Key: HBASE-18269
> URL: https://issues.apache.org/jira/browse/HBASE-18269
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Affects Versions: 1.3.1, 1.2.6, 1.5.0, 1.4.2, 2.0.0
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Labels: beginner
> Attachments: HBASE-18269.v01.patch, HBASE-18269.v02.patch
>
>
> The documentation describing how to launch Jython + HBase is out of date. -
> https://hbase.apache.org/book.html#jython
> First, we would set the classpath differently:
> {noformat}
> HBASE_CLASSPATH=/home/hbase/jython.jar bin/hbase org.python.util.jython
> {noformat}
> Then, the actual code example is out of date too:
> {noformat}
> >>> desc = HTableDescriptor(tablename)
> >>> desc.addFamily(HColumnDescriptor("content:"))
> Traceback (most recent call last):
> File "", line 1, in
> at
> org.apache.hadoop.hbase.HColumnDescriptor.isLegalFamilyName(HColumnDescriptor.java:566)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:470)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:425)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:390)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:338)
> at
> org.apache.hadoop.hbase.HColumnDescriptor.(HColumnDescriptor.java:327)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> org.python.core.PyReflectedConstructor.constructProxy(PyReflectedConstructor.java:211)
> {noformat}
> We should make sure that the examples we claim are runnable actually are.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20175) hbase-spark needs scala dependency convergance
[
https://issues.apache.org/jira/browse/HBASE-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412259#comment-16412259
]
Artem Ervits commented on HBASE-20175:
--
[~mdrob] furthermore, if you prefer the exclusion method, here's a fix for that
{code:java}
scalatest_${scala.binary.version}
2.2.4
test
+
+
+ org.scala-lang
+ scala-library
+
+
org.scalamock
scalamock-scalatest-support_${scala.binary.version}
3.1.4
test
+
+
+ org.scala-lang
+ scala-library
+
+
com.fasterxml.jackson.module{code}
let me know which one you prefer
> hbase-spark needs scala dependency convergance
> --
>
> Key: HBASE-20175
> URL: https://issues.apache.org/jira/browse/HBASE-20175
> Project: HBase
> Issue Type: Bug
> Components: dependencies, spark
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Attachments: HBASE-20175.v01.patch
>
>
> This is a follow-on to HBASE-16179 - I think we might need to specify an
> exclude in the dependency management.
> {noformat}
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> hbase-spark ---
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> {noformat}
> [~tedyu] - since you're already fiddling in this area, do you want to take a
> look?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-16848) Usage for show_peer_tableCFs command doesn't include peer
[
https://issues.apache.org/jira/browse/HBASE-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412261#comment-16412261
]
Hudson commented on HBASE-16848:
Results for branch branch-1.2
[build #276 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/276/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/276//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/276//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/276//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Usage for show_peer_tableCFs command doesn't include peer
> -
>
> Key: HBASE-16848
> URL: https://issues.apache.org/jira/browse/HBASE-16848
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Peter Somogyi
>Priority: Minor
> Labels: documentation, replication, shell
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
> Attachments: HBASE-16848.master.001.patch,
> HBASE-16848.master.001.patch
>
>
> {code}
> hbase(main):003:0> show_peer_tableCFs
> ERROR: wrong number of arguments (0 for 1)
> Here is some help for this command:
> Show replicable table-cf config for the specified peer.
> hbase> show_peer_tableCFs
> {code}
> The sample usage should include peer id.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20175) hbase-spark needs scala dependency convergance
[
https://issues.apache.org/jira/browse/HBASE-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Ervits updated HBASE-20175:
-
Status: Patch Available (was: Open)
[~mdrob] [~yuzhih...@gmail.com] please review, bumping scalatest won't work,
found version 3.0.2 I believe had compatible scala.version but it brought in
more dependencies with incompatible versions. major.minor versions of Scala are
guaranteed to be backwards compatible as of Scala 2.10. This patch supresses
the warning.
> hbase-spark needs scala dependency convergance
> --
>
> Key: HBASE-20175
> URL: https://issues.apache.org/jira/browse/HBASE-20175
> Project: HBase
> Issue Type: Bug
> Components: dependencies, spark
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Attachments: HBASE-20175.v01.patch
>
>
> This is a follow-on to HBASE-16179 - I think we might need to specify an
> exclude in the dependency management.
> {noformat}
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> hbase-spark ---
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> {noformat}
> [~tedyu] - since you're already fiddling in this area, do you want to take a
> look?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20175) hbase-spark needs scala dependency convergance
[
https://issues.apache.org/jira/browse/HBASE-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Ervits updated HBASE-20175:
-
Attachment: HBASE-20175.v01.patch
> hbase-spark needs scala dependency convergance
> --
>
> Key: HBASE-20175
> URL: https://issues.apache.org/jira/browse/HBASE-20175
> Project: HBase
> Issue Type: Bug
> Components: dependencies, spark
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
> Attachments: HBASE-20175.v01.patch
>
>
> This is a follow-on to HBASE-16179 - I think we might need to specify an
> exclude in the dependency management.
> {noformat}
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> hbase-spark ---
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> {noformat}
> [~tedyu] - since you're already fiddling in this area, do you want to take a
> look?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-20175) hbase-spark needs scala dependency convergance
[
https://issues.apache.org/jira/browse/HBASE-20175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Ervits reassigned HBASE-20175:
Assignee: Artem Ervits
> hbase-spark needs scala dependency convergance
> --
>
> Key: HBASE-20175
> URL: https://issues.apache.org/jira/browse/HBASE-20175
> Project: HBase
> Issue Type: Bug
> Components: dependencies, spark
>Reporter: Mike Drob
>Assignee: Artem Ervits
>Priority: Major
>
> This is a follow-on to HBASE-16179 - I think we might need to specify an
> exclude in the dependency management.
> {noformat}
> [INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @
> hbase-spark ---
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> {noformat}
> [~tedyu] - since you're already fiddling in this area, do you want to take a
> look?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20267) Fix for warning multiple versions of scala libraries detected
[
https://issues.apache.org/jira/browse/HBASE-20267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Ervits updated HBASE-20267:
-
Resolution: Duplicate
Status: Resolved (was: Patch Available)
Duplicate of https://issues.apache.org/jira/browse/HBASE-20175
> Fix for warning multiple versions of scala libraries detected
> -
>
> Key: HBASE-20267
> URL: https://issues.apache.org/jira/browse/HBASE-20267
> Project: HBase
> Issue Type: Bug
> Environment: last revision: ad47c2daf4d9dc3b85ec91e0fe8385aa6dd9c492
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T14:49:05-05:00)
> Maven home: /opt/apache-maven-3.5.3
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: HBASE-20267.v01.patch
>
>
> {code:java}
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> [WARNING] Multiple versions of scala libraries detected!{code}
> as of Scala 2.10 all major.minor versions are backwards compatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19504) Add TimeRange support into checkAndMutate
[
https://issues.apache.org/jira/browse/HBASE-19504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412243#comment-16412243
]
Hudson commented on HBASE-19504:
Results for branch branch-2.0
[build #80 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Add TimeRange support into checkAndMutate
> -
>
> Key: HBASE-19504
> URL: https://issues.apache.org/jira/browse/HBASE-19504
> Project: HBase
> Issue Type: New Feature
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-19504.v0.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-16848) Usage for show_peer_tableCFs command doesn't include peer
[
https://issues.apache.org/jira/browse/HBASE-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412242#comment-16412242
]
Hudson commented on HBASE-16848:
Results for branch branch-2.0
[build #80 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/80//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Usage for show_peer_tableCFs command doesn't include peer
> -
>
> Key: HBASE-16848
> URL: https://issues.apache.org/jira/browse/HBASE-16848
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Peter Somogyi
>Priority: Minor
> Labels: documentation, replication, shell
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
> Attachments: HBASE-16848.master.001.patch,
> HBASE-16848.master.001.patch
>
>
> {code}
> hbase(main):003:0> show_peer_tableCFs
> ERROR: wrong number of arguments (0 for 1)
> Here is some help for this command:
> Show replicable table-cf config for the specified peer.
> hbase> show_peer_tableCFs
> {code}
> The sample usage should include peer id.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20257) hbase-spark should not depend on com.google.code.findbugs.jsr305
[
https://issues.apache.org/jira/browse/HBASE-20257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412241#comment-16412241
]
Artem Ervits commented on HBASE-20257:
--
[~busbey]
I did the following:
1) removed the dependency
2) added exclusion to hadoop-common:test-jar
3) ran `mvn clean test` on the hbase-spark module with no failures
Let me know if you need anything else
> hbase-spark should not depend on com.google.code.findbugs.jsr305
>
>
> Key: HBASE-20257
> URL: https://issues.apache.org/jira/browse/HBASE-20257
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 3.0.0
>Reporter: Ted Yu
>Assignee: Artem Ervits
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-20257.v01.patch
>
>
> The following can be observed in the build output of master branch:
> {code}
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
> Here is related snippet from hbase-spark/pom.xml:
> {code}
>
> com.google.code.findbugs
> jsr305
> {code}
> Dependency on jsr305 should be dropped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19258) IntegrationTest for Backup and Restore
[
https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412240#comment-16412240
]
Hadoop QA commented on HBASE-19258:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
30s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
15s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
24s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 29s{color}
| {color:red} hbase-it generated 2 new + 51 unchanged - 0 fixed = 53 total (was
51) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
47s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
20m 20s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 7m 45s{color}
| {color:red} hbase-backup in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
58s{color} | {color:green} hbase-it in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 51m 1s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.backup.TestBackupHFileCleaner |
| | hadoop.hbase.backup.TestBackupSmallTests |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19258 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915980/HBASE-19258.v3.patch |
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux dc0bd7603020 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12
21:23:04 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision
[jira] [Commented] (HBASE-16848) Usage for show_peer_tableCFs command doesn't include peer
[
https://issues.apache.org/jira/browse/HBASE-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412238#comment-16412238
]
Hudson commented on HBASE-16848:
Results for branch branch-2
[build #521 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Usage for show_peer_tableCFs command doesn't include peer
> -
>
> Key: HBASE-16848
> URL: https://issues.apache.org/jira/browse/HBASE-16848
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Peter Somogyi
>Priority: Minor
> Labels: documentation, replication, shell
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
> Attachments: HBASE-16848.master.001.patch,
> HBASE-16848.master.001.patch
>
>
> {code}
> hbase(main):003:0> show_peer_tableCFs
> ERROR: wrong number of arguments (0 for 1)
> Here is some help for this command:
> Show replicable table-cf config for the specified peer.
> hbase> show_peer_tableCFs
> {code}
> The sample usage should include peer id.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19504) Add TimeRange support into checkAndMutate
[
https://issues.apache.org/jira/browse/HBASE-19504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412239#comment-16412239
]
Hudson commented on HBASE-19504:
Results for branch branch-2
[build #521 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/521//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Add TimeRange support into checkAndMutate
> -
>
> Key: HBASE-19504
> URL: https://issues.apache.org/jira/browse/HBASE-19504
> Project: HBase
> Issue Type: New Feature
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-19504.v0.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20269:
---
Resolution: Later
Status: Resolved (was: Patch Available)
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19681) Online snapshot creation failing with missing store file
[
https://issues.apache.org/jira/browse/HBASE-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1641#comment-1641
]
Saad Mufti commented on HBASE-19681:
We are facing the exact same situation in HBase 1.4.0 on AWS EMR based HBase.
Anyone have any potential recovery process? We haven't tried restart but we
migrated the region using the "assign" command in the shell that moved the
region but the problems persists. We have also seen the exception in both the
snapshot thread and compaction thread.
> Online snapshot creation failing with missing store file
>
>
> Key: HBASE-19681
> URL: https://issues.apache.org/jira/browse/HBASE-19681
> Project: HBase
> Issue Type: Bug
> Components: backuprestore, Performance, scaling, snapshots
>Affects Versions: 1.3.0
> Environment: Hadoop - 2.7.3
> HBase 1.3.0
> OS - GNU/Linux x86_64
> Cluster - Amazon Elastic Mapreduce
>Reporter: Anirban Roy
>Priority: Major
> Attachments: region-server-missing file-log.doc,
> region-server-snapshot-exception-log.doc
>
>
> We are facing problem creating online snapshot of our HBase table. The table
> contains 20TB data and receiving ~1 writes per second. The snapshot
> creating failing intermittently with error that some hfile missing, see the
> detailed output below. Once we locate the region server hosting the region
> and restart the region server, snapshot creation succeeds. It seems the
> missing hfile removed due to minor compaction, but region server still holds
> the pointer to the file.
> [hadoop@ip-10-0-12-164 ~]$ hbase shell
> HBase Shell; enter 'help' for list of supported commands.
> Type "exit" to leave the HBase Shell
> Version 1.3.0, rUnknown, Fri Feb 17 18:15:07 UTC 2017
>
> hbase(main):001:0> snapshot ‘x_table’, ‘x_snapshot’
>
> ERROR: org.apache.hadoop.hbase.snapshot.HBaseSnapshotException: Snapshot {
> ss=x_snapshot table=x_table type=FLUSH } had an error. Procedure x_snapshot
> { waiting=[] done=[ip-10-0-9-31.ec2.internal,16020,1508372578254,
> ip-10-0-0-32.ec2.internal,16020,1508372591059,
> ip-10-0-14-221.ec2.internal,16020,1508372580873,
> ip-10-0-15-185.ec2.internal,16020,1508372588507,
> ip-10-0-9-43.ec2.internal,16020,1508372569107,
> ip-10-0-10-62.ec2.internal,16020,1512885921693,
> ip-10-0-8-216.ec2.internal,16020,1508372584133,
> ip-10-0-1-207.ec2.internal,16020,1508372580144,
> ip-10-0-0-173.ec2.internal,16020,1508372584969,
> ip-10-0-4-79.ec2.internal,16020,1508372587161,
> ip-10-0-3-165.ec2.internal,16020,1508372593566,
> ip-10-0-14-137.ec2.internal,16020,1508372583225,
> ip-10-0-6-33.ec2.internal,16020,1508372581587,
> ip-10-0-15-199.ec2.internal,16020,1508372587478,
> ip-10-0-5-253.ec2.internal,16020,1508372581243,
> ip-10-0-1-99.ec2.internal,16020,1508372609684] }
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:354)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.isSnapshotDone(MasterRpcServices.java:1058)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:61089)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2328)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:188)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:168)
> Caused by:
> org.apache.hadoop.hbase.errorhandling.ForeignException$ProxyThrowable via
> ip-10-0-3-13.ec2.internal,16020,1508372563772:org.apache.hadoop.hbase.errorhandling.ForeignException$ProxyThrowable:
> java.io.FileNotFoundException: File does not exist:
> hdfs://ip-10-0-12-164.ec2.internal:8020/user/hbase/data/default/x_table/ecbb3aeaf7c5b1f65742deab5812362c/d/f76d8827c29244b99bf9344982956523
> at
> org.apache.hadoop.hbase.errorhandling.ForeignExceptionDispatcher.rethrowException(ForeignExceptionDispatcher.java:83)
> at
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler.rethrowExceptionIfFailed(TakeSnapshotHandler.java:315)
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:344)
> ... 6 more
> Caused by:
> org.apache.hadoop.hbase.errorhandling.ForeignException$ProxyThrowable:
> java.io.FileNotFoundException: File does not exist:
> hdfs://ip-10-0-12-164.ec2.internal:8020/user/hbase/data/default/x_table/ecbb3aeaf7c5b1f65742deab5812362c/d/f76d8827c29244b99bf9344982956523
> at
> org.apache.hadoop.hbase.regionserver.snapshot.RegionServerSnapshotManager$SnapshotSubprocedurePool.waitForOutstandingTasks(RegionServerSnapshotManager.java:347)
> at
>
[jira] [Comment Edited] (HBASE-19681) Online snapshot creation failing with missing store file
[
https://issues.apache.org/jira/browse/HBASE-19681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1641#comment-1641
]
Saad Mufti edited comment on HBASE-19681 at 3/23/18 11:01 PM:
--
We are facing the exact same situation in HBase 1.4.0 on AWS EMR based HBase.
Anyone have any potential recovery process? We haven't tried restart but we
migrated the region using the "assign" command in the shell that moved the
region but the problem persists. We have also seen the exception in both the
snapshot thread and compaction thread.
was (Author: saadmufti):
We are facing the exact same situation in HBase 1.4.0 on AWS EMR based HBase.
Anyone have any potential recovery process? We haven't tried restart but we
migrated the region using the "assign" command in the shell that moved the
region but the problems persists. We have also seen the exception in both the
snapshot thread and compaction thread.
> Online snapshot creation failing with missing store file
>
>
> Key: HBASE-19681
> URL: https://issues.apache.org/jira/browse/HBASE-19681
> Project: HBase
> Issue Type: Bug
> Components: backuprestore, Performance, scaling, snapshots
>Affects Versions: 1.3.0
> Environment: Hadoop - 2.7.3
> HBase 1.3.0
> OS - GNU/Linux x86_64
> Cluster - Amazon Elastic Mapreduce
>Reporter: Anirban Roy
>Priority: Major
> Attachments: region-server-missing file-log.doc,
> region-server-snapshot-exception-log.doc
>
>
> We are facing problem creating online snapshot of our HBase table. The table
> contains 20TB data and receiving ~1 writes per second. The snapshot
> creating failing intermittently with error that some hfile missing, see the
> detailed output below. Once we locate the region server hosting the region
> and restart the region server, snapshot creation succeeds. It seems the
> missing hfile removed due to minor compaction, but region server still holds
> the pointer to the file.
> [hadoop@ip-10-0-12-164 ~]$ hbase shell
> HBase Shell; enter 'help' for list of supported commands.
> Type "exit" to leave the HBase Shell
> Version 1.3.0, rUnknown, Fri Feb 17 18:15:07 UTC 2017
>
> hbase(main):001:0> snapshot ‘x_table’, ‘x_snapshot’
>
> ERROR: org.apache.hadoop.hbase.snapshot.HBaseSnapshotException: Snapshot {
> ss=x_snapshot table=x_table type=FLUSH } had an error. Procedure x_snapshot
> { waiting=[] done=[ip-10-0-9-31.ec2.internal,16020,1508372578254,
> ip-10-0-0-32.ec2.internal,16020,1508372591059,
> ip-10-0-14-221.ec2.internal,16020,1508372580873,
> ip-10-0-15-185.ec2.internal,16020,1508372588507,
> ip-10-0-9-43.ec2.internal,16020,1508372569107,
> ip-10-0-10-62.ec2.internal,16020,1512885921693,
> ip-10-0-8-216.ec2.internal,16020,1508372584133,
> ip-10-0-1-207.ec2.internal,16020,1508372580144,
> ip-10-0-0-173.ec2.internal,16020,1508372584969,
> ip-10-0-4-79.ec2.internal,16020,1508372587161,
> ip-10-0-3-165.ec2.internal,16020,1508372593566,
> ip-10-0-14-137.ec2.internal,16020,1508372583225,
> ip-10-0-6-33.ec2.internal,16020,1508372581587,
> ip-10-0-15-199.ec2.internal,16020,1508372587478,
> ip-10-0-5-253.ec2.internal,16020,1508372581243,
> ip-10-0-1-99.ec2.internal,16020,1508372609684] }
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:354)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.isSnapshotDone(MasterRpcServices.java:1058)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:61089)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2328)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:123)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:188)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:168)
> Caused by:
> org.apache.hadoop.hbase.errorhandling.ForeignException$ProxyThrowable via
> ip-10-0-3-13.ec2.internal,16020,1508372563772:org.apache.hadoop.hbase.errorhandling.ForeignException$ProxyThrowable:
> java.io.FileNotFoundException: File does not exist:
> hdfs://ip-10-0-12-164.ec2.internal:8020/user/hbase/data/default/x_table/ecbb3aeaf7c5b1f65742deab5812362c/d/f76d8827c29244b99bf9344982956523
> at
> org.apache.hadoop.hbase.errorhandling.ForeignExceptionDispatcher.rethrowException(ForeignExceptionDispatcher.java:83)
> at
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler.rethrowExceptionIfFailed(TakeSnapshotHandler.java:315)
> at
> org.apache.hadoop.hbase.master.snapshot.SnapshotManager.isSnapshotDone(SnapshotManager.java:344)
> ... 6 more
> Caused by:
>
[jira] [Commented] (HBASE-20135) NullPointerException during reading bloom filter when upgraded from hbase-1 to hbase-2
[
https://issues.apache.org/jira/browse/HBASE-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412207#comment-16412207
]
Umesh Agashe commented on HBASE-20135:
--
Thanks for the patch [~jatsakthi]!
> NullPointerException during reading bloom filter when upgraded from hbase-1
> to hbase-2
> --
>
> Key: HBASE-20135
> URL: https://issues.apache.org/jira/browse/HBASE-20135
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Sakthi
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: hbase-20135.master.001.patch,
> hbase-20135.master.002.patch
>
>
> When upgraded from hbase-1 to hbase-2, found following exception logged
> multiple times in the log:
> {code:java}
> ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader: Error
> reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> java.io.IOException: Comparator class
> org.apache.hadoop.hbase.KeyValue$RawBytesComparator is not instantiable
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComparator(FixedFileTrailer.java:628)
> at
> org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(CompoundBloomFilter.java:79)
> at
> org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMeta(BloomFilterFactory.java:104)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBloomfilter(StoreFileReader.java:479)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreFile.java:425)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(HStoreFile.java:460)
> at
> org.apache.hadoop.hbase.regionserver.HStore.createStoreFileAndReader(HStore.java:671)
> at
> org.apache.hadoop.hbase.regionserver.HStore.lambda$openStoreFiles$0(HStore.java:537)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException{code}
>
> Analysis from [~anoop.hbase]:
> Checking the related code. There seems no issue.. We are not going
> to even fail reading the bloom. In 2.0 code base we expect the
> comparator class name to be null. But in 1.x we write old KV based
> Raw Bytes comparator class name. So reading that back, we will return
> class name as null and we get NPE it looks like.
> {code:java}
> else if
> (comparatorClassName.equals("org.apache.hadoop.hbase.KeyValue$RawBytesComparator")
> ||
> comparatorClassName.equals("org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator"))
> {
> // When the comparator to be used is Bytes.BYTES_RAWCOMPARATOR,
> we just return null from here
> // Bytes.BYTES_RAWCOMPARATOR is not a CellComparator
> comparatorKlass = null;
> }
> {code}
> We can better do a null check before trying the comparator class
> instantiation so that we can avoid this scary error logs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20268) It takes more than 15 seconds to bring up hbase shell
[
https://issues.apache.org/jira/browse/HBASE-20268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412208#comment-16412208
]
Mike Drob commented on HBASE-20268:
---
I have good news and bad news here...
Looks like ~35 sec of that was from {{@hbase = Hbase::Hbase.new}} in
{{bin/hirb.rb}}, creating a connection.
Except after I start an HBase locally, because I didn't have one running
before, the whole time cuts down to ~9 seconds, which is still slow but
bearable.
I went ahead and borrowed your cluster (hope you don't mind!) and added
{{export JRUBY_OPTS=--profile}} and tried running things again.
{code}
main profile results:
Total time: 12.36
totalselfchildren calls method
5.915.910.00 343 File.file?
5.620.005.62 1 IRB.start
5.460.005.46 1 IRB.setup
5.440.005.44 2 IRB::Locale#load
5.420.005.42 2 IRB::Locale#find
5.420.005.42 2 IRB::Locale#search_file
5.420.005.42 2 IRB::Locale#each_localized_path
5.420.005.41 2 IRB::Locale#each_sublocale
5.280.075.20 420 Class#new
5.150.005.15 9 Gem.try_activate
5.150.005.15 9 Gem::Specification.find_by_path
4.890.014.88 14 Enumerable.find
4.860.014.85 108
Gem::BasicSpecification#contains_requirable_file?
4.850.014.85 108
Gem::BasicSpecification#have_file?
4.840.014.83 228 Array#any?
4.480.044.44 579 Kernel.require
3.190.003.19 1 IRB.init_config
3.190.003.19 1 IRB::Locale#initialize
2.880.112.77 366 Array#each
2.460.002.45 272 Kernel.require
2.390.142.25 27 Kernel.load
2.260.002.26 1 IRB.init_error
1.860.011.85 16 Gem::Specification.load
1.730.001.73 1 Gem::Specification.load_defaults
1.730.001.73 1 Gem::Specification.each_spec
1.730.001.73 1 Gem::Specification.each_gemspec
1.710.001.71 1 Hbase::Hbase#initialize
1.671.670.00 1
Java::OrgApacheHadoopHbaseClient::ConnectionFactory.createConnection
0.670.000.67 1 Object#require_jar
0.670.000.67 1 Jars.require_jar
0.650.000.65 1 Jars.require_jar_with_block
0.650.000.65 1 Jars.do_require
0.630.000.63 1 Jars.home
0.630.000.63 1 Jars.local_maven_repo
0.630.010.62 1 Jars.maven_local_settings
0.620.000.61 13 Shell.load_command_group
0.610.020.59 137 Shell.load_command
0.560.560.00 15 IO.read
0.550.010.55 29 Kernel.gem
0.530.000.53 4 Gem::Dependency#to_spec
0.530.000.53 168 Kernel.send
0.530.000.53 4 Gem::Dependency#to_specs
0.530.000.53 4 Gem::Dependency#matching_specs
0.510.510.00 73 Java::JavaPackage#method_missing
0.480.000.48 16 Array#select
0.480.000.47 10
Gem::Specification.gemspec_stubs_in
0.470.000.47 5 Gem::Specification.default_stubs
0.460.010.45 442 Gem::StubSpecification#data
0.450.000.45 16 Gem::StubSpecification#valid?
0.450.010.44 16 Kernel.open
{code}
I'll look more at this on Monday.
> It takes more than 15 seconds to bring up hbase shell
> -
>
> Key: HBASE-20268
> URL: https://issues.apache.org/jira/browse/HBASE-20268
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Affects Versions: 2.0.0-alpha-4
>Reporter: huaxiang sun
>Assignee: Mike Drob
>Priority: Major
>
> On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase
> shell.
> Output:
> {noformat}
> # [root@hsun-1 ~]#
[jira] [Commented] (HBASE-20135) NullPointerException during reading bloom filter when upgraded from hbase-1 to hbase-2
[
https://issues.apache.org/jira/browse/HBASE-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412198#comment-16412198
]
Sakthi commented on HBASE-20135:
Thanks [~stack] & [~uagashe] for this one!
> NullPointerException during reading bloom filter when upgraded from hbase-1
> to hbase-2
> --
>
> Key: HBASE-20135
> URL: https://issues.apache.org/jira/browse/HBASE-20135
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Sakthi
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: hbase-20135.master.001.patch,
> hbase-20135.master.002.patch
>
>
> When upgraded from hbase-1 to hbase-2, found following exception logged
> multiple times in the log:
> {code:java}
> ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader: Error
> reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> java.io.IOException: Comparator class
> org.apache.hadoop.hbase.KeyValue$RawBytesComparator is not instantiable
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComparator(FixedFileTrailer.java:628)
> at
> org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(CompoundBloomFilter.java:79)
> at
> org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMeta(BloomFilterFactory.java:104)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBloomfilter(StoreFileReader.java:479)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreFile.java:425)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(HStoreFile.java:460)
> at
> org.apache.hadoop.hbase.regionserver.HStore.createStoreFileAndReader(HStore.java:671)
> at
> org.apache.hadoop.hbase.regionserver.HStore.lambda$openStoreFiles$0(HStore.java:537)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException{code}
>
> Analysis from [~anoop.hbase]:
> Checking the related code. There seems no issue.. We are not going
> to even fail reading the bloom. In 2.0 code base we expect the
> comparator class name to be null. But in 1.x we write old KV based
> Raw Bytes comparator class name. So reading that back, we will return
> class name as null and we get NPE it looks like.
> {code:java}
> else if
> (comparatorClassName.equals("org.apache.hadoop.hbase.KeyValue$RawBytesComparator")
> ||
> comparatorClassName.equals("org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator"))
> {
> // When the comparator to be used is Bytes.BYTES_RAWCOMPARATOR,
> we just return null from here
> // Bytes.BYTES_RAWCOMPARATOR is not a CellComparator
> comparatorKlass = null;
> }
> {code}
> We can better do a null check before trying the comparator class
> instantiation so that we can avoid this scary error logs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412192#comment-16412192
]
Sean Busbey commented on HBASE-20270:
-
not at all!
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: hbase-20270.master.001.patch
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20135) NullPointerException during reading bloom filter when upgraded from hbase-1 to hbase-2
[
https://issues.apache.org/jira/browse/HBASE-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20135:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to branch-2.0+. Thanks for the clean-up [~jatsakthi]
> NullPointerException during reading bloom filter when upgraded from hbase-1
> to hbase-2
> --
>
> Key: HBASE-20135
> URL: https://issues.apache.org/jira/browse/HBASE-20135
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.0.0-beta-2
>Reporter: Umesh Agashe
>Assignee: Sakthi
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: hbase-20135.master.001.patch,
> hbase-20135.master.002.patch
>
>
> When upgraded from hbase-1 to hbase-2, found following exception logged
> multiple times in the log:
> {code:java}
> ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader: Error
> reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> java.io.IOException: Comparator class
> org.apache.hadoop.hbase.KeyValue$RawBytesComparator is not instantiable
> at
> org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComparator(FixedFileTrailer.java:628)
> at
> org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(CompoundBloomFilter.java:79)
> at
> org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMeta(BloomFilterFactory.java:104)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBloomfilter(StoreFileReader.java:479)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreFile.java:425)
> at
> org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(HStoreFile.java:460)
> at
> org.apache.hadoop.hbase.regionserver.HStore.createStoreFileAndReader(HStore.java:671)
> at
> org.apache.hadoop.hbase.regionserver.HStore.lambda$openStoreFiles$0(HStore.java:537)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException{code}
>
> Analysis from [~anoop.hbase]:
> Checking the related code. There seems no issue.. We are not going
> to even fail reading the bloom. In 2.0 code base we expect the
> comparator class name to be null. But in 1.x we write old KV based
> Raw Bytes comparator class name. So reading that back, we will return
> class name as null and we get NPE it looks like.
> {code:java}
> else if
> (comparatorClassName.equals("org.apache.hadoop.hbase.KeyValue$RawBytesComparator")
> ||
> comparatorClassName.equals("org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator"))
> {
> // When the comparator to be used is Bytes.BYTES_RAWCOMPARATOR,
> we just return null from here
> // Bytes.BYTES_RAWCOMPARATOR is not a CellComparator
> comparatorKlass = null;
> }
> {code}
> We can better do a null check before trying the comparator class
> instantiation so that we can avoid this scary error logs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20267) Fix for warning multiple versions of scala libraries detected
[
https://issues.apache.org/jira/browse/HBASE-20267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412188#comment-16412188
]
Hadoop QA commented on HBASE-20267:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
31s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 10m
48s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
14s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
52s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
21m 35s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
30s{color} | {color:green} hbase-spark in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 44m 20s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20267 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915968/HBASE-20267.v01.patch
|
| Optional Tests | asflicense javac javadoc unit shadedjars hadoopcheck
xml compile |
| uname | Linux 61cb1ea587c0 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 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 / 65bd0881e2 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12111/testReport/ |
| Max. process+thread count | 910 (vs. ulimit of 1) |
| modules | C: hbase-spark U: hbase-spark |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12111/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Fix for warning multiple versions of scala libraries detected
> -
>
> Key: HBASE-20267
> URL: https://issues.apache.org/jira/browse/HBASE-20267
> Project: HBase
> Issue Type: Bug
> Environment: last revision: ad47c2daf4d9dc3b85ec91e0fe8385aa6dd9c492
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T14:49:05-05:00)
> Maven home:
[jira] [Commented] (HBASE-19158) Ref guide needs upgrade update
[
https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412185#comment-16412185
]
Hadoop QA commented on HBASE-19158:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
24s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
5s{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} javadoc {color} | {color:green} 2m
20s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}168m
13s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}182m 7s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-19158 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915957/HBASE-19158.2.patch |
| Optional Tests | asflicense javac javadoc unit |
| uname | Linux a613bc2fca52 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / ad47c2daf4 |
| maven | version: Apache Maven 3.5.3
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_162 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/12109/testReport/ |
| Max. process+thread count | 5139 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12109/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Ref guide needs upgrade update
> --
>
> Key: HBASE-19158
> URL: https://issues.apache.org/jira/browse/HBASE-19158
> Project: HBase
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.0.0-beta-1
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-19158.0.patch, HBASE-19158.1.patch,
> HBASE-19158.2.patch
>
>
> Our ref guide has lots of references in the upgrade section to obsolete
> versions and no references to the 2.0.0-* releases. We should correct this
> for beta-1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakthi updated HBASE-20270:
---
Status: Patch Available (was: Open)
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: hbase-20270.master.001.patch
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakthi updated HBASE-20270:
---
Attachment: hbase-20270.master.001.patch
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: hbase-20270.master.001.patch
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakthi reassigned HBASE-20270:
--
Assignee: Sakthi
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Sakthi
>Priority: Major
> Fix For: 2.0.0
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20270) Turn off command help that follows all errors in shell
[
https://issues.apache.org/jira/browse/HBASE-20270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412172#comment-16412172
]
Sakthi commented on HBASE-20270:
Hey [~busbey] , Do you mind if I assign it to myself?
> Turn off command help that follows all errors in shell
> --
>
> Key: HBASE-20270
> URL: https://issues.apache.org/jira/browse/HBASE-20270
> Project: HBase
> Issue Type: Task
> Components: shell
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Priority: Major
> Fix For: 2.0.0
>
>
> Right now if a shell command gives an error, any error, it then echos the
> command help. It makes it harder to see the actual error text and is annoying.
> example:
> {code}
>
>
>
> hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> ERROR: Unknown namespace test!
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
> Create a table with namespace=ns1 and table qualifier=t1
> hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
> Create a table with namespace=default and table qualifier=t1
> hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
> hbase> # The above in shorthand would be the following:
> hbase> create 't1', 'f1', 'f2', 'f3'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000,
> BLOCKCACHE => true}
> hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
> {'hbase.hstore.blockingStoreFiles' => '10'}}
> hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD =>
> 100, MOB_COMPACT_PARTITION_POLICY => 'weekly'}
> Table configuration options can be put at the end.
> Examples:
> hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
> hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
> hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
> 'myvalue' }
> hbase> # Optionally pre-split the table into NUMREGIONS, using
> hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
> hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
> REGION_REPLICATION => 2, CONFIGURATION =>
> {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
> You can also keep around a reference to the created table:
> hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> Took 0.0221 seconds
>
>
> hbase(main):008:0> create_namespace 'test'
> Took 0.2554 seconds
>
>
> hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
> SPLITALGO => 'HexStringSplit'}
> Created table test:a_table
> Took 1.2264 seconds
> {code}
> I was trying to make a table in the test namespace before making the
> namespace. Much faster to recognize and move on when the error text isn't
> followed by 80x the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-19158) Ref guide needs upgrade update
[ https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412168#comment-16412168 ] Mike Drob commented on HBASE-19158: --- oh, misread your questions, yea, fine to push as long as the rest of the notes don't get lost. > Ref guide needs upgrade update > -- > > Key: HBASE-19158 > URL: https://issues.apache.org/jira/browse/HBASE-19158 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-beta-1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-19158.0.patch, HBASE-19158.1.patch, > HBASE-19158.2.patch > > > Our ref guide has lots of references in the upgrade section to obsolete > versions and no references to the 2.0.0-* releases. We should correct this > for beta-1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19158) Ref guide needs upgrade update
[ https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412166#comment-16412166 ] Mike Drob commented on HBASE-19158: --- would like to see notes that: * hbase.master.cleaner.interval changed from 1 min to 10 min * MasterProcedureConstants.MASTER_PROCEDURE_THREADS defaults to CPU/4 instead of CPU * hbase.rpc.server.nativetransport renamed to hbase.netty.nativetransport * hbase.netty.rpc.server.worker.count renamed to base.netty.worker.count * hbase.hfile.compactions.discharger.interval renamed to hbase.hfile.compaction.discharger.interval * hbase.hregion.percolumnfamilyflush.size.lower.bound removed at site level, but can still be applied at table level * hbase.client.reties.number now counts the total number of retries, not the total number of tries > Ref guide needs upgrade update > -- > > Key: HBASE-19158 > URL: https://issues.apache.org/jira/browse/HBASE-19158 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-beta-1 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-19158.0.patch, HBASE-19158.1.patch, > HBASE-19158.2.patch > > > Our ref guide has lots of references in the upgrade section to obsolete > versions and no references to the 2.0.0-* releases. We should correct this > for beta-1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-19919) Tidying up logging
[ https://issues.apache.org/jira/browse/HBASE-19919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-19919: -- Release Note: (I thought this change innocuous but I made work for a co-worker when I upped interval between log cleaner runs -- meant a smoke test failed because we were slow doing an expected cleanup). Edit of log lines removing redundancy. Shorten thread names shown in log. Made some log TRACE instead of DEBUG. Capitalizations. Upped log cleaner interval from every minute to every ten minutes. hbase.master.cleaner.interval Lowered default count of threads started by Procedure Executor from count of CPUs to 1/4 of count of CPUs. was: (I thought this change innocuous but I made work for a co-worker when I upped interval between log cleaner runs -- meant a smoke test failed because we were slow doing an expected cleanup). Edit of log lines removing redundancy. Shorten thread names shown in log. Made some log TRACE instead of DEBUG. Capitalizations. Upped log cleaner interval from every minute to every ten minutes. Lowered default count of threads started by Procedure Executor from count of CPUs to 1/4 of count of CPUs. > Tidying up logging > -- > > Key: HBASE-19919 > URL: https://issues.apache.org/jira/browse/HBASE-19919 > Project: HBase > Issue Type: Bug >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-2, 2.0.0 > > Attachments: 0001-HBASE-19919-Tidying-up-logging.patch, > HBASE-19919.branch-2.001.patch > > > Reading logs, there is a bunch of stuff we don't need, thread names are too > long, etc. Doing a little tidying. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20223) Use hbase-thirdparty 2.1.0
[
https://issues.apache.org/jira/browse/HBASE-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412143#comment-16412143
]
Josh Elser commented on HBASE-20223:
{quote}Good eye. Definitely at least one thing to remove there. Building those
artifacts and poking at them now.
{quote}
Actually, I take it back. Because our hbase-shaded-client is using Hadoop
artifacts directly (and not the hadoop shaded artifacts), we have to shade
their commons-cli 1.2 and commons-collections 3, even though we use neither
(and have them banned) in our tree. That's fun :)
> Use hbase-thirdparty 2.1.0
> --
>
> Key: HBASE-20223
> URL: https://issues.apache.org/jira/browse/HBASE-20223
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-20223.001.patch, HBASE-20223.002.branch-2.0.patch
>
>
> Update hbase to account for the changes to hbase-thirdparty:
> * new (internal) protobuf version
> * shaded commons-cli
> * shaded commons-collections4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20269:
---
Description:
In ZKReplicationQueueStorage#setWALPosition :
{code}
addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
{code}
If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
should be skipped.
was:
The following test failure is reproducible in master branch:
{code}
testRegionReplicaReplicationIgnoresDroppedTables(org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint)
Time elapsed: 21.493 sec <<< FAILURE!
java.lang.AssertionError
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:260)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:243)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:439)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDroppedTables(TestRegionReplicaReplicationEndpoint.java:372)
{code}
In ZKReplicationQueueStorage#setWALPosition :
{code}
addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
{code}
If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
should be skipped.
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20223) Use hbase-thirdparty 2.1.0
[
https://issues.apache.org/jira/browse/HBASE-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412131#comment-16412131
]
Josh Elser commented on HBASE-20223:
{quote}Do we need to update the relocations in {{hbase-shaded/pom.xml}}?
{quote}
Good eye. Definitely at least one thing to remove there. Building those
artifacts and poking at them now.
> Use hbase-thirdparty 2.1.0
> --
>
> Key: HBASE-20223
> URL: https://issues.apache.org/jira/browse/HBASE-20223
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-20223.001.patch, HBASE-20223.002.branch-2.0.patch
>
>
> Update hbase to account for the changes to hbase-thirdparty:
> * new (internal) protobuf version
> * shaded commons-cli
> * shaded commons-collections4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20270) Turn off command help that follows all errors in shell
Sean Busbey created HBASE-20270:
---
Summary: Turn off command help that follows all errors in shell
Key: HBASE-20270
URL: https://issues.apache.org/jira/browse/HBASE-20270
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 2.0.0
Reporter: Sean Busbey
Fix For: 2.0.0
Right now if a shell command gives an error, any error, it then echos the
command help. It makes it harder to see the actual error text and is annoying.
example:
{code}
hbase(main):007:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
SPLITALGO => 'HexStringSplit'}
ERROR: Unknown namespace test!
Creates a table. Pass a table name, and a set of column family
specifications (at least one), and, optionally, table configuration.
Column specification can be a simple string (name), or a dictionary
(dictionaries are described below in main help output), necessarily
including NAME attribute.
Examples:
Create a table with namespace=ns1 and table qualifier=t1
hbase> create 'ns1:t1', {NAME => 'f1', VERSIONS => 5}
Create a table with namespace=default and table qualifier=t1
hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
hbase> # The above in shorthand would be the following:
hbase> create 't1', 'f1', 'f2', 'f3'
hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000, BLOCKCACHE
=> true}
hbase> create 't1', {NAME => 'f1', CONFIGURATION =>
{'hbase.hstore.blockingStoreFiles' => '10'}}
hbase> create 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD => 100,
MOB_COMPACT_PARTITION_POLICY => 'weekly'}
Table configuration options can be put at the end.
Examples:
hbase> create 'ns1:t1', 'f1', SPLITS => ['10', '20', '30', '40']
hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' =>
'myvalue' }
hbase> # Optionally pre-split the table into NUMREGIONS, using
hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit',
REGION_REPLICATION => 2, CONFIGURATION =>
{'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
hbase> create 't1', {NAME => 'f1', DFS_REPLICATION => 1}
You can also keep around a reference to the created table:
hbase> t1 = create 't1', 'f1'
Which gives you a reference to the table named 't1', on which you can then
call methods.
Took 0.0221 seconds
hbase(main):008:0> create_namespace 'test'
Took 0.2554 seconds
hbase(main):009:0> create 'test:a_table', 'family', { NUMREGIONS => 20,
SPLITALGO => 'HexStringSplit'}
Created table test:a_table
Took 1.2264 seconds
{code}
I was trying to make a table in the test namespace before making the namespace.
Much faster to recognize and move on when the error text isn't followed by 80x
the text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20268) It takes more than 15 seconds to bring up hbase shell
[
https://issues.apache.org/jira/browse/HBASE-20268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412113#comment-16412113
]
Mike Drob commented on HBASE-20268:
---
On my local macbook I get ~4 sec with jruby alone and ~45 seconds through the
shell against tip of master branch. We're almost certainly doing something
extra that causes a terrible user experience here.
> It takes more than 15 seconds to bring up hbase shell
> -
>
> Key: HBASE-20268
> URL: https://issues.apache.org/jira/browse/HBASE-20268
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Affects Versions: 2.0.0-alpha-4
>Reporter: huaxiang sun
>Assignee: Mike Drob
>Priority: Major
>
> On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase
> shell.
> Output:
> {noformat}
> # [root@hsun-1 ~]# echo exit | time /usr/java/default/bin/java -jar
> /opt/cloudera/parcels/CDH/jars/jruby-complete-9.1.10.0.jar -S irb
> # Switch to inspect mode.
> # exit
> # 9.81user 0.30system 0:03.59elapsed 281%CPU (0avgtext+0avgdata
> 308672maxresident)k
> # 0inputs+776outputs (0major+79787minor)pagefaults 0swaps
> #
> # [root@hsun-1 ~]# echo exit | time hbase shell
> # Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is
> deprecated and will likely be removed in a future release
> # HBase Shell
> # Use "help" to get list of supported commands.
> # Use "exit" to quit this interactive shell.
> # Version 2.0.0-cdh6.0.x-SNAPSHOT, rUnknown, Thu Mar 22 12:30:22 PDT 2018
> # Took 0.0040 seconds
> # exit
> # 33.92user 1.20system 0:15.21elapsed 230%CPU (0avgtext+0avgdata
> 360928maxresident)k
> # 0inputs+1064outputs (0major+176658minor)pagefaults 0swaps
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20223) Use hbase-thirdparty 2.1.0
[
https://issues.apache.org/jira/browse/HBASE-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412103#comment-16412103
]
Mike Drob commented on HBASE-20223:
---
Do we need to update the relocations in {{hbase-shaded/pom.xml}}?
> Use hbase-thirdparty 2.1.0
> --
>
> Key: HBASE-20223
> URL: https://issues.apache.org/jira/browse/HBASE-20223
> Project: HBase
> Issue Type: Task
> Components: dependencies
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-20223.001.patch, HBASE-20223.002.branch-2.0.patch
>
>
> Update hbase to account for the changes to hbase-thirdparty:
> * new (internal) protobuf version
> * shaded commons-cli
> * shaded commons-collections4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-19983) Update ref guide for hadoop versions to include 2.8 and 2.9
[ https://issues.apache.org/jira/browse/HBASE-19983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19983: Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) thanks for the review! > Update ref guide for hadoop versions to include 2.8 and 2.9 > --- > > Key: HBASE-19983 > URL: https://issues.apache.org/jira/browse/HBASE-19983 > Project: HBase > Issue Type: Sub-task > Components: documentation, hadoop2 >Reporter: Mike Drob >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0 > > Attachments: HBASE-19983.0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-19983) Update ref guide for hadoop versions to include 2.8 and 2.9
[ https://issues.apache.org/jira/browse/HBASE-19983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19983: Component/s: hadoop2 documentation > Update ref guide for hadoop versions to include 2.8 and 2.9 > --- > > Key: HBASE-19983 > URL: https://issues.apache.org/jira/browse/HBASE-19983 > Project: HBase > Issue Type: Sub-task > Components: documentation, hadoop2 >Reporter: Mike Drob >Assignee: Sean Busbey >Priority: Major > Fix For: 3.0.0 > > Attachments: HBASE-19983.0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20269:
---
Status: Patch Available (was: Open)
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> The following test failure is reproducible in master branch:
> {code}
> testRegionReplicaReplicationIgnoresDroppedTables(org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint)
> Time elapsed: 21.493 sec <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:260)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:243)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:439)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDroppedTables(TestRegionReplicaReplicationEndpoint.java:372)
> {code}
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
[
https://issues.apache.org/jira/browse/HBASE-20269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20269:
---
Attachment: 20269.v1.txt
> ZKReplicationQueueStorage#setWALPosition should only call
> ZKUtil#multiOrSequential when there is at least one ZKUtilOp
> --
>
> Key: HBASE-20269
> URL: https://issues.apache.org/jira/browse/HBASE-20269
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Attachments: 20269.v1.txt
>
>
> The following test failure is reproducible in master branch:
> {code}
> testRegionReplicaReplicationIgnoresDroppedTables(org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint)
> Time elapsed: 21.493 sec <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:260)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:243)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:439)
> at
> org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDroppedTables(TestRegionReplicaReplicationEndpoint.java:372)
> {code}
> In ZKReplicationQueueStorage#setWALPosition :
> {code}
> addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
> ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
> {code}
> If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
> should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20268) It takes more than 15 seconds to bring up hbase shell
[
https://issues.apache.org/jira/browse/HBASE-20268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-20268:
--
Description:
On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase
shell.
Output:
{noformat}
# [root@hsun-1 ~]# echo exit | time /usr/java/default/bin/java -jar
/opt/cloudera/parcels/CDH/jars/jruby-complete-9.1.10.0.jar -S irb
# Switch to inspect mode.
# exit
# 9.81user 0.30system 0:03.59elapsed 281%CPU (0avgtext+0avgdata
308672maxresident)k
# 0inputs+776outputs (0major+79787minor)pagefaults 0swaps
#
# [root@hsun-1 ~]# echo exit | time hbase shell
# Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is
deprecated and will likely be removed in a future release
# HBase Shell
# Use "help" to get list of supported commands.
# Use "exit" to quit this interactive shell.
# Version 2.0.0-cdh6.0.x-SNAPSHOT, rUnknown, Thu Mar 22 12:30:22 PDT 2018
# Took 0.0040 seconds
# exit
# 33.92user 1.20system 0:15.21elapsed 230%CPU (0avgtext+0avgdata
360928maxresident)k
# 0inputs+1064outputs (0major+176658minor)pagefaults 0swaps
{noformat}
was:
On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase
shell.
Output:
# [root@hsun-1 ~]# echo exit | time /usr/java/default/bin/java -jar
/opt/cloudera/parcels/CDH/jars/jruby-complete-9.1.10.0.jar -S irb
# Switch to inspect mode.
# exit
# 9.81user 0.30system 0:03.59elapsed 281%CPU (0avgtext+0avgdata
308672maxresident)k
# 0inputs+776outputs (0major+79787minor)pagefaults 0swaps
#
# [root@hsun-1 ~]# echo exit | time hbase shell
# Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is
deprecated and will likely be removed in a future release
# HBase Shell
# Use "help" to get list of supported commands.
# Use "exit" to quit this interactive shell.
# Version 2.0.0-cdh6.0.x-SNAPSHOT, rUnknown, Thu Mar 22 12:30:22 PDT 2018
# Took 0.0040 seconds
# exit
# 33.92user 1.20system 0:15.21elapsed 230%CPU (0avgtext+0avgdata
360928maxresident)k
# 0inputs+1064outputs (0major+176658minor)pagefaults 0swaps
> It takes more than 15 seconds to bring up hbase shell
> -
>
> Key: HBASE-20268
> URL: https://issues.apache.org/jira/browse/HBASE-20268
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Affects Versions: 2.0.0-alpha-4
>Reporter: huaxiang sun
>Assignee: Mike Drob
>Priority: Major
>
> On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase
> shell.
> Output:
> {noformat}
> # [root@hsun-1 ~]# echo exit | time /usr/java/default/bin/java -jar
> /opt/cloudera/parcels/CDH/jars/jruby-complete-9.1.10.0.jar -S irb
> # Switch to inspect mode.
> # exit
> # 9.81user 0.30system 0:03.59elapsed 281%CPU (0avgtext+0avgdata
> 308672maxresident)k
> # 0inputs+776outputs (0major+79787minor)pagefaults 0swaps
> #
> # [root@hsun-1 ~]# echo exit | time hbase shell
> # Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is
> deprecated and will likely be removed in a future release
> # HBase Shell
> # Use "help" to get list of supported commands.
> # Use "exit" to quit this interactive shell.
> # Version 2.0.0-cdh6.0.x-SNAPSHOT, rUnknown, Thu Mar 22 12:30:22 PDT 2018
> # Took 0.0040 seconds
> # exit
> # 33.92user 1.20system 0:15.21elapsed 230%CPU (0avgtext+0avgdata
> 360928maxresident)k
> # 0inputs+1064outputs (0major+176658minor)pagefaults 0swaps
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20269) ZKReplicationQueueStorage#setWALPosition should only call ZKUtil#multiOrSequential when there is at least one ZKUtilOp
Ted Yu created HBASE-20269:
--
Summary: ZKReplicationQueueStorage#setWALPosition should only call
ZKUtil#multiOrSequential when there is at least one ZKUtilOp
Key: HBASE-20269
URL: https://issues.apache.org/jira/browse/HBASE-20269
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
The following test failure is reproducible in master branch:
{code}
testRegionReplicaReplicationIgnoresDroppedTables(org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint)
Time elapsed: 21.493 sec <<< FAILURE!
java.lang.AssertionError
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:260)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:243)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:439)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDroppedTables(TestRegionReplicaReplicationEndpoint.java:372)
{code}
In ZKReplicationQueueStorage#setWALPosition :
{code}
addLastSeqIdsToOps(queueId, lastSeqIds, listOfOps);
ZKUtil.multiOrSequential(zookeeper, listOfOps, false);
{code}
If there is no ZKUtilOp in listOfOps, the call to ZKUtil#multiOrSequential
should be skipped.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20192) RedirectServlet not getting registered in HMaster.putUpJettyServer() in local mode
[ https://issues.apache.org/jira/browse/HBASE-20192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samir Ahmic updated HBASE-20192: Resolution: Fixed Status: Resolved (was: Patch Available) I also can not reproduce this issue any more. HBASE-20224 fixed this closing this issue [~uagashe]. > RedirectServlet not getting registered in HMaster.putUpJettyServer() in local > mode > -- > > Key: HBASE-20192 > URL: https://issues.apache.org/jira/browse/HBASE-20192 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 2.0.0-beta-2 >Reporter: Samir Ahmic >Assignee: Samir Ahmic >Priority: Major > Attachments: HBASE-20192.branch-2.0.01.patch, Screen Shot 2018-03-14 > at 09.23.34.png, Screen Shot 2018-03-14 at 09.24.06.png > > > Jetty is returning 404 when trying to open master-status page from RS status > page in local cluster mode. > After some debugging it looks like request never hits jetty RedirectServlet > so i assume RedirectServlet is not properly registered in jetty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19258) IntegrationTest for Backup and Restore
[ https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412096#comment-16412096 ] Josh Elser commented on HBASE-19258: No worries, Mike. Just wanted to make sure we didn't move on without you. > IntegrationTest for Backup and Restore > -- > > Key: HBASE-19258 > URL: https://issues.apache.org/jira/browse/HBASE-19258 > Project: HBase > Issue Type: Test > Components: integration tests >Reporter: Josh Elser >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 3.0.0 > > Attachments: HBASE-19258.v1.patch, HBASE-19258.v2.patch, > HBASE-19258.v3.patch > > > See chatter at https://docs.google.com/document/d/1xbPlLKjOcPq2LDqjbSkF6uND > AG0mzgOxek6P3POLeMc/edit?usp=sharing > We need to get an IntegrationTest in place for backup and restore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-17819) Reduce the heap overhead for BucketCache
[
https://issues.apache.org/jira/browse/HBASE-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412092#comment-16412092
]
Hadoop QA commented on HBASE-17819:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
35s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
33s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
49s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
35s{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} shadedjars {color} | {color:green} 4m
50s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
20m 26s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
20s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}107m
22s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
37s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}162m 2s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-17819 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12915945/HBASE-17819_new_V2.patch
|
| Optional Tests | asflicense javac javadoc unit findbugs shadedjars
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux c7f739743b20 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9
14:43:09 UTC 2018 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 / ad47c2daf4 |
| maven | version:
[jira] [Commented] (HBASE-19983) Update ref guide for hadoop versions to include 2.8 and 2.9
[ https://issues.apache.org/jira/browse/HBASE-19983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412072#comment-16412072 ] Mike Drob commented on HBASE-19983: --- +1 > Update ref guide for hadoop versions to include 2.8 and 2.9 > --- > > Key: HBASE-19983 > URL: https://issues.apache.org/jira/browse/HBASE-19983 > Project: HBase > Issue Type: Sub-task >Reporter: Mike Drob >Assignee: Sean Busbey >Priority: Major > Attachments: HBASE-19983.0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19258) IntegrationTest for Backup and Restore
[ https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412068#comment-16412068 ] Mike Drob commented on HBASE-19258: --- I'm trying to focus on 2.0 right now, probably not going to have too much effort to follow this for until that wraps. > IntegrationTest for Backup and Restore > -- > > Key: HBASE-19258 > URL: https://issues.apache.org/jira/browse/HBASE-19258 > Project: HBase > Issue Type: Test > Components: integration tests >Reporter: Josh Elser >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 3.0.0 > > Attachments: HBASE-19258.v1.patch, HBASE-19258.v2.patch, > HBASE-19258.v3.patch > > > See chatter at https://docs.google.com/document/d/1xbPlLKjOcPq2LDqjbSkF6uND > AG0mzgOxek6P3POLeMc/edit?usp=sharing > We need to get an IntegrationTest in place for backup and restore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-16848) Usage for show_peer_tableCFs command doesn't include peer
[
https://issues.apache.org/jira/browse/HBASE-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412066#comment-16412066
]
Hudson commented on HBASE-16848:
Results for branch branch-1.4
[build #264 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/264/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/264//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/264//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/264//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Usage for show_peer_tableCFs command doesn't include peer
> -
>
> Key: HBASE-16848
> URL: https://issues.apache.org/jira/browse/HBASE-16848
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Peter Somogyi
>Priority: Minor
> Labels: documentation, replication, shell
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.4.3, 2.0.0
>
> Attachments: HBASE-16848.master.001.patch,
> HBASE-16848.master.001.patch
>
>
> {code}
> hbase(main):003:0> show_peer_tableCFs
> ERROR: wrong number of arguments (0 for 1)
> Here is some help for this command:
> Show replicable table-cf config for the specified peer.
> hbase> show_peer_tableCFs
> {code}
> The sample usage should include peer id.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20267) Fix for warning multiple versions of scala libraries detected
[
https://issues.apache.org/jira/browse/HBASE-20267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412064#comment-16412064
]
Mike Drob commented on HBASE-20267:
---
Looks the same as HBASE-20175?
> Fix for warning multiple versions of scala libraries detected
> -
>
> Key: HBASE-20267
> URL: https://issues.apache.org/jira/browse/HBASE-20267
> Project: HBase
> Issue Type: Bug
> Environment: last revision: ad47c2daf4d9dc3b85ec91e0fe8385aa6dd9c492
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T14:49:05-05:00)
> Maven home: /opt/apache-maven-3.5.3
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac"
>Reporter: Artem Ervits
>Assignee: Artem Ervits
>Priority: Minor
> Attachments: HBASE-20267.v01.patch
>
>
> {code:java}
> [WARNING] Expected all dependencies to require Scala version: 2.11.8
> [WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala
> version: 2.11.8
> [WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
> [WARNING] Multiple versions of scala libraries detected!{code}
> as of Scala 2.10 all major.minor versions are backwards compatible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-19258) IntegrationTest for Backup and Restore
[ https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-19258: -- Attachment: HBASE-19258.v3.patch > IntegrationTest for Backup and Restore > -- > > Key: HBASE-19258 > URL: https://issues.apache.org/jira/browse/HBASE-19258 > Project: HBase > Issue Type: Test > Components: integration tests >Reporter: Josh Elser >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 3.0.0 > > Attachments: HBASE-19258.v1.patch, HBASE-19258.v2.patch, > HBASE-19258.v3.patch > > > See chatter at https://docs.google.com/document/d/1xbPlLKjOcPq2LDqjbSkF6uND > AG0mzgOxek6P3POLeMc/edit?usp=sharing > We need to get an IntegrationTest in place for backup and restore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-19258) IntegrationTest for Backup and Restore
[ https://issues.apache.org/jira/browse/HBASE-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412049#comment-16412049 ] Vladimir Rodionov commented on HBASE-19258: --- Patch v3. > IntegrationTest for Backup and Restore > -- > > Key: HBASE-19258 > URL: https://issues.apache.org/jira/browse/HBASE-19258 > Project: HBase > Issue Type: Test > Components: integration tests >Reporter: Josh Elser >Assignee: Vladimir Rodionov >Priority: Blocker > Fix For: 3.0.0 > > Attachments: HBASE-19258.v1.patch, HBASE-19258.v2.patch, > HBASE-19258.v3.patch > > > See chatter at https://docs.google.com/document/d/1xbPlLKjOcPq2LDqjbSkF6uND > AG0mzgOxek6P3POLeMc/edit?usp=sharing > We need to get an IntegrationTest in place for backup and restore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20268) It takes more than 15 seconds to bring up hbase shell
huaxiang sun created HBASE-20268: Summary: It takes more than 15 seconds to bring up hbase shell Key: HBASE-20268 URL: https://issues.apache.org/jira/browse/HBASE-20268 Project: HBase Issue Type: Improvement Components: shell Affects Versions: 2.0.0-alpha-4 Reporter: huaxiang sun Assignee: Mike Drob On a hbase 2.0 based cluster, it takes more than 15 seconds to bring up hbase shell. Output: # [root@hsun-1 ~]# echo exit | time /usr/java/default/bin/java -jar /opt/cloudera/parcels/CDH/jars/jruby-complete-9.1.10.0.jar -S irb # Switch to inspect mode. # exit # 9.81user 0.30system 0:03.59elapsed 281%CPU (0avgtext+0avgdata 308672maxresident)k # 0inputs+776outputs (0major+79787minor)pagefaults 0swaps # # [root@hsun-1 ~]# echo exit | time hbase shell # Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release # HBase Shell # Use "help" to get list of supported commands. # Use "exit" to quit this interactive shell. # Version 2.0.0-cdh6.0.x-SNAPSHOT, rUnknown, Thu Mar 22 12:30:22 PDT 2018 # Took 0.0040 seconds # exit # 33.92user 1.20system 0:15.21elapsed 230%CPU (0avgtext+0avgdata 360928maxresident)k # 0inputs+1064outputs (0major+176658minor)pagefaults 0swaps -- This message was sent by Atlassian JIRA (v7.6.3#76005)
