[jira] [Resolved] (HBASE-28747) HBase-Nightly-s390x Build failures
[
https://issues.apache.org/jira/browse/HBASE-28747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28747.
---
Assignee: Duo Zhang
Resolution: Fixed
> HBase-Nightly-s390x Build failures
> --
>
> Key: HBASE-28747
> URL: https://issues.apache.org/jira/browse/HBASE-28747
> Project: HBase
> Issue Type: Task
> Components: community, jenkins
>Reporter: Soham Munshi
>Assignee: Duo Zhang
>Priority: Major
>
> Hi [~zhangduo]
> This is regarding recent [s390x CI
> failures|https://ci-hbase.apache.org/job/HBase-Nightly-s390x/] .
> The install.log and junit.log has got below output -
> {code:java}
> /tmp/jenkins18056117051185954087.sh: line 12:
> /home/jenkins/tools/maven/latest3//bin/mvn: No such file or directory{code}
> Upon checking the machine stats it seems like the Apache Maven path is not
> getting set properly, since the mvn_home outputs -
> {code:java}
> MAVEN_HOME: /home/jenkins/tools/maven/latest3/{code}
> where as the mvn_version outputs the following -
> {code:java}
> [1mApache Maven 3.6.3[m Maven home: /usr/share/maven Java version: 11.0.23,
> vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-s390x Default locale:
> en_US, platform encoding: UTF-8 OS name: "linux", version:
> "5.4.0-174-generic", arch: "s390x", family: "unix"{code}
> Could you please help us get this fixed?
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28722) Should wipe out all the output directories before unstash in nightly job
[ https://issues.apache.org/jira/browse/HBASE-28722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28722. --- Hadoop Flags: Reviewed Resolution: Fixed > Should wipe out all the output directories before unstash in nightly job > > > Key: HBASE-28722 > URL: https://issues.apache.org/jira/browse/HBASE-28722 > Project: HBase > Issue Type: Bug > Components: jenkins, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11 > > > For master and branch-3, we do not have jdk8 and jdk11 stages but we can > still see there are comments on jira which include these stages's results. > I think the problem is that, in the 'init health results' stage, we want to > stash some empty results but actually there are some build results for > previous builds there so we stash some non empty results. > We should wipe out these directories first before stash them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28760) Client integration test fails on master branch
Duo Zhang created HBASE-28760:
-
Summary: Client integration test fails on master branch
Key: HBASE-28760
URL: https://issues.apache.org/jira/browse/HBASE-28760
Project: HBase
Issue Type: Bug
Components: jenkins, scripts
Reporter: Duo Zhang
Permission denied...
Not sure what is the real problem.
{noformat}
17:17:52 [Sun Jul 28 09:17:51 AM UTC 2024 INFO]: Personality: patch mvninstall
17:17:52 cd /home/jenkins/jenkins-home/workspace/HBase_Nightly_master/component
17:17:52 /opt/maven/bin/mvn --batch-mode
-Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/HBase_Nightly_master/yetus-m2/hbase-master-full-0
--threads=2
-Djava.io.tmpdir=/home/jenkins/jenkins-home/workspace/HBase_Nightly_master/component/target
-DHBasePatchProcess -fae clean install -DskipTests=true
-Dmaven.javadoc.skip=true -Dcheckstyle.skip=true -Dfindbugs.skip=true
-Dspotbugs.skip=true >
/home/jenkins/jenkins-home/workspace/HBase_Nightly_master/output-general/patch-mvninstall-root.txt
2>&1
17:21:17 Building a binary tarball from the source tarball succeeded.
[Pipeline] echo
17:21:17 unpacking the hbase bin tarball into 'hbase-install' and the client
tarball into 'hbase-client'
[Pipeline] sh
17:21:18 tar: /jaxws-ri-2.3.2.pom: Cannot open: Permission denied
17:21:20 tar: Exiting with failure status due to previous errors
Post stage
[Pipeline] stash
17:21:20 Warning: overwriting stash ‘srctarball-result’
17:21:20 Stashed 2 file(s)
[Pipeline] sshPublisher
17:21:20 SSH: Current build result is [FAILURE], not going to run.
[Pipeline] sh
17:21:20 Remove
/home/jenkins/jenkins-home/workspace/HBase_Nightly_master/output-srctarball/hbase-src.tar.gz
for saving space
[Pipeline] archiveArtifacts
17:21:20 Archiving artifacts
[Pipeline] archiveArtifacts
17:21:20 Archiving artifacts
[Pipeline] archiveArtifacts
17:21:20 Archiving artifacts
[Pipeline] archiveArtifacts
17:21:20 Archiving artifacts
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
17:21:20 Failed in branch packaging and integration
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28758) Remove the aarch64 profile
Duo Zhang created HBASE-28758: - Summary: Remove the aarch64 profile Key: HBASE-28758 URL: https://issues.apache.org/jira/browse/HBASE-28758 Project: HBase Issue Type: Improvement Components: build, pom Reporter: Duo Zhang We do not depend on protobuf 2.5 on branch-3+, so we do not need the special protoc compiler for arm any more. Just remove the profile. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28719) Use ExtendedCell in WALEdit
[ https://issues.apache.org/jira/browse/HBASE-28719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28719. --- Fix Version/s: 3.0.0-beta-2 Resolution: Fixed Pushed to master and branch-3. Thanks [~sunxin] for reviewing! > Use ExtendedCell in WALEdit > --- > > Key: HBASE-28719 > URL: https://issues.apache.org/jira/browse/HBASE-28719 > Project: HBase > Issue Type: Sub-task > Components: wal >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28748) Replication blocking: InvalidProtocolBufferException$InvalidWireTypeException: Protocol message tag had invalid wire type.
[ https://issues.apache.org/jira/browse/HBASE-28748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28748. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.6+. Thanks for [~leojie] for reporting this issue and helping verifying the patch. Thanks [~sunxin] for reviewing! > Replication blocking: > InvalidProtocolBufferException$InvalidWireTypeException: Protocol message tag > had invalid wire type. > -- > > Key: HBASE-28748 > URL: https://issues.apache.org/jira/browse/HBASE-28748 > Project: HBase > Issue Type: Bug > Components: Replication, wal >Affects Versions: 2.6.0 > Environment: hbase2.6.0 > hadoop3.3.6 >Reporter: Longping Jie >Assignee: Duo Zhang >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > Attachments: image-2024-07-23-12-33-50-395.png, > rs-replciation-error.log, > tx1-int-hbase-main-prod-4%2C16020%2C1720602602602.1720609818921 > > > h2. replication queue overstock, As shown below: > !image-2024-07-23-12-33-50-395.png! > > In the figure, the first wal file no longer exists, but has not been skipped, > causing replciation to block. > the second and third wal file were moved oldWals, you can see the attachment, > the reading of these two files faile. > h2. The error log in rs is > 2024-07-22T17:47:49,130 WARN > [RS_CLAIM_REPLICATION_QUEUE-regionserver/sh2-int-hbase-main-ha-9:16020-0.replicationSource,test_hbase_258-tx1-int-hbase-main-prod-3,16020,1720602522464.replicationSource.wal-reader.tx1-int-hbase-main-prod-3%2C16020%2C1720602522464,test_hbase_258-tx1-int-hbase-main-prod-3,16020,1720602522464] > wal.ProtobufWALStreamReader: Error while reading WALKey, originalPosition=0, > currentPosition=81 > org.apache.hbase.thirdparty.com.google.protobuf.InvalidProtocolBufferException$InvalidWireTypeException: > Protocol message tag had invalid wire type. > at > org.apache.hbase.thirdparty.com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:119) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:503) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.GeneratedMessage$Builder.parseUnknownField(GeneratedMessage.java:770) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hadoop.hbase.shaded.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:2829) > ~[hbase-protocol-shaded-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.shaded.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:4212) > ~[hbase-protocol-shaded-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.shaded.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:4204) > ~[hbase-protocol-shaded-2.6.0.jar:2.6.0] > at > org.apache.hbase.thirdparty.com.google.protobuf.AbstractParser.parsePartialFrom(AbstractParser.java:192) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:209) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:214) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:25) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hbase.thirdparty.com.google.protobuf.GeneratedMessage.parseWithIOException(GeneratedMessage.java:321) > ~[hbase-shaded-protobuf-4.1.7.jar:4.1.7] > at > org.apache.hadoop.hbase.shaded.protobuf.generated.WALProtos$WALKey.parseFrom(WALProtos.java:2321) > ~[hbase-protocol-shaded-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.regionserver.wal.ProtobufWALTailingReader.readWALKey(ProtobufWALTailingReader.java:128) > ~[hbase-server-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.regionserver.wal.ProtobufWALTailingReader.next(ProtobufWALTailingReader.java:257) > ~[hbase-server-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.readNextEntryAndRecordReaderPosition(WALEntryStream.java:490) > ~[hbase-server-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.lastAttempt(WALEntryStream.java:306) > ~[hbase-server-2.6.0.jar:2.6.0] > at > org.apache.hadoop.hbase.replication.regionserver.WALEntryStream.tryAdvanceEntry(WALEntryStream.java:388) > ~[hbase-server-2.6.0.jar:2.6.0] > at >
[jira] [Resolved] (HBASE-28522) UNASSIGN proc indefinitely stuck on dead rs
[
https://issues.apache.org/jira/browse/HBASE-28522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28522.
---
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.11
Hadoop Flags: Reviewed
Assignee: Duo Zhang (was: Prathyusha)
Resolution: Fixed
Pushed to all active branches.
Thanks all for helping and reviewing!
> UNASSIGN proc indefinitely stuck on dead rs
> ---
>
> Key: HBASE-28522
> URL: https://issues.apache.org/jira/browse/HBASE-28522
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2, Region Assignment
>Reporter: Prathyusha
>Assignee: Duo Zhang
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
> Attachments: timeline.jpg
>
>
> One scenario we noticed in production -
> we had DisableTableProc and SCP almost triggered at similar time
> 2024-03-16 17:59:23,014 INFO [PEWorker-11] procedure.DisableTableProcedure -
> Set to state=DISABLING
> 2024-03-16 17:59:15,243 INFO [PEWorker-26] procedure.ServerCrashProcedure -
> Start pid=21592440, state=RUNNABLE:SERVER_CRASH_START, locked=true;
> ServerCrashProcedure
> , splitWal=true, meta=false
> DisabeTableProc creates unassign procs, and at this time ASSIGNs of SCP is
> not completed
> {{2024-03-16 17:59:23,003 DEBUG [PEWorker-40] procedure2.ProcedureExecutor -
> LOCK_EVENT_WAIT pid=21594220, ppid=21592440,
> state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE;
> TransitRegionStateProcedure table=, region=, ASSIGN}}
> UNASSIGN created by DisableTableProc is stuck on the dead regionserver and we
> had to manually bypass unassign of DisableTableProc and then do ASSIGN.
> If we can break the loop for UNASSIGN procedure to not retry if there is scp
> for that server, we do not need manual intervention?, at least the
> DisableTableProc can go to a rollback state?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28742) CompactionTool fails with NPE when mslab is enabled
[
https://issues.apache.org/jira/browse/HBASE-28742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28742.
---
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.11
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to all active branches.
Thanks [~vineet.4008] for contributing and [~PankajKumar] for reviewing!
> CompactionTool fails with NPE when mslab is enabled
> ---
>
> Key: HBASE-28742
> URL: https://issues.apache.org/jira/browse/HBASE-28742
> Project: HBase
> Issue Type: Bug
> Components: Compaction
>Affects Versions: 2.6.0, 3.0.0-beta-1, 2.5.9
>Reporter: Vineet Kumar Maheshwari
>Assignee: Vineet Kumar Maheshwari
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> While using the CompactionTool, NPE is observed.
> *Command:*
> {code:java}
> hbase org.apache.hadoop.hbase.regionserver.CompactionTool -major
> {code}
> *Exception Details:*
> {code:java}
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.recycleChunks(MemStoreLABImpl.java:296)
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.lambda$new$0(MemStoreLABImpl.java:109)
> at org.apache.hadoop.hbase.nio.RefCnt.deallocate(RefCnt.java:95)
> at
> org.apache.hbase.thirdparty.io.netty.util.AbstractReferenceCounted.handleRelease(AbstractReferenceCounted.java:86)
> at
> org.apache.hbase.thirdparty.io.netty.util.AbstractReferenceCounted.release(AbstractReferenceCounted.java:76)
> at org.apache.hadoop.hbase.nio.RefCnt.release(RefCnt.java:84)
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.close(MemStoreLABImpl.java:269)
> at
> org.apache.hadoop.hbase.regionserver.Segment.close(Segment.java:143)
> at
> org.apache.hadoop.hbase.regionserver.AbstractMemStore.close(AbstractMemStore.java:381)
> at
> org.apache.hadoop.hbase.regionserver.HStore.closeWithoutLock(HStore.java:723)
> at org.apache.hadoop.hbase.regionserver.HStore.close(HStore.java:795)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool$CompactionWorker.compactStoreFiles(CompactionTool.java:171)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool$CompactionWorker.compactRegion(CompactionTool.java:137)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool$CompactionWorker.compactTable(CompactionTool.java:129)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool$CompactionWorker.compact(CompactionTool.java:118)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool.doClient(CompactionTool.java:374)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool.run(CompactionTool.java:424)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.regionserver.CompactionTool.main(CompactionTool.java:460){code}
> *Fix Suggestions:*
> Initialize the ChunkCreator in CompactionTool when
> hbase.hregion.memstore.mslab.enabled is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28743) Snapshot based mapreduce jobs fails with NPE while trying to close mslab within mapper
[
https://issues.apache.org/jira/browse/HBASE-28743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28743.
---
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.11
(was: 2.5.9)
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to all active branches.
THanks [~vineet.4008] for contributing!
> Snapshot based mapreduce jobs fails with NPE while trying to close mslab
> within mapper
> --
>
> Key: HBASE-28743
> URL: https://issues.apache.org/jira/browse/HBASE-28743
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Ujjawal Kumar
>Assignee: Vineet Kumar Maheshwari
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> {code:java}
> 2024-07-11 10:20:38,800 WARN [main] client.ClientSideRegionScanner -
> Exception while closing region
> java.io.IOException: java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1808)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:1557)
> at
> org.apache.hadoop.hbase.client.ClientSideRegionScanner.close(ClientSideRegionScanner.java:133)
> at
> org.apache.hadoop.hbase.mapreduce.TableSnapshotInputFormatImpl$RecordReader.close(TableSnapshotInputFormatImpl.java:310)
> at
> org.apache.hadoop.hbase.mapreduce.TableSnapshotInputFormat$TableSnapshotRegionRecordReader.close(TableSnapshotInputFormat.java:184)
> at
> org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.close(MapTask.java:536)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:804)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:348)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:178)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:172)
> Caused by: java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.recycleChunks(MemStoreLABImpl.java:296)
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.lambda$new$0(MemStoreLABImpl.java:109)
> at org.apache.hadoop.hbase.nio.RefCnt.deallocate(RefCnt.java:95)
> at
> org.apache.hbase.thirdparty.io.netty.util.AbstractReferenceCounted.handleRelease(AbstractReferenceCounted.java:86)
> at
> org.apache.hbase.thirdparty.io.netty.util.AbstractReferenceCounted.release(AbstractReferenceCounted.java:76)
> at org.apache.hadoop.hbase.nio.RefCnt.release(RefCnt.java:84)
> at
> org.apache.hadoop.hbase.regionserver.MemStoreLABImpl.close(MemStoreLABImpl.java:269)
> at
> org.apache.hadoop.hbase.regionserver.Segment.close(Segment.java:143)
> at
> org.apache.hadoop.hbase.regionserver.AbstractMemStore.close(AbstractMemStore.java:381)
> at
> org.apache.hadoop.hbase.regionserver.HStore.closeWithoutLock(HStore.java:723)
> at org.apache.hadoop.hbase.regionserver.HStore.close(HStore.java:795)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$2.call(HRegion.java:1786)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$2.call(HRegion.java:1783)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750) {code}
> This happens because the ChunkCreator is only initialized as part of
> HRegionServer
> [here.|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/HBaseServerBase.java#L410-L431]
> HRegion created on top of snapshot files within mapper wouldn't have
> ChunkCreator initialized causing NPE while trying to close the memstore
> This is seen after https://issues.apache.org/jira/browse/HBASE-28401
> There are 2 possible solutions here :
> 1. Initialize ChunkCreator as while trying to create HRegion within snapashot
> based mapper
> 2. Disable the mslab altogether (via hbase.hregion.memstore.mslab.enabled set
> to false) within snapashot based mapper
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (HBASE-28734) Improve HBase shell snapshot command Doc with TTL option
[
https://issues.apache.org/jira/browse/HBASE-28734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-28734:
---
> Improve HBase shell snapshot command Doc with TTL option
> -
>
> Key: HBASE-28734
> URL: https://issues.apache.org/jira/browse/HBASE-28734
> Project: HBase
> Issue Type: Improvement
> Components: shell
>Reporter: Ashok shetty
>Assignee: Liangjun He
>Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The current HBase shell snapshot command allows users to create a snapshot of
> a specific table. While this command is useful, it could be enhanced by
> adding a TTL (Time-to-Live) option. This would allow users to specify a time
> period after which the snapshot would automatically be deleted.
> I propose we introduce a TTL option in the snapshot command doc as follows:
> hbase> snapshot 'sourceTable', 'snapshotName', \{TTL => '7d'}
> This would create a snapshot of 'sourceTable' called 'snapshotName' that
> would automatically be deleted after 7 days. The addition document of a TTL
> option would provide a better user experience and assist with efficient
> storage management.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28735) Move our official slack channel from apache-hbase.slack.com to the one in the-asf.slack.com
[ https://issues.apache.org/jira/browse/HBASE-28735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28735. --- Assignee: Duo Zhang Resolution: Fixed Done. > Move our official slack channel from apache-hbase.slack.com to the one in > the-asf.slack.com > --- > > Key: HBASE-28735 > URL: https://issues.apache.org/jira/browse/HBASE-28735 > Project: HBase > Issue Type: Task > Components: community >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > > According to this thread in the mailing list > https://lists.apache.org/thread/cyr8vfxvfqm2srz7m1kkp4mkk015r8wx > Let's do the move. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28738) Send notice email to all mailing list to mention the slack channel change
[ https://issues.apache.org/jira/browse/HBASE-28738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28738. --- Resolution: Fixed Done. > Send notice email to all mailing list to mention the slack channel change > - > > Key: HBASE-28738 > URL: https://issues.apache.org/jira/browse/HBASE-28738 > Project: HBase > Issue Type: Sub-task > Components: community >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28737) Add the slack channel related information in README.md
[ https://issues.apache.org/jira/browse/HBASE-28737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28737. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.10 Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks [~meiyi] for reviewing! > Add the slack channel related information in README.md > -- > > Key: HBASE-28737 > URL: https://issues.apache.org/jira/browse/HBASE-28737 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28736) Modify our ref guide about the slack channel change
[ https://issues.apache.org/jira/browse/HBASE-28736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28736. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~meiyi] for reviewing! > Modify our ref guide about the slack channel change > --- > > Key: HBASE-28736 > URL: https://issues.apache.org/jira/browse/HBASE-28736 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28740) Need to call parent class's serialization methods in CloseExcessRegionReplicasProcedure
Duo Zhang created HBASE-28740: - Summary: Need to call parent class's serialization methods in CloseExcessRegionReplicasProcedure Key: HBASE-28740 URL: https://issues.apache.org/jira/browse/HBASE-28740 Project: HBase Issue Type: Bug Components: proc-v2 Reporter: Duo Zhang Assignee: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28737) Add the slack channel related inforamtion in README.md
Duo Zhang created HBASE-28737: - Summary: Add the slack channel related inforamtion in README.md Key: HBASE-28737 URL: https://issues.apache.org/jira/browse/HBASE-28737 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28738) Send notice email to all mailing list to mention the slack channel change
Duo Zhang created HBASE-28738: - Summary: Send notice email to all mailing list to mention the slack channel change Key: HBASE-28738 URL: https://issues.apache.org/jira/browse/HBASE-28738 Project: HBase Issue Type: Sub-task Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28735) Move our official slack channel from apache-hbase.slack.com to the one in the-asf.slack.com
Duo Zhang created HBASE-28735: - Summary: Move our official slack channel from apache-hbase.slack.com to the one in the-asf.slack.com Key: HBASE-28735 URL: https://issues.apache.org/jira/browse/HBASE-28735 Project: HBase Issue Type: Task Components: community Reporter: Duo Zhang According to this thread in the mailing list https://lists.apache.org/thread/cyr8vfxvfqm2srz7m1kkp4mkk015r8wx Let's do the move. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28736) Modify our ref guide about the slack channel change
Duo Zhang created HBASE-28736: - Summary: Modify our ref guide about the slack channel change Key: HBASE-28736 URL: https://issues.apache.org/jira/browse/HBASE-28736 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28674) Bump minimum supported java version to 17 for HBase 3.x
[ https://issues.apache.org/jira/browse/HBASE-28674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28674. --- Fix Version/s: 3.0.0-beta-2 Release Note: HBase 3.x can only be compiled and run by JDK17+. We set release to 17 when compiling so the generated byte code can only be executed by JRE17+, and we also change the scripts to check JDK version to be 17+ before actually doing anything. Resolution: Fixed > Bump minimum supported java version to 17 for HBase 3.x > --- > > Key: HBASE-28674 > URL: https://issues.apache.org/jira/browse/HBASE-28674 > Project: HBase > Issue Type: Umbrella > Components: build, java >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-beta-2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28683) Only allow one TableProcedureInterface for a single table to run at the same time for some special procedure types
[ https://issues.apache.org/jira/browse/HBASE-28683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28683. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.10 Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks [~vjasani] for reviewing! > Only allow one TableProcedureInterface for a single table to run at the same > time for some special procedure types > -- > > Key: HBASE-28683 > URL: https://issues.apache.org/jira/browse/HBASE-28683 > Project: HBase > Issue Type: Improvement > Components: master, proc-v2 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10 > > > We have a table lock in the MasterProcedureScheduler, which is designed to > only allow one procedure to run at the same time when they require exclusive > lock. > But there is a problem that for availability, usually we can not always hold > the exclusive lock through the whole procedure life time, as if so, we can > not execute region assignment for this table too. The solution is to set > holdLock to false, which means we will release the table lock after one > execution cycle. > In this way, it is possible that different table procedures may execute at > the same time, which could mess things up. > Especially that, in HBASE-28522, we find out that it is even impossible for > DisableTableProcedure to hold the exclusive lock all the time. If the steps > for DisableTableProcedure can be overlapped with other procedures like > ModifyTableProcedure or even EnableTableProcedure, things will be > definationly messed up... > So we need to find another way to ensure that for a single table, only one of > these procedures can be executed at the same time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28727) SteppingSplitPolicy may not work when table enables region replication
[
https://issues.apache.org/jira/browse/HBASE-28727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28727.
---
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.10
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to all active branches.
Thanks [~guluo] for contributing!
> SteppingSplitPolicy may not work when table enables region replication
> --
>
> Key: HBASE-28727
> URL: https://issues.apache.org/jira/browse/HBASE-28727
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.4.13
>Reporter: guluo
>Assignee: guluo
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10
>
>
> Reproduction:
> 1. Create a table with region replication, and ensure that the primary region
> and replica region are on the same RS (eg: the HBase cluster has only one RS)
> create 't01', 'info', \{REGION_REPLICATION => 2}
> 2. The first region does not split when storefile size exceed flushsize * 2,
> because that we get 2 regions about this table on this RS (1 primary region
> and 1 replica region)
>
> I think we should ignore the replica reggion when getting the count of
> regions on this same regionserver.
> Is my idea correct? maybe can discuss it .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28732) Fix typo in Jenkinsfile_Github for jdk8 hadoop2 check
Duo Zhang created HBASE-28732: - Summary: Fix typo in Jenkinsfile_Github for jdk8 hadoop2 check Key: HBASE-28732 URL: https://issues.apache.org/jira/browse/HBASE-28732 Project: HBase Issue Type: Improvement Components: jenkins Reporter: Duo Zhang https://github.com/apache/hbase/blob/9dee538f65d84a900724d424c71793dff46e9684/dev-support/Jenkinsfile_GitHub#L314 This line PR JDK8 Hadoop3 Check Report Should be PR JDK8 Hadoop2 Check Report -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28731) Remove the IA.Private annotation on WALEdit's add methods as they have already been used by CP users
Duo Zhang created HBASE-28731: - Summary: Remove the IA.Private annotation on WALEdit's add methods as they have already been used by CP users Key: HBASE-28731 URL: https://issues.apache.org/jira/browse/HBASE-28731 Project: HBase Issue Type: Task Components: Coprocessors, wal Reporter: Duo Zhang Assignee: Duo Zhang Per the discussion thread here https://lists.apache.org/thread/b7zfyqmxo9lrt2rpo0lc0m6vsomn217w -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28723) [JDK17] TestSecureIPC fails under JDK17
[
https://issues.apache.org/jira/browse/HBASE-28723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28723.
---
Hadoop Flags: Reviewed
Resolution: Fixed
The flaky dashboard is OK for branch-2.5.
Resolve.
> [JDK17] TestSecureIPC fails under JDK17
> ---
>
> Key: HBASE-28723
> URL: https://issues.apache.org/jira/browse/HBASE-28723
> Project: HBase
> Issue Type: Sub-task
> Components: java, test
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10
>
>
> Although the tests only fail on branch-2.5, the same exception also produced
> on other active branches, so even if the tests passes, it does not test what
> we want I think.
> {noformat}
> 2024-07-11T11:56:44,323 DEBUG [Thread-3 {}] ipc.BlockingRpcConnection$1(409):
> Exception encountered while connecting to the server localhost:39851
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> transient java.lang.String java.net.InetAddress.canonicalHostName accessible:
> module java.base does not "opens java.net" to unnamed module @26a7b76d
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
> ~[?:?]
> at
> java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
> ~[?:?]
> at java.lang.reflect.Field.checkCanSetAccessible(Field.java:178) ~[?:?]
> at java.lang.reflect.Field.setAccessible(Field.java:172) ~[?:?]
> at
> org.apache.hadoop.hbase.security.AbstractTestSecureIPC$CanonicalHostnameTestingAuthenticationProviderSelector$1.createClient(AbstractTestSecureIPC.java:202)
> ~[test-classes/:?]
> at
> org.apache.hadoop.hbase.security.AbstractHBaseSaslRpcClient.(AbstractHBaseSaslRpcClient.java:79)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.security.HBaseSaslRpcClient.(HBaseSaslRpcClient.java:74)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection.setupSaslConnection(BlockingRpcConnection.java:366)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$2.run(BlockingRpcConnection.java:541)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$2.run(BlockingRpcConnection.java:1)
> ~[classes/:?]
> at
> java.security.AccessController.doPrivileged(AccessController.java:712) ~[?:?]
> at javax.security.auth.Subject.doAs(Subject.java:439) ~[?:?]
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899)
> ~[hadoop-common-3.3.5.jar:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection.setupIOstreams(BlockingRpcConnection.java:538)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection.writeRequest(BlockingRpcConnection.java:685)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection$4.run(BlockingRpcConnection.java:819)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.HBaseRpcControllerImpl.notifyOnCancel(HBaseRpcControllerImpl.java:276)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.BlockingRpcConnection.sendRequest(BlockingRpcConnection.java:792)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.callMethod(AbstractRpcClient.java:449)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:336)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:606)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.shaded.ipc.protobuf.generated.TestRpcServiceProtos$TestProtobufRpcProto$BlockingStub.echo(TestRpcServiceProtos.java:500)
> ~[classes/:?]
> at
> org.apache.hadoop.hbase.security.AbstractTestSecureIPC$TestThread.run(AbstractTestSecureIPC.java:451)
> ~[test-classes/:?]
> {noformat}
> We need to open java.net too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28729) Change the generic type of List in InternalScanner.next
Duo Zhang created HBASE-28729: - Summary: Change the generic type of List in InternalScanner.next Key: HBASE-28729 URL: https://issues.apache.org/jira/browse/HBASE-28729 Project: HBase Issue Type: Sub-task Components: Coprocessors, regionserver Reporter: Duo Zhang Plan to change it from List to List, so we could pass both List and List to it, or even List for coprocessors. This could save a lot of casting in our main code. This is an incompatible change for coprocessors, so it will only go into branch-3+, and will be marked as incompatible change. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28713) Add 2.6.x in hadoop support matrix in our ref guide
[ https://issues.apache.org/jira/browse/HBASE-28713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28713. --- Fix Version/s: 3.0.0-beta-2 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~bbeaudreault] for reviewing! > Add 2.6.x in hadoop support matrix in our ref guide > --- > > Key: HBASE-28713 > URL: https://issues.apache.org/jira/browse/HBASE-28713 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > Now it is only up to 2.5.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28684) Remove CellWrapper and use ExtendedCell internally in client side data structure
[ https://issues.apache.org/jira/browse/HBASE-28684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28684. --- Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) Resolution: Fixed Pushed to master and branch-3. Thanks [~Ddupg] for reviewing! > Remove CellWrapper and use ExtendedCell internally in client side data > structure > > > Key: HBASE-28684 > URL: https://issues.apache.org/jira/browse/HBASE-28684 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > > In general, all Cells in HBase are ExtendedCells, we introduce Cell interface > is only for preventing user to call some methods which damage the system. > So I think we should have internal methods which can get ExtendedCell from > the client side data structures so we do not need to cast everywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28707) Backport the code changes in HBASE-28675 to branch-2.x
[ https://issues.apache.org/jira/browse/HBASE-28707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28707. --- Fix Version/s: 2.7.0 2.6.1 2.5.10 Hadoop Flags: Reviewed Assignee: Duo Zhang Resolution: Fixed Pushed to all branch-2.x. Thanks [~ndimiduk] for reviewing! > Backport the code changes in HBASE-28675 to branch-2.x > -- > > Key: HBASE-28707 > URL: https://issues.apache.org/jira/browse/HBASE-28707 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 2.6.1, 2.5.10 > > > For aligning the code between different branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28723) [JDK17] TestSecureIPC fails under JDK17
Duo Zhang created HBASE-28723:
-
Summary: [JDK17] TestSecureIPC fails under JDK17
Key: HBASE-28723
URL: https://issues.apache.org/jira/browse/HBASE-28723
Project: HBase
Issue Type: Sub-task
Reporter: Duo Zhang
Although the tests only fail on branch-2.5, the same exception also produced on
other active branches, so even if the tests passes, it does not test what we
want I think.
{noformat}
2024-07-11T11:56:44,323 DEBUG [Thread-3 {}] ipc.BlockingRpcConnection$1(409):
Exception encountered while connecting to the server localhost:39851
java.lang.reflect.InaccessibleObjectException: Unable to make field private
transient java.lang.String java.net.InetAddress.canonicalHostName accessible:
module java.base does not "opens java.net" to unnamed module @26a7b76d
at
java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
~[?:?]
at
java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
~[?:?]
at java.lang.reflect.Field.checkCanSetAccessible(Field.java:178) ~[?:?]
at java.lang.reflect.Field.setAccessible(Field.java:172) ~[?:?]
at
org.apache.hadoop.hbase.security.AbstractTestSecureIPC$CanonicalHostnameTestingAuthenticationProviderSelector$1.createClient(AbstractTestSecureIPC.java:202)
~[test-classes/:?]
at
org.apache.hadoop.hbase.security.AbstractHBaseSaslRpcClient.(AbstractHBaseSaslRpcClient.java:79)
~[classes/:?]
at
org.apache.hadoop.hbase.security.HBaseSaslRpcClient.(HBaseSaslRpcClient.java:74)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection.setupSaslConnection(BlockingRpcConnection.java:366)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection$2.run(BlockingRpcConnection.java:541)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection$2.run(BlockingRpcConnection.java:1)
~[classes/:?]
at
java.security.AccessController.doPrivileged(AccessController.java:712) ~[?:?]
at javax.security.auth.Subject.doAs(Subject.java:439) ~[?:?]
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899)
~[hadoop-common-3.3.5.jar:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection.setupIOstreams(BlockingRpcConnection.java:538)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection.writeRequest(BlockingRpcConnection.java:685)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection$4.run(BlockingRpcConnection.java:819)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.HBaseRpcControllerImpl.notifyOnCancel(HBaseRpcControllerImpl.java:276)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.BlockingRpcConnection.sendRequest(BlockingRpcConnection.java:792)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.AbstractRpcClient.callMethod(AbstractRpcClient.java:449)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:336)
~[classes/:?]
at
org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:606)
~[classes/:?]
at
org.apache.hadoop.hbase.shaded.ipc.protobuf.generated.TestRpcServiceProtos$TestProtobufRpcProto$BlockingStub.echo(TestRpcServiceProtos.java:500)
~[classes/:?]
at
org.apache.hadoop.hbase.security.AbstractTestSecureIPC$TestThread.run(AbstractTestSecureIPC.java:451)
~[test-classes/:?]
{noformat}
We need to open java.net too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28722) Should wipe out all the output directories in the 'init health results' stage in nightly job
Duo Zhang created HBASE-28722: - Summary: Should wipe out all the output directories in the 'init health results' stage in nightly job Key: HBASE-28722 URL: https://issues.apache.org/jira/browse/HBASE-28722 Project: HBase Issue Type: Bug Components: jenkins, scripts Reporter: Duo Zhang For master and branch-3, we do not have jdk8 and jdk11 stages but we can still see there are comments on jira which include these stages's results. I think the problem is that, in the 'init health results' stage, we want to stash some empty results but actually there are some build results for previous builds there so we stash some non empty results. We should wipe out these directories first before stash them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28668) Add documentation about specifying connection uri in replication and map reduce jobs
[ https://issues.apache.org/jira/browse/HBASE-28668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28668. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~bbeaudreault] and [~ndimiduk] for reviewing! > Add documentation about specifying connection uri in replication and map > reduce jobs > > > Key: HBASE-28668 > URL: https://issues.apache.org/jira/browse/HBASE-28668 > Project: HBase > Issue Type: Task > Components: documentation, mapreduce, Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28714) Hadoop check for hadoop 3.4.0 is failing
[ https://issues.apache.org/jira/browse/HBASE-28714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28714. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks [~ndimiduk] for reviewing! > Hadoop check for hadoop 3.4.0 is failing > > > Key: HBASE-28714 > URL: https://issues.apache.org/jira/browse/HBASE-28714 > Project: HBase > Issue Type: Bug > Components: dependencies, hadoop3 >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.10 > > > In hadoop 3.4.0, hadoop common depends on org.bouncycastle:bcprov-jdk15on, > where we an enforcer rule to force depending on org.bouncycastle:*-jdk18on. > We should exlude org.bouncycastle:bcprov-jdk15on from hadoop. > And also remove direct references of protobuf 2.5 in our asyncfs code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28721) AsyncFSWAL is broken when running against hadoop 3.4.0
Duo Zhang created HBASE-28721:
-
Summary: AsyncFSWAL is broken when running against hadoop 3.4.0
Key: HBASE-28721
URL: https://issues.apache.org/jira/browse/HBASE-28721
Project: HBase
Issue Type: Bug
Components: hadoop3, wal
Reporter: Duo Zhang
{noformat}
2024-07-10T10:09:33,161 ERROR [master/localhost:0:becomeActiveMaster {}]
asyncfs.FanOutOneBlockAsyncDFSOutputHelper(258): Couldn't properly initialize
access to HDFS internals. Please update your WAL Provider to not make use of
the 'asyncfs' provider. See HBASE-16110 for more information.
java.lang.NoSuchMethodException:
org.apache.hadoop.hdfs.DFSClient.beginFileLease(long,org.apache.hadoop.hdfs.DFSOutputStream)
at java.lang.Class.getDeclaredMethod(Class.java:2675) ~[?:?]
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createLeaseManager(FanOutOneBlockAsyncDFSOutputHelper.java:175)
~[hbase-asyncfs-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.(FanOutOneBlockAsyncDFSOutputHelper.java:252)
~[hbase-asyncfs-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
at java.lang.Class.forName0(Native Method) ~[?:?]
at java.lang.Class.forName(Class.java:375) ~[?:?]
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.load(AsyncFSWALProvider.java:149)
~[classes/:?]
at
org.apache.hadoop.hbase.wal.WALFactory.getProviderClass(WALFactory.java:174)
~[classes/:?]
at org.apache.hadoop.hbase.wal.WALFactory.(WALFactory.java:262)
~[classes/:?]
at org.apache.hadoop.hbase.wal.WALFactory.(WALFactory.java:231)
~[classes/:?]
at
org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:383)
~[classes/:?]
at
org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:135)
~[classes/:?]
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:1003)
~[classes/:?]
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2524)
~[classes/:?]
at
org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:613)
~[classes/:?]
at
org.apache.hadoop.hbase.trace.TraceUtil.lambda$tracedRunnable$2(TraceUtil.java:155)
~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28719) Use ExtendedCell in WALEdit
Duo Zhang created HBASE-28719: - Summary: Use ExtendedCell in WALEdit Key: HBASE-28719 URL: https://issues.apache.org/jira/browse/HBASE-28719 Project: HBase Issue Type: Sub-task Components: wal Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28718) Should support the license name 'Apache-2.0'
Duo Zhang created HBASE-28718: - Summary: Should support the license name 'Apache-2.0' Key: HBASE-28718 URL: https://issues.apache.org/jira/browse/HBASE-28718 Project: HBase Issue Type: Improvement Reporter: Duo Zhang Assignee: Duo Zhang Starting from v29 of apache parent pom, the license name was changed from 'Apache License, Version 2.0' to 'Apache-2.0'. We should support it so we do not need to set lots of exceptions in supplemental-models.xml. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28714) Exclude org.bouncycastle:bcprov-jdk15on from hadoop
Duo Zhang created HBASE-28714: - Summary: Exclude org.bouncycastle:bcprov-jdk15on from hadoop Key: HBASE-28714 URL: https://issues.apache.org/jira/browse/HBASE-28714 Project: HBase Issue Type: Bug Components: dependencies, hadoop3 Reporter: Duo Zhang In hadoop 3.4.0, hadoop common depends on org.bouncycastle:bcprov-jdk15on, where we an enforcer rule to force depending on org.bouncycastle:*-jdk18on. We should exlude org.bouncycastle:bcprov-jdk15on from hadoop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28698) Add hadoop 3.4.0 in hadoop check
[ https://issues.apache.org/jira/browse/HBASE-28698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28698. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Assignee: Duo Zhang Resolution: Fixed Pushed to all active branches. Thanks [~pankajkumar] for reviewing! > Add hadoop 3.4.0 in hadoop check > > > Key: HBASE-28698 > URL: https://issues.apache.org/jira/browse/HBASE-28698 > Project: HBase > Issue Type: Task > Components: jenkins, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28475) Mark 2.4.x as EOL
[ https://issues.apache.org/jira/browse/HBASE-28475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28475. --- Assignee: Duo Zhang Resolution: Fixed Done. > Mark 2.4.x as EOL > - > > Key: HBASE-28475 > URL: https://issues.apache.org/jira/browse/HBASE-28475 > Project: HBase > Issue Type: Umbrella > Components: community >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28711) Update the information about the EOL for 2.4.x on https://downloads.apache.org/hbase/
[ https://issues.apache.org/jira/browse/HBASE-28711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28711. --- Resolution: Fixed Committed to svn dist-release. > Update the information about the EOL for 2.4.x on > https://downloads.apache.org/hbase/ > - > > Key: HBASE-28711 > URL: https://issues.apache.org/jira/browse/HBASE-28711 > Project: HBase > Issue Type: Sub-task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28713) Add 2.6.x in hadoop support matrix in our ref guide
Duo Zhang created HBASE-28713: - Summary: Add 2.6.x in hadoop support matrix in our ref guide Key: HBASE-28713 URL: https://issues.apache.org/jira/browse/HBASE-28713 Project: HBase Issue Type: Task Components: documentation Reporter: Duo Zhang Now it is only up to 2.5.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28712) Add JDK17 in the support matrix in our ref guide
Duo Zhang created HBASE-28712: - Summary: Add JDK17 in the support matrix in our ref guide Key: HBASE-28712 URL: https://issues.apache.org/jira/browse/HBASE-28712 Project: HBase Issue Type: Task Components: documentation Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28711) Update the information about the EOL for 2.4.x on https://downloads.apache.org/hbase/
Duo Zhang created HBASE-28711: - Summary: Update the information about the EOL for 2.4.x on https://downloads.apache.org/hbase/ Key: HBASE-28711 URL: https://issues.apache.org/jira/browse/HBASE-28711 Project: HBase Issue Type: Sub-task Components: website Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28710) Remove download links for 2.4.x on download page
Duo Zhang created HBASE-28710: - Summary: Remove download links for 2.4.x on download page Key: HBASE-28710 URL: https://issues.apache.org/jira/browse/HBASE-28710 Project: HBase Issue Type: Sub-task Components: website Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28709) Bump certifi from 2023.7.22 to 2024.7.4 in /dev-support/git-jira-release-audit
[ https://issues.apache.org/jira/browse/HBASE-28709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28709. --- Fix Version/s: 4.0.0-alpha-1 Resolution: Fixed Merged to master. > Bump certifi from 2023.7.22 to 2024.7.4 in /dev-support/git-jira-release-audit > -- > > Key: HBASE-28709 > URL: https://issues.apache.org/jira/browse/HBASE-28709 > Project: HBase > Issue Type: Task > Components: dependabot, scripts, security >Reporter: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28709) Bump certifi from 2023.7.22 to 2024.7.4 in /dev-support/git-jira-release-audit
Duo Zhang created HBASE-28709: - Summary: Bump certifi from 2023.7.22 to 2024.7.4 in /dev-support/git-jira-release-audit Key: HBASE-28709 URL: https://issues.apache.org/jira/browse/HBASE-28709 Project: HBase Issue Type: Task Components: dependabot, scripts, security Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28700) Change hbase site build to use jdk 17
[ https://issues.apache.org/jira/browse/HBASE-28700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28700. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~sunxin] for reviewing! > Change hbase site build to use jdk 17 > - > > Key: HBASE-28700 > URL: https://issues.apache.org/jira/browse/HBASE-28700 > Project: HBase > Issue Type: Sub-task > Components: jenkins, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > > After HBASE-28676 we need to use jdk 17 for building master branch, so we > also need to upgrade website build to use jdk 17. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28708) Modify hbase scripts to only support java 17
Duo Zhang created HBASE-28708: - Summary: Modify hbase scripts to only support java 17 Key: HBASE-28708 URL: https://issues.apache.org/jira/browse/HBASE-28708 Project: HBase Issue Type: Sub-task Components: scripts Reporter: Duo Zhang I think now the script worked fine with java17, but I think we need to add some checks that if users use a jdk version less 17, we should fail immediately and post the correct error message. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28675) Change releaseTarget to 17 and also remove unused profile for older jdk versions in pom
[ https://issues.apache.org/jira/browse/HBASE-28675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28675. --- Fix Version/s: 3.0.0-beta-2 Hadoop Flags: Reviewed Release Note: Change javac compiler to generate byte code for java 17+. Resolution: Fixed Pushed to master and branch-3. Thanks [~ndimiduk] for reviewing! > Change releaseTarget to 17 and also remove unused profile for older jdk > versions in pom > --- > > Key: HBASE-28675 > URL: https://issues.apache.org/jira/browse/HBASE-28675 > Project: HBase > Issue Type: Sub-task > Components: build, java, pom >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28707) Backport the code changes in HBASE-28675 to branch-2.x
Duo Zhang created HBASE-28707: - Summary: Backport the code changes in HBASE-28675 to branch-2.x Key: HBASE-28707 URL: https://issues.apache.org/jira/browse/HBASE-28707 Project: HBase Issue Type: Task Reporter: Duo Zhang For aligning the code between different branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-22372) Revert back to upstream maven-fluido-skin for website
[ https://issues.apache.org/jira/browse/HBASE-22372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-22372. --- Resolution: Duplicate Implemented by HBASE-28617. > Revert back to upstream maven-fluido-skin for website > - > > Key: HBASE-22372 > URL: https://issues.apache.org/jira/browse/HBASE-22372 > Project: HBase > Issue Type: Task > Components: website >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Minor > > MSKINS-137 was resolved which had our hack for the mobile menu in it. No need > to use the fork I was maintaining/publishing after maven-fluido-skin:1.8 gets > released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28703) Data race in RecoveredEditsOutputSink
Duo Zhang created HBASE-28703:
-
Summary: Data race in RecoveredEditsOutputSink
Key: HBASE-28703
URL: https://issues.apache.org/jira/browse/HBASE-28703
Project: HBase
Issue Type: Bug
Components: wal
Reporter: Duo Zhang
Hit this error while testing jdk17 locally
{noformat}
Tests run: 37, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 42.3 s <<<
FAILURE! - in org.apache.hadoop.hbase.wal.TestWALSplitValueCompression
org.apache.hadoop.hbase.wal.TestWALSplitValueCompression.testEmptyLogFiles
Time elapsed: 0.359 s <<< ERROR!
java.io.IOException: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of
bounds for length 0
at
org.apache.hadoop.hbase.wal.RecoveredEditsOutputSink.closeWriters(RecoveredEditsOutputSink.java:129)
at
org.apache.hadoop.hbase.wal.RecoveredEditsOutputSink.close(RecoveredEditsOutputSink.java:96)
at
org.apache.hadoop.hbase.wal.WALSplitter.splitWAL(WALSplitter.java:416)
at org.apache.hadoop.hbase.wal.WALSplitter.split(WALSplitter.java:219)
at
org.apache.hadoop.hbase.wal.TestWALSplit.splitAndCount(TestWALSplit.java:529)
at
org.apache.hadoop.hbase.wal.TestWALSplit.testEmptyLogFiles(TestWALSplit.java:563)
at
org.apache.hadoop.hbase.wal.TestWALSplit.testEmptyLogFiles(TestWALSplit.java:548)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for
length 0
at java.base/java.util.ArrayList.add(ArrayList.java:455)
at java.base/java.util.ArrayList.add(ArrayList.java:467)
at
org.apache.hadoop.hbase.wal.RecoveredEditsOutputSink.lambda$closeWriters$0(RecoveredEditsOutputSink.java:111)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
... 1 more
{noformat}
It is a bit strange that we meet ArrayIndexOutOfBounds in ArrayList.add.
Then I noticed that, we use a thread pool to close the writers but splits field
is just an ArrayList, which is not thread safe...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard
Duo Zhang created HBASE-28702: - Summary: TestBackupMerge fails 100% of times on flaky dashboard Key: HBASE-28702 URL: https://issues.apache.org/jira/browse/HBASE-28702 Project: HBase Issue Type: Bug Components: backuprestore Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28701) Cleanup deprecated methods around Operation related data sttructures
[ https://issues.apache.org/jira/browse/HBASE-28701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28701. --- Resolution: Not A Problem Looking to the wrong branch... Sorry for the noise... > Cleanup deprecated methods around Operation related data sttructures > > > Key: HBASE-28701 > URL: https://issues.apache.org/jira/browse/HBASE-28701 > Project: HBase > Issue Type: Sub-task > Components: API, Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > > There are still some deprecated methods there, like compareTo, setTimeStamp > etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28701) Cleanup deprecated methods around Operation related data sttructures
Duo Zhang created HBASE-28701: - Summary: Cleanup deprecated methods around Operation related data sttructures Key: HBASE-28701 URL: https://issues.apache.org/jira/browse/HBASE-28701 Project: HBase Issue Type: Sub-task Components: API, Client Reporter: Duo Zhang There are still some deprecated methods there, like compareTo, setTimeStamp etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28700) Change hbase site build to use jdk 17
Duo Zhang created HBASE-28700: - Summary: Change hbase site build to use jdk 17 Key: HBASE-28700 URL: https://issues.apache.org/jira/browse/HBASE-28700 Project: HBase Issue Type: Sub-task Components: jenkins, scripts Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28694) Make client integration and packaging test work with java 17
[ https://issues.apache.org/jira/browse/HBASE-28694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28694. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.6+. We use a different hadoop version for branch-2.5 and the code is a bit different so I do not change it. Thanks [~sunxin] for reviewing! > Make client integration and packaging test work with java 17 > > > Key: HBASE-28694 > URL: https://issues.apache.org/jira/browse/HBASE-28694 > Project: HBase > Issue Type: Sub-task > Components: jenkins, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1 > > > Now branch-3.x requires building with jdk 17+ but we still use older jdk in > this check so the nightly jobs for master and branch-3 fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28699) Bump jdk and maven versions in pre commit and nighly dockerfile
[ https://issues.apache.org/jira/browse/HBASE-28699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28699. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Release Note: maven 3.8.6 -> 3.9.8 temurin openjdk8 8u352-b08 -> 8u412-b08 temurin openjdk11 11.0.17_8 -> 11.0.23_9 temurin openjdk17 17.0.10_7 -> 17.0.11_9 Resolution: Fixed Pushed to all active branches. Thanks [~sunxin] for reviewing! > Bump jdk and maven versions in pre commit and nighly dockerfile > --- > > Key: HBASE-28699 > URL: https://issues.apache.org/jira/browse/HBASE-28699 > Project: HBase > Issue Type: Task > Components: jenkins, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > Bump to the newest version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28678) Make nightly builds for 3.x java 17 only and add java 17 test for 2.x
[ https://issues.apache.org/jira/browse/HBASE-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28678. --- Resolution: Fixed Pushed addendum to all branch-2.x. > Make nightly builds for 3.x java 17 only and add java 17 test for 2.x > - > > Key: HBASE-28678 > URL: https://issues.apache.org/jira/browse/HBASE-28678 > Project: HBase > Issue Type: Sub-task > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-28678) Make nightly builds for 3.x java 17 only and add java 17 test for 2.x
[ https://issues.apache.org/jira/browse/HBASE-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-28678: --- Still missed to patch a place which may cause something error when skipping some stages... > Make nightly builds for 3.x java 17 only and add java 17 test for 2.x > - > > Key: HBASE-28678 > URL: https://issues.apache.org/jira/browse/HBASE-28678 > Project: HBase > Issue Type: Sub-task > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28699) Bump jdk and maven versions in pre commit and nighly dockerfile
Duo Zhang created HBASE-28699: - Summary: Bump jdk and maven versions in pre commit and nighly dockerfile Key: HBASE-28699 URL: https://issues.apache.org/jira/browse/HBASE-28699 Project: HBase Issue Type: Task Components: jenkins, scripts Reporter: Duo Zhang Bump to the newest version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28698) Add hadoop 3.4.0 in hadoop check
Duo Zhang created HBASE-28698: - Summary: Add hadoop 3.4.0 in hadoop check Key: HBASE-28698 URL: https://issues.apache.org/jira/browse/HBASE-28698 Project: HBase Issue Type: Task Components: jenkins, scripts Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28678) Make nightly builds for 3.x java 17 only and add java 17 test for 2.x
[ https://issues.apache.org/jira/browse/HBASE-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28678. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Assignee: Duo Zhang Resolution: Fixed Pushed to all active branches. Thanks [~sunxin] for reviewing! > Make nightly builds for 3.x java 17 only and add java 17 test for 2.x > - > > Key: HBASE-28678 > URL: https://issues.apache.org/jira/browse/HBASE-28678 > Project: HBase > Issue Type: Sub-task > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28694) Make client integration and packaging test work with java 17
Duo Zhang created HBASE-28694: - Summary: Make client integration and packaging test work with java 17 Key: HBASE-28694 URL: https://issues.apache.org/jira/browse/HBASE-28694 Project: HBase Issue Type: Sub-task Components: jenkins, scripts Reporter: Duo Zhang Now branch-3.x requires building with jdk 17+ but we still use older jdk in this check so the nightly jobs for master and branch-3 fail. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28693) Change flaky tests to run with jdk17
[ https://issues.apache.org/jira/browse/HBASE-28693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28693. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Assignee: Duo Zhang Resolution: Fixed Pushed to all active branches. Thanks [~sunxin] for reviewing! > Change flaky tests to run with jdk17 > > > Key: HBASE-28693 > URL: https://issues.apache.org/jira/browse/HBASE-28693 > Project: HBase > Issue Type: Sub-task > Components: flakies, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > Now we use jdk8 to run flaky tests jenkins jobs. > Let's change to use jdk17 for all active branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28693) Change flaky tests to run with jdk17
Duo Zhang created HBASE-28693: - Summary: Change flaky tests to run with jdk17 Key: HBASE-28693 URL: https://issues.apache.org/jira/browse/HBASE-28693 Project: HBase Issue Type: Sub-task Components: flakies, jenkins Reporter: Duo Zhang Now we use jdk8 to run flaky tests jenkins jobs. Let's change to use jdk17 for all active branches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28688) Correct the usage for blanks ignore options in yetus
[ https://issues.apache.org/jira/browse/HBASE-28688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28688. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks [~zghao] for reviewing! > Correct the usage for blanks ignore options in yetus > > > Key: HBASE-28688 > URL: https://issues.apache.org/jira/browse/HBASE-28688 > Project: HBase > Issue Type: Bug > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28658) The failsafe snapshot should be deleted after rollback successfully
[ https://issues.apache.org/jira/browse/HBASE-28658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28658. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.5+. Thanks [~guluo] for contributing! > The failsafe snapshot should be deleted after rollback successfully > --- > > Key: HBASE-28658 > URL: https://issues.apache.org/jira/browse/HBASE-28658 > Project: HBase > Issue Type: Bug > Components: Client, snapshots >Affects Versions: 2.4.13 >Reporter: guluo >Assignee: guluo >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > When a table exists and is in a disabled state, hbase supports to restore by > the snapshot of this table. > In this scenario, hbase would create a failsafe snapshot for this disabled > table, and hbase would rollback by this failsafe snapshot when fail to > restore. > However on hbase cluster, the failsafe snapshot still exists after rollback > successfully by failsafe snapshot. > I think when restore failed by table snapshot but rollback successfully by > failsafe snapshot, this failsafe snapshot should be deleted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28689) Add more files in spotless for trim tailing whitespaces
Duo Zhang created HBASE-28689: - Summary: Add more files in spotless for trim tailing whitespaces Key: HBASE-28689 URL: https://issues.apache.org/jira/browse/HBASE-28689 Project: HBase Issue Type: Improvement Components: build, pom Reporter: Duo Zhang Assignee: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28688) Correct the usage for blanks ignore options in yetus
Duo Zhang created HBASE-28688: - Summary: Correct the usage for blanks ignore options in yetus Key: HBASE-28688 URL: https://issues.apache.org/jira/browse/HBASE-28688 Project: HBase Issue Type: Bug Components: build, jenkins Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28679) Upgrade yetus to a newer version
[ https://issues.apache.org/jira/browse/HBASE-28679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28679. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Release Note: Upgrade yetus to 0.15.0. Some notable differences: Whitespace related checks are renamed to blanks Use xmllint instead of jrunscript for validating xml files. For github there is an extra step to write commit status back to github but for HBase it does not work due to insufficient permission. Resolution: Fixed Pushed to all active branches. Thanks [~ndimiduk] for reviewing! > Upgrade yetus to a newer version > > > Key: HBASE-28679 > URL: https://issues.apache.org/jira/browse/HBASE-28679 > Project: HBase > Issue Type: Sub-task > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > Now we use the one in yetus for validating, where it uses jrunscript to > execute a simple javascript script. > But the javascript engine has been removed from JDK starting from JDK 15, so > in JDK 17 we can not use this way any more. > https://openjdk.java.net/jeps/372 > We should find another way to validate xml files. > = > In newer version, yetus has already changed to use xmllint, so let's see how > to upgreade yetus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28476) Remove jenkins files for branch-2.4
[ https://issues.apache.org/jira/browse/HBASE-28476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28476. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.4. Thanks [~sunxin]! > Remove jenkins files for branch-2.4 > --- > > Key: HBASE-28476 > URL: https://issues.apache.org/jira/browse/HBASE-28476 > Project: HBase > Issue Type: Sub-task > Components: jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28684) Remove CellWrapper and use ExtendedCell internally in client side data structure
Duo Zhang created HBASE-28684: - Summary: Remove CellWrapper and use ExtendedCell internally in client side data structure Key: HBASE-28684 URL: https://issues.apache.org/jira/browse/HBASE-28684 Project: HBase Issue Type: Sub-task Components: API, Client Reporter: Duo Zhang In general, all Cells in HBase are ExtendedCells, we introduce Cell interface is only for preventing user to call some methods which damage the system. So I think we should have internal methods which can get ExtendedCell from the client side data structures so we do not need to cast everywhere. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28644) Use ExtendedCell instead of Cell in KeyValueScanner
[ https://issues.apache.org/jira/browse/HBASE-28644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28644. --- Fix Version/s: 2.7.0 3.0.0-beta-2 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2+. Thanks [~apurtell] for reviewing and [~stoty] for helping fixing Phoenix! > Use ExtendedCell instead of Cell in KeyValueScanner > --- > > Key: HBASE-28644 > URL: https://issues.apache.org/jira/browse/HBASE-28644 > Project: HBase > Issue Type: Sub-task > Components: API, regionserver, Scanners >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2 > > > Need to do this before removing some deprecated methods in Cell, as we still > need to use these method at server side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28617. --- Resolution: Fixed Change category back to http://projects.apache.org/category/database > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-28617: --- For addressing doap issues. > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28683) Only allow one TableProcedureInterface for a single table to run at the same time for some special procedure types
Duo Zhang created HBASE-28683: - Summary: Only allow one TableProcedureInterface for a single table to run at the same time for some special procedure types Key: HBASE-28683 URL: https://issues.apache.org/jira/browse/HBASE-28683 Project: HBase Issue Type: Improvement Components: master, proc-v2 Reporter: Duo Zhang We have a table lock in the MasterProcedureScheduler, which is designed to only allow one procedure to run at the same time when they require exclusive lock. But there is a problem that for availability, usually we can not always hold the exclusive lock through the whole procedure life time, as if so, we can not execute region assignment for this table too. The solution is to set holdLock to false, which means we will release the table lock after one execution cycle. In this way, it is possible that different table procedures may execute at the same time, which could mess things up. Especially that, in HBASE-28522, we find out that it is even impossible for DisableTableProcedure to hold the exclusive lock all the time. If the steps for DisableTableProcedure can be overlapped with other procedures like ModifyTableProcedure or even EnableTableProcedure, things will be definationly messed up... So we need to find another way to ensure that for a single table, only one of these procedures can be executed at the same time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28548) Add documentation about the URI based connection registry
[ https://issues.apache.org/jira/browse/HBASE-28548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28548. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~ndimiduk] for reviewing! > Add documentation about the URI based connection registry > - > > Key: HBASE-28548 > URL: https://issues.apache.org/jira/browse/HBASE-28548 > Project: HBase > Issue Type: Sub-task > Components: Client, documentation >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28617. --- Resolution: Fixed Updated doap. > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-28617: --- > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28681) Remove unused pages on our website and update doap.rdf
[ https://issues.apache.org/jira/browse/HBASE-28681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28681. --- Resolution: Fixed Via commit https://github.com/apache/hbase-site/commit/cbf1cee6587e9a26860d4f839fd7ebd345e6c57c > Remove unused pages on our website and update doap.rdf > -- > > Key: HBASE-28681 > URL: https://issues.apache.org/jira/browse/HBASE-28681 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28681) Remove unused pages on our website and update doap.rdf
Duo Zhang created HBASE-28681: - Summary: Remove unused pages on our website and update doap.rdf Key: HBASE-28681 URL: https://issues.apache.org/jira/browse/HBASE-28681 Project: HBase Issue Type: Task Components: website Reporter: Duo Zhang Assignee: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28679) Try another way to validate xml files
Duo Zhang created HBASE-28679: - Summary: Try another way to validate xml files Key: HBASE-28679 URL: https://issues.apache.org/jira/browse/HBASE-28679 Project: HBase Issue Type: Sub-task Components: build, jenkins Reporter: Duo Zhang Now we use the one in yetus for validating, where it uses jrunscript to execute a simple javascript script. But the javascript engine has been removed from JDK starting from JDK 15, so in JDK 17 we can not use this way any more. We should find another way to validate xml files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28617. --- Resolution: Fixed > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-28617: --- Need to revert some css changes as some of our pages are broken... > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28678) Make nightly builds for 3.x java 17 only and add java 17 test for 2.x
Duo Zhang created HBASE-28678: - Summary: Make nightly builds for 3.x java 17 only and add java 17 test for 2.x Key: HBASE-28678 URL: https://issues.apache.org/jira/browse/HBASE-28678 Project: HBase Issue Type: Sub-task Components: jenkins Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28676) Make pre commit and nightly build for 3.x to only run jdk 17 test
Duo Zhang created HBASE-28676: - Summary: Make pre commit and nightly build for 3.x to only run jdk 17 test Key: HBASE-28676 URL: https://issues.apache.org/jira/browse/HBASE-28676 Project: HBase Issue Type: Sub-task Components: build, jenkins Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28677) Add jdk 17 task for pre commit and nightly build for 2.x
Duo Zhang created HBASE-28677: - Summary: Add jdk 17 task for pre commit and nightly build for 2.x Key: HBASE-28677 URL: https://issues.apache.org/jira/browse/HBASE-28677 Project: HBase Issue Type: Sub-task Components: build, jenkins Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28675) Change pom to java 17 only
Duo Zhang created HBASE-28675: - Summary: Change pom to java 17 only Key: HBASE-28675 URL: https://issues.apache.org/jira/browse/HBASE-28675 Project: HBase Issue Type: Sub-task Components: build, java, pom Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28674) Bump minimum supported java version to 17 for HBase 3.x
Duo Zhang created HBASE-28674: - Summary: Bump minimum supported java version to 17 for HBase 3.x Key: HBASE-28674 URL: https://issues.apache.org/jira/browse/HBASE-28674 Project: HBase Issue Type: Umbrella Components: build, java Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28673) Bump urllib3 from 1.26.18 to 1.26.19 in /dev-support/git-jira-release-audit
[ https://issues.apache.org/jira/browse/HBASE-28673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28673. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed > Bump urllib3 from 1.26.18 to 1.26.19 in /dev-support/git-jira-release-audit > --- > > Key: HBASE-28673 > URL: https://issues.apache.org/jira/browse/HBASE-28673 > Project: HBase > Issue Type: Task > Components: dependabot, scripts, security >Reporter: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28673) Bump urllib3 from 1.26.18 to 1.26.19 in /dev-support/git-jira-release-audit
Duo Zhang created HBASE-28673: - Summary: Bump urllib3 from 1.26.18 to 1.26.19 in /dev-support/git-jira-release-audit Key: HBASE-28673 URL: https://issues.apache.org/jira/browse/HBASE-28673 Project: HBase Issue Type: Task Components: dependabot, scripts, security Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28617) Add trademark statement in footer on our website
[ https://issues.apache.org/jira/browse/HBASE-28617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28617. --- Fix Version/s: 4.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thanks [~ndimiduk] for reviewing! > Add trademark statement in footer on our website > > > Key: HBASE-28617 > URL: https://issues.apache.org/jira/browse/HBASE-28617 > Project: HBase > Issue Type: Task > Components: website >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0-alpha-1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28668) Add documentation about specifying connection uri in replication and map reduce jobs
Duo Zhang created HBASE-28668: - Summary: Add documentation about specifying connection uri in replication and map reduce jobs Key: HBASE-28668 URL: https://issues.apache.org/jira/browse/HBASE-28668 Project: HBase Issue Type: Task Components: documentation, mapreduce, Replication Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28565) Make map reduce jobs accept connection uri when specifying peer cluster
[ https://issues.apache.org/jira/browse/HBASE-28565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28565. --- Resolution: Fixed Pushed to master and branch-3. Thanks [~ndimiduk] for reviewing! > Make map reduce jobs accept connection uri when specifying peer cluster > --- > > Key: HBASE-28565 > URL: https://issues.apache.org/jira/browse/HBASE-28565 > Project: HBase > Issue Type: Improvement > Components: mapreduce, Replication >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0-beta-2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28651) Reformat the javadoc for CellChunkMap
Duo Zhang created HBASE-28651: - Summary: Reformat the javadoc for CellChunkMap Key: HBASE-28651 URL: https://issues.apache.org/jira/browse/HBASE-28651 Project: HBase Issue Type: Improvement Components: documentation, regionserver Reporter: Duo Zhang It was messed up while introducing spotless, let's restore it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28648) Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker
Duo Zhang created HBASE-28648: - Summary: Change the deprecation cycle for RegionObserver.postInstantiateDeleteTracker Key: HBASE-28648 URL: https://issues.apache.org/jira/browse/HBASE-28648 Project: HBase Issue Type: Sub-task Components: Coprocessors Reporter: Duo Zhang Visibility label feature still use this method so it can not be removed in 3.0.0. Should change the deprecation cycle javadoc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-28644) Use ExtendedCell instead of Cell in KeyValueScanner
Duo Zhang created HBASE-28644: - Summary: Use ExtendedCell instead of Cell in KeyValueScanner Key: HBASE-28644 URL: https://issues.apache.org/jira/browse/HBASE-28644 Project: HBase Issue Type: Sub-task Components: API, regionserver, Scanners Reporter: Duo Zhang Need to do this before removing some deprecated methods in Cell, as we still need to use these method at server side. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-28549) Make shell commands support column qualifiers with colons
[
https://issues.apache.org/jira/browse/HBASE-28549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28549.
---
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.9
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2.5+.
Thanks [~junegunn]!
> Make shell commands support column qualifiers with colons
> -
>
> Key: HBASE-28549
> URL: https://issues.apache.org/jira/browse/HBASE-28549
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Junegunn Choi
>Assignee: Junegunn Choi
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9
>
>
> Revisiting abandonded HBASE-13788.
> h2. Problem
> Shell commands do not support column qualifiers with colons (which are
> actually quite common in practice) because the part after the first colon is
> always treated as a converter expression.
> This can be too restrictive because:
> # Converters are only used for {{get}} and {{scan}} commands. They are not
> supported anyway for other mutating commands such as {{put}}, {{delete}},
> {{incr}}, etc.
> # Converter expression should follow a specific pattern. It should either be
> a method name of the {{Bytes}} class, or should be in {{c(CLASS).METHOD}}
> format. We ignore the part after the first colon even if it does not follow
> the pattern.
> h2. Suggested solution
> I suggest applying two approaches to make the commands support column
> qualifiers with colons.
> # Do not interpret column qualifiers when using commands that don't support
> converters.
> # If the part after the first colon does not follow the pattern, treat it as
> a part of the column qualifier
> h2. Counterargument
> Depending on how you see it, this makes the commands inconsistent in how they
> handle column qualifiers. For example, a user may want to use the same column
> expression throughout the commands.
> {code}
> create 't1', 'cf'
> col = 'cf:cq:toLong'
> # Expecting incr command to automatically ignore :toLong part
> incr 't1', 'r1', col, 1
> get 't1', 'r1', COLUMNS => [col]
> {code}
> However, if we see the converter as an option that is supported by only a few
> commands, passing it to a command that doesn't support it can be considered
> to be a user error. {{help 'put'}} or {{help 'delete'}} don't mention
> anything about converters.
> h2. Alternative solution
> An alternative solution would be to add a global switch that disables the
> converter interpretation altogether.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HBASE-28636) Add UTs for testing copy/sync table between clusters
[ https://issues.apache.org/jira/browse/HBASE-28636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-28636. --- Fix Version/s: 2.7.0 3.0.0-beta-2 2.6.1 2.5.9 Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks [~sunxin] for reviewing! > Add UTs for testing copy/sync table between clusters > > > Key: HBASE-28636 > URL: https://issues.apache.org/jira/browse/HBASE-28636 > Project: HBase > Issue Type: Improvement > Components: mapreduce, test >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9 > > > While implementing HBASE-28565, I found out that there is no test for testing > these two tools between clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
