[jira] [Updated] (HBASE-24423) No need to get lock in canSplit because hasReferences will get lock too
[ https://issues.apache.org/jira/browse/HBASE-24423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Vissapragada updated HBASE-24423: - Fix Version/s: 3.0.0-alpha-1 > No need to get lock in canSplit because hasReferences will get lock too > --- > > Key: HBASE-24423 > URL: https://issues.apache.org/jira/browse/HBASE-24423 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Minor > Fix For: 3.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24423) No need to get lock in canSplit because hasReferences will get lock too
[ https://issues.apache.org/jira/browse/HBASE-24423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116459#comment-17116459 ] Bharath Vissapragada commented on HBASE-24423: -- Thanks for fixing this [~filtertip]. Let me check if this applies to other branches. > No need to get lock in canSplit because hasReferences will get lock too > --- > > Key: HBASE-24423 > URL: https://issues.apache.org/jira/browse/HBASE-24423 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24431) RSGroupInfo add configuration map to store something extra
Sun Xin created HBASE-24431: --- Summary: RSGroupInfo add configuration map to store something extra Key: HBASE-24431 URL: https://issues.apache.org/jira/browse/HBASE-24431 Project: HBase Issue Type: Improvement Components: rsgroup Affects Versions: 3.0.0-alpha-1 Reporter: Sun Xin Assignee: Sun Xin Fix For: 3.0.0-alpha-1 Maybe we should add a _Map configuration_ into RSGroupInfo to store extra infomation. For example, we can store the minimum number of machines the group needs, in order to move machine into this group automatically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24430) upgrading standalone-mode hbase from 2.2 to 2.3 fails because of local filesystem not supporting hflush
[
https://issues.apache.org/jira/browse/HBASE-24430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhuqi Jin updated HBASE-24430:
--
Component/s: (was: wal)
Affects Version/s: 3.0.0-alpha-1
Description:
When we tested upgrading HBASE from 2.2 to 2.4/2.5, the upgraded node failed to
start.
The error message is shown below:
{code:java}
2020-05-26 02:46:33,124 ERROR [master/9f0ca3fedcda:16000:becomeActiveMaster]
wal.AsyncFSWALProvider: The RegionServer async write ahead log provider relies
on the ability to call hflush for proper operation during component failures,
but the current FileSystem does not support doing so. Please check the config
value of 'hbase.wal.dir' and ensure it points to a FileSystem mount that has
suitable capabilities for output streams.2020-05-26 02:46:33,124 ERROR
[master/9f0ca3fedcda:16000:becomeActiveMaster] wal.AsyncFSWALProvider: The
RegionServer async write ahead log provider relies on the ability to call
hflush for proper operation during component failures, but the current
FileSystem does not support doing so. Please check the config value of
'hbase.wal.dir' and ensure it points to a FileSystem mount that has suitable
capabilities for output streams.2020-05-26 02:46:33,130 INFO
[master/9f0ca3fedcda:16000:becomeActiveMaster] wal.AbstractFSWAL: Closed WAL:
AsyncFSWAL 9f0ca3fedcda%2C16000%2C1590461189948:(num 1590461193109)2020-05-26
02:46:33,134 ERROR [master/9f0ca3fedcda:16000:becomeActiveMaster]
master.HMaster: Failed to become active masterjava.io.IOException: cannot get
log writer at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:838)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:548)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:489)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:157)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:297) at
org.apache.hadoop.hbase.master.store.LocalRegion.createWAL(LocalRegion.java:193)
at
org.apache.hadoop.hbase.master.store.LocalRegion.bootstrap(LocalRegion.java:213)
at
org.apache.hadoop.hbase.master.store.LocalRegion.create(LocalRegion.java:310)
at org.apache.hadoop.hbase.master.store.LocalStore.create(LocalStore.java:148)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:969)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2245)
at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:626) at
java.lang.Thread.run(Thread.java:748)Caused by:
org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException:
hflush at
org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:71)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:169)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:166)
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:105)
... 17 more2020-05-26 02:46:33,135 ERROR
[master/9f0ca3fedcda:16000:becomeActiveMaster] master.HMaster: * ABORTING
master 9f0ca3fedcda,16000,1590461189948: Unhandled exception. Starting
shutdown. *java.io.IOException: cannot get log writer at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:838)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:548)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:489)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:157)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:297) at
org.apache.hadoop.hbase.master.store.LocalRegion.createWAL(LocalRegion.java:193)
at
[jira] [Created] (HBASE-24430) upgrading standalone-mode hbase from 2.2 to 2.3 fails because of local filesystem not supporting hflush
Zhuqi Jin created HBASE-24430:
-
Summary: upgrading standalone-mode hbase from 2.2 to 2.3 fails
because of local filesystem not supporting hflush
Key: HBASE-24430
URL: https://issues.apache.org/jira/browse/HBASE-24430
Project: HBase
Issue Type: Bug
Components: wal
Affects Versions: 2.3.0
Reporter: Zhuqi Jin
When we tested upgrading HBASE from 2.2 to 2.4/2.5, the upgraded node failed to
start.
The error message is shown below:
{code:java}
2020-05-26 02:46:33,124 ERROR [master/9f0ca3fedcda:16000:becomeActiveMaster]
wal.AsyncFSWALProvider: The RegionServer async write ahead log provider relies
on the ability to call hflush for proper operation during component failures,
but the current FileSystem does not support doing so. Please check the config
value of 'hbase.wal.dir' and ensure it points to a FileSystem mount that has
suitable capabilities for output streams.2020-05-26 02:46:33,124 ERROR
[master/9f0ca3fedcda:16000:becomeActiveMaster] wal.AsyncFSWALProvider: The
RegionServer async write ahead log provider relies on the ability to call
hflush for proper operation during component failures, but the current
FileSystem does not support doing so. Please check the config value of
'hbase.wal.dir' and ensure it points to a FileSystem mount that has suitable
capabilities for output streams.2020-05-26 02:46:33,130 INFO
[master/9f0ca3fedcda:16000:becomeActiveMaster] wal.AbstractFSWAL: Closed WAL:
AsyncFSWAL 9f0ca3fedcda%2C16000%2C1590461189948:(num 1590461193109)2020-05-26
02:46:33,134 ERROR [master/9f0ca3fedcda:16000:becomeActiveMaster]
master.HMaster: Failed to become active masterjava.io.IOException: cannot get
log writer at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:838)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:548)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:489)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:157)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:297) at
org.apache.hadoop.hbase.master.store.LocalRegion.createWAL(LocalRegion.java:193)
at
org.apache.hadoop.hbase.master.store.LocalRegion.bootstrap(LocalRegion.java:213)
at
org.apache.hadoop.hbase.master.store.LocalRegion.create(LocalRegion.java:310)
at org.apache.hadoop.hbase.master.store.LocalStore.create(LocalStore.java:148)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:969)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2245)
at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:626) at
java.lang.Thread.run(Thread.java:748)Caused by:
org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException:
hflush at
org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:71)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:169)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:166)
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:105)
... 17 more2020-05-26 02:46:33,135 ERROR
[master/9f0ca3fedcda:16000:becomeActiveMaster] master.HMaster: * ABORTING
master 9f0ca3fedcda,16000,1590461189948: Unhandled exception. Starting
shutdown. *java.io.IOException: cannot get log writer at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:838)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:548)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:489)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:157)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at
[jira] [Commented] (HBASE-24401) Cell size limit check on append should consider 0 or less value to disable the check
[
https://issues.apache.org/jira/browse/HBASE-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116377#comment-17116377
]
Hudson commented on HBASE-24401:
Results for branch branch-2
[build #2676 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/]:
(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/2676/General_20Nightly_20Build_20Report/]
(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/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Cell size limit check on append should consider 0 or less value to disable
> the check
>
>
> Key: HBASE-24401
> URL: https://issues.apache.org/jira/browse/HBASE-24401
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.2.0, 1.4.10, 2.3.0, 2.1.5
>Reporter: wenbang
>Assignee: wenbang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> HBASE-22274 added a cell size check for append in HRegion, but did not
> consider 0 and less values.
> If we set the parameter *hbase.server.keyvalue.maxsize* to 0, expect to turn
> off the cell size check, all append operations will fail.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24387) TableSnapshotInputFormatImpl support row limit on each InputSplit
[
https://issues.apache.org/jira/browse/HBASE-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116376#comment-17116376
]
Hudson commented on HBASE-24387:
Results for branch branch-2
[build #2676 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/]:
(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/2676/General_20Nightly_20Build_20Report/]
(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/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> TableSnapshotInputFormatImpl support row limit on each InputSplit
> -
>
> Key: HBASE-24387
> URL: https://issues.apache.org/jira/browse/HBASE-24387
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In some scenario , We want to scan limited rows on each InputSplit for
> sampling data extraction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24427) HStore.add log format error
[
https://issues.apache.org/jira/browse/HBASE-24427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116380#comment-17116380
]
Hudson commented on HBASE-24427:
Results for branch branch-2
[build #2676 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/]:
(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/2676/General_20Nightly_20Build_20Report/]
(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/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> HStore.add log format error
> ---
>
> Key: HBASE-24427
> URL: https://issues.apache.org/jira/browse/HBASE-24427
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.3.0, master, 2.2.4
>Reporter: wenfeiyi666
>Assignee: wenfeiyi666
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.10, 2.2.5
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24417) update copyright notices year to 2020
[
https://issues.apache.org/jira/browse/HBASE-24417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116378#comment-17116378
]
Hudson commented on HBASE-24417:
Results for branch branch-2
[build #2676 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/]:
(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/2676/General_20Nightly_20Build_20Report/]
(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/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> update copyright notices year to 2020
> -
>
> Key: HBASE-24417
> URL: https://issues.apache.org/jira/browse/HBASE-24417
> Project: HBase
> Issue Type: Task
> Components: documentation
>Reporter: Guangxu Cheng
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24426) Missing regionName while logging warning in HBCKServerCrashProcedure
[
https://issues.apache.org/jira/browse/HBASE-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116379#comment-17116379
]
Hudson commented on HBASE-24426:
Results for branch branch-2
[build #2676 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/]:
(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/2676/General_20Nightly_20Build_20Report/]
(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/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2676/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Missing regionName while logging warning in HBCKServerCrashProcedure
>
>
> Key: HBASE-24426
> URL: https://issues.apache.org/jira/browse/HBASE-24426
> Project: HBase
> Issue Type: Bug
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24376) MergeNormalizer is merging non-adjacent regions and causing region overlaps/holes.
[
https://issues.apache.org/jira/browse/HBASE-24376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116344#comment-17116344
]
Guanghao Zhang commented on HBASE-24376:
{quote}bq. do you want this Jira in 2.2? If so, I will do a backport to 2.2
branch, thanks.
{quote}
Yes. Thanks.
> MergeNormalizer is merging non-adjacent regions and causing region
> overlaps/holes.
> --
>
> Key: HBASE-24376
> URL: https://issues.apache.org/jira/browse/HBASE-24376
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Critical
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0
>
>
> Currently, we found normalizer was merging regions which are non-adjacent, it
> will cause inconsistencies in the cluster.
> {code:java}
> 439055 2020-05-08 17:47:09,814 INFO
> org.apache.hadoop.hbase.master.normalizer.MergeNormalizationPlan: Executing
> merging normalization plan: MergeNormalizationPlan{firstRegion={ENCODED =>
> 47fe236a5e3649ded95cb64ad0c08492, NAME =>
> 'TABLE,\x03\x01\x05\x01\x04\x02,1554838974870.47fe236a5e3649ded95cb64ad
> 0c08492.', STARTKEY => '\x03\x01\x05\x01\x04\x02', ENDKEY =>
> '\x03\x01\x05\x01\x04\x02\x01\x02\x02201904082200\x00\x00\x03Mac\x00\x00\x00\x00\x00\x00\x00\x00\x00iMac13,1\x00\x00\x00\x00\x00\x049.3-14E260\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x05'},
> secondRegion={ENCODED => 0c0f2aa67f4329d5c4 8ba0320f173d31, NAME =>
> 'TABLE,\x03\x01\x05\x02\x01\x01,1554830735526.0c0f2aa67f4329d5c48ba0320f173d31.',
> STARTKEY => '\x03\x01\x05\x02\x01\x01', ENDKEY =>
> '\x03\x01\x05\x02\x01\x02'}}
> 439056 2020-05-08 17:47:11,438 INFO org.apache.hadoop.hbase.ScheduledChore:
> CatalogJanitor-*:16000 average execution time: 1676219193 ns.
> 439057 2020-05-08 17:47:11,730 INFO org.apache.hadoop.hbase.master.HMaster:
> Client=null/null merge regions [47fe236a5e3649ded95cb64ad0c08492],
> [0c0f2aa67f4329d5c48ba0320f173d31]
> {code}
>
> The root cause is that getMergeNormalizationPlan() uses a list of regionInfo
> which is ordered by regionName. regionName does not necessary guarantee the
> order of STARTKEY (let's say 'aa1', 'aa1!', in order of regionName, it will
> be 'aa1!' followed by 'aa1'. This will result in normalizer merging
> non-adjacent regions into one and creates overlaps. This is not an issue in
> branch-1 as the list is already ordered by RegionInfo.COMPARATOR in
> normalizer.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23296) Add CompositeBucketCache to support tiered BC
[ https://issues.apache.org/jira/browse/HBASE-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116335#comment-17116335 ] chenxu commented on HBASE-23296: sorry，make it as public already [~anoop.hbase] > Add CompositeBucketCache to support tiered BC > - > > Key: HBASE-23296 > URL: https://issues.apache.org/jira/browse/HBASE-23296 > Project: HBase > Issue Type: New Feature > Components: BlockCache >Reporter: chenxu >Assignee: chenxu >Priority: Major > > LruBlockCache is not suitable in the following scenarios: > (1) cache size too large (will take too much heap memory, and > evictBlocksByHfileName is not so efficient, as HBASE-23277 mentioned) > (2) block evicted frequently, especially cacheOnWrite & prefetchOnOpen are > enabled. > Since block‘s data is reclaimed by GC, this may affect GC performance. > So how about enabling a Bucket based L1 Cache. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24376) MergeNormalizer is merging non-adjacent regions and causing region overlaps/holes.
[
https://issues.apache.org/jira/browse/HBASE-24376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-24376.
--
Fix Version/s: 2.4.0
2.3.0
3.0.0-alpha-1
Resolution: Fixed
> MergeNormalizer is merging non-adjacent regions and causing region
> overlaps/holes.
> --
>
> Key: HBASE-24376
> URL: https://issues.apache.org/jira/browse/HBASE-24376
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Critical
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0
>
>
> Currently, we found normalizer was merging regions which are non-adjacent, it
> will cause inconsistencies in the cluster.
> {code:java}
> 439055 2020-05-08 17:47:09,814 INFO
> org.apache.hadoop.hbase.master.normalizer.MergeNormalizationPlan: Executing
> merging normalization plan: MergeNormalizationPlan{firstRegion={ENCODED =>
> 47fe236a5e3649ded95cb64ad0c08492, NAME =>
> 'TABLE,\x03\x01\x05\x01\x04\x02,1554838974870.47fe236a5e3649ded95cb64ad
> 0c08492.', STARTKEY => '\x03\x01\x05\x01\x04\x02', ENDKEY =>
> '\x03\x01\x05\x01\x04\x02\x01\x02\x02201904082200\x00\x00\x03Mac\x00\x00\x00\x00\x00\x00\x00\x00\x00iMac13,1\x00\x00\x00\x00\x00\x049.3-14E260\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x05'},
> secondRegion={ENCODED => 0c0f2aa67f4329d5c4 8ba0320f173d31, NAME =>
> 'TABLE,\x03\x01\x05\x02\x01\x01,1554830735526.0c0f2aa67f4329d5c48ba0320f173d31.',
> STARTKEY => '\x03\x01\x05\x02\x01\x01', ENDKEY =>
> '\x03\x01\x05\x02\x01\x02'}}
> 439056 2020-05-08 17:47:11,438 INFO org.apache.hadoop.hbase.ScheduledChore:
> CatalogJanitor-*:16000 average execution time: 1676219193 ns.
> 439057 2020-05-08 17:47:11,730 INFO org.apache.hadoop.hbase.master.HMaster:
> Client=null/null merge regions [47fe236a5e3649ded95cb64ad0c08492],
> [0c0f2aa67f4329d5c48ba0320f173d31]
> {code}
>
> The root cause is that getMergeNormalizationPlan() uses a list of regionInfo
> which is ordered by regionName. regionName does not necessary guarantee the
> order of STARTKEY (let's say 'aa1', 'aa1!', in order of regionName, it will
> be 'aa1!' followed by 'aa1'. This will result in normalizer merging
> non-adjacent regions into one and creates overlaps. This is not an issue in
> branch-1 as the list is already ordered by RegionInfo.COMPARATOR in
> normalizer.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24370) Avoid aggressive MergeRegion and GCMultipleMergedRegionsProcedure
[ https://issues.apache.org/jira/browse/HBASE-24370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huaxiang Sun resolved HBASE-24370. -- Fix Version/s: 2.4.0 2.3.0 3.0.0-alpha-1 Resolution: Fixed > Avoid aggressive MergeRegion and GCMultipleMergedRegionsProcedure > -- > > Key: HBASE-24370 > URL: https://issues.apache.org/jira/browse/HBASE-24370 > Project: HBase > Issue Type: Bug > Components: master >Reporter: Huaxiang Sun >Assignee: Huaxiang Sun >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0 > > > In > [https://github.com/apache/hbase/blob/a40a0322a73add68d9cb0579abacdd6a2e41e8fb/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/MergeTableRegionsProcedure.java#L478, > > |https://github.com/apache/hbase/blob/a40a0322a73add68d9cb0579abacdd6a2e41e8fb/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/MergeTableRegionsProcedure.java#L478] > prepareMergeRegion, it checks if one of merged parent regions is a merged > child region and has not been GCed. If it is ready to GC, it will kick off a > GCMultipleMergedRegionsProcedure and also start the MergeRegionProcedure. > There is a race condition here. If MergeRegionProcedure finishes first, it > will delete meta row for the merged child region. Then > GCMultipleMergedRegionsProcedure runs, and because the newly added check, it > thinks GC has been done and wont schedule GCRegionProcedure to clean up those > merged parent regions. The end result is that these merged parent regions are > left as orphans on Filesystem. > > [https://github.com/apache/hbase/blob/a40a0322a73add68d9cb0579abacdd6a2e41e8fb/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/GCMultipleMergedRegionsProcedure.java#L105] > > The proposed solution is to avoid being so aggressive, if it needs to kick > off GCMultipleMergedRegionsProcedure, then abort MergeRegionProcedure and > user can try MergeRegionProcedure later. > [|https://github.com/apache/hbase/blob/a40a0322a73add68d9cb0579abacdd6a2e41e8fb/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/MergeTableRegionsProcedure.java#L478] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24376) MergeNormalizer is merging non-adjacent regions and causing region overlaps/holes.
[
https://issues.apache.org/jira/browse/HBASE-24376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116302#comment-17116302
]
Huaxiang Sun commented on HBASE-24376:
--
Resolve it for now.
> MergeNormalizer is merging non-adjacent regions and causing region
> overlaps/holes.
> --
>
> Key: HBASE-24376
> URL: https://issues.apache.org/jira/browse/HBASE-24376
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Critical
>
> Currently, we found normalizer was merging regions which are non-adjacent, it
> will cause inconsistencies in the cluster.
> {code:java}
> 439055 2020-05-08 17:47:09,814 INFO
> org.apache.hadoop.hbase.master.normalizer.MergeNormalizationPlan: Executing
> merging normalization plan: MergeNormalizationPlan{firstRegion={ENCODED =>
> 47fe236a5e3649ded95cb64ad0c08492, NAME =>
> 'TABLE,\x03\x01\x05\x01\x04\x02,1554838974870.47fe236a5e3649ded95cb64ad
> 0c08492.', STARTKEY => '\x03\x01\x05\x01\x04\x02', ENDKEY =>
> '\x03\x01\x05\x01\x04\x02\x01\x02\x02201904082200\x00\x00\x03Mac\x00\x00\x00\x00\x00\x00\x00\x00\x00iMac13,1\x00\x00\x00\x00\x00\x049.3-14E260\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x05'},
> secondRegion={ENCODED => 0c0f2aa67f4329d5c4 8ba0320f173d31, NAME =>
> 'TABLE,\x03\x01\x05\x02\x01\x01,1554830735526.0c0f2aa67f4329d5c48ba0320f173d31.',
> STARTKEY => '\x03\x01\x05\x02\x01\x01', ENDKEY =>
> '\x03\x01\x05\x02\x01\x02'}}
> 439056 2020-05-08 17:47:11,438 INFO org.apache.hadoop.hbase.ScheduledChore:
> CatalogJanitor-*:16000 average execution time: 1676219193 ns.
> 439057 2020-05-08 17:47:11,730 INFO org.apache.hadoop.hbase.master.HMaster:
> Client=null/null merge regions [47fe236a5e3649ded95cb64ad0c08492],
> [0c0f2aa67f4329d5c48ba0320f173d31]
> {code}
>
> The root cause is that getMergeNormalizationPlan() uses a list of regionInfo
> which is ordered by regionName. regionName does not necessary guarantee the
> order of STARTKEY (let's say 'aa1', 'aa1!', in order of regionName, it will
> be 'aa1!' followed by 'aa1'. This will result in normalizer merging
> non-adjacent regions into one and creates overlaps. This is not an issue in
> branch-1 as the list is already ordered by RegionInfo.COMPARATOR in
> normalizer.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24369) Provide more information about merged child regions in Hbck Overlaps section, which cannot be fixed immediately
[ https://issues.apache.org/jira/browse/HBASE-24369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Huaxiang Sun resolved HBASE-24369. -- Fix Version/s: 2.4.0 2.3.0 3.0.0-alpha-1 Resolution: Fixed > Provide more information about merged child regions in Hbck Overlaps > section, which cannot be fixed immediately > - > > Key: HBASE-24369 > URL: https://issues.apache.org/jira/browse/HBASE-24369 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 2.3.0 >Reporter: Huaxiang Sun >Assignee: Huaxiang Sun >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0 > > Attachments: Screen Shot 2020-05-21 at 11.14.48 AM.png > > > Right now, in Master's hbck page, pairs of overlap regions are listed. > with Hbck2 -fixMeta, it will merge these overlap regions. However, if one of > the region is a newly merged child region and GC has not kicked in yet, they > are not fixable (merge will fail). > Users get confused as why after HBCK2 -fixMeta and still there are overlaps. > To avoid this confusion, propose a new subsection saying that master is doing > GC on these regions and these regions cannot be fixed/merged at this moment, > wait until these regions are ready (not showing up in this subsection) to > start the fix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-24376) MergeNormalizer is merging non-adjacent regions and causing region overlaps/holes.
[
https://issues.apache.org/jira/browse/HBASE-24376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116300#comment-17116300
]
Huaxiang Sun edited comment on HBASE-24376 at 5/25/20, 11:12 PM:
-
Hi [~zghao], do you want this Jira in 2.2? If so, I will do a backport to 2.2
branch, thanks.
was (Author: huaxiangsun):
Hi [~zghao], do you want this Jira backport to 2.2? If so, I will do a backport
to 2.2 branch, thanks.
> MergeNormalizer is merging non-adjacent regions and causing region
> overlaps/holes.
> --
>
> Key: HBASE-24376
> URL: https://issues.apache.org/jira/browse/HBASE-24376
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Critical
>
> Currently, we found normalizer was merging regions which are non-adjacent, it
> will cause inconsistencies in the cluster.
> {code:java}
> 439055 2020-05-08 17:47:09,814 INFO
> org.apache.hadoop.hbase.master.normalizer.MergeNormalizationPlan: Executing
> merging normalization plan: MergeNormalizationPlan{firstRegion={ENCODED =>
> 47fe236a5e3649ded95cb64ad0c08492, NAME =>
> 'TABLE,\x03\x01\x05\x01\x04\x02,1554838974870.47fe236a5e3649ded95cb64ad
> 0c08492.', STARTKEY => '\x03\x01\x05\x01\x04\x02', ENDKEY =>
> '\x03\x01\x05\x01\x04\x02\x01\x02\x02201904082200\x00\x00\x03Mac\x00\x00\x00\x00\x00\x00\x00\x00\x00iMac13,1\x00\x00\x00\x00\x00\x049.3-14E260\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x05'},
> secondRegion={ENCODED => 0c0f2aa67f4329d5c4 8ba0320f173d31, NAME =>
> 'TABLE,\x03\x01\x05\x02\x01\x01,1554830735526.0c0f2aa67f4329d5c48ba0320f173d31.',
> STARTKEY => '\x03\x01\x05\x02\x01\x01', ENDKEY =>
> '\x03\x01\x05\x02\x01\x02'}}
> 439056 2020-05-08 17:47:11,438 INFO org.apache.hadoop.hbase.ScheduledChore:
> CatalogJanitor-*:16000 average execution time: 1676219193 ns.
> 439057 2020-05-08 17:47:11,730 INFO org.apache.hadoop.hbase.master.HMaster:
> Client=null/null merge regions [47fe236a5e3649ded95cb64ad0c08492],
> [0c0f2aa67f4329d5c48ba0320f173d31]
> {code}
>
> The root cause is that getMergeNormalizationPlan() uses a list of regionInfo
> which is ordered by regionName. regionName does not necessary guarantee the
> order of STARTKEY (let's say 'aa1', 'aa1!', in order of regionName, it will
> be 'aa1!' followed by 'aa1'. This will result in normalizer merging
> non-adjacent regions into one and creates overlaps. This is not an issue in
> branch-1 as the list is already ordered by RegionInfo.COMPARATOR in
> normalizer.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24376) MergeNormalizer is merging non-adjacent regions and causing region overlaps/holes.
[
https://issues.apache.org/jira/browse/HBASE-24376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116300#comment-17116300
]
Huaxiang Sun commented on HBASE-24376:
--
Hi [~zghao], do you want this Jira backport to 2.2? If so, I will do a backport
to 2.2 branch, thanks.
> MergeNormalizer is merging non-adjacent regions and causing region
> overlaps/holes.
> --
>
> Key: HBASE-24376
> URL: https://issues.apache.org/jira/browse/HBASE-24376
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Critical
>
> Currently, we found normalizer was merging regions which are non-adjacent, it
> will cause inconsistencies in the cluster.
> {code:java}
> 439055 2020-05-08 17:47:09,814 INFO
> org.apache.hadoop.hbase.master.normalizer.MergeNormalizationPlan: Executing
> merging normalization plan: MergeNormalizationPlan{firstRegion={ENCODED =>
> 47fe236a5e3649ded95cb64ad0c08492, NAME =>
> 'TABLE,\x03\x01\x05\x01\x04\x02,1554838974870.47fe236a5e3649ded95cb64ad
> 0c08492.', STARTKEY => '\x03\x01\x05\x01\x04\x02', ENDKEY =>
> '\x03\x01\x05\x01\x04\x02\x01\x02\x02201904082200\x00\x00\x03Mac\x00\x00\x00\x00\x00\x00\x00\x00\x00iMac13,1\x00\x00\x00\x00\x00\x049.3-14E260\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x05'},
> secondRegion={ENCODED => 0c0f2aa67f4329d5c4 8ba0320f173d31, NAME =>
> 'TABLE,\x03\x01\x05\x02\x01\x01,1554830735526.0c0f2aa67f4329d5c48ba0320f173d31.',
> STARTKEY => '\x03\x01\x05\x02\x01\x01', ENDKEY =>
> '\x03\x01\x05\x02\x01\x02'}}
> 439056 2020-05-08 17:47:11,438 INFO org.apache.hadoop.hbase.ScheduledChore:
> CatalogJanitor-*:16000 average execution time: 1676219193 ns.
> 439057 2020-05-08 17:47:11,730 INFO org.apache.hadoop.hbase.master.HMaster:
> Client=null/null merge regions [47fe236a5e3649ded95cb64ad0c08492],
> [0c0f2aa67f4329d5c48ba0320f173d31]
> {code}
>
> The root cause is that getMergeNormalizationPlan() uses a list of regionInfo
> which is ordered by regionName. regionName does not necessary guarantee the
> order of STARTKEY (let's say 'aa1', 'aa1!', in order of regionName, it will
> be 'aa1!' followed by 'aa1'. This will result in normalizer merging
> non-adjacent regions into one and creates overlaps. This is not an issue in
> branch-1 as the list is already ordered by RegionInfo.COMPARATOR in
> normalizer.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HBASE-24429) Flaky test, TestFromClientSide5.testScanMetrics[2]
[
https://issues.apache.org/jira/browse/HBASE-24429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun reassigned HBASE-24429:
Assignee: Huaxiang Sun
> Flaky test, TestFromClientSide5.testScanMetrics[2]
> --
>
> Key: HBASE-24429
> URL: https://issues.apache.org/jira/browse/HBASE-24429
> Project: HBase
> Issue Type: Bug
> Components: scan
>Affects Versions: master
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Major
>
> I see this test failure with master branch, assume this is a flakey test.
> {code:java}
> precommit checks / yetus jdk8 Hadoop3 checks /
> org.apache.hadoop.hbase.client.TestFromClientSide5.testScanMetrics[2]Failing
> for the past 1 build (Since #2 )Took 4.3 sec.Error MessageDid not count the
> result bytes expected:<60> but was:<180>Stacktracejava.lang.AssertionError:
> Did not count the result bytes expected:<60> but was:<180>
> at
> org.apache.hadoop.hbase.client.TestFromClientSide5.testScanMetrics(TestFromClientSide5.java:1007)
> Standard Output2020-05-25 13:42:55,389 INFO [Time-limited test]
> hbase.ResourceChecker(151): before:
> client.TestFromClientSide5#testCacheOnWriteEvictOnClose[0] Thread=6,
> OpenFileDescriptor=220, MaxFileDescriptor=1048576, SystemLoadAverage=2329,
> ProcessCount=18, AvailableMemoryMB=16442
> 2020-05-25 13:42:56,056 DEBUG [Time-limited test]
> hbase.HBaseTestingUtility(333): Setting hbase.rootdir to
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0
> 2020-05-25 13:42:56,073 INFO [Time-limited test]
> hbase.HBaseTestingUtility(1047): Starting up minicluster with option:
> StartMiniClusterOption{numMasters=1, masterClass=null, numRegionServers=1,
> rsPorts=, rsClass=null, numDataNodes=1, dataNodeHosts=null, numZkServers=1,
> createRootDir=false, createWALDir=false}
> 2020-05-25 13:42:56,075 INFO [Time-limited test]
> hbase.HBaseZKTestingUtility(83): Created new mini-cluster data directory:
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/cluster_21ceb59f-5cc8-f531-e8c5-108c3a2d3cbb,
> deleteOnExit=true
> 2020-05-25 13:42:56,076 INFO [Time-limited test]
> hbase.HBaseTestingUtility(1061): STARTING DFS
> 2020-05-25 13:42:56,077 INFO [Time-limited test]
> hbase.HBaseTestingUtility(736): Setting test.cache.data to
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/test.cache.data
> in system properties and HBase conf
> 2020-05-25 13:42:56,079 INFO [Time-limited test]
> hbase.HBaseTestingUtility(736): Setting hadoop.tmp.dir to
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/hadoop.tmp.dir
> in system properties and HBase conf
> 2020-05-25 13:42:56,080 INFO [Time-limited test]
> hbase.HBaseTestingUtility(736): Setting hadoop.log.dir to
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/hadoop.log.dir
> in system properties and HBase conf
> 2020-05-25 13:42:56,082 INFO [Time-limited test]
> hbase.HBaseTestingUtility(736): Setting mapreduce.cluster.local.dir to
> /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/mapreduce.cluster.local.dir
> in system properties and HBase conf
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24429) Flaky test, TestFromClientSide5.testScanMetrics[2]
Huaxiang Sun created HBASE-24429:
Summary: Flaky test, TestFromClientSide5.testScanMetrics[2]
Key: HBASE-24429
URL: https://issues.apache.org/jira/browse/HBASE-24429
Project: HBase
Issue Type: Bug
Components: scan
Affects Versions: master
Reporter: Huaxiang Sun
I see this test failure with master branch, assume this is a flakey test.
{code:java}
precommit checks / yetus jdk8 Hadoop3 checks /
org.apache.hadoop.hbase.client.TestFromClientSide5.testScanMetrics[2]Failing
for the past 1 build (Since #2 )Took 4.3 sec.Error MessageDid not count the
result bytes expected:<60> but was:<180>Stacktracejava.lang.AssertionError: Did
not count the result bytes expected:<60> but was:<180>
at
org.apache.hadoop.hbase.client.TestFromClientSide5.testScanMetrics(TestFromClientSide5.java:1007)
Standard Output2020-05-25 13:42:55,389 INFO [Time-limited test]
hbase.ResourceChecker(151): before:
client.TestFromClientSide5#testCacheOnWriteEvictOnClose[0] Thread=6,
OpenFileDescriptor=220, MaxFileDescriptor=1048576, SystemLoadAverage=2329,
ProcessCount=18, AvailableMemoryMB=16442
2020-05-25 13:42:56,056 DEBUG [Time-limited test]
hbase.HBaseTestingUtility(333): Setting hbase.rootdir to
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0
2020-05-25 13:42:56,073 INFO [Time-limited test]
hbase.HBaseTestingUtility(1047): Starting up minicluster with option:
StartMiniClusterOption{numMasters=1, masterClass=null, numRegionServers=1,
rsPorts=, rsClass=null, numDataNodes=1, dataNodeHosts=null, numZkServers=1,
createRootDir=false, createWALDir=false}
2020-05-25 13:42:56,075 INFO [Time-limited test]
hbase.HBaseZKTestingUtility(83): Created new mini-cluster data directory:
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/cluster_21ceb59f-5cc8-f531-e8c5-108c3a2d3cbb,
deleteOnExit=true
2020-05-25 13:42:56,076 INFO [Time-limited test]
hbase.HBaseTestingUtility(1061): STARTING DFS
2020-05-25 13:42:56,077 INFO [Time-limited test]
hbase.HBaseTestingUtility(736): Setting test.cache.data to
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/test.cache.data
in system properties and HBase conf
2020-05-25 13:42:56,079 INFO [Time-limited test]
hbase.HBaseTestingUtility(736): Setting hadoop.tmp.dir to
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/hadoop.tmp.dir
in system properties and HBase conf
2020-05-25 13:42:56,080 INFO [Time-limited test]
hbase.HBaseTestingUtility(736): Setting hadoop.log.dir to
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/hadoop.log.dir
in system properties and HBase conf
2020-05-25 13:42:56,082 INFO [Time-limited test]
hbase.HBaseTestingUtility(736): Setting mapreduce.cluster.local.dir to
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1770/yetus-jdk8-hadoop3-check/src/hbase-server/target/test-data/7fed70ca-373b-e224-a047-f4c0dd8789c0/mapreduce.cluster.local.dir
in system properties and HBase conf
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24427) HStore.add log format error
[
https://issues.apache.org/jira/browse/HBASE-24427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116293#comment-17116293
]
Hudson commented on HBASE-24427:
Results for branch branch-2.2
[build #876 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/876/]:
(/) *{color:green}+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.2/876//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.2/876//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.2/876//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> HStore.add log format error
> ---
>
> Key: HBASE-24427
> URL: https://issues.apache.org/jira/browse/HBASE-24427
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 2.3.0, master, 2.2.4
>Reporter: wenfeiyi666
>Assignee: wenfeiyi666
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.10, 2.2.5
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24426) Missing regionName while logging warning in HBCKServerCrashProcedure
[
https://issues.apache.org/jira/browse/HBASE-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116292#comment-17116292
]
Hudson commented on HBASE-24426:
Results for branch branch-2.2
[build #876 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/876/]:
(/) *{color:green}+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.2/876//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.2/876//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.2/876//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Missing regionName while logging warning in HBCKServerCrashProcedure
>
>
> Key: HBASE-24426
> URL: https://issues.apache.org/jira/browse/HBASE-24426
> Project: HBase
> Issue Type: Bug
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24401) Cell size limit check on append should consider 0 or less value to disable the check
[
https://issues.apache.org/jira/browse/HBASE-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116291#comment-17116291
]
Hudson commented on HBASE-24401:
Results for branch branch-2.2
[build #876 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/876/]:
(/) *{color:green}+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.2/876//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.2/876//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.2/876//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Cell size limit check on append should consider 0 or less value to disable
> the check
>
>
> Key: HBASE-24401
> URL: https://issues.apache.org/jira/browse/HBASE-24401
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.2.0, 1.4.10, 2.3.0, 2.1.5
>Reporter: wenbang
>Assignee: wenbang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> HBASE-22274 added a cell size check for append in HRegion, but did not
> consider 0 and less values.
> If we set the parameter *hbase.server.keyvalue.maxsize* to 0, expect to turn
> off the cell size check, all append operations will fail.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24387) TableSnapshotInputFormatImpl support row limit on each InputSplit
[
https://issues.apache.org/jira/browse/HBASE-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116290#comment-17116290
]
Hudson commented on HBASE-24387:
Results for branch branch-2.2
[build #876 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/876/]:
(/) *{color:green}+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.2/876//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.2/876//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.2/876//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> TableSnapshotInputFormatImpl support row limit on each InputSplit
> -
>
> Key: HBASE-24387
> URL: https://issues.apache.org/jira/browse/HBASE-24387
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In some scenario , We want to scan limited rows on each InputSplit for
> sampling data extraction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24154) HdfsFileStatus incompatibility when used with Hadoop 3.1.3 and Hbase version 2.2.4
[
https://issues.apache.org/jira/browse/HBASE-24154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116269#comment-17116269
]
Mohankumar K H commented on HBASE-24154:
Hi,
I was able to solve below problem by changing below two file from downloaded
hbase-2.2.4 source and re-compile with below options and it started working
fine.
hbase-2.2.4/dev-support/hbase-personality.sh
From:
yetus_info "Setting Hadoop 3 versions to test based on
branch-2.2+/master/feature branch rules"
if [[ "${QUICK_HADOOPCHECK}" == "true" ]]; then
hbase_hadoop3_versions="{color:#de350b}3.1.2{color}"
else
hbase_hadoop3_versions="3.1.1 3.1.2"
fi
To:
yetus_info "Setting Hadoop 3 versions to test based on
branch-2.2+/master/feature branch rules"
if [[ "${QUICK_HADOOPCHECK}" == "true" ]]; then
hbase_hadoop3_versions="{color:#57d9a3}3.1.3{color}"
else
hbase_hadoop3_versions="3.1.1 3.1.2 {color:#57d9a3}3.1.3{color}"
fi
hbase-2.2.4/pom.xml
From:
${compileSource}
2.8.5
{color:#de350b}3.1.2{color}
To:
${compileSource}
2.8.5
{color:#57d9a3}3.1.3{color}
Re-compile with below options and started working fine.
mvn -DskipTests clean install && mvn -Dhadoop.profile=3.0
-Dhadoop-three.version=3.1.3 -DskipTests package assembly:single
Thanks
Mohan
> HdfsFileStatus incompatibility when used with Hadoop 3.1.3 and Hbase version
> 2.2.4
> --
>
> Key: HBASE-24154
> URL: https://issues.apache.org/jira/browse/HBASE-24154
> Project: HBase
> Issue Type: Bug
> Components: hadoop3, regionserver
>Affects Versions: 2.2.4
> Environment: cenots 7.6
> util.VersionInfo: HBase 2.2.4,/usr/lib/jvm/java-1.8.0-openjdk
>Reporter: Mohankumar K H
>Priority: Blocker
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi,
> Even after compiling from source I am getting below error message. Hbasse
> master start without any issue, but region server fails with below message
> handler.AssignRegionHandler: Fatal error occurred while opening region
> hbase:meta,,1.1588230740, aborting...
> java.lang.IncompatibleClassChangeError: Found interface
> org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:496)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:116)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:576)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:571)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:584)
> at
> org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:51)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:169)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:166)
> at
> org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:113)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:643)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:126)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:767)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:501)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:442)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:156)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:61)
> at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:284)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getWAL(HRegionServer.java:2181)
> at
> org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler.process(AssignRegionHandler.java:133)
> at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
> 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)
[jira] [Created] (HBASE-24428) Priority compaction for recently split daughter regions
Andrew Kyle Purtell created HBASE-24428:
---
Summary: Priority compaction for recently split daughter regions
Key: HBASE-24428
URL: https://issues.apache.org/jira/browse/HBASE-24428
Project: HBase
Issue Type: Improvement
Components: Compaction
Reporter: Andrew Kyle Purtell
We observe that under hotspotting conditions that splitting will proceed very
slowly and the "_Cannot split region due to reference files being there_" log
line will be logged excessively. (branch-1 based production.) This is because
after a region is split it must be compacted before it can be split again.
Reference files must be replaced by real HFiles, normal housekeeping performed
during compaction. However if the regionserver is under excessive load, its
compaction queues may become deep. The daughters of a recently split
hotspotting region may themselves continue to hotspot and will rapidly need to
split again. If the scheduled compaction work to remove/replace reference files
is queued hundreds or thousands of compaction queue elements behind current,
the recently split daughter regions will not be able to split again for a long
time and may grow very large, producing additional complications (very large
regions, very deep replication queues).
To help avoid this condition we should prioritize the compaction of recently
split daughter regions. Compaction requests include a {{priority}} field and
CompactionRequest implements a comparator that sorts by this field. We already
detect when a compaction request involves a region that has reference files, to
ensure that it gets selected to be eligible for compaction, but we do not seem
to prioritize the requests for post-split housekeeping. Split work should be
placed at the top of the queue. Ensure that this is happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24387) TableSnapshotInputFormatImpl support row limit on each InputSplit
[
https://issues.apache.org/jira/browse/HBASE-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116091#comment-17116091
]
Hudson commented on HBASE-24387:
Results for branch master
[build #1736 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/]: (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/master/1736/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//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/master/1736/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> TableSnapshotInputFormatImpl support row limit on each InputSplit
> -
>
> Key: HBASE-24387
> URL: https://issues.apache.org/jira/browse/HBASE-24387
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In some scenario , We want to scan limited rows on each InputSplit for
> sampling data extraction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24417) update copyright notices year to 2020
[
https://issues.apache.org/jira/browse/HBASE-24417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116093#comment-17116093
]
Hudson commented on HBASE-24417:
Results for branch master
[build #1736 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/]: (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/master/1736/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//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/master/1736/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> update copyright notices year to 2020
> -
>
> Key: HBASE-24417
> URL: https://issues.apache.org/jira/browse/HBASE-24417
> Project: HBase
> Issue Type: Task
> Components: documentation
>Reporter: Guangxu Cheng
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24422) Remove hbase-native-client code from the master branch
[
https://issues.apache.org/jira/browse/HBASE-24422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116089#comment-17116089
]
Hudson commented on HBASE-24422:
Results for branch master
[build #1736 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/]: (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/master/1736/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//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/master/1736/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Remove hbase-native-client code from the master branch
> --
>
> Key: HBASE-24422
> URL: https://issues.apache.org/jira/browse/HBASE-24422
> Project: HBase
> Issue Type: Task
>Affects Versions: master
>Reporter: Bharath Vissapragada
>Assignee: Bharath Vissapragada
>Priority: Minor
> Fix For: 3.0.0-alpha-1
>
>
> Per recent discussions in the slack channel, there is not much value
> in having this code in the master branch. This code has it's dedicated
> git repo at https://github.com/apache/hbase-native-client.
> It was already removed from branch-1 (HBASE-19419) and branch-2
> (HBASE-19176)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24401) Cell size limit check on append should consider 0 or less value to disable the check
[
https://issues.apache.org/jira/browse/HBASE-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116092#comment-17116092
]
Hudson commented on HBASE-24401:
Results for branch master
[build #1736 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/]: (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/master/1736/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//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/master/1736/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Cell size limit check on append should consider 0 or less value to disable
> the check
>
>
> Key: HBASE-24401
> URL: https://issues.apache.org/jira/browse/HBASE-24401
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.2.0, 1.4.10, 2.3.0, 2.1.5
>Reporter: wenbang
>Assignee: wenbang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> HBASE-22274 added a cell size check for append in HRegion, but did not
> consider 0 and less values.
> If we set the parameter *hbase.server.keyvalue.maxsize* to 0, expect to turn
> off the cell size check, all append operations will fail.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24369) Provide more information about merged child regions in Hbck Overlaps section, which cannot be fixed immediately
[
https://issues.apache.org/jira/browse/HBASE-24369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116090#comment-17116090
]
Hudson commented on HBASE-24369:
Results for branch master
[build #1736 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/]: (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/master/1736/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//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/master/1736/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1736/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Provide more information about merged child regions in Hbck Overlaps
> section, which cannot be fixed immediately
> -
>
> Key: HBASE-24369
> URL: https://issues.apache.org/jira/browse/HBASE-24369
> Project: HBase
> Issue Type: Improvement
> Components: master
>Affects Versions: 2.3.0
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Major
> Attachments: Screen Shot 2020-05-21 at 11.14.48 AM.png
>
>
> Right now, in Master's hbck page, pairs of overlap regions are listed.
> with Hbck2 -fixMeta, it will merge these overlap regions. However, if one of
> the region is a newly merged child region and GC has not kicked in yet, they
> are not fixable (merge will fail).
> Users get confused as why after HBCK2 -fixMeta and still there are overlaps.
> To avoid this confusion, propose a new subsection saying that master is doing
> GC on these regions and these regions cannot be fixed/merged at this moment,
> wait until these regions are ready (not showing up in this subsection) to
> start the fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24417) update copyright notices year to 2020
[
https://issues.apache.org/jira/browse/HBASE-24417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116042#comment-17116042
]
Hudson commented on HBASE-24417:
Results for branch branch-2.3
[build #104 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/]:
(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.3/104/General_20Nightly_20Build_20Report/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> update copyright notices year to 2020
> -
>
> Key: HBASE-24417
> URL: https://issues.apache.org/jira/browse/HBASE-24417
> Project: HBase
> Issue Type: Task
> Components: documentation
>Reporter: Guangxu Cheng
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24387) TableSnapshotInputFormatImpl support row limit on each InputSplit
[
https://issues.apache.org/jira/browse/HBASE-24387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116040#comment-17116040
]
Hudson commented on HBASE-24387:
Results for branch branch-2.3
[build #104 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/]:
(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.3/104/General_20Nightly_20Build_20Report/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> TableSnapshotInputFormatImpl support row limit on each InputSplit
> -
>
> Key: HBASE-24387
> URL: https://issues.apache.org/jira/browse/HBASE-24387
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
>Reporter: niuyulin
>Assignee: niuyulin
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In some scenario , We want to scan limited rows on each InputSplit for
> sampling data extraction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24401) Cell size limit check on append should consider 0 or less value to disable the check
[
https://issues.apache.org/jira/browse/HBASE-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116041#comment-17116041
]
Hudson commented on HBASE-24401:
Results for branch branch-2.3
[build #104 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/]:
(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.3/104/General_20Nightly_20Build_20Report/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(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.3/104/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/104/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Cell size limit check on append should consider 0 or less value to disable
> the check
>
>
> Key: HBASE-24401
> URL: https://issues.apache.org/jira/browse/HBASE-24401
> Project: HBase
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1, 2.2.0, 1.4.10, 2.3.0, 2.1.5
>Reporter: wenbang
>Assignee: wenbang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> HBASE-22274 added a cell size check for append in HRegion, but did not
> consider 0 and less values.
> If we set the parameter *hbase.server.keyvalue.maxsize* to 0, expect to turn
> off the cell size check, all append operations will fail.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22120) Replace HTrace with OpenTracing
[ https://issues.apache.org/jira/browse/HBASE-22120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116076#comment-17116076 ] Guanghao Zhang commented on HBASE-22120: [~weichiu] sir, what is the status here? Seems OpenTracing was merged to the new project OpenTelemetry. Do we have plan to use OpenTelemetry directly? > Replace HTrace with OpenTracing > --- > > Key: HBASE-22120 > URL: https://issues.apache.org/jira/browse/HBASE-22120 > Project: HBase > Issue Type: New Feature > Components: tracing >Affects Versions: 3.0.0-alpha-1 >Reporter: Sergey Shelukhin >Assignee: Wei-Chiu Chuang >Priority: Major > > h2. Deprecate HTrace usage in HBase > * HBase 1.x (branch-1) > * Declare HTrace (htrace 3.x) deprecated in the user doc. > * HBase 2.x (branch-2) > * Declare HTrace deprecated in the user doc. Furthermore, state that it is > known not working. > * Either fix the trace context propagation bug in HBase 2.x, or backport > OpenTracing support from the master branch. I am inclined to the latter. > * HBase 3.x (master branch) > * Remove HTrace entirely. > * Add OpenTracing APIs. Potentially backport to HBase 2.4. > * Replace OpenTracing API with OpenTelemetry when the latter stabilizes. > h1. Milestones > # Doc -- deprecation notice > # Replace existing HTrace code with OpenTracing code in the master branch > (3.x) > # Java (a [poc|https://github.com/jojochuang/hbase/tree/HBASE-22120] is > currently under way) > # HBase shell and scripts (Ruby, shell script) > # Doc > # Add new trace instrumentation code for new features not instrumented by > the existing HTace code. > # Propagate the traces to other systems such as HDFS and MapReduce. > # Support other OpenTracing tracers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24427) HStore.add log format error
[ https://issues.apache.org/jira/browse/HBASE-24427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-24427. -- Fix Version/s: (was: 2.2.4) (was: master) 2.2.5 2.1.10 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed to master, branch-2, 2.3, 2.2, 2.1. Thanks [~wenfeiyi666]. > HStore.add log format error > --- > > Key: HBASE-24427 > URL: https://issues.apache.org/jira/browse/HBASE-24427 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.3.0, master, 2.2.4 >Reporter: wenfeiyi666 >Assignee: wenfeiyi666 >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.10, 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] virajjasani merged pull request #1773: HBASE-24427 HStore.add log format error
virajjasani merged pull request #1773: URL: https://github.com/apache/hbase/pull/1773 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1730: HBASE-24289 Heterogeneous Storage for Date Tiered Compaction
Apache-HBase commented on pull request #1730: URL: https://github.com/apache/hbase/pull/1730#issuecomment-633557067 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 1m 7s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +0 :ok: | mvndep | 0m 20s | Maven dependency ordering for branch | | +1 :green_heart: | mvninstall | 4m 36s | master passed | | +1 :green_heart: | compile | 3m 7s | master passed | | +1 :green_heart: | shadedjars | 6m 24s | branch has no errors when building our shaded downstream artifacts. | | -0 :warning: | javadoc | 0m 15s | root in master failed. | | -0 :warning: | javadoc | 0m 16s | hbase-common in master failed. | | -0 :warning: | javadoc | 0m 40s | hbase-server in master failed. | ||| _ Patch Compile Tests _ | | +0 :ok: | mvndep | 0m 11s | Maven dependency ordering for patch | | +1 :green_heart: | mvninstall | 4m 30s | the patch passed | | +1 :green_heart: | compile | 3m 3s | the patch passed | | +1 :green_heart: | javac | 3m 3s | the patch passed | | +1 :green_heart: | shadedjars | 6m 25s | patch has no errors when building our shaded downstream artifacts. | | -0 :warning: | javadoc | 0m 14s | hbase-common in the patch failed. | | -0 :warning: | javadoc | 0m 40s | hbase-server in the patch failed. | | -0 :warning: | javadoc | 0m 14s | root in the patch failed. | ||| _ Other Tests _ | | +1 :green_heart: | unit | 246m 10s | root in the patch passed. | | | | 280m 45s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1730 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux 23eb6f403b97 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | Default Java | 2020-01-14 | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/testReport/ | | Max. process+thread count | 4793 (vs. ulimit of 12500) | | modules | C: hbase-common hbase-server . U: . | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] virajjasani commented on pull request #1771: HBASE-24425 Run hbck_chore_run and catalogjanitor_run on draw of 'HBC…
virajjasani commented on pull request #1771: URL: https://github.com/apache/hbase/pull/1771#issuecomment-633555753 > LGTM. branch-2 only? Looks like a clean apply to master and branch-2.3 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] virajjasani commented on a change in pull request #1771: HBASE-24425 Run hbck_chore_run and catalogjanitor_run on draw of 'HBC…
virajjasani commented on a change in pull request #1771:
URL: https://github.com/apache/hbase/pull/1771#discussion_r429914409
##
File path: hbase-server/src/main/resources/hbase-webapps/master/hbck.jsp
##
@@ -37,9 +37,17 @@
<%@ page import="org.apache.hadoop.hbase.util.Pair" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor.Report" %>
+<%@ page import="org.apache.hadoop.hbase.util.Threads" %>
<%
+ final String cacheParameterValue = request.getParameter("cache");
+ boolean cache = Boolean.valueOf(cacheParameterValue);
Review comment:
nit: Since we need `boolean`, we can directly use:
`Boolean.parseBoolean(cacheParameterValue)`
##
File path: hbase-server/src/main/resources/hbase-webapps/master/hbck.jsp
##
@@ -37,9 +37,17 @@
<%@ page import="org.apache.hadoop.hbase.util.Pair" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor.Report" %>
+<%@ page import="org.apache.hadoop.hbase.util.Threads" %>
Review comment:
Not being used it seems.
##
File path: hbase-server/src/main/resources/hbase-webapps/master/hbck.jsp
##
@@ -37,9 +37,17 @@
<%@ page import="org.apache.hadoop.hbase.util.Pair" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor" %>
<%@ page import="org.apache.hadoop.hbase.master.CatalogJanitor.Report" %>
+<%@ page import="org.apache.hadoop.hbase.util.Threads" %>
<%
+ final String cacheParameterValue = request.getParameter("cache");
+ boolean cache = Boolean.valueOf(cacheParameterValue);
final HMaster master = (HMaster)
getServletContext().getAttribute(HMaster.MASTER);
pageContext.setAttribute("pageTitle", "HBase Master HBCK Report: " +
master.getServerName());
+ if (!cache) {
+// Run the two reporters inline w/ drawing of the page. If exception, will
show in page draw.
+master.getMasterRpcServices().runHbckChore(null, null);
+master.getMasterRpcServices().runCatalogScan(null, null);
Review comment:
MasterRpcServices throw `ServiceException` for both `runHbckChore` and
`runCatalogScan`. Maybe we can handle it and print some nice error message?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Resolved] (HBASE-24426) Missing regionName while logging warning in HBCKServerCrashProcedure
[ https://issues.apache.org/jira/browse/HBASE-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-24426. -- Fix Version/s: 2.2.5 2.3.0 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed to master, branch-2, 2.3, 2.2. > Missing regionName while logging warning in HBCKServerCrashProcedure > > > Key: HBASE-24426 > URL: https://issues.apache.org/jira/browse/HBASE-24426 > Project: HBase > Issue Type: Bug >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] Apache-HBase commented on pull request #1770: HBASE-24416 RegionNormalizer spliting region should not be limited by…
Apache-HBase commented on pull request #1770: URL: https://github.com/apache/hbase/pull/1770#issuecomment-633542791 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 36s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 1s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 4m 28s | master passed | | +1 :green_heart: | checkstyle | 1m 5s | master passed | | +1 :green_heart: | spotbugs | 1m 58s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 20s | the patch passed | | -0 :warning: | checkstyle | 1m 2s | hbase-server: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0) | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 11m 17s | Patch does not cause any errors with Hadoop 3.1.2 3.2.1. | | +1 :green_heart: | spotbugs | 2m 21s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 15s | The patch does not generate ASF License warnings. | | | | 34m 4s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1770/2/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1770 | | Optional Tests | dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle | | uname | Linux b166b4ff585d 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | checkstyle | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1770/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt | | Max. process+thread count | 94 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1770/2/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12 | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] virajjasani merged pull request #1772: HBASE-24426 : Provide regionName in warning during failure to move re…
virajjasani merged pull request #1772: URL: https://github.com/apache/hbase/pull/1772 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (HBASE-22738) Fallback to default group to choose RS when there are no RS in current group
[ https://issues.apache.org/jira/browse/HBASE-22738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17115943#comment-17115943 ] Sun Xin commented on HBASE-22738: - Hi [~Xiaolin Ha] , are you still working on this issue? If not, I could finish it. > Fallback to default group to choose RS when there are no RS in current group > > > Key: HBASE-22738 > URL: https://issues.apache.org/jira/browse/HBASE-22738 > Project: HBase > Issue Type: Bug > Components: rsgroup >Reporter: Guanghao Zhang >Assignee: Xiaolin Ha >Priority: Major > > We configure one regionserver for hbase system table. But when rolling > upgrade, you need move the region to other regionservers. But because there > are no other regionservers in this group, you cannot move the region... > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] Apache-HBase commented on pull request #1773: HBASE-24427 HStore.add log format error
Apache-HBase commented on pull request #1773: URL: https://github.com/apache/hbase/pull/1773#issuecomment-633523744 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 30s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 42s | master passed | | +1 :green_heart: | checkstyle | 1m 6s | master passed | | +1 :green_heart: | spotbugs | 1m 59s | master passed | | -0 :warning: | patch | 2m 8s | Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary. | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 19s | the patch passed | | +1 :green_heart: | checkstyle | 1m 4s | the patch passed | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 11m 2s | Patch does not cause any errors with Hadoop 3.1.2 3.2.1. | | +1 :green_heart: | spotbugs | 2m 8s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 15s | The patch does not generate ASF License warnings. | | | | 32m 14s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1773/1/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1773 | | Optional Tests | dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle | | uname | Linux 1f0a49f910eb 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | Max. process+thread count | 94 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1773/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12 | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (HBASE-24424) Make it easy to delete all data for specify qualifiers
[
https://issues.apache.org/jira/browse/HBASE-24424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17115939#comment-17115939
]
Zheng Wang commented on HBASE-24424:
Good idea, let me see.
Thanks.
> Make it easy to delete all data for specify qualifiers
> --
>
> Key: HBASE-24424
> URL: https://issues.apache.org/jira/browse/HBASE-24424
> Project: HBase
> Issue Type: New Feature
> Components: Compaction
>Reporter: Zheng Wang
>Assignee: Zheng Wang
>Priority: Major
>
> We developed a great many user features that each one as a qualifier stored
> in a table which has only one column family, when we planed to decommission
> some of them, but found not easy to do.
>
> My propasal is add a hint for major_compact, eg:
> {code:java}
> major_compact_delete_extra_qualifiers 'table', 'cf','q1','q2'{code}
> This command will delete all of the cells for q1 and q2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [hbase] WenFeiYi opened a new pull request #1773: HBASE-24427 HStore.add log format error
WenFeiYi opened a new pull request #1773: URL: https://github.com/apache/hbase/pull/1773 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (HBASE-24427) HStore.add log format error
wenfeiyi666 created HBASE-24427: --- Summary: HStore.add log format error Key: HBASE-24427 URL: https://issues.apache.org/jira/browse/HBASE-24427 Project: HBase Issue Type: Improvement Affects Versions: 2.2.4, 2.3.0, master Reporter: wenfeiyi666 Assignee: wenfeiyi666 Fix For: 2.3.0, master, 2.2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] Apache-HBase commented on pull request #1772: HBASE-24426 : Provide regionName in warning during failure to move re…
Apache-HBase commented on pull request #1772: URL: https://github.com/apache/hbase/pull/1772#issuecomment-633486037 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 29s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 4m 17s | master passed | | +1 :green_heart: | compile | 1m 3s | master passed | | +1 :green_heart: | shadedjars | 5m 44s | branch has no errors when building our shaded downstream artifacts. | | -0 :warning: | javadoc | 0m 42s | hbase-server in master failed. | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 4m 3s | the patch passed | | +1 :green_heart: | compile | 1m 3s | the patch passed | | +1 :green_heart: | javac | 1m 3s | the patch passed | | +1 :green_heart: | shadedjars | 5m 45s | patch has no errors when building our shaded downstream artifacts. | | -0 :warning: | javadoc | 0m 40s | hbase-server in the patch failed. | ||| _ Other Tests _ | | +1 :green_heart: | unit | 133m 13s | hbase-server in the patch passed. | | | | 158m 47s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1772 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux e7ad41244f7f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | Default Java | 2020-01-14 | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/testReport/ | | Max. process+thread count | 4233 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1772: HBASE-24426 : Provide regionName in warning during failure to move re…
Apache-HBase commented on pull request #1772: URL: https://github.com/apache/hbase/pull/1772#issuecomment-633485331 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 29s | Docker mode activated. | | -0 :warning: | yetus | 0m 3s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 44s | master passed | | +1 :green_heart: | compile | 0m 54s | master passed | | +1 :green_heart: | shadedjars | 5m 37s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 36s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 25s | the patch passed | | +1 :green_heart: | compile | 0m 55s | the patch passed | | +1 :green_heart: | javac | 0m 55s | the patch passed | | +1 :green_heart: | shadedjars | 5m 29s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 37s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 133m 15s | hbase-server in the patch passed. | | | | 157m 11s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1772 | | Optional Tests | javac javadoc unit shadedjars compile | | uname | Linux 7613bac9a14b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | Default Java | 1.8.0_232 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/testReport/ | | Max. process+thread count | 4792 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1730: HBASE-24289 Heterogeneous Storage for Date Tiered Compaction
Apache-HBase commented on pull request #1730: URL: https://github.com/apache/hbase/pull/1730#issuecomment-633466022 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 30s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +0 :ok: | shelldocs | 0m 0s | Shelldocs was not available. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +0 :ok: | mvndep | 0m 22s | Maven dependency ordering for branch | | +1 :green_heart: | mvninstall | 3m 31s | master passed | | +1 :green_heart: | checkstyle | 1m 56s | master passed | | +1 :green_heart: | spotbugs | 11m 3s | master passed | ||| _ Patch Compile Tests _ | | +0 :ok: | mvndep | 0m 14s | Maven dependency ordering for patch | | +1 :green_heart: | mvninstall | 3m 18s | the patch passed | | +1 :green_heart: | checkstyle | 2m 1s | the patch passed | | +1 :green_heart: | shellcheck | 0m 0s | There were no new shellcheck issues. | | -0 :warning: | whitespace | 0m 0s | The patch has 7 line(s) that end in whitespace. Use git apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply | | +1 :green_heart: | hadoopcheck | 11m 6s | Patch does not cause any errors with Hadoop 3.1.2 3.2.1. | | +1 :green_heart: | spotbugs | 11m 57s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 41s | The patch does not generate ASF License warnings. | | | | 54m 29s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1730 | | Optional Tests | dupname asflicense shellcheck shelldocs spotbugs hadoopcheck hbaseanti checkstyle | | uname | Linux 8843114c49be 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | whitespace | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/artifact/yetus-general-check/output/whitespace-eol.txt | | Max. process+thread count | 137 (vs. ulimit of 12500) | | modules | C: hbase-common hbase-server . U: . | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1730/3/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) shellcheck=0.4.6 spotbugs=3.1.12 | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (HBASE-24410) Generate CHANGES.md and RELEASENOTES.md for 2.2.5
[ https://issues.apache.org/jira/browse/HBASE-24410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-24410. Resolution: Fixed > Generate CHANGES.md and RELEASENOTES.md for 2.2.5 > - > > Key: HBASE-24410 > URL: https://issues.apache.org/jira/browse/HBASE-24410 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.2.5 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-24344) Release 2.2.5
[ https://issues.apache.org/jira/browse/HBASE-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reopened HBASE-24344: > Release 2.2.5 > - > > Key: HBASE-24344 > URL: https://issues.apache.org/jira/browse/HBASE-24344 > Project: HBase > Issue Type: Umbrella >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-24411) Set version to 2.2.5 in branch-2.2 for first RC of 2.2.5
[ https://issues.apache.org/jira/browse/HBASE-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang reassigned HBASE-24411: -- Assignee: Guanghao Zhang > Set version to 2.2.5 in branch-2.2 for first RC of 2.2.5 > > > Key: HBASE-24411 > URL: https://issues.apache.org/jira/browse/HBASE-24411 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.2.5 >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (HBASE-24426) Missing regionName while logging warning in HBCKServerCrashProcedure
[ https://issues.apache.org/jira/browse/HBASE-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-24426 started by Viraj Jasani. > Missing regionName while logging warning in HBCKServerCrashProcedure > > > Key: HBASE-24426 > URL: https://issues.apache.org/jira/browse/HBASE-24426 > Project: HBase > Issue Type: Bug >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] pengmq1 commented on pull request #1730: HBASE-24289 Heterogeneous Storage for Date Tiered Compaction
pengmq1 commented on pull request #1730: URL: https://github.com/apache/hbase/pull/1730#issuecomment-633438561 > Can you get the scope document into a markdown file in `dev-support/design-docs/`? OK, I add it to `dev-support/design-docs/` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1772: HBASE-24426 : Provide regionName in warning during failure to move re…
Apache-HBase commented on pull request #1772: URL: https://github.com/apache/hbase/pull/1772#issuecomment-633429862 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 1m 35s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 0s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | ||| _ master Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 42s | master passed | | +1 :green_heart: | checkstyle | 1m 7s | master passed | | +1 :green_heart: | spotbugs | 1m 57s | master passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 19s | the patch passed | | +1 :green_heart: | checkstyle | 1m 4s | the patch passed | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | hadoopcheck | 11m 3s | Patch does not cause any errors with Hadoop 3.1.2 3.2.1. | | +1 :green_heart: | spotbugs | 2m 8s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | asflicense | 0m 14s | The patch does not generate ASF License warnings. | | | | 33m 13s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/artifact/yetus-general-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1772 | | Optional Tests | dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle | | uname | Linux 9f1b5757a65a 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | master / 92673342ec | | Max. process+thread count | 94 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1772/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12 | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1745: HBASE-24402 Moving the meta region causes MetricsException when using above 2.6.0 hadoop version
Apache-HBase commented on pull request #1745: URL: https://github.com/apache/hbase/pull/1745#issuecomment-633419860 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 7m 5s | Docker mode activated. | ||| _ Prechecks _ | | +1 :green_heart: | dupname | 0m 0s | No case conflicting files found. | | +1 :green_heart: | hbaseanti | 0m 1s | Patch does not have any anti-patterns. | | +1 :green_heart: | @author | 0m 0s | The patch does not contain any @author tags. | | +1 :green_heart: | test4tests | 0m 0s | The patch appears to include 1 new or modified test files. | ||| _ branch-1 Compile Tests _ | | +1 :green_heart: | mvninstall | 9m 46s | branch-1 passed | | +1 :green_heart: | compile | 0m 15s | branch-1 passed with JDK v1.8.0_252 | | +1 :green_heart: | compile | 0m 18s | branch-1 passed with JDK v1.7.0_262 | | +1 :green_heart: | checkstyle | 0m 26s | branch-1 passed | | +1 :green_heart: | shadedjars | 3m 2s | branch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | javadoc | 0m 31s | branch-1 passed with JDK v1.8.0_252 | | +1 :green_heart: | javadoc | 0m 19s | branch-1 passed with JDK v1.7.0_262 | | +0 :ok: | spotbugs | 1m 1s | Used deprecated FindBugs config; considering switching to SpotBugs. | | +1 :green_heart: | findbugs | 0m 57s | branch-1 passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 1m 51s | the patch passed | | +1 :green_heart: | compile | 0m 15s | the patch passed with JDK v1.8.0_252 | | +1 :green_heart: | javac | 0m 15s | the patch passed | | +1 :green_heart: | compile | 0m 19s | the patch passed with JDK v1.7.0_262 | | +1 :green_heart: | javac | 0m 19s | the patch passed | | +1 :green_heart: | checkstyle | 0m 16s | hbase-hadoop2-compat: The patch generated 0 new + 2 unchanged - 1 fixed = 2 total (was 3) | | +1 :green_heart: | whitespace | 0m 0s | The patch has no whitespace issues. | | +1 :green_heart: | shadedjars | 2m 50s | patch has no errors when building our shaded downstream artifacts. | | +1 :green_heart: | hadoopcheck | 4m 40s | Patch does not cause any errors with Hadoop 2.8.5 2.9.2. | | +1 :green_heart: | javadoc | 0m 14s | the patch passed with JDK v1.8.0_252 | | +1 :green_heart: | javadoc | 0m 18s | the patch passed with JDK v1.7.0_262 | | +1 :green_heart: | findbugs | 0m 50s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 0m 37s | hbase-hadoop2-compat in the patch passed. | | +1 :green_heart: | asflicense | 0m 21s | The patch does not generate ASF License warnings. | | | | 38m 36s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1745/2/artifact/out/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1745 | | Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile | | uname | Linux dc8388090280 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1745/out/precommit/personality/provided.sh | | git revision | branch-1 / 3235b56 | | Default Java | 1.7.0_262 | | Multi-JDK versions | /usr/lib/jvm/zulu-8-amd64:1.8.0_252 /usr/lib/jvm/zulu-7-amd64:1.7.0_262 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1745/2/testReport/ | | Max. process+thread count | 87 (vs. ulimit of 1) | | modules | C: hbase-hadoop2-compat U: hbase-hadoop2-compat | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1745/2/console | | versions | git=1.9.1 maven=3.0.5 findbugs=3.0.1 | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (HBASE-24344) Release 2.2.5
[ https://issues.apache.org/jira/browse/HBASE-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-24344. Fix Version/s: 2.2.5 Assignee: Guanghao Zhang Resolution: Fixed > Release 2.2.5 > - > > Key: HBASE-24344 > URL: https://issues.apache.org/jira/browse/HBASE-24344 > Project: HBase > Issue Type: Umbrella >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > Fix For: 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24411) Set version to 2.2.5 in branch-2.2 for first RC of 2.2.5
[ https://issues.apache.org/jira/browse/HBASE-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-24411. Fix Version/s: 2.2.5 Resolution: Fixed > Set version to 2.2.5 in branch-2.2 for first RC of 2.2.5 > > > Key: HBASE-24411 > URL: https://issues.apache.org/jira/browse/HBASE-24411 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.2.5 >Reporter: Guanghao Zhang >Priority: Major > Fix For: 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] virajjasani opened a new pull request #1772: HBASE-24426 : Provide regionName in warning during failure to move re…
virajjasani opened a new pull request #1772: URL: https://github.com/apache/hbase/pull/1772 …gion from CLOSING to CLOSED This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (HBASE-24426) Missing regionName while logging warning in HBCKServerCrashProcedure
Viraj Jasani created HBASE-24426: Summary: Missing regionName while logging warning in HBCKServerCrashProcedure Key: HBASE-24426 URL: https://issues.apache.org/jira/browse/HBASE-24426 Project: HBase Issue Type: Bug Reporter: Viraj Jasani Assignee: Viraj Jasani -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [hbase] Apache-HBase commented on pull request #1771: HBASE-24425 Run hbck_chore_run and catalogjanitor_run on draw of 'HBC…
Apache-HBase commented on pull request #1771: URL: https://github.com/apache/hbase/pull/1771#issuecomment-633399486 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 34s | Docker mode activated. | | -0 :warning: | yetus | 0m 5s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ branch-2 Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 41s | branch-2 passed | | +1 :green_heart: | javadoc | 0m 38s | branch-2 passed | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 12s | the patch passed | | +1 :green_heart: | javadoc | 0m 34s | the patch passed | ||| _ Other Tests _ | | +1 :green_heart: | unit | 130m 56s | hbase-server in the patch passed. | | | | 141m 47s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1771 | | Optional Tests | javac javadoc unit | | uname | Linux a91b4d6eefe5 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | branch-2 / 03929770fe | | Default Java | 1.8.0_232 | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/testReport/ | | Max. process+thread count | 3881 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [hbase] Apache-HBase commented on pull request #1771: HBASE-24425 Run hbck_chore_run and catalogjanitor_run on draw of 'HBC…
Apache-HBase commented on pull request #1771: URL: https://github.com/apache/hbase/pull/1771#issuecomment-633396672 :confetti_ball: **+1 overall** | Vote | Subsystem | Runtime | Comment | |::|--:|:|:| | +0 :ok: | reexec | 0m 35s | Docker mode activated. | | -0 :warning: | yetus | 0m 6s | Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck | ||| _ Prechecks _ | ||| _ branch-2 Compile Tests _ | | +1 :green_heart: | mvninstall | 4m 17s | branch-2 passed | | -0 :warning: | javadoc | 0m 41s | hbase-server in branch-2 failed. | ||| _ Patch Compile Tests _ | | +1 :green_heart: | mvninstall | 3m 59s | the patch passed | | -0 :warning: | javadoc | 0m 39s | hbase-server in the patch failed. | ||| _ Other Tests _ | | +1 :green_heart: | unit | 120m 33s | hbase-server in the patch passed. | | | | 132m 56s | | | Subsystem | Report/Notes | |--:|:-| | Docker | Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile | | GITHUB PR | https://github.com/apache/hbase/pull/1771 | | Optional Tests | javac javadoc unit | | uname | Linux 9521dab4ac3a 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | dev-support/hbase-personality.sh | | git revision | branch-2 / 03929770fe | | Default Java | 2020-01-14 | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt | | javadoc | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt | | Test Results | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/testReport/ | | Max. process+thread count | 4546 (vs. ulimit of 12500) | | modules | C: hbase-server U: hbase-server | | Console output | https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1771/1/console | | versions | git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) | | Powered by | Apache Yetus 0.11.1 https://yetus.apache.org | This message was automatically generated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
