Re: [VOTE] The first HBase 2.2.7 release candidate (RC0) is available
+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_202-ea): ok - mvn clean apache-rat:check * Built from source (1.8.0_202-ea): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_202-ea): ok - mvn package -P runSmallTests -Dsurefire.rerunFailingTestsCount=3 Verified the compatibility report, as well as the changes and release notes. From: Guanghao Zhang Reply-To: "user@hbase.apache.org" Date: Sunday, April 11, 2021 at 2:34 PM To: HBase Dev List , Hbase-User Subject: [VOTE] The first HBase 2.2.7 release candidate (RC0) is available [CAUTION] The sender of this email is outside our organization. Please DO NOT CLICK links, download attachments or respond unless you recognize the sender and know the content is safe. Please contact IT immediately in case you find it suspicious. Please vote on this release candidate (RC) for Apache HBase 2.2.7. Meanwhile, as branch-2.2 will be EOL, please don't push new commits to it. And this will be the last one of the 2.2.x releases. Thanks. The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache HBase 2.2.7 [ ] -1 Do not release this package because ... The tag to be voted on is 2.2.7RC0. The release files, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1440/ Signatures used for HBase RCs can be found in this file: https://dist.apache.org/repos/dist/release/hbase/KEYS The list of bug fixes going into 2.2.7 can be found in included CHANGES.md and RELEASENOTES.md available here: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/CHANGES.md https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/RELEASENOTES.md A detailed source and binary compatibility report for this release is available at: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/api_compare_2.2.7RC0_to_2.2.6.html To learn more about Apache HBase, please see http://hbase.apache.org/ Thanks, Guanghao Zhang
[VOTE] The first HBase 2.2.7 release candidate (RC0) is available
Please vote on this release candidate (RC) for Apache HBase 2.2.7. Meanwhile, as branch-2.2 will be EOL, please don't push new commits to it. And this will be the last one of the 2.2.x releases. Thanks. The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache HBase 2.2.7 [ ] -1 Do not release this package because ... The tag to be voted on is 2.2.7RC0. The release files, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1440/ Signatures used for HBase RCs can be found in this file: https://dist.apache.org/repos/dist/release/hbase/KEYS The list of bug fixes going into 2.2.7 can be found in included CHANGES.md and RELEASENOTES.md available here: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/CHANGES.md https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/RELEASENOTES.md A detailed source and binary compatibility report for this release is available at: https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/api_compare_2.2.7RC0_to_2.2.6.html To learn more about Apache HBase, please see http://hbase.apache.org/ Thanks, Guanghao Zhang
Re: Direct cluster upgrade from HBase 1.4 to 2.3
In the doc section [1], it is clearly written that rolling upgrades are experimental for HBase 1 to 2 upgrades. However, based on rolling upgrade done in the past from 1.4 to 2.1 specifically, the steps are given because it has been tested already. The reason why doc is not updated for 1.4 to 2.3 upgrade is because no one has done it so far and without doing it in production scale, we can’t be confident to write about this. Once you start this exercise and if able to perform this upgrade successfully in prod, you can take up ownership to update the doc for 1.4 to 2.3 with your experience and that would be a great help for the community. I can guide on how to update the doc if required. Thank you, please keep us posted on any bugs encountered while testing (creating Jira would be nice) 1. https://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades On Sun, 11 Apr 2021 at 1:37 PM, MS dehghan wrote: > ُThank you very much for your response. > > We will try this workflow and I will report back any issues encountered. > What about the docs? Shouldn't it be updated to contain info about > upgrading to higher versions? > > Our setup: We have two HBase masters but there is no cluster replication > for now. We use Ansible to provision our cluster and rolling upgrade. In > the past we upgraded HBase from 1.2.7 to 1.4.12 without any issues. > > On 2021/04/07 07:43:11, Viraj Jasani wrote: > > Hi, > > > > Thanks for bringing this up. > > Steps mentioned for 1.4 -> 2.1 upgrade should also be applicable to 1.4 > -> > > 2.3/2.4 upgrade. As mentioned in the steps on the doc, you could try > > upgrading RegionServers first (RegionServer serving meta region should be > > upgraded first) followed by masters and before the upgrade, ensure that > 1.4 > > has Zookeeper less region assignment enabled. > > > > Since HBase doesn’t provide guarantees for smooth upgrades from any 1.x > to > > any 2.x versions, we might have to test the upgrade with caution. > > Please feel free to give this workflow a try and you can report back with > > any issues you encounter, will be happy to help. > > > > Moreover, how is your cluster setup? Are you using HBase replication > pairs? > > What have you been using to upgrade your clusters so far? > > > > > > On Wed, 7 Apr 2021 at 3:15 AM, MS dehghan wrote: > > > > > Hello > > > > > > We are using HBase 1.4.12 in our cluster and recently we are planning > to > > > upgrade it to 2.3.x. > > > I would like to know if direct upgrade from 1.4 to 2.3 is possible and > > > safe. Actually I couldn't find anything about this in the docs. > According > > > to the docs upgrade from 1.4 to 2.1 is tested but direct upgrading to > > > higher versions is not mentioned. > > > > > > I would be grateful if anyone could give me further information and > share > > > their experiences about upgrading from 1.4 to 2.x . > > > > > > Best Regards. > > > > > >
Re: Direct cluster upgrade from HBase 1.4 to 2.3
ُThank you very much for your response. We will try this workflow and I will report back any issues encountered. What about the docs? Shouldn't it be updated to contain info about upgrading to higher versions? Our setup: We have two HBase masters but there is no cluster replication for now. We use Ansible to provision our cluster and rolling upgrade. In the past we upgraded HBase from 1.2.7 to 1.4.12 without any issues. On 2021/04/07 07:43:11, Viraj Jasani wrote: > Hi, > > Thanks for bringing this up. > Steps mentioned for 1.4 -> 2.1 upgrade should also be applicable to 1.4 -> > 2.3/2.4 upgrade. As mentioned in the steps on the doc, you could try > upgrading RegionServers first (RegionServer serving meta region should be > upgraded first) followed by masters and before the upgrade, ensure that 1.4 > has Zookeeper less region assignment enabled. > > Since HBase doesn’t provide guarantees for smooth upgrades from any 1.x to > any 2.x versions, we might have to test the upgrade with caution. > Please feel free to give this workflow a try and you can report back with > any issues you encounter, will be happy to help. > > Moreover, how is your cluster setup? Are you using HBase replication pairs? > What have you been using to upgrade your clusters so far? > > > On Wed, 7 Apr 2021 at 3:15 AM, MS dehghan wrote: > > > Hello > > > > We are using HBase 1.4.12 in our cluster and recently we are planning to > > upgrade it to 2.3.x. > > I would like to know if direct upgrade from 1.4 to 2.3 is possible and > > safe. Actually I couldn't find anything about this in the docs. According > > to the docs upgrade from 1.4 to 2.1 is tested but direct upgrading to > > higher versions is not mentioned. > > > > I would be grateful if anyone could give me further information and share > > their experiences about upgrading from 1.4 to 2.x . > > > > Best Regards. > > >