[jira] [Resolved] (HBASE-27911) log4j configuration file not worked
[
https://issues.apache.org/jira/browse/HBASE-27911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
caijialiang resolved HBASE-27911.
-
Resolution: Not A Bug
> log4j configuration file not worked
> ---
>
> Key: HBASE-27911
> URL: https://issues.apache.org/jira/browse/HBASE-27911
> Project: HBase
> Issue Type: Bug
>Reporter: caijialiang
>Priority: Major
>
> HBase sets the HBASE_ROOT_LOGGER variable in many startup scripts, and
> finally places this variable in the startup parameters in the bin/hbase
> script, "-Dhbase.root.logger=${HBASE_ROOT_LOGGER:-INFO,console}". This is
> really strange as it overrides the log4j configuration, which is not
> beneficial for users who are not familiar with HBase because they cannot
> enable debug by modifying the log4j configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27921) Bump up jruby to 9.4.2.0 and related joni and jcodings to 2.1.48 and 1.0.58 respectively
Sercan Tekin created HBASE-27921: Summary: Bump up jruby to 9.4.2.0 and related joni and jcodings to 2.1.48 and 1.0.58 respectively Key: HBASE-27921 URL: https://issues.apache.org/jira/browse/HBASE-27921 Project: HBase Issue Type: Bug Reporter: Sercan Tekin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27920) Skipping compact for this region if the table disable compaction
guluo created HBASE-27920:
-
Summary: Skipping compact for this region if the table disable
compaction
Key: HBASE-27920
URL: https://issues.apache.org/jira/browse/HBASE-27920
Project: HBase
Issue Type: Improvement
Components: Compaction
Affects Versions: 2.4.13, 2.3.7
Environment: HBase 2.3.7
Reporter: guluo
CompactionChecker.chore() is called periodically for compacting. as follow:
{code:java}
//代码占位符
protected void chore() {
for (Region r : this.instance.onlineRegions.values()) {
// Skip compaction if region is read only
if (r == null || r.isReadOnly()) {
continue;
}
HRegion hr = (HRegion) r;
for (HStore s : hr.stores.values()) {
// ...
}
}
} {code}
Just skip compact for the region if table disable compaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)
+1 for hbase-kustomize On Mon, Jun 5, 2023 at 4:44 AM Nick Dimiduk wrote: > Hello, > > As I work through the integration of these kustomize definitions into the > existing java project structure that is hbase-operator-tools, I'm > increasingly of the opinion that this is too much of a clash of concerns. I > think that this contribution would make better sense as its own repository > with its own release cycle. I'm neither aware of nor can I imagine a > technical coupling between the kustomize resources and the rest of the > utilities in operator-tools. Likewise, this change set introduces new > requirements (docker, buildx, KinD and/or minikube) to the build and test > environment that are not otherwise needed by operator-tools. > > What do you think? SHould we request a new repository for the > kustomize files? I propose hbase-kustomize.git. > > Thanks, > Nick > > On Mon, May 22, 2023 at 4:33 PM Nick Dimiduk wrote: > > > I went ahead and rebuilt the Hadoop image module in the same style. I > > rebased the zookeeper-single and hdfs kustimize implementations onto the > > same structure. So, PR’s #118, #119, #120, and #121 are all in this > style. > > I don’t have a place for running integration tests, but unit tests are > now > > running in Jenkins. > > > > I appreciate any attention you can provide. > > > > Thanks, > > Nick > > > > On Mon, 22 May 2023 at 16:02, TAK-LON WU wrote: > > > >> Sorry that I’m on vacation and will be back online after 06/06 , but > >> thanks > >> for putting the PR out and I believe someone on our side will review it > . > >> ( > >> or when I come back I will review them) > >> > >> -Stephen > >> > >> On Mon, May 22, 2023 at 6:08 PM Nick Dimiduk > wrote: > >> > >> > Heya team, > >> > > >> > I have rebuilt one of the early PRs so that the docker image build > >> pieces > >> > are integrated with the maven build. If this is acceptable to the > >> > reviewers, I'll go forward with integrating the other images and > >> > kustomize/kuttl tests in the same way. > >> > > >> > Please take a look. > >> > > >> > Thanks, > >> > Nick > >> > > >> > https://github.com/apache/hbase-operator-tools/pull/118 > >> > > >> > On Fri, May 12, 2023 at 4:19 PM Nick Dimiduk > >> wrote: > >> > > >> > > Heya team, > >> > > > >> > > I have created individual pull-requests for each of the major > >> functional > >> > > pieces outlined in the initial branch. These await review. > >> > > > >> > > I've now started working integrating the test harness into the maven > >> > > build. After a brief detour for a Yetus plugin, I'm now looking > >> instead > >> > at > >> > > maven integration via exec-maven-plugin. I'm also investigating how > to > >> > pull > >> > > the container image build up into maven as well. > >> > > > >> > > Thanks, > >> > > Nic, > >> > > > >> > > On Thu, May 4, 2023 at 2:42 PM Nick Dimiduk > >> wrote: > >> > > > >> > >> Heya team, > >> > >> > >> > >> I've created a feature ticket [0] from which this contribution can > >> hang. > >> > >> I've created an associated release version [1] and feature branch > [2] > >> > >> against which we can target PRs while things take shape. I've > >> published > >> > my > >> > >> initial extraction of this feature as a whole for your review [3] > -- > >> > take a > >> > >> look at the big picture there. For each commit on that branch, I've > >> > created > >> > >> a sub-task on HBASE-27827. Probably reviewers will find other items > >> we > >> > need > >> > >> to peel off as sub-tasks. I'll start turning each of these commits > >> into > >> > PRs > >> > >> suitable for the Apache repo and your perusal. > >> > >> > >> > >> I think we're getting due for the 1.3 release of Operator Tools, > so I > >> > >> expect this will land in 1.4. > >> > >> > >> > >> Thanks, > >> > >> Nick > >> > >> > >> > >> [0]: https://issues.apache.org/jira/browse/HBASE-27827 > >> > >> [1]: > >> https://issues.apache.org/jira/browse/HBASE/fixforversion/12353199 > >> > >> [2]: > >> > >> > >> > > >> > https://github.com/apache/hbase-operator-tools/tree/HBASE-27827-kubernetes-deployment > >> > >> [3]: > >> > >> > >> > > >> > https://github.com/apache/hbase-operator-tools/compare/HBASE-27827-kubernetes-deployment...ndimiduk:hbase-operator-tools:HBASE-27827-kubernetes-deployment > >> > >> > >> > >> > >> > >> > >> > >> On Mon, Mar 13, 2023 at 11:28 AM Nick Dimiduk > > >> > >> wrote: > >> > >> > >> > >>> Heya team, > >> > >>> > >> > >>> Over here at $dayjob, we have an increasing reliance on Kubernetes > >> for > >> > >>> both development and production workloads. Our tools are maturing > >> and > >> > >>> we're hoping that they might be of interest to the wider > community. > >> > >>> I'd like to see if there's community interest in receiving > some/any > >> of > >> > >>> them as a contribution. I think we'll also need a plan from ASF > >> Infra > >> > >>> that makes kubernetes available to us as a project. > >> > >>> > >> > >>> We have implemented a basic stack of tools for orchestrating
[jira] [Created] (HBASE-27919) Run ITBLL for branch-3
Duo Zhang created HBASE-27919: - Summary: Run ITBLL for branch-3 Key: HBASE-27919 URL: https://issues.apache.org/jira/browse/HBASE-27919 Project: HBase Issue Type: Sub-task Components: integration tests Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27918) Remove useless content for branch-3
Duo Zhang created HBASE-27918: - Summary: Remove useless content for branch-3 Key: HBASE-27918 URL: https://issues.apache.org/jira/browse/HBASE-27918 Project: HBase Issue Type: Sub-task Reporter: Duo Zhang For example, the ref guide related stuff. Let's alian with branch-2. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27917) Set version to 4.0.0-alpha-1-SNAPSHOT on master
Duo Zhang created HBASE-27917: - Summary: Set version to 4.0.0-alpha-1-SNAPSHOT on master Key: HBASE-27917 URL: https://issues.apache.org/jira/browse/HBASE-27917 Project: HBase Issue Type: Sub-task Components: build, pom Reporter: Duo Zhang Fix For: 4.0.0-alpha-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27916) Cut branch-3
Duo Zhang created HBASE-27916: - Summary: Cut branch-3 Key: HBASE-27916 URL: https://issues.apache.org/jira/browse/HBASE-27916 Project: HBase Issue Type: Sub-task Components: community Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Introduce new git repository for kustomize definitions (was: Kubernetes Orchestration for ZK, HDFS, and HBase)
+1 and thanks for all the work (will catch up those emails sooner or later this week) -Stephen On Mon, Jun 5, 2023 at 9:02 PM 张铎(Duo Zhang) wrote: > +1 > > Nick Dimiduk 于2023年6月5日周一 19:44写道： > > > Hello, > > > > As I work through the integration of these kustomize definitions into the > > existing java project structure that is hbase-operator-tools, I'm > > increasingly of the opinion that this is too much of a clash of > concerns. I > > think that this contribution would make better sense as its own > repository > > with its own release cycle. I'm neither aware of nor can I imagine a > > technical coupling between the kustomize resources and the rest of the > > utilities in operator-tools. Likewise, this change set introduces new > > requirements (docker, buildx, KinD and/or minikube) to the build and test > > environment that are not otherwise needed by operator-tools. > > > > What do you think? SHould we request a new repository for the > > kustomize files? I propose hbase-kustomize.git. > > > > Thanks, > > Nick > > > > On Mon, May 22, 2023 at 4:33 PM Nick Dimiduk > wrote: > > > > > I went ahead and rebuilt the Hadoop image module in the same style. I > > > rebased the zookeeper-single and hdfs kustimize implementations onto > the > > > same structure. So, PR’s #118, #119, #120, and #121 are all in this > > style. > > > I don’t have a place for running integration tests, but unit tests are > > now > > > running in Jenkins. > > > > > > I appreciate any attention you can provide. > > > > > > Thanks, > > > Nick > > > > > > On Mon, 22 May 2023 at 16:02, TAK-LON WU wrote: > > > > > >> Sorry that I’m on vacation and will be back online after 06/06 , but > > >> thanks > > >> for putting the PR out and I believe someone on our side will review > it > > . > > >> ( > > >> or when I come back I will review them) > > >> > > >> -Stephen > > >> > > >> On Mon, May 22, 2023 at 6:08 PM Nick Dimiduk > > wrote: > > >> > > >> > Heya team, > > >> > > > >> > I have rebuilt one of the early PRs so that the docker image build > > >> pieces > > >> > are integrated with the maven build. If this is acceptable to the > > >> > reviewers, I'll go forward with integrating the other images and > > >> > kustomize/kuttl tests in the same way. > > >> > > > >> > Please take a look. > > >> > > > >> > Thanks, > > >> > Nick > > >> > > > >> > https://github.com/apache/hbase-operator-tools/pull/118 > > >> > > > >> > On Fri, May 12, 2023 at 4:19 PM Nick Dimiduk > > >> wrote: > > >> > > > >> > > Heya team, > > >> > > > > >> > > I have created individual pull-requests for each of the major > > >> functional > > >> > > pieces outlined in the initial branch. These await review. > > >> > > > > >> > > I've now started working integrating the test harness into the > maven > > >> > > build. After a brief detour for a Yetus plugin, I'm now looking > > >> instead > > >> > at > > >> > > maven integration via exec-maven-plugin. I'm also investigating > how > > to > > >> > pull > > >> > > the container image build up into maven as well. > > >> > > > > >> > > Thanks, > > >> > > Nic, > > >> > > > > >> > > On Thu, May 4, 2023 at 2:42 PM Nick Dimiduk > > >> wrote: > > >> > > > > >> > >> Heya team, > > >> > >> > > >> > >> I've created a feature ticket [0] from which this contribution > can > > >> hang. > > >> > >> I've created an associated release version [1] and feature branch > > [2] > > >> > >> against which we can target PRs while things take shape. I've > > >> published > > >> > my > > >> > >> initial extraction of this feature as a whole for your review [3] > > -- > > >> > take a > > >> > >> look at the big picture there. For each commit on that branch, > I've > > >> > created > > >> > >> a sub-task on HBASE-27827. Probably reviewers will find other > items > > >> we > > >> > need > > >> > >> to peel off as sub-tasks. I'll start turning each of these > commits > > >> into > > >> > PRs > > >> > >> suitable for the Apache repo and your perusal. > > >> > >> > > >> > >> I think we're getting due for the 1.3 release of Operator Tools, > > so I > > >> > >> expect this will land in 1.4. > > >> > >> > > >> > >> Thanks, > > >> > >> Nick > > >> > >> > > >> > >> [0]: https://issues.apache.org/jira/browse/HBASE-27827 > > >> > >> [1]: > > >> https://issues.apache.org/jira/browse/HBASE/fixforversion/12353199 > > >> > >> [2]: > > >> > >> > > >> > > > >> > > > https://github.com/apache/hbase-operator-tools/tree/HBASE-27827-kubernetes-deployment > > >> > >> [3]: > > >> > >> > > >> > > > >> > > > https://github.com/apache/hbase-operator-tools/compare/HBASE-27827-kubernetes-deployment...ndimiduk:hbase-operator-tools:HBASE-27827-kubernetes-deployment > > >> > >> > > >> > >> > > >> > >> > > >> > >> On Mon, Mar 13, 2023 at 11:28 AM Nick Dimiduk < > ndimi...@apache.org > > > > > >> > >> wrote: > > >> > >> > > >> > >>> Heya team, > > >> > >>> > > >> > >>> Over here at $dayjob, we have an increasing reliance on > Kubernetes > > >> for > > >> > >>> both development and p
Re: Call for Presentations, Community Over Code Asia 2023
Thanks to Duo for submitting the proposal! Please share the google and we can input information respectively. -Stephen On Tue, Jun 6, 2023 at 10:50 AM Duo Zhang wrote: > BTW, I've already submitted a representation about the new features > introduced in HBase recently. > > Title: What's new in the recent and upcoming HBase releases > Description: > Apache HBase™ is the Hadoop database, a distributed, scalable, big data > store. > The HBase community is preparing new major release 3.0.0 and new minor > release 2.6.0, with some brand new features. In this presentation, we will > introduce these new features, about how they benefit our users and how we > implement them in HBase. Like: > - OpenTelemetry Tracing: HBASE-22120, HBASE-26419 > - The new region replication framework: HBASE-26233 > - Move the logging framework from log4j to log4j2: HBASE-19577 > - Cloud native supports > - Introduce StoreFileTracker for better object storage support: > HBASE-26067, HBASE-26584 > - K8s deployment support: HBASE-27827, in progress > - No persistent data on zookeeper > - Move meta location off zookeeper: HBASE-26193 > - Table based replication queue storage: HBASE-27109 > - File system based replication peer storage: HBASE-27110 > - redeploy cluster with only root directory on object storage: > HBASE-26245 > - Future? > - HBase on Ozone > - WAL on Ozone: HBASE-27740 > - Fully cloud native, no other self deployed services other than HBase > itself > - New WAL implementation: BookKeeper? Embedded WAL service? > > Plan to create a google doc online so others in the community could also > help polishing the slides, as I do not know all the details about these > features. > > Thanks. > > Duo Zhang 于2023年6月6日周二 10:36写道： > > > FYI. The CFP deadline has been extended to 6.18, please submit your > > representations :) > > > > 会议的中文介绍见：https://www.bagevent.com/event/8409854 > > > > > > > > -- Forwarded message - > > 发件人： Rich Bowen > > Date: 2023年6月6日周二 00:09 > > Subject: Call for Presentations, Community Over Code Asia 2023 > > To: rbo...@apache.org > > > > > > You are receiving this message because you are subscribed to one more > > more developer mailing lists at the Apache Software Foundation. > > > > The call for presentations is now open at > > "https://apachecon.com/acasia2023/cfp.html";, and will be closed by > > Sunday, Jun 18th, 2023 11:59 PM GMT. > > > > The event will be held in Beijing, China, August 18-20, 2023. > > > > We are looking for presentations about anything relating to Apache > > Software Foundation projects, open-source governance, community, and > > software development. > > In particular, this year we are building content tracks around the > > following specific topics/projects: > > > > AI / Machine learning > > API / Microservice > > Community > > CloudNative > > Data Storage & Computing > > DataOps > > Data Lake & Data Warehouse > > OLAP & Data Analysis > > Performance Engineering > > Incubator > > IoT/IIoT > > Messaging > > RPC > > Streaming > > Workflow / Data Processing > > Web Server / Tomcat > > > > If your proposed presentation falls into one of these categories, > > please select that topic in the CFP entry form. Or select Others if > > it’s related to another topic or project area. > > > > Looking forward to hearing from you! > > > > Willem Jiang, and the Community Over Code planners > > > > >
[jira] [Created] (HBASE-27915) Update hbase_docker with an extra Dockerfile compatible with mac m1 platfrom
Wellington Chevreuil created HBASE-27915:
Summary: Update hbase_docker with an extra Dockerfile compatible
with mac m1 platfrom
Key: HBASE-27915
URL: https://issues.apache.org/jira/browse/HBASE-27915
Project: HBase
Issue Type: Bug
Reporter: Wellington Chevreuil
Assignee: Wellington Chevreuil
When trying to use the current Dockerfile under "./dev-support/hbase_docker" on
m1 macs, the docker build fails at the git clone & mvn build stage with below
error:
{noformat}
#0 8.214 qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such
file or directory
{noformat}
It turns out for mac m1, we have to explicitly define the platform flag for the
ubuntu image. I thought we could add a note in this readme, together with an
"m1" subfolder containing a modified copy of this Dockerfile that works on mac
m1s.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HBASE-27914) Finish 3.0.0-alpha-4 release
Duo Zhang created HBASE-27914: - Summary: Finish 3.0.0-alpha-4 release Key: HBASE-27914 URL: https://issues.apache.org/jira/browse/HBASE-27914 Project: HBase Issue Type: Sub-task Components: community Reporter: Duo Zhang Assignee: Duo Zhang Release the artifacts on repository.apache.org Move the binaries from dist-dev to dist-release Add xml to download page(via HBASE-27913) Push tag 3.0.0-alpha-4RC0 as tag rel/3.0.0-alpha-4 Release 3.0.0-alpha-4 on JIRA https://issues.apache.org/jira/projects/HBASE/versions/12351845 Add release data on https://reporter.apache.org/addrelease.html?hbase Send announcement email -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27913) Add 3.0.0-alpha-4 to download page
Duo Zhang created HBASE-27913: - Summary: Add 3.0.0-alpha-4 to download page Key: HBASE-27913 URL: https://issues.apache.org/jira/browse/HBASE-27913 Project: HBase Issue Type: Sub-task Components: website Reporter: Duo Zhang Assignee: Duo Zhang Fix For: 3.0.0-beta-1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27895) Put 3.0.0-alpha-4RC0
[ https://issues.apache.org/jira/browse/HBASE-27895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27895. --- Resolution: Fixed Done. > Put 3.0.0-alpha-4RC0 > > > Key: HBASE-27895 > URL: https://issues.apache.org/jira/browse/HBASE-27895 > 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)
[RESULT][VOTE] First release candidate for hbase 3.0.0-alpha-4 is available for download
WIth 4 binding +1s, and 2 non-binding +1s, the vote passes. Thanks all for helping! Let me push this release out and also start other works around the final 3.0.0 release. 张铎(Duo Zhang) 于2023年6月7日周三 21:59写道： > Here is my own +1. > > Guanghao Zhang 于2023年6月7日周三 14:46写道： > >> +1 (binding) >> >> * Checksum : ok >> * Rat check (1.8.0_362): ok >> - mvn clean apache-rat:check >> * Built from source (1.8.0_362): ok >> - mvn clean install -DskipTests >> * Unit tests pass (1.8.0_362): ok >> - mvn clean package -P runSmallTests >> -Dsurefire.rerunFailingTestsCount=3 >> >> Shanmukha Haripriya Kota 于2023年6月7日周三 >> 08:17写道： >> >> > +1 >> > >> > [INFO] >> > >> > [INFO] BUILD SUCCESS >> > [INFO] >> > >> > [INFO] Total time: 33:55 min >> > [INFO] Finished at: 2023-06-06T19:00:23-05:00 >> > [INFO] >> > >> > ~/Desktop/hbase300/hbase-3.0.0-alpha-4/dev-support >> > * Signature: ok >> > * Checksum : ok >> > * Rat check (11.0.10): ok >> > - mvn clean apache-rat:check >> > * Built from source (11.0.10): ok >> > - mvn clean install -DskipTests >> > * Unit tests pass (11.0.10): ok >> > - mvn clean package -P runSmallTests >> > -Dsurefire.rerunFailingTestsCount=3 >> > >> > [1] + 19163 done ./hbase-vote.sh -s -f >> > https://dist.apache.org/repos/dist/release/hbase/KEYS >> > >> > On Tue, Jun 6, 2023 at 10:22 AM Andrew Purtell >> > wrote: >> > >> > > +1 (binding) >> > > >> > > * Signature: ok >> > > * Checksum : ok >> > > * Rat check (11.0.19): ok >> > > - mvn clean apache-rat:check >> > > * Built from source (11.0.19): ok >> > > - mvn clean install -DskipTests >> > > * Unit tests pass (11.0.19): failed >> > > - mvn clean package -P runAllTests >> > > -Dsurefire.rerunFailingTestsCount=3 >> > > >> > > TestSpnegoHttpServer and TestProxyUserSpnegoHttpServer in hbase-http >> > > consistently failed but it may be environmental, related to local >> keberos >> > > configs. >> > > >> > > On Sun, May 28, 2023 at 8:13 AM Duo Zhang >> wrote: >> > > >> > > > Please vote on this Apache hbase release candidate, >> > > > hbase-3.0.0-alpha-4RC0 >> > > > >> > > > The VOTE will remain open for at least 72 hours. >> > > > >> > > > [ ] +1 Release this package as Apache hbase 3.0.0-alpha-4 >> > > > [ ] -1 Do not release this package because ... >> > > > >> > > > The tag to be voted on is 3.0.0-alpha-4RC0: >> > > > >> > > > https://github.com/apache/hbase/tree/3.0.0-alpha-4RC0 >> > > > >> > > > This tag currently points to git reference >> > > > >> > > > e44cc02c75ecae7ece845f04722eb16b7528393f >> > > > >> > > > The release files, including signatures, digests, as well as >> CHANGES.md >> > > > and RELEASENOTES.md included in this RC can be found at: >> > > > >> > > > https://dist.apache.org/repos/dist/dev/hbase/3.0.0-alpha-4RC0/ >> > > > >> > > > Maven artifacts are available in a staging repository at: >> > > > >> > > > >> > > >> https://repository.apache.org/content/repositories/orgapachehbase-1520/ >> > > > >> > > > Maven artifacts for hadoop3 are available in a staging repository >> at: >> > > > >> > > > >> https://repository.apache.org/content/repositories/not-applicable/ >> > > > >> > > > Artifacts were signed with the 0x9AD2AE49 key which can be found in: >> > > > >> > > > https://downloads.apache.org/hbase/KEYS >> > > > >> > > > 3.0.0-alpha-4 is the fourth alpha release for our 3.0.0 major >> release >> > > line. >> > > > HBase 3.0.0 includes the following big feature/changes: >> > > > Synchronous Replication >> > > > OpenTelemetry Tracing >> > > > Distributed MOB Compaction >> > > > Backup and Restore >> > > > Move RSGroup balancer to core >> > > > Reimplement sync client on async client >> > > > CPEPs on shaded protobuf >> > > > Move the logging framework from log4j to log4j2 >> > > > Decouple region replication and general replication framework, and >> > > > also make region replication can work when SKIP_WAL is used >> > > > A new file system based replication peer storage >> > > > Used hbase table instead of zookeeper for tracking hbase >> replication >> > > > queue >> > > > >> > > > Notice that this is not a production ready release. It is used to >> let >> > our >> > > > users try and test the new major release, to get feedback before the >> > > final >> > > > GA release is out. >> > > > So please do NOT use it in production. Just try it and report back >> > > > everything you find unusual. >> > > > >> > > > And this time we will not include CHANGES.md and RELEASENOTE.md >> > > > in our source code, you can find it on the download site. For >> getting >> > > these >> > > > two files for old releases, please g
Re: [VOTE] First release candidate for hbase 3.0.0-alpha-4 is available for download
Here is my own +1. Guanghao Zhang 于2023年6月7日周三 14:46写道： > +1 (binding) > > * Checksum : ok > * Rat check (1.8.0_362): ok > - mvn clean apache-rat:check > * Built from source (1.8.0_362): ok > - mvn clean install -DskipTests > * Unit tests pass (1.8.0_362): ok > - mvn clean package -P runSmallTests > -Dsurefire.rerunFailingTestsCount=3 > > Shanmukha Haripriya Kota 于2023年6月7日周三 > 08:17写道： > > > +1 > > > > [INFO] > > > > [INFO] BUILD SUCCESS > > [INFO] > > > > [INFO] Total time: 33:55 min > > [INFO] Finished at: 2023-06-06T19:00:23-05:00 > > [INFO] > > > > ~/Desktop/hbase300/hbase-3.0.0-alpha-4/dev-support > > * Signature: ok > > * Checksum : ok > > * Rat check (11.0.10): ok > > - mvn clean apache-rat:check > > * Built from source (11.0.10): ok > > - mvn clean install -DskipTests > > * Unit tests pass (11.0.10): ok > > - mvn clean package -P runSmallTests > > -Dsurefire.rerunFailingTestsCount=3 > > > > [1] + 19163 done ./hbase-vote.sh -s -f > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > On Tue, Jun 6, 2023 at 10:22 AM Andrew Purtell > > wrote: > > > > > +1 (binding) > > > > > > * Signature: ok > > > * Checksum : ok > > > * Rat check (11.0.19): ok > > > - mvn clean apache-rat:check > > > * Built from source (11.0.19): ok > > > - mvn clean install -DskipTests > > > * Unit tests pass (11.0.19): failed > > > - mvn clean package -P runAllTests > > > -Dsurefire.rerunFailingTestsCount=3 > > > > > > TestSpnegoHttpServer and TestProxyUserSpnegoHttpServer in hbase-http > > > consistently failed but it may be environmental, related to local > keberos > > > configs. > > > > > > On Sun, May 28, 2023 at 8:13 AM Duo Zhang wrote: > > > > > > > Please vote on this Apache hbase release candidate, > > > > hbase-3.0.0-alpha-4RC0 > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > [ ] +1 Release this package as Apache hbase 3.0.0-alpha-4 > > > > [ ] -1 Do not release this package because ... > > > > > > > > The tag to be voted on is 3.0.0-alpha-4RC0: > > > > > > > > https://github.com/apache/hbase/tree/3.0.0-alpha-4RC0 > > > > > > > > This tag currently points to git reference > > > > > > > > e44cc02c75ecae7ece845f04722eb16b7528393f > > > > > > > > The release files, including signatures, digests, as well as > CHANGES.md > > > > and RELEASENOTES.md included in this RC can be found at: > > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/3.0.0-alpha-4RC0/ > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1520/ > > > > > > > > Maven artifacts for hadoop3 are available in a staging repository at: > > > > > > > > https://repository.apache.org/content/repositories/not-applicable/ > > > > > > > > Artifacts were signed with the 0x9AD2AE49 key which can be found in: > > > > > > > > https://downloads.apache.org/hbase/KEYS > > > > > > > > 3.0.0-alpha-4 is the fourth alpha release for our 3.0.0 major release > > > line. > > > > HBase 3.0.0 includes the following big feature/changes: > > > > Synchronous Replication > > > > OpenTelemetry Tracing > > > > Distributed MOB Compaction > > > > Backup and Restore > > > > Move RSGroup balancer to core > > > > Reimplement sync client on async client > > > > CPEPs on shaded protobuf > > > > Move the logging framework from log4j to log4j2 > > > > Decouple region replication and general replication framework, and > > > > also make region replication can work when SKIP_WAL is used > > > > A new file system based replication peer storage > > > > Used hbase table instead of zookeeper for tracking hbase > replication > > > > queue > > > > > > > > Notice that this is not a production ready release. It is used to let > > our > > > > users try and test the new major release, to get feedback before the > > > final > > > > GA release is out. > > > > So please do NOT use it in production. Just try it and report back > > > > everything you find unusual. > > > > > > > > And this time we will not include CHANGES.md and RELEASENOTE.md > > > > in our source code, you can find it on the download site. For getting > > > these > > > > two files for old releases, please go to > > > > > > > > https://archive.apache.org/dist/hbase/ > > > > > > > > To learn more about Apache hbase, please see > > > > > > > > http://hbase.apache.org/ > > > > > > > > Thanks, > > > > Your HBase Release Manager > > > > > > > > > > > > > -- > > > Best regards, > > > Andrew > > > > > > Unrest, ignorance distilled, nihilistic imbeciles - > > > I
Re: Hmaster starting issue.
Do you want to start a single node pseudo distributed hbase cluster, or a fully distributed cluster? For the former one, you do not need to start hdfs or zookeeper, just type ./start-hbase.sh with default configuration is enough. If you want a fully distributed cluster, and want it to use pre deployed zookeeper and HDFS, please read this section in our ref guide. https://hbase.apache.org/book.html#standalone_dist And make sure you have subscribed to the user@hbase or user-zh@hbase mailing list otherwise you may not receive the response. Thanks. Nick dan 于2023年6月7日周三 21:48写道： > Hi, > I'm doing Hbase 2.4.17 configuration on hadoop 3.2.4 after all the > configuration when I'm starting start-hbase.sh on mastr node i'm able to > see this. > jps > 15299 Jps > 13764 NameNode > 14981 HMaster > 14296 ResourceManager > 15177 HRegionServer > 14876 HQuorumPeer > 14063 SecondaryNameNode > but after going into shell if i'm creating some table it is giving me error > of *ERROR: KeeperErrorCode = NoNode for /hbase/master.* > Can you help me how to start hbase. >
[jira] [Resolved] (HBASE-27897) ConnectionImplementation#locateRegionInMeta should pause and retry when taking user region lock failed
[ https://issues.apache.org/jira/browse/HBASE-27897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaolin Ha resolved HBASE-27897. Fix Version/s: 2.6.0 2.4.18 2.5.6 Resolution: Fixed Merged to branch-2, branch-2.4 and branch-2.5, thanks [~wchevreuil] for reviewing! > ConnectionImplementation#locateRegionInMeta should pause and retry when > taking user region lock failed > -- > > Key: HBASE-27897 > URL: https://issues.apache.org/jira/browse/HBASE-27897 > Project: HBase > Issue Type: Improvement > Components: Client >Affects Versions: 2.4.17, 2.5.4 >Reporter: Xiaolin Ha >Assignee: Xiaolin Ha >Priority: Major > Fix For: 2.6.0, 2.4.18, 2.5.6 > > > It just throws exception and skips the pause and retry logic when > ConnectionImplementation#takeUserRegionLock fails. In some circumstances, no > pause and retry by outer logic will make next > ConnectionImplementation#takeUserRegionLock still fails, since all the > threads simultaneously grab the lock. -- This message was sent by Atlassian Jira (v8.20.10#820010)
