Re: [ANNOUNCE] New HBase committer Andor Molnár

[Viraj Jasani]

Congratulations and Welcome, Andor! Well deserved!!


On Wed, May 29, 2024 at 7:36 AM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor Molnár's
> generous contributions thus far and look forward to his continued
> involvement.
>
> Congratulations and welcome, Andor Molnár!
>
> 我很高兴代表 Apache HBase PMC 宣布 Andor Molnár 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Andor Molnár 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Andor Molnár！
>

Re: [ANNOUNCE] New HBase committer Andor Molnár

[Viraj Jasani]

Congratulations and Welcome, Andor! Well deserved!!


On Wed, May 29, 2024 at 7:36 AM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Andor Molnár(andor) has accepted the PMC's invitation to become a
> committer on the project. We appreciate all of Andor Molnár's
> generous contributions thus far and look forward to his continued
> involvement.
>
> Congratulations and welcome, Andor Molnár!
>
> 我很高兴代表 Apache HBase PMC 宣布 Andor Molnár 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Andor Molnár 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Andor Molnár！
>

Re: [ANNOUNCE] New HBase committer Istvan Toth

[Viraj Jasani]

Many Congratulations and Welcome, Istvan!!!


On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous contributions thus far and look forward to
> his continued involvement.
>
> Congratulations and welcome, Istvan Toth!
>
> 我很高兴代表 Apache HBase PMC 宣布 Istvan Toth 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Istvan Toth 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Istvan Toth！
>

Re: [ANNOUNCE] New HBase committer Istvan Toth

[Viraj Jasani]

Many Congratulations and Welcome, Istvan!!!


On Tue, Apr 2, 2024 at 4:23 AM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Istvan Toth(stoty)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Istvan Toth's generous contributions thus far and look forward to
> his continued involvement.
>
> Congratulations and welcome, Istvan Toth!
>
> 我很高兴代表 Apache HBase PMC 宣布 Istvan Toth 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Istvan Toth 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Istvan Toth！
>

Engineering blog post on HBase/Phoenix major upgrade without downtime

[Viraj Jasani]

Hello,

We have completed major upgrade of HBase/Phoenix from 1.6/4.16 to 2.4/5.1
versions and continuing journey to 2.5 release in production. Would like to
share some insights on how we achieved in-place rolling upgrade of major
release without any downtime.

Here is the Engineering Blog on Implementing Salesforce’s Largest Database
Upgrade:
https://engineering.salesforce.com/implementing-salesforces-largest-database-upgrade-inside-the-migration-to-hbase-2/


Detailed insights available on
https://engineering.salesforce.com/wp-content/uploads/2023/12/SFDC-HBase2-Phoenix5-Paper-2023.pdf

Re: [ANNOUNCE] Please welcome Bryan Beaudreault to the HBase PMC

[Viraj Jasani]

Many congratulations Bryan!! Very well deserved!!


On Mon, Oct 16, 2023 at 6:32 PM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Bryan Beaudreault has accepted our invitation to become a PMC member
> on the Apache HBase project. We appreciate Bryan Beaudreault
> stepping up to take more responsibility in the HBase project.
>
> Please join me in welcoming Bryan Beaudreault to the HBase PMC!
>
> 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请，
> 成为 Apache HBase 项目的 PMC 成员。感谢 Bryan Beaudreault 愿意在 HBase
> 项目中承担更大的责任。
>
> 欢迎 Bryan Beaudreault！
>

Re: [ANNOUNCE] Please welcome Bryan Beaudreault to the HBase PMC

[Viraj Jasani]

Many congratulations Bryan!! Very well deserved!!


On Mon, Oct 16, 2023 at 6:32 PM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Bryan Beaudreault has accepted our invitation to become a PMC member
> on the Apache HBase project. We appreciate Bryan Beaudreault
> stepping up to take more responsibility in the HBase project.
>
> Please join me in welcoming Bryan Beaudreault to the HBase PMC!
>
> 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请，
> 成为 Apache HBase 项目的 PMC 成员。感谢 Bryan Beaudreault 愿意在 HBase
> 项目中承担更大的责任。
>
> 欢迎 Bryan Beaudreault！
>

Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)

[Viraj Jasani]

Congratulations and Welcome, Hui Ruan!

On Fri, Sep 15, 2023 at 2:08 AM 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Hui
> Ruan(frostruan)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Hui's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Hui Ruan!
>
> 我很高兴代表 Apache HBase PMC 宣布阮辉已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢阮辉一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎阮辉！
>

Re: [ANNOUNCE] New HBase committer Hui Ruan(阮辉)

[Viraj Jasani]

Congratulations and Welcome, Hui Ruan!

On Fri, Sep 15, 2023 at 2:08 AM 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Hui
> Ruan(frostruan)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Hui's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Hui Ruan!
>
> 我很高兴代表 Apache HBase PMC 宣布阮辉已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢阮辉一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎阮辉！
>

Re: [ANNOUNCE] New HBase committer Nihal Jain

[Viraj Jasani]

Congratulations Nihal!! Very well deserved!!

On Wed, May 3, 2023 at 5:12 AM Nick Dimiduk  wrote:

> Hello!
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Nihal Jain
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all of Nihal's generous contributions thus far and look forward
> to his continued involvement.
>
> Congratulations and welcome, Nihal Jain!
>
> Thanks,
> Nick
>

Re: [ANNOUNCE] New HBase committer Nihal Jain

[Viraj Jasani]

Congratulations Nihal!! Very well deserved!!

On Wed, May 3, 2023 at 5:12 AM Nick Dimiduk  wrote:

> Hello!
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Nihal Jain
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all of Nihal's generous contributions thus far and look forward
> to his continued involvement.
>
> Congratulations and welcome, Nihal Jain!
>
> Thanks,
> Nick
>

Re: [ANNOUNCE] New HBase committer Tianhang Tang(唐天航)

[Viraj Jasani]

Congratulations and Welcome, Tianhang Tang !

On Wed, Mar 15, 2023 at 9:02 PM 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Tianhang
> Tang(thangTang)
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all
> of Tianhang's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Tianhang Tang!
>
> 我很高兴代表 Apache HBase PMC 宣布 唐天航 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 唐天航 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 唐天航！
>

Re: [ANNOUNCE] New HBase committer Tianhang Tang(唐天航)

[Viraj Jasani]

Congratulations and Welcome, Tianhang Tang !

On Wed, Mar 15, 2023 at 9:02 PM 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Tianhang
> Tang(thangTang)
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all
> of Tianhang's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Tianhang Tang!
>
> 我很高兴代表 Apache HBase PMC 宣布 唐天航 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 唐天航 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 唐天航！
>

Re: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the HBase PMC

[Viraj Jasani]

Congratulations! Well deserved!


On Sun, Jan 29, 2023 at 6:50 PM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Tak Lon (Stephen) Wu has accepted our invitation to become a PMC member
> on the Apache HBase project. We appreciate Tak Lon (Stephen) Wu stepping
> up to take more responsibility in the HBase project.
>
> Please join me in welcoming Tak Lon (Stephen) Wu to the HBase PMC!
>
> 我很高兴代表 Apache HBase PMC 宣布 Tak Lon (Stephen) Wu 已接受我们的邀请，
> 成为 Apache HBase 项目的 PMC 成员。感谢 Tak Lon (Stephen) Wu 愿意在 HBase
> 项目中承担更大的责任。
>
> 欢迎 Tak Lon (Stephen) Wu！
>

Re: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the HBase PMC

[Viraj Jasani]

Congratulations! Well deserved!


On Sun, Jan 29, 2023 at 6:50 PM Duo Zhang  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Tak Lon (Stephen) Wu has accepted our invitation to become a PMC member
> on the Apache HBase project. We appreciate Tak Lon (Stephen) Wu stepping
> up to take more responsibility in the HBase project.
>
> Please join me in welcoming Tak Lon (Stephen) Wu to the HBase PMC!
>
> 我很高兴代表 Apache HBase PMC 宣布 Tak Lon (Stephen) Wu 已接受我们的邀请，
> 成为 Apache HBase 项目的 PMC 成员。感谢 Tak Lon (Stephen) Wu 愿意在 HBase
> 项目中承担更大的责任。
>
> 欢迎 Tak Lon (Stephen) Wu！
>

Re: [ANNOUNCE] New HBase committer Rushabh Shah

[Viraj Jasani]

Very well deserved! Congratulations and Welcome, Rushabh!!


On Wed, Dec 14, 2022 at 10:57 PM 张铎(Duo Zhang) 
wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Rushabh Shah(shahrs87)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Rushabh's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Rushabh Shah!
>
> 我很高兴代表 Apache HBase PMC 宣布 Rushabh Shah 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Rushabh Shah 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Rushabh Shah！
>

Re: [ANNOUNCE] New HBase committer Rushabh Shah

[Viraj Jasani]

Very well deserved! Congratulations and Welcome, Rushabh!!


On Wed, Dec 14, 2022 at 10:57 PM 张铎(Duo Zhang) 
wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that
> Rushabh Shah(shahrs87)
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all
> of Rushabh's generous contributions thus far and look forward to his
> continued involvement.
>
> Congratulations and welcome, Rushabh Shah!
>
> 我很高兴代表 Apache HBase PMC 宣布 Rushabh Shah 已接受我们的邀请，成
> 为 Apache HBase 项目的 Committer。感谢 Rushabh Shah 一直以来为 HBase 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎 Rushabh Shah！
>

Re: [ANNOUNCE] New HBase Committer Liangjun He

[Viraj Jasani]

Congratulations!!

On Sat, Dec 3, 2022 at 5:51 AM Yu Li  wrote:

> Hi All,
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Liangjun
> He (heliangjun) has accepted the PMC's invitation to become a committer on
> the project. We appreciate all of Liangjun's generous contributions thus
> far and look forward to his continued involvement.
>
> Congratulations and welcome, Liangjun!
>
> 我很高兴代表 Apache HBase PMC 宣布 Liangjun He (何良均) 已接受我们的邀请，成为 Apache HBase 项目的
> Committer。感谢何良均一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎良均！
>
> Best Regards,
> Yu
> --
> Best Regards,
> Yu
>

Re: [ANNOUNCE] New HBase Committer Liangjun He

[Viraj Jasani]

Congratulations!!

On Sat, Dec 3, 2022 at 5:51 AM Yu Li  wrote:

> Hi All,
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Liangjun
> He (heliangjun) has accepted the PMC's invitation to become a committer on
> the project. We appreciate all of Liangjun's generous contributions thus
> far and look forward to his continued involvement.
>
> Congratulations and welcome, Liangjun!
>
> 我很高兴代表 Apache HBase PMC 宣布 Liangjun He (何良均) 已接受我们的邀请，成为 Apache HBase 项目的
> Committer。感谢何良均一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎良均！
>
> Best Regards,
> Yu
> --
> Best Regards,
> Yu
>

Re: HBase master unable to recover with error "Cannot seek after EOF"

[Viraj Jasani]

> Your fix is a bit dangerous since you may lose some ongoing procedures,
but
> if you did not experience any inconsistency on your cluster, for example,
> some regions are not online, then it is OK.

Duo, out of curiosity, even if some regions are offline and/or some servers
go offline, wouldn't master failover re-trigger SCPs and TRSPs to bring all
regions ONLINE?
I have played around with removal of MasterProcWAL on hbase1 only (WAL proc
store) and have seen new SCPs getting triggered i.e. AM doesn bring all
regions ONLINE eventually.


On Thu, Dec 16, 2021 at 9:57 PM 张铎(Duo Zhang)  wrote:

> I guess this should be a bug. For the master local region we do not handle
> broken WAL files which do not even have a valid header.
>
> Will take a look at the code tomorrow to confirm whether this is the case.
>
> Your fix is a bit dangerous since you may lose some ongoing procedures, but
> if you did not experience any inconsistency on your cluster, for example,
> some regions are not online, then it is OK.
>
> Thanks for reporting.
>
> Claude M  于2021年12月16日周四 03:37写道：
>
> > Hello,
> >
> > I have the following installed:
> >
> >- Hadoop 3.2.2
> >- HBase 2.3.5
> >
> >
> > When all the datanodes in Hadoop are stopped but the HBase cluster is
> > still running, the HBase master crashes w/ the attached exception and is
> > not recoverable.
> >
> > If I delete the contents under the following directories in hdfs, the
> > master will then recover:
> >
> >- /hbase/MasterData/WALs/
> >- /hbase/MasterData/data/master/store/*/recovered.wals/
> >
> > Is this an appropriate way to resolve the issue?  If not, what should be
> > done?
> >
> >
> > Thanks
> >
>

Re: [ANNOUNCE] New HBase committer Zhuoyue Huang(GeorryHuang)

[Viraj Jasani]

Congratulations!!


On Thu, 14 Oct 2021 at 12:44 PM, Guanghao Zhang  wrote:

> Folks,
>
> On behalf of the Apache HBase PMC I am pleased to announce that Zhuoyue
> Huang has accepted the PMC's invitation to become a committer on the
> project.
>
> We appreciate all of the great contributions Zhuoyue Huang has made to the
> community thus far and we look forward to his continued involvement.
>
> Allow me to be the first to congratulate Zhuoyue Huang on his new role!
>
> Thanks.
>

Re: Blog post series on "Evolution of Region assignment in HBase architecture"

[Viraj Jasani]

We have the "Part 3" of the blog series published.
Thanks to the co-writers: Duo Zhang and Andrew Purtell.

Part 3:
https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-3-e03b814ae92

On Mon, Sep 13, 2021 at 10:53 PM Viraj Jasani  wrote:

> Thanks Duo for your offer to coordinate on writing "Part 3" of this
> series, sounds great!
> Although I see TRSP#assign being used by SCP directly while assigning the
> regions, I am yet to take a detailed look into HBASE-20881
> <https://issues.apache.org/jira/browse/HBASE-20881> and the relevant
> work. Let me reach out to you over Slack and we can take it from there.
>
> On Sun, Sep 12, 2021 at 7:02 PM 张铎(Duo Zhang) 
> wrote:
>
>> Thank you Viraj and Andrew, the blog posts are outstanding!
>>
>> And I think we'd better have a part 3, about the ServerCrashProcedure(SCP)
>> :)
>>
>> In 2.0 and 2.1, we use MoveRegionProcedure, AssignRegionProcedure and
>> UnassignRegionProcedure, and one of the reasons why we removed them all
>> and
>> introduced a single TRSP to do assign/unassign/move/reopen, is because of
>> SCP.
>>
>> If a region server crashed, obviously, we can not assign regions to it any
>> more, so we should have a way to stop the procedure which are still trying
>> to assign regions to the dead server. And even for unassigning a region,
>> we
>> still need to make it online first and then unassign it. For example, when
>> disabling a table, we must make sure that all the data in memstore have
>> been flushed to storage, so we will need make it online, and then do a
>> clean close.
>> In 2.0 and 2.1, we had 3 procedures for region assignment, and there were
>> lots of corner cases when we want to interrupt them from SCP, which made
>> the code really hard to understand and buggy. So finally, we introduced a
>> TRSP to replace them all. So SCP only needs to interrupt one type of
>> procedure.
>>
>> This is the story :)
>>
>> I could help if you guys want to write the part 3 about SCP :)
>>
>> Thanks.
>>
>> Viraj Jasani  于2021年9月8日周三 上午2:27写道：
>>
>> > As some of the HBase users are still running HBase 1.x versions in their
>> > production environment, and branch-1 is trending toward EOL, now is
>> really
>> > the right time to evaluate as well as understand the features and core
>> > design changes provided by HBase 2.x versions.
>> >
>> > As the majority of us are already aware, one of the key features with
>> > significant architectural changes provided by HBase 2 is
>> > AssignmentManagerV2 (AMv2).
>> > However, we don't seem to have one place explaining 1) *the evolution
>> > of AM* and
>> > 2) how it manages region assignments with better scalability,
>> reliability
>> > and fault-tolerance.
>> > Keeping this in mind, Andrew and I have published a series of two-part
>> blog
>> > posts explaining this evolution. Part 1 provides a) some basic
>> introduction
>> > to HBase concepts, and b) AM and it's shortcomings from previous
>> versions
>> > that AMv2 is trying to resolve. Part 2 provides detailed info about Pv2
>> and
>> > how AMv2 leverages it, and also state diagrams explaining some of the
>> > complex region assignment workflows. The intention of state diagrams is
>> for
>> > dev/users to be able to a) understand region assignment workflows
>> in-depth,
>> > b) easier code walk-through and c) debug and root cause issues with
>> > better knowledge.
>> >
>> > Part 1:
>> >
>> >
>> https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-1-c43b1becc522
>> > Part 2:
>> >
>> >
>> https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-2-9568fb3790b
>> >
>>
>

Re: Blog post series on "Evolution of Region assignment in HBase architecture"

[Viraj Jasani]

Thanks Duo for your offer to coordinate on writing "Part 3" of this series,
sounds great!
Although I see TRSP#assign being used by SCP directly while assigning the
regions, I am yet to take a detailed look into HBASE-20881
<https://issues.apache.org/jira/browse/HBASE-20881> and the relevant work.
Let me reach out to you over Slack and we can take it from there.

On Sun, Sep 12, 2021 at 7:02 PM 张铎(Duo Zhang)  wrote:

> Thank you Viraj and Andrew, the blog posts are outstanding!
>
> And I think we'd better have a part 3, about the ServerCrashProcedure(SCP)
> :)
>
> In 2.0 and 2.1, we use MoveRegionProcedure, AssignRegionProcedure and
> UnassignRegionProcedure, and one of the reasons why we removed them all and
> introduced a single TRSP to do assign/unassign/move/reopen, is because of
> SCP.
>
> If a region server crashed, obviously, we can not assign regions to it any
> more, so we should have a way to stop the procedure which are still trying
> to assign regions to the dead server. And even for unassigning a region, we
> still need to make it online first and then unassign it. For example, when
> disabling a table, we must make sure that all the data in memstore have
> been flushed to storage, so we will need make it online, and then do a
> clean close.
> In 2.0 and 2.1, we had 3 procedures for region assignment, and there were
> lots of corner cases when we want to interrupt them from SCP, which made
> the code really hard to understand and buggy. So finally, we introduced a
> TRSP to replace them all. So SCP only needs to interrupt one type of
> procedure.
>
> This is the story :)
>
> I could help if you guys want to write the part 3 about SCP :)
>
> Thanks.
>
> Viraj Jasani  于2021年9月8日周三 上午2:27写道：
>
> > As some of the HBase users are still running HBase 1.x versions in their
> > production environment, and branch-1 is trending toward EOL, now is
> really
> > the right time to evaluate as well as understand the features and core
> > design changes provided by HBase 2.x versions.
> >
> > As the majority of us are already aware, one of the key features with
> > significant architectural changes provided by HBase 2 is
> > AssignmentManagerV2 (AMv2).
> > However, we don't seem to have one place explaining 1) *the evolution
> > of AM* and
> > 2) how it manages region assignments with better scalability, reliability
> > and fault-tolerance.
> > Keeping this in mind, Andrew and I have published a series of two-part
> blog
> > posts explaining this evolution. Part 1 provides a) some basic
> introduction
> > to HBase concepts, and b) AM and it's shortcomings from previous versions
> > that AMv2 is trying to resolve. Part 2 provides detailed info about Pv2
> and
> > how AMv2 leverages it, and also state diagrams explaining some of the
> > complex region assignment workflows. The intention of state diagrams is
> for
> > dev/users to be able to a) understand region assignment workflows
> in-depth,
> > b) easier code walk-through and c) debug and root cause issues with
> > better knowledge.
> >
> > Part 1:
> >
> >
> https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-1-c43b1becc522
> > Part 2:
> >
> >
> https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-2-9568fb3790b
> >
>

Blog post series on "Evolution of Region assignment in HBase architecture"

[Viraj Jasani]

As some of the HBase users are still running HBase 1.x versions in their
production environment, and branch-1 is trending toward EOL, now is really
the right time to evaluate as well as understand the features and core
design changes provided by HBase 2.x versions.

As the majority of us are already aware, one of the key features with
significant architectural changes provided by HBase 2 is
AssignmentManagerV2 (AMv2).
However, we don't seem to have one place explaining 1) *the evolution
of AM* and
2) how it manages region assignments with better scalability, reliability
and fault-tolerance.
Keeping this in mind, Andrew and I have published a series of two-part blog
posts explaining this evolution. Part 1 provides a) some basic introduction
to HBase concepts, and b) AM and it's shortcomings from previous versions
that AMv2 is trying to resolve. Part 2 provides detailed info about Pv2 and
how AMv2 leverages it, and also state diagrams explaining some of the
complex region assignment workflows. The intention of state diagrams is for
dev/users to be able to a) understand region assignment workflows in-depth,
b) easier code walk-through and c) debug and root cause issues with
better knowledge.

Part 1:
https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-1-c43b1becc522
Part 2:
https://engineering.salesforce.com/evolution-of-region-assignment-in-the-apache-hbase-architecture-part-2-9568fb3790b

[ANNOUNCE] New HBase PMC Bharath Vissapragada

[Viraj Jasani]

On behalf of the Apache HBase PMC I am pleased to announce that Bharath
Vissapragada has accepted our invitation to become a PMC member on the
HBase project. We appreciate Bharath stepping up to take more
responsibility for the project.

Congratulations and welcome, Bharath!

Re: [ANNOUNCE] New HBase committer Baiqiang Zhao

[Viraj Jasani]

Congratulations Baiqiang!


On Sun, 11 Jul 2021 at 6:11 PM, 张铎(Duo Zhang)  wrote:

> Congratulations!
>
> zheng wang <18031...@qq.com.invalid> 于2021年7月11日周日 下午6:47写道：
>
> > Congratulations~
> >
> >
> >
> >
> > --原始邮件--
> > 发件人:
> >   "user"
> > <
> > ndimi...@apache.org;
> > 发送时间:2021年7月11日(星期天) 凌晨3:18
> > 收件人:"hbase-dev" > user@hbase.apache.org;"user-zh" >
> > 主题:[ANNOUNCE] New HBase committer Baiqiang Zhao
> >
> >
> >
> > Hi everyone,
> >
> > On behalf of the Apache HBase PMC I am pleased to announce that Baiqiang
> > Zhao has accepted the PMC's invitation to become a committer on the
> > project!
> >
> > We appreciate all of the great contributions Baiqiang has made to
> > the community thus far and we look forward to his continued involvement.
> >
> > Allow me to be the first to congratulate Baiqiang on his new role!
> >
> > Thanks,
> > Nick
>

Re: [DISCUSS] EOL 4.16 and 4.x?

[Viraj Jasani]

All Phoenix devs/users (in addition to SFDC and Cloudera), please feel free
to provide your opinions on whether you are using 4.x versions and what
your future plans look like, what category of issues you are facing (if
any) from stable features provided by Apache Phoenix 4.x.
Your opinions are most welcome and would really help the community
determine the direction of the project and release management.


On Wed, 19 May 2021 at 12:28 PM, Viraj Jasani  wrote:

> I agree, EOL schedule is more important as we prepare to move to Phoenix 5.
> We are going to initiate official discussion for the upcoming big features
> e.g dual cluster support and where it fits well (as discussed over slack by
> Daniel).
>
> As far as 4.16 is concerned, IMHO we should prefer retiring it sooner than
> 4.x. Unless critical bugs are discovered, 4.16.1 could be the last release
> in 4.16 release line. Hopefully, we will have better answers in coming days.
>
>
> On Wed, 19 May 2021 at 11:52 AM, Istvan Toth  wrote:
>
>> Hi!
>>
>> I am looking forward to less backports, and I want to use Java 8 features
>> freely as much as the next developer.
>>
>> However, I'm going to play the devil's advocate here, and spell out what
>> Ankit hinted at:
>>
>> We know that SFDC is the main contributor, and probably also the single
>> largest user of Phoenix, and that they still use 4.x in production.
>> Dropping 4.x and causing SFDC to maintain their production branch
>> internally may not be in the best  interest of the Apache project,
>> as it may divert SFDC resources from the public branches, and may result
>> in
>> delaying or even missing fixes there.
>>
>> I think that it would be useful to know what EOL schedule would work best
>> for SFDC, and align our plans with that.
>>
>> Perhaps Lars or someone else from SFDC could share their "official"
>> opinion, and help set an EOL schedule that works for everyone.
>>
>> Istvan
>>
>> On Tue, May 18, 2021 at 11:30 PM Ankit Singhal 
>> wrote:
>>
>> > +1 for EOL'ing 4.x branches.
>> >
>> > As Josh and I, share the feedback from the same set of users,
>> > it would still be a good idea to hear from others but as it's been
>> already
>> > been 12 days since your first mail out, just a notice can be given for
>> > 72hrs(?)
>> > before dropping the next 4.x versions from JIRA and cleaning branches in
>> > case any volunteer comes up to maintain these branches.
>> >
>> >
>> >
>> >
>> >
>> > On Mon, May 10, 2021 at 9:27 PM Josh Elser  wrote:
>> >
>> > > No objections over here! Y'all already know the work Istvan and
>> Richard
>> > > have been doing to push on Phoenix 5.1. That continues to be our
>> focus.
>> > >
>> > > On 5/7/21 11:13 AM, Viraj Jasani wrote:
>> > > > Hi,
>> > > >
>> > > > Based on HBase community's decision to EOL branch-1 after 1.7.0
>> release
>> > > as
>> > > > per the discussion thread [1], it is inevitable that we will also
>> have
>> > to
>> > > > consider EOL of 4.x release line sometime soon.
>> > > >
>> > > > As we have discussed in the past, even though Phoenix 4.x should
>> > support
>> > > > Java 7 only (as it supports HBase 1), we are not strictly following
>> > this
>> > > > compatibility. With HBase 2 / Phoenix 5, we no longer have to worry
>> > about
>> > > > this source compatibility. Tephra also continues to support HBase 1
>> and
>> > > > hence should follow Java 7 source compatibility rules and yet I see
>> > many
>> > > > Java 8 Optional imports in tephra-hbase-compat-2.x modules. Source
>> > > > compatibility is just one of the reasons behind HBase community's
>> > > decision
>> > > > to EOL branch-1, many other important reasons are discussed over
>> thread
>> > > [1].
>> > > > Overall, HBase 2 is already widely adopted and deployed in
>> production
>> > and
>> > > > so should be Phoenix 5 IMHO.
>> > > >
>> > > > Given that there are no apparent functional differences b/ 4.16 and
>> > > 5.1(and
>> > > > master) except for maybe few pending forward-ports (if any), I
>> believe
>> > it
>> > > > is worth considering the ongoing 4.16 patch release as the last one
>> on
>> > > 4.x
>> > > > release line and EOL 4.16 and 4.x.
>> > > > Thoughts?
>> > > >
>> > > > 1. https://s.apache.org/rs2bk
>> > > >
>> > >
>> >
>>
>

Re: [DISCUSS] EOL 4.16 and 4.x?

[Viraj Jasani]

I agree, EOL schedule is more important as we prepare to move to Phoenix 5.
We are going to initiate official discussion for the upcoming big features
e.g dual cluster support and where it fits well (as discussed over slack by
Daniel).

As far as 4.16 is concerned, IMHO we should prefer retiring it sooner than
4.x. Unless critical bugs are discovered, 4.16.1 could be the last release
in 4.16 release line. Hopefully, we will have better answers in coming days.


On Wed, 19 May 2021 at 11:52 AM, Istvan Toth  wrote:

> Hi!
>
> I am looking forward to less backports, and I want to use Java 8 features
> freely as much as the next developer.
>
> However, I'm going to play the devil's advocate here, and spell out what
> Ankit hinted at:
>
> We know that SFDC is the main contributor, and probably also the single
> largest user of Phoenix, and that they still use 4.x in production.
> Dropping 4.x and causing SFDC to maintain their production branch
> internally may not be in the best  interest of the Apache project,
> as it may divert SFDC resources from the public branches, and may result in
> delaying or even missing fixes there.
>
> I think that it would be useful to know what EOL schedule would work best
> for SFDC, and align our plans with that.
>
> Perhaps Lars or someone else from SFDC could share their "official"
> opinion, and help set an EOL schedule that works for everyone.
>
> Istvan
>
> On Tue, May 18, 2021 at 11:30 PM Ankit Singhal 
> wrote:
>
> > +1 for EOL'ing 4.x branches.
> >
> > As Josh and I, share the feedback from the same set of users,
> > it would still be a good idea to hear from others but as it's been
> already
> > been 12 days since your first mail out, just a notice can be given for
> > 72hrs(?)
> > before dropping the next 4.x versions from JIRA and cleaning branches in
> > case any volunteer comes up to maintain these branches.
> >
> >
> >
> >
> >
> > On Mon, May 10, 2021 at 9:27 PM Josh Elser  wrote:
> >
> > > No objections over here! Y'all already know the work Istvan and Richard
> > > have been doing to push on Phoenix 5.1. That continues to be our focus.
> > >
> > > On 5/7/21 11:13 AM, Viraj Jasani wrote:
> > > > Hi,
> > > >
> > > > Based on HBase community's decision to EOL branch-1 after 1.7.0
> release
> > > as
> > > > per the discussion thread [1], it is inevitable that we will also
> have
> > to
> > > > consider EOL of 4.x release line sometime soon.
> > > >
> > > > As we have discussed in the past, even though Phoenix 4.x should
> > support
> > > > Java 7 only (as it supports HBase 1), we are not strictly following
> > this
> > > > compatibility. With HBase 2 / Phoenix 5, we no longer have to worry
> > about
> > > > this source compatibility. Tephra also continues to support HBase 1
> and
> > > > hence should follow Java 7 source compatibility rules and yet I see
> > many
> > > > Java 8 Optional imports in tephra-hbase-compat-2.x modules. Source
> > > > compatibility is just one of the reasons behind HBase community's
> > > decision
> > > > to EOL branch-1, many other important reasons are discussed over
> thread
> > > [1].
> > > > Overall, HBase 2 is already widely adopted and deployed in production
> > and
> > > > so should be Phoenix 5 IMHO.
> > > >
> > > > Given that there are no apparent functional differences b/ 4.16 and
> > > 5.1(and
> > > > master) except for maybe few pending forward-ports (if any), I
> believe
> > it
> > > > is worth considering the ongoing 4.16 patch release as the last one
> on
> > > 4.x
> > > > release line and EOL 4.16 and 4.x.
> > > > Thoughts?
> > > >
> > > > 1. https://s.apache.org/rs2bk
> > > >
> > >
> >
>

Re: [ANNOUNCE] New HBase Committer Xiaolin Ha(哈晓琳)

[Viraj Jasani]

Congratulations and welcome, Xiaolin Ha!!


On Sat, 15 May 2021 at 7:41 PM, 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Xiaolin
> Ha(sunhelly) has accepted the PMC's invitation to become a committer on the
> project. We appreciate all of Xiaolin's generous contributions thus far and
> look forward to her continued involvement.
>
> Congratulations and welcome, Xiaolin Ha!
>
> 我很高兴代表Apache HBase PMC宣布哈晓琳已接受我们的邀请，成为Apache
> HBase项目的Committer。感谢哈晓琳一直以来为HBase项目做出的贡献，并期待她在未来继续承担更多的责任。
>
> 欢迎哈晓琳！
>

Re: [ANNOUNCE] New HBase Committer Xiaolin Ha(哈晓琳)

[Viraj Jasani]

Congratulations and welcome, Xiaolin Ha!!


On Sat, 15 May 2021 at 7:41 PM, 张铎(Duo Zhang)  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Xiaolin
> Ha(sunhelly) has accepted the PMC's invitation to become a committer on the
> project. We appreciate all of Xiaolin's generous contributions thus far and
> look forward to her continued involvement.
>
> Congratulations and welcome, Xiaolin Ha!
>
> 我很高兴代表Apache HBase PMC宣布哈晓琳已接受我们的邀请，成为Apache
> HBase项目的Committer。感谢哈晓琳一直以来为HBase项目做出的贡献，并期待她在未来继续承担更多的责任。
>
> 欢迎哈晓琳！
>

[ANNOUNCE] New HBase PMC Huaxiang Sun

[Viraj Jasani]

On behalf of the Apache HBase PMC I am pleased to announce that Huaxiang
Sun has accepted our invitation to become a PMC member on the HBase
project. We appreciate Huaxiang stepping up to take more responsibility for
the project.

Congratulations and welcome, Huaxiang!

Re: Direct cluster upgrade from HBase 1.4 to 2.3

[Viraj Jasani]

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.
> > >
> >
>

[ANNOUNCE] New HBase committer Geoffrey Jacoby

[Viraj Jasani]

On behalf of the Apache HBase PMC I am pleased to announce that Geoffrey
Jacoby has accepted the PMC's invitation to become a committer on the
project.

Thanks so much for the work you've been contributing. We look forward to
your continued involvement.

Congratulations and welcome, Geoffrey!

Re: Direct cluster upgrade from HBase 1.4 to 2.3

[Viraj Jasani]

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: EOL branch-1 and all 1.x ?

[Viraj Jasani]

+1 to EOL'ing branch-1 and all other branch-1.x too (if they are still
active at all)


On Thu, 1 Apr 2021 at 8:53 AM, Andrew Purtell 
wrote:

> EOL of branch-1 doesn’t mean we take down the 1.6.0 release. It would be
> fine to leave that in place. That can be a separate, future, discussion,
> although if branch-1 becomes EOL its eventual removal would be certain. The
> question is really if we plan to maintain branch-1 going forward. Based on
> lack of interest and demand in releasing it, there does not seem reason to.
>
>
> > On Mar 31, 2021, at 7:51 PM, Reid Chan  wrote:
> >
> > My only concern is about the performance, once in a while there'll be
> > some emails like "2.x.y is slower than 1.x.y".
> >
> >
> >> On Thu, Apr 1, 2021 at 6:03 AM Andrew Purtell 
> wrote:
> >>
> >> Is it time to consider EOL of branch-1 and all 1.x releases ?
> >>
> >> There doesn't seem to be much developer interest in branch-1 beyond
> >> occasional maintenance. This is understandable. Per our compatibility
> >> guidelines, branch-1 commits must be compatible with Java 7, and the
> range
> >> of acceptable versions of third party dependencies is also restricted
> due
> >> to Java 7 compatibility requirements. Most developers are writing code
> with
> >> Java 8+ idioms these days. For that reason and because the branch-1 code
> >> base is generally aged at this point, all but trivial (or lucky!)
> backports
> >> require substantial changes in order to integrate adequately. Let me
> also
> >> observe that branch-1 artifacts are not fully compatible with Java 11 or
> >> later. (The shell is a good example of such issues: The version of
> >> jruby-complete required by branch-1 is not compatible with Java 11 and
> >> upgrading to the version used by branch-2 causes shell commands to error
> >> out due to Ruby language changes.)
> >>
> >> We can a priori determine there is insufficient motivation for
> production
> >> of release artifacts for the PMC to vote upon. Otherwise, someone would
> >> have done it. We had 12 releases from branch-2 derived code in 2019, 13
> >> releases from branch-2 derived code in 2020, and so far we have had 3
> >> releases from branch-2 derived code in 2021. In contrast, we had 8
> releases
> >> from branch-1 derived code in 2019, 0 releases from branch-1 in 2020,
> and
> >> so far 0 releases from branch-1 in 2021.
> >>
> >> *  2021202020191.x0282.x31312*
> >>
> >> If there is someone interested in continuing branch-1, now is the time
> to
> >> commit. However let me be clear that simply expressing an abstract
> desire
> >> to see continued branch-1 releases will not be that useful. It will be
> >> noted, but will not have much real world impact. Apache is a do-ocracy.
> In
> >> the absence of intrinsic motivation of project participants, which is
> what
> >> we seem to have here, you will need to do something: Fix the
> compatibility
> >> issues, if any between the last release of 1.x and the current branch-1
> >> head; fix any failing and flaky unit tests; produce release artifacts;
> and
> >> submit those artifacts to the PMC for voting. Or, convince someone with
> >> commit rights and/or PMC membership to undertake these actions on your
> >> behalf.
> >>
> >> Otherwise, I respectfully submit for your consideration, it is time to
> >> declare  branch-1 and all 1.x code lines EOL, simply acknowledging what
> has
> >> effectively already happened.
> >>
> >> --
> >> Best regards,
> >> Andrew
> >>
> >> Words like orphans lost among the crosstalk, meaning torn from truth's
> >> decrepit hands
> >>   - A23, Crosstalk
> >>
>

Re: [ANNOUNCE] New HBase committer Xin Sun

[Viraj Jasani]

Congratulations and Welcome Xin Sun !!


On Thu, 3 Dec 2020 at 2:43 PM, Guanghao Zhang  wrote:

> Folks,
>
> On behalf of the Apache HBase PMC I am pleased to announce that Xin Sun has
> accepted the PMC's invitation to become a committer on the project.
>
> We appreciate all of the great contributions Xin Sun has made to the
> community thus far and we look forward to his continued involvement.
>
> Allow me to be the first to congratulate Xin Sun on his new role!
>
> Thanks.
>

Re: [ANNOUNCE] New HBase committer Yulin Niu

[Viraj Jasani]

Congratulations and Welcome Yulin Niu !!


On Thu, 3 Dec 2020 at 2:42 PM, Guanghao Zhang  wrote:

> Folks,
>
> On behalf of the Apache HBase PMC I am pleased to announce that Yulin Niu
> has accepted the PMC's invitation to become a committer on the project.
>
> We appreciate all of the great contributions Yulin has made to the
> community thus far and we look forward to his continued involvement.
>
> Allow me to be the first to congratulate Yulin on his new role!
>
> Thanks.
>

Re: [DISCUSS] HBASE-25299 Scan#setRowPrefixFilter Unexpected behavior

[Viraj Jasani]

+1 to deprecating setRowPrefixFilter. PR looks good, as I commented
yesterday, if you could include your nice example as a unit test with this
PR, that would be really great.
Thanks for this nice find!


On Thu, 19 Nov 2020 at 6:02 AM, Guanghao Zhang  wrote:

> I am +1 to deprecated setRowPrefixFilter method. This method name is
> setRowPrefixFilter but not use filter and only set start row and end row. I
> thought this could be done by user.
>
> 唐天航  于2020年11月19日周四 上午12:45写道：
>
> > Hi,
> >   I have opened an issue HBASE-25299
> >  about
> > Scan#setRowPrefixFilter
> > Unexpected behavior.
> >
> > e.g.
> >
> > startRow : "112"
> >
> > rowPrefixFilter : "11"
> >
> > The Result of this scan might contain : "111", which is unexpected.
> >
> >   public Scan setRowPrefixFilter(byte[] rowPrefix) {
> > if (rowPrefix == null) {
> >   setStartRow(HConstants.EMPTY_START_ROW);
> >   setStopRow(HConstants.EMPTY_END_ROW);
> > } else {
> >   this.setStartRow(rowPrefix);
> >   this.setStopRow(calculateTheClosestNextRowKeyForPrefix(rowPrefix));
> > }
> > return this;
> >   }
> >
> >  Scan#setRowPrefixFilter achieves this function by setting startRow and
> > stopRow, ignoring the situation that startRow may have been set.
> >
> >
> > I have discussed this issue with @infraio and he suggested to deprecate
> > this method because modifying it may cause compatibility issues.
> >
> > Is this plan acceptable? Hope to get some suggestions.
> >
> >
> > Thank you. Regards
> >
>

[ANNOUNCE] Apache HBase 2.3.3 is now available for download

[Viraj Jasani]

The HBase team is happy to announce the immediate availability of HBase
2.3.3.

Apache HBase™ is an open-source, distributed, versioned, non-relational
database.
Apache HBase gives you low latency random access to billions of rows with
millions of columns atop non-specialized hardware. To learn more about
HBase,
see https://hbase.apache.org/.

HBase 2.3.3 is the third patch release in the HBase 2.3.x line, which aims
to
improve the stability and reliability of HBase. This release includes 37 bug
fixes and improvements since 2.3.2.

The full list of issues and release notes can be found here:
CHANGELOG: https://downloads.apache.org/hbase/2.3.3/CHANGES.md
RELEASENOTES: https://downloads.apache.org/hbase/2.3.3/RELEASENOTES.md

or via our issue tracker:
https://issues.apache.org/jira/projects/HBASE/versions/12346441

To download please follow the links and instructions on our website:

https://hbase.apache.org/downloads.html


Questions, comments, and problems are always welcome at:
d...@hbase.apache.org
user@hbase.apache.org

Thanks to all who contributed and made this release possible.

Cheers,
The HBase Dev Team

Re: [ANNOUNCE] Please welcome Viraj Jasani to the Apache HBase PMC

[Viraj Jasani]

Thanks a lot everyone for your warm wishes!
Looking forward to helping the community achieve more.


On Mon, 5 Oct 2020 at 10:28 PM, Andrew Purtell  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that
> Viraj Jasani has accepted our invitation to become a PMC member on the
> HBase project. We appreciate Viraj stepping up to take more
> responsibility for the project.
>
> Please join me in welcoming Viraj to the HBase PMC!
>
>
> As a reminder, if anyone would like to nominate another person as a
> committer or PMC member, even if you are not currently a committer or
> PMC member, you can always drop a note to priv...@hbase.apache.org
> to let us know.
>
> --
> Best regards,
> Andrew
>

[ANNOUNCE] Apache HBase 2.3.2 is now available for download

[Viraj Jasani]

The HBase team is happy to announce the immediate availability of HBase
2.3.2.

Apache HBase™ is an open-source, distributed, versioned, non-relational
database.
Apache HBase gives you low latency random access to billions of rows with
millions of columns atop non-specialized hardware. To learn more about
HBase,
see https://hbase.apache.org/.

HBase 2.3.2 is the second patch release in the HBase 2.3.x line, which aims
to
improve the stability and reliability of HBase. This release includes 47 bug
fixes and improvements since 2.3.1.

The full list of issues and release notes can be found here:
CHANGELOG: https://downloads.apache.org/hbase/2.3.2/CHANGELOG.2.3.2.md
RELEASENOTES: https://downloads.apache.org/hbase/2.3.2/RELEASENOTES.2.3.2.md

or via our issue tracker:
https://issues.apache.org/jira/projects/HBASE/versions/12348671

To download please follow the links and instructions on our website:

https://hbase.apache.org/downloads.html


Questions, comments, and problems are always welcome at:
d...@hbase.apache.org
user@hbase.apache.org

Thanks to all who contributed and made this release possible.

Cheers,
The HBase Dev Team

Re: Could not iterate StoreFileScanner - during compaction

[Viraj Jasani]

Hi Meeran,

BlockHeaders output has NegativeArraySizeException while reading a block.
Did you try scanning the table or specific rowkey range from the region? Is
it all good?
Also, since you were able to upgrade the cluster to 2.2.4, I am assuming
all services are good, but can you once confirm inconsistencies using
hbck and fsck commands for both HBase and HDFS?


On 2020/07/08 07:44:36, Meeran  wrote: 
> Hi Sean,
> 
> 
> 
> We upgraded the cluster to latest stable version HBase-2.2.4. We are still 
> facing the issue. Any help on this please?
> 
> 
> 
> Thanks,
> 
> Meeran
> 
> 
> 
>  On Mon, 06 Jul 2020 14:24:16 +0530 test gmail test 
>  wrote 
> 
> 
> Hi Sean,
> 
> 
> 
> printblocks output - https://pastebin.com/EYUpi6LL
> 
> blockheaders output - https://pastebin.com/TJBqgwsp
> 
> 
> 
> We are yet to test it on HBase-2.2. Will upgrade the cluster and let you 
> know. Thanks for the help.
> 
>  
> 
> Regards,
> 
> Meeran
> 
> 
> 
> 
> 
>  On Sat, 04 Jul 2020 05:26:46 +0530 Sean Busbey 
>  wrote 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> File attachments won't work on the mailing list. Can you put the files on 
> some hosting service? 
>  
> Can you reproduce the problem on hbase 2.2? HBase 2.1 has been EOM since 
> May. 
>  
>  
> On Fri, Jul 3, 2020, 18:20 Mohamed Meeran 
>  
> wrote: 
>  
> > Hi, 
> > 
> > We are using HBase-2.1.9 (Hadoop-3.1.3) in our setup. In the logs, we see 
> > major compaction failed for some of the regions with the following error 
> > logs. 
> > 
> > Caused by: java.io.IOException: Could not iterate 
> > StoreFileScanner[HFileScanner for reader 
> > reader=hdfs://TestCluster/hbasedata/data/Test/Test/6472f3839fc9b0a1d4b64e182043bc52/hb/2ec37243628b4a03ae3d937da4c27081,
> >  
> > compression=none, cacheConf=blockCache=LruBlockCache{blockCount=332, 
> > currentSize=485.88 MB, freeSize=333.32 MB, maxSize=819.20 MB, 
> > heapSize=485.88 MB, minSize=778.24 MB, minFactor=0.95, multiSize=389.12 MB, 
> > multiFactor=0.5, singleSize=194.56 MB, singleFactor=0.25}, 
> > cacheDataOnRead=true, cacheDataOnWrite=false, cacheIndexesOnWrite=false, 
> > cacheBloomsOnWrite=false, cacheEvictOnClose=false, 
> > cacheDataCompressed=false, prefetchOnOpen=false, 
> > firstKey=Optional[10259783_10101578129/hb:B/1490097103780/Put/seqid=0],
> >  
> > lastKey=Optional[10260211_100965800470017/hb:H/1490097295354/Put/seqid=0],
> >  
> > avgKeyLen=43, avgValueLen=213357, entries=10134, length=2163318554, 
> > cur=10259783_10101578851/hb:B/1490097148981/Put/vlen=16591695/seqid=0]
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.StoreFileScanner.next(StoreFileScanner.java:217)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:120)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:654)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:153)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:6593)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:6757)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:6527)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:3158)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:3407)
> >  
> > ... 5 more 
> > Caused by: java.io.IOException: Invalid onDisksize=-969694035: expected to 
> > be at least 33 and at most 2147483647, or -1 
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.checkAndGetSizeAsInt(HFileBlock.java:1673)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockDataInternal(HFileBlock.java:1746)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileBlock$FSReaderImpl.readBlockData(HFileBlock.java:1610)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl.readBlock(HFileReaderImpl.java:1496)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl$HFileScannerImpl.readNextDataBlock(HFileReaderImpl.java:931)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl$HFileScannerImpl.isNextBlock(HFileReaderImpl.java:1064)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl$HFileScannerImpl.positionForNextBlock(HFileReaderImpl.java:1058)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl$HFileScannerImpl._next(HFileReaderImpl.java:1076)
> >  
> > at 
> > org.apache.hadoop.hbase.io.hfile.HFileReaderImpl$HFileScannerImpl.next(HFileReaderImpl.java:1097)
> >  
> > at 
> > org.apache.hadoop.hbase.regionserver.StoreFileScanner.next(StoreFileScanner.java:208)
> >  
> > ... 13 more 
> > 
> > We analysed a file using the hfile tool. Attaching the output for 
> > printblocks and printblockheaders. 

Re: error while running start-hbase.sh by cygwin

[Viraj Jasani]

Hi Prashant,

Since file attachments don't work here, it is recommended to upload it
on hosting service and provide the link here.

Moreover, HBase community does not recommend running cluster on
Windows because not all functioning is tested well on Windows.


On 2020/07/05 08:01:27, Prashant Prakash Jadhav 
 wrote: 
> Hi Team,
> I am trying to run hbase on window as per apache guidance
> I am getting following error.
> [cid:image001.png@01D652CE.ECEE5030]
> 

Re: regionserver can't connect to master

[Viraj Jasani]

   {
> 
>   "href" : 
> "http://10.0.1.245:8080/api/v1/clusters/Grandline/services/YARN;,
> 
>   "ServiceInfo" : {
> 
> "cluster_name" : "Grandline",
> 
> "service_name" : "YARN"
> 
>   }
> 
> },
> 
> {
> 
>   "href" : 
> "http://10.0.1.245:8080/api/v1/clusters/Grandline/services/ZEPPELIN;,
> 
>   "ServiceInfo" : {
> 
> "cluster_name" : "Grandline",
> 
> "service_name" : "ZEPPELIN"
> 
>   }
> 
> },
> 
> {
> 
>   "href" : 
> "http://10.0.1.245:8080/api/v1/clusters/Grandline/services/ZOOKEEPER;,
> 
>   "ServiceInfo" : {
> 
> "cluster_name" : "Grandline",
> 
> "service_name" : "ZOOKEEPER"
> 
>   }
> 
> }
> 
>   ]
> 
> }
> 
> 
> Are they connected(e.g. NN and DN) and only RS is having trouble connecting 
> to HM?
> 
> Yes, this is my understanding
> 
> 
> Although telnet seems correct, can you also try "nc -zv gl-hdp-ctrl03.local 
> 16000" from RS just to double check?
> 
> $ nc -zv gl-hdp-ctrl03.local 16000
> 
> Ncat: Version 7.50 ( https://nmap.org/ncat )
> 
> Ncat: Connected to 192.168.20.248:16000.
> 
> Ncat: 0 bytes sent, 0 bytes received in 0.02 seconds.
> 
> 
> thank you
> 
> 
> From: Viraj Jasani 
> Sent: Sunday, 22 March 2020 2:47:09 AM
> To: user@hbase.apache.org
> Subject: Re: regionserver can't connect to master
> 
> Which HBase version are you using? You are bringing up fresh cluster and not 
> doing an upgrade right? Has Ambari successfully brought up NameNodes and 
> DataNodes? How-many components are already running so far? Are they 
> connected(e.g. NN and DN) and only RS is having trouble connecting to HM? 
> Although telnet seems correct, can you also try "nc -zv gl-hdp-ctrl03.local 
> 16000" from RS just to double check?
> Thanks
> 
> On 2020/03/20 23:45:28, Manuel Sopena Ballesteros  
> wrote:
> > Dear HBase community,
> >
> > I am having an issue with my ambari hbase deployment where regionserver is 
> > not able to connect to master
> >
> > Hbase Master log files:
> > 2020-03-21 02:36:53,614 INFO [Thread-16] master.ServerManager: Waiting on 
> > regionserver count=0; waited=3174901ms, expecting min=1 server(s), 
> > max=NO_LIMIT server(s), timeout=3ms, lastChange=-3174901ms
> > 2020-03-21 02:36:54,287 WARN [master/gl-hdp-ctrl03:16000] 
> > assignment.AssignmentManager: No servers available; cannot place 1 
> > unassigned regions.
> >
> > Hbase region server logs:
> > Caused by: java.net.ConnectException: Call to 
> > gl-hdp-ctrl03.local/192.168.20.248:16000 failed on connection exception: 
> > org.apache.hbase.thirdparty.io.netty.channel.ConnectTimeoutException: 
> > connection timed out: gl-hdp-ctrl03.local/192.168.20.248:16000
> > at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:166)
> > at 
> > org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390)
> > at 
> > org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95)
> > at 
> > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410)
> > at 
> > org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406)
> > at org.apache.hadoop.hbase.ipc.Call.callComplete(Call.java:103)
> > at org.apache.hadoop.hbase.ipc.Call.setException(Call.java:118)
> >
> >
> > Test connectivity from region server to master
> > $ telnet gl-hdp-ctrl03.local 16000
> > Trying 192.168.20.248...
> > Connected to gl-hdp-ctrl03.local.
> > Escape character is '^]'.
> >
> > Any idea of why region can't connect?
> >
> > Thank you very much
> > NOTICE
> > Please consider the environment before printing this email. This message 
> > and any attachments are intended for the addressee named and may contain 
> > legally privileged/confidential/copyright information. If you are not the 
> > intended recipient, you should not read, use, disclose, copy or distribute 
> > this communication. If you have received this message in error please 
> > notify us at once by return email and then delete both messages. We accept 
> > no liability for the distribution of viruses or similar in electronic 
> > communications. This notice should not be removed.
> >
> 
> NOTICE
> Please consider the environment before printing this email. This message and 
> any attachments are intended for the addressee named and may contain legally 
> privileged/confidential/copyright information. If you are not the intended 
> recipient, you should not read, use, disclose, copy or distribute this 
> communication. If you have received this message in error please notify us at 
> once by return email and then delete both messages. We accept no liability 
> for the distribution of viruses or similar in electronic communications. This 
> notice should not be removed.
> 

Re: regionserver can't connect to master

[Viraj Jasani]

Which HBase version are you using? You are bringing up fresh cluster and not 
doing an upgrade right? Has Ambari successfully brought up NameNodes and 
DataNodes? How-many components are already running so far? Are they 
connected(e.g. NN and DN) and only RS is having trouble connecting to HM? 
Although telnet seems correct, can you also try "nc -zv gl-hdp-ctrl03.local 
16000" from RS just to double check?
Thanks

On 2020/03/20 23:45:28, Manuel Sopena Ballesteros  
wrote: 
> Dear HBase community,
> 
> I am having an issue with my ambari hbase deployment where regionserver is 
> not able to connect to master
> 
> Hbase Master log files:
> 2020-03-21 02:36:53,614 INFO [Thread-16] master.ServerManager: Waiting on 
> regionserver count=0; waited=3174901ms, expecting min=1 server(s), 
> max=NO_LIMIT server(s), timeout=3ms, lastChange=-3174901ms
> 2020-03-21 02:36:54,287 WARN [master/gl-hdp-ctrl03:16000] 
> assignment.AssignmentManager: No servers available; cannot place 1 unassigned 
> regions.
> 
> Hbase region server logs:
> Caused by: java.net.ConnectException: Call to 
> gl-hdp-ctrl03.local/192.168.20.248:16000 failed on connection exception: 
> org.apache.hbase.thirdparty.io.netty.channel.ConnectTimeoutException: 
> connection timed out: gl-hdp-ctrl03.local/192.168.20.248:16000
> at org.apache.hadoop.hbase.ipc.IPCUtil.wrapException(IPCUtil.java:166)
> at 
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.onCallFinished(AbstractRpcClient.java:390)
> at 
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.access$100(AbstractRpcClient.java:95)
> at 
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:410)
> at 
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$3.run(AbstractRpcClient.java:406)
> at org.apache.hadoop.hbase.ipc.Call.callComplete(Call.java:103)
> at org.apache.hadoop.hbase.ipc.Call.setException(Call.java:118)
> 
> 
> Test connectivity from region server to master
> $ telnet gl-hdp-ctrl03.local 16000
> Trying 192.168.20.248...
> Connected to gl-hdp-ctrl03.local.
> Escape character is '^]'.
> 
> Any idea of why region can't connect?
> 
> Thank you very much
> NOTICE
> Please consider the environment before printing this email. This message and 
> any attachments are intended for the addressee named and may contain legally 
> privileged/confidential/copyright information. If you are not the intended 
> recipient, you should not read, use, disclose, copy or distribute this 
> communication. If you have received this message in error please notify us at 
> once by return email and then delete both messages. We accept no liability 
> for the distribution of viruses or similar in electronic communications. This 
> notice should not be removed.
> 

Re: Issue in running hbase-2.2.3 in cygwin

[Viraj Jasani]

Hi Prakash,

The error is reg connection loss with ZK. Where is Zookeeper running? Are you 
using standalone or pseudo distributed mode? Also, where is hbase.rootdir 
pointing to? Is it local FileSystem or HDFS? If local FileSystem, have you 
provided the path that exists on your system?

I haven't used cygwin, but if you could refer to HBase book 
https://hbase.apache.org/book.html for setting up local cluster with properties 
as mentioned, I am sure you would be able to make good progress. Please spend 
some time and you wouldn't regret it :)


On 2020/03/01 06:31:50, PRAKASH GOPALSAMY  wrote: 
>   Hi Team,
> I am trying to run the hbase-2.2.3 in cygwint in windows. While running the
> hbase shell, I am getting the below exception. Kindly help me to solve this
> issue
> 
> Mar 01, 2020 11:46:01 AM
> org.apache.hadoop.hbase.zookeeper.ReadOnlyZKClient$ZKTask$1 exec
> WARNING: 0x434c186b to localhost:2181 failed for get of /hbase/hbaseid,
> code = CONNECTIONLOSS, retries = 14
> Mar 01, 2020 11:46:02 AM org.apache.zookeeper.ClientCnxn$SendThread
> logStartConnect
> INFO: Opening socket connection to server kubernetes.docker.internal/
> 127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
> Mar 01, 2020 11:46:03 AM org.apache.zookeeper.ClientCnxn$SendThread run
> WARNING: Session 0x0 for server null, unexpected error, closing socket
> connection and attempting reconnect
> java.net.ConnectException: Connection refused: no further information
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
> at
> org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
> 

Re: Error in running hbase1.2.0 in local mode in cygwin

[Viraj Jasani]

Hi,

>From the cygwin page, download HBase release redirects you to 
>http://apachemirror.wuchna.com/hbase/ 
 , where you can see: "1.2 was EOM'd June 2019"
It is recommended to use stable releases from the download page: stable or 
stable-1 (based on whether you are already using HBase 1.x or 2.x). If you are 
trying to setup HBase cluster for the first time, you can try downloading 
stable release(2.2.3).
Btw how many nodes of cluster you are planning to bring up?


On 2020/02/29 18:59:22, PRAKASH GOPALSAMY  wrote: 
> Hi Team,
> I am trying to run hbase 1.2.0 in local mode using cygwin. I have followed
> the setup instructions in the link: https://hbase.apache.org/cygwin.html.
> But when I start hbase and try running the hbase shell command, I am
> getting the below exception. Kindly help me to resolve this issue.
> 2020-02-29 22:23:11,969 FATAL [CHNMCT279526L:49334.activeMasterManager]
> master.HMaster: Failed to become active master
> java.lang.NullPointerException
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1012)
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:482)
> at org.apache.hadoop.util.Shell.run(Shell.java:455)
> at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:702)
> at org.apache.hadoop.util.Shell.execCommand(Shell.java:791)
> at org.apache.hadoop.util.Shell.execCommand(Shell.java:774)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:646)
> at
> org.apache.hadoop.fs.RawLocalFileSystem.create(RawLocalFileSystem.java:293)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:451)
> at
> org.apache.hadoop.fs.ChecksumFileSystem.create(ChecksumFileSystem.java:426)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:906)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:887)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:784)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:773)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:727)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:705)
> at org.apache.hadoop.hbase.util.FSUtils.checkVersion(FSUtils.java:662)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:462)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:153)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:128)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:638)
> at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:184)
> at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1729)
> at java.lang.Thread.run(Thread.java:813)
> 
> 
> ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Master not initialized after 20ms seconds
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:225)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:447)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:226)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:138)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2411)
> 

Re: [ANNOUNCE] New HBase committer Bharath Vissapragada

[Viraj Jasani]

Congratulations Bharath..!! Well done :)

On Thu, 6 Feb 2020 at 8:36 AM, Nick Dimiduk  wrote:

> On behalf of the Apache HBase PMC I am pleased to announce that Bharath
> Vissapragada has accepted the PMC's invitation to become a commiter on the
> project. We appreciate all of Bharath's generous contributions thus far and
> look forward to his continued involvement.
>
> Allow me to be the first to congratulate and welcome Bharath into his new
> role!
>
> Thanks,
> Nick
>
-- 
Thanks,
Viraj

Re: [ANNOUNCE] New HBase committer Viraj Jasani

[Viraj Jasani]

Thanks a lot everyone! Thanks for all your help!
Looking forward to helping the community achieve greater milestones with
bigger impacts.
Thank you!


On Sat, 28 Dec 2019 at 8:25 AM, aman poonia 
wrote:

> Congratulations Viraj Jasani.
>
> -- *Aman Poonia*
>
>
> On Sat, Dec 28, 2019 at 7:35 AM Toshihiro Suzuki 
> wrote:
>
> > Congratulations! Viraj
> >
> > On Sat, Dec 28, 2019 at 3:13 AM Andrew Purtell  >
> > wrote:
> >
> > > Congratulations and welcome Viraj, thanks for all of your efforts so
> far.
> > >
> > > > On Dec 27, 2019, at 5:02 AM, Peter Somogyi 
> > wrote:
> > > >
> > > > On behalf of the Apache HBase PMC I am pleased to announce that
> > > > Viraj Jasani has accepted the PMC's invitation to become a
> > > > commiter on the project.
> > > >
> > > > Thanks so much for the work you've been contributing. We look forward
> > > > to your continued involvement.
> > > >
> > > > Congratulations and welcome!
> > >
> >
>
-- 
Thanks,
Viraj

Re: Snapshots TTL doesn't work in HBase-1.4.10

[Viraj Jasani]

Hi Alexander,

Snapshot TTL feature is available on major releases 1.5.0 and 2.3.0 as of
now and not on any 1.4 patch releases.


On Mon, 4 Nov 2019 at 5:51 AM, Alexander Batyrshin <0x62...@gmail.com>
wrote:

>  Hello,
> I observe that snapshots option TTL has no effect in HBase-1.4.10.
> Our snapshots created every night:
>
> > snapshot ’VIRT_STORAGE', 'snapshot-VIRT_STORAGE-${SNAP_DATE}', {TTL =>
> 1209600}
>
> Right now I see:
>
> snapshot-VIRT_STORAGE-20191016   VIRT_STORAGE
> (Wed Oct 16 03:20:19 +0400 2019)
> snapshot-VIRT_STORAGE-20191017   VIRT_STORAGE
> (Thu Oct 17 03:20:11 +0400 2019)
> snapshot-VIRT_STORAGE-20191018   VIRT_STORAGE
> (Fri Oct 18 03:19:28 +0400 2019)
> snapshot-VIRT_STORAGE-20191019   VIRT_STORAGE
> (Sat Oct 19 03:20:09 +0400 2019)
> snapshot-VIRT_STORAGE-20191020   VIRT_STORAGE
> (Sun Oct 20 03:20:06 +0400 2019)
> snapshot-VIRT_STORAGE-20191021   VIRT_STORAGE
> (Mon Oct 21 03:20:07 +0400 2019)
> snapshot-VIRT_STORAGE-20191022   VIRT_STORAGE
> (Tue Oct 22 03:20:21 +0400 2019)
> snapshot-VIRT_STORAGE-20191023   VIRT_STORAGE
> (Wed Oct 23 03:20:19 +0400 2019)
> snapshot-VIRT_STORAGE-20191024   VIRT_STORAGE
> (Thu Oct 24 03:21:21 +0400 2019)
> snapshot-VIRT_STORAGE-20191025   VIRT_STORAGE
> (Fri Oct 25 03:22:06 +0400 2019)
> snapshot-VIRT_STORAGE-20191026   VIRT_STORAGE
> (Sat Oct 26 03:21:53 +0400 2019)
> snapshot-VIRT_STORAGE-20191027   VIRT_STORAGE
> (Sun Oct 27 02:22:16 +0300 2019)
> snapshot-VIRT_STORAGE-20191028   VIRT_STORAGE
> (Mon Oct 28 02:21:44 +0300 2019)
> snapshot-VIRT_STORAGE-20191029   VIRT_STORAGE
> (Tue Oct 29 02:35:41 +0300 2019)
> snapshot-VIRT_STORAGE-20191030   VIRT_STORAGE
> (Wed Oct 30 02:18:58 +0300 2019)
> snapshot-VIRT_STORAGE-20191031   VIRT_STORAGE
> (Thu Oct 31 02:16:56 +0300 2019)
> snapshot-VIRT_STORAGE-20191101   VIRT_STORAGE
> (Fri Nov 01 02:16:46 +0300 2019)
> snapshot-VIRT_STORAGE-20191102   VIRT_STORAGE
> (Sat Nov 02 02:17:05 +0300 2019)
> snapshot-VIRT_STORAGE-20191103   VIRT_STORAGE
> (Sun Nov 03 02:17:20 +0300 2019)
> snapshot-VIRT_STORAGE-20191104   VIRT_STORAGE
> (Mon Nov 04 02:17:03 +0300 2019)
>
> As a reminder: HBase-1.4.10 doesn’t has ‘snapshot_cleanup_switch’ command.
>
> Any ideas what is going wrong?

-- 
Thanks,
Viraj