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

[Zach York]

Congratulations and welcome Stephen! Well deserved!

On Tue, Jan 31, 2023 at 8:52 AM Rushabh Shah
 wrote:

> Congratulations Stephen !
>
>
> On Mon, Jan 30, 2023 at 10:54 PM Tak Lon (Stephen) Wu 
> wrote:
>
> > Thank you everyone ! So happy to be here and will continue to interact
> > with you guys.
> >
> > -Stephen
> >
> > On Mon, Jan 30, 2023 at 9:06 PM rajeshb...@apache.org
> >  wrote:
> > >
> > > Congratulations Stephen.
> > >
> > >
> > > Thanks,
> > > Rajeshbabu.
> > >
> > > On Mon, Jan 30, 2023, 7:33 PM Bryan Beaudreault <
> bbeaudrea...@gmail.com>
> > > wrote:
> > >
> > > > Congrats!
> > > >
> > > > On Mon, Jan 30, 2023 at 4:10 AM Balazs Meszaros <
> meszib...@apache.org>
> > > > wrote:
> > > >
> > > > > Congratulations!
> > > > >
> > > > > On Mon, Jan 30, 2023 at 9:19 AM Jan Hentschel
> > > > >  wrote:
> > > > >
> > > > > > Congratulations and welcome!
> > > > > >
> > > > > > From: Duo Zhang 
> > > > > > Date: Monday, January 30, 2023 at 3:50 AM
> > > > > > To: HBase Dev List , hbase-user <
> > > > > > user@hbase.apache.org>, user-zh 
> > > > > > Subject: [ANNOUNCE] Please welcome Tak Lon (Stephen) Wu to the
> > HBase
> > > > PMC
> > > > > > 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: [DISCUSS] Removing problematic terms from our project

[Zach York]

+1 for all proposed modifications. Happy to help with the effort as well.

On Wed, Jun 24, 2020 at 10:14 PM 张铎(Duo Zhang) 
wrote:

> -0/+1/+1/+1
>
> I’m the one who asked whether ‘master’ is safe to use without ‘slave’ in
> the private list.
>
> I’m still not convinced that it is really necessary and I do not think
> other words like ‘coordinator’ can fully describe the role of HMaster in
> HBase. HBase is more than 10 years old. In the context of HBase, the word
> ‘HMaster’ has its own meaning. Changing the name will hurt our users and
> make them confusing, especially for us non native English speakers...
>
> Thanks.
>
> Stack 于2020年6月25日 周四06:34写道：
>
> > +1/+1/+1/+1 where hbase3 adds the deprecation and hbase4 follows hbase3
> > soon after sounds good to me. I'm up for working on this.
> > S
> >
> > On Wed, Jun 24, 2020 at 2:26 PM Xu Cang  wrote:
> >
> > > Strongly agree with what Nick said here:
> > >
> > >  " From my perspective, we gain nothing as a project or as a community
> be
> > > willfully retaining use of language that is well understood to be
> > > problematic or hurtful, On the contrary, we have much to gain by
> > > encouraging
> > > contributions from as many people as possible."
> > >
> > > +1 to Andrew's proposal.
> > >
> > > It might be good to have a source of truth web page or README file for
> > > developers and users to refer to regarding all naming transitions. It's
> > > going to help both developers changing the code and users looking for
> > some
> > > answers online that use old namings.
> > >
> > > Xu
> > >
> > > On Wed, Jun 24, 2020 at 2:21 PM Nick Dimiduk 
> > wrote:
> > >
> > > > On Tue, Jun 23, 2020 at 13:11 Sean Busbey  wrote:
> > > >
> > > > > I would like to make sure I am emphatically clear that "master" by
> > > itself
> > > > > is not okay if the context is the same as what would normally be a
> > > > > master/slave context. Furthermore our use of master is clearly
> such a
> > > > > context.
> > > >
> > > >
> > > > I agree: to me “Master”, as in “HMaster” caries with it the
> > master/slave
> > > > baggage. As an alternative, I prefer the term “coordinator” over
> > > “leader”.
> > > > Thus we would have daemons called “coordinator” and “region server”.
> > > >
> > > > To me, “master” as in “master branch” does not carry the same
> baggage,
> > > but
> > > > I’m also in favor changing the name of our default branch to a word
> > that
> > > is
> > > > less conflicted. I see nothing that we gain as a community by
> > continuing
> > > to
> > > > use this word.
> > > >
> > > > It seems to me we have, broadly speaking, consensus around making
> > *some*
> > > > > changes. I haven't seen a strong push for "break everything in the
> > name
> > > > of
> > > > > expediency" (I would personally be fine with this). So barring
> > > additional
> > > > > discussion that favors breaking changes, current approaches should
> > > > comport
> > > > > with our existing project compatibility goals.
> > > > >
> > > > > Maybe we could stop talking about what-ifs and look at actual
> > practical
> > > > > examples? If anyone is currently up for doing the work of a PR we
> can
> > > > look
> > > > > at for one of these?
> > > > >
> > > > > If folks would prefer we e.g. just say "we should break whatever we
> > > need
> > > > to
> > > > > in 3.0.0 to make this happen" then it would be good to speak up.
> > > > Otherwise
> > > > > likely we would be done with needed changes circa hbase 4, probably
> > > late
> > > > > 2021 or 2022.
> > > > >
> > > > >
> > > > > On Tue, Jun 23, 2020, 03:03 zheng wang <18031...@qq.com> wrote:
> > > > >
> > > > > > IMO, master is ok if not used with slave together.
> > > > > >
> > > > > >
> > > > > > -1/+1/+1/+1
> > > > > >
> > > > > >
> > > > > > --原始邮件--
> > > > > > 发件人:"Andrew Purtell" > > > > > 发送时间:2020年6月23日(星期二) 凌晨5:24
> > > > > > 收件人:"Hbase-User" > > > > > 抄送:"dev" > > > > > 主题:Re: [DISCUSS] Removing problematic terms from our
> project
> > > > > >
> > > > > >
> > > > > >
> > > > > > In observing something like voting happening on this thread to
> > > express
> > > > > > alignment or not, it might be helpful to first, come up with a
> list
> > > of
> > > > > > terms to change (if any), and then propose replacements,
> > > individually.
> > > > So
> > > > > > far we might break this apart into four proposals:
> > > > > >
> > > > > > 1. Replace "master"/"hmaster" with ??? ("coordinator" is one
> > option),
> > > > > this
> > > > > > one has by far the most significant impact and both opinion and
> > > > > > interpretation on this one is mixed.
> > > > > >
> > > > > > 2. Replace "slave" with "follower", seems to impact the cross
> > cluster
> > > > > > replication subsystem only.
> > > > > >
> > > > > > 3. Replace "black list" with "deny list".
> > > > > >
> > > > > > 4. Replace "white list" with "accept list".
> > > > > >
> > > > > > Perhaps if you are inclined to respond with a +1/-1/+0/-0, it
> would
> > > be
> > > > 

Re: Empty REGIONINFO after Region Server Restart

[Zach York]

This is definitely not expected behavior (either on S3 or HDFS).

I agree with Stack's request to try to trace how these are happening.
Since this is with EMR, you can also create a customer support ticket to
help debug the issue.

On Wed, Apr 22, 2020, 1:58 AM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:

> >
> > I am running HBase 1.4.10 on AWS EMR 5.29.0
> >
> Which file system is hbase root dir under? If it's S3, it's very likely
> some of its lack of consistency issues leading to missing regioninfo files.
>
> Em qua., 22 de abr. de 2020 às 02:21, Stack  escreveu:
>
> > On Mon, Apr 20, 2020 at 7:59 AM Mike Linsinbigler <
> mlinsinbig...@ccri.com>
> > wrote:
> >
> > > Hello,
> > >
> > > I am running HBase 1.4.10 on AWS EMR 5.29.0 and have had issues after
> > > some of our Region Servers restart (due to a variety of reasons) and
> the
> > > cluster enters an inconsistent state after they come back up.
> > >
> > > Running hbck, I am presented with many instances of:
> > >
> > > ERROR: Empty REGIONINFO_QUALIFIER found in hbase:meta
> > >
> > >
> > > I am able to resolve this issue by running:
> > >
> > > "hbase hbck -fixEmptyMetaCells"
> > >
> > >
> > > However, this is only a fix until the next time one of our region
> > > servers restart which is currently a daily event. Does anyone know how
> > > to prevent this issue from occurring in the first place? It looks like
> > > our Region Server was in the middle of splitting and compaction
> > > operations before aborting.
> > >
> > > I've noticed that writing to hbase while these errors are present can
> > > result in ingest issues within our application so I'd really like to
> > > understand how the meta table can get into this state.
> > >
> > >
> > Rows in hbase:meta w/ empty REGIONINFO_QUALIFIER will mess you up.
> Shoudn't
> > be happening. Have you tried tracing the lifecycle of one of these empty
> > rows? The row name is the region name. Search master logs over time using
> > the regionname. See if you can get a sense of what is happening
> > manufacturing empty rows.
> >
> > Yours,
> > S
> >
> >
> >
> > > Thanks,
> > >
> > > Mike
> > >
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Bharath Vissapragada

[Zach York]

Congratulations and welcome Bharath! :)

On Thu, Feb 6, 2020 at 11:50 AM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:

> Congratulations and welcome to the team, Bharath!
>
> Em qui., 6 de fev. de 2020 às 19:25, Esteban Gutierrez
>  escreveu:
>
> > Yay! Congratulations Bharath!
> >
> > esteban.
> > --
> > Cloudera, Inc.
> >
> >
> >
> > On Thu, Feb 6, 2020 at 12:07 PM Andrew Purtell 
> > wrote:
> >
> > > Congratulations and welcome, Bharath!
> > >
> > > On Wed, Feb 5, 2020 at 7:36 PM 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
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>

Re: [ANNOUNCE] Please welcome Guangxu Cheng the HBase PMC

[Zach York]

Congratulations and welcome Guangxu!!

On Mon, Dec 9, 2019 at 10:25 AM Esteban Gutierrez
 wrote:

> Congrats Guangxu!
> --
> Cloudera, Inc.
>
>
>
> On Mon, Dec 9, 2019 at 12:03 PM Karthik Palanisamy <
> karthikshva...@gmail.com>
> wrote:
>
> > Superb!! Congratulations Guangxu Cheng!!!
> >
> > On Mon, Dec 9, 2019 at 5:58 AM Jan Hentschel <
> > jan.hentsc...@ultratendency.com> wrote:
> >
> > > Congratulations and welcome!
> > >
> > > From: Duo Zhang 
> > > Reply-To: "d...@hbase.apache.org" 
> > > Date: Monday, December 9, 2019 at 10:47 AM
> > > To: HBase Dev List , hbase-user <
> > > user@hbase.apache.org>
> > > Subject: [ANNOUNCE] Please welcome Guangxu Cheng the HBase PMC
> > >
> > > On behalf of the Apache HBase PMC I am pleased to announce that Guangxu
> > > Cheng has accepted our invitation to become a PMC member on the Apache
> > > HBase project. We appreciate Guangxu Cheng stepping up to take more
> > > responsibility in the HBase project.
> > >
> > > Please join me in welcoming Guangxu Cheng to the HBase PMC!
> > >
> > >
> >
>

Re: [ANNOUNCE] Please welcome Wellington Chevreuil to the Apache HBase PMC

[Zach York]

Welcome Wellington! Congratulations!

On Wed, Oct 23, 2019 at 1:19 PM Salvatore LaMendola (BLOOMBERG/ 731 LEX) <
slamendo...@bloomberg.net> wrote:

> Congrats Sakthi and Wellington!
>
> From: d...@hbase.apache.org At: 10/23/19 16:17:58To:  d...@hbase.apache.org
> Cc:  user@hbase.apache.org
> Subject: Re: [ANNOUNCE] Please welcome Wellington Chevreuil to the Apache
> HBase PMC
>
> Congrats Wellington!
>
> Sakthi
>
> On Wed, Oct 23, 2019 at 1:16 PM Sean Busbey  wrote:
>
> > On behalf of the Apache HBase PMC I am pleased to announce that
> > Wellington Chevreuil has accepted our invitation to become a PMC member
> on
> > the
> > HBase project. We appreciate Wellington stepping up to take more
> > responsibility in the HBase project.
> >
> > Please join me in welcoming Wellington 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.
> >
>
>
>

Re: [Announce] 张铎 (Duo Zhang) is Apache HBase PMC chair

[Zach York]

Congratulations Duo! Thanks for offering to take on the additional work!

On Fri, Jul 19, 2019 at 10:34 AM Stack  wrote:

> Thank you Misty for your years of service (FYI, for non-PMCers, the reports
> Misty wrote to the Apache Board on our behalf were repeatedly called out
> for their quality and thoughtfulness).
>
> Duo Zhang, thank you for taking on the mantle.
>
> S
>
> On Thu, Jul 18, 2019 at 10:46 AM Misty Linville  wrote:
>
> > Each Apache project has a project management committee (PMC) that
> oversees
> > governance of the project, votes on new committers and PMC members, and
> > ensures that the software we produce adheres to the standards of the
> > Foundation. One of the roles on the PMC is the PMC chair. The PMC chair
> > represents the project as a Vice President of the Foundation and
> > communicates to the board about the project's health, once per quarter
> and
> > at other times as needed.
> >
> > It's been my honor to serve as your PMC chair since 2017, when I took
> over
> > from Andrew Purtell. I've decided to step back from my volunteer ASF
> > activities to leave room in my life for other things. The HBase PMC
> > nominated Duo for this role, and Duo has kindly agreed! The board passed
> > this resolution in its meeting yesterday[1] and it is already
> official[2].
> > Congratulations, Duo, and thank you for continuing to honor the project
> > with your dedication.
> >
> > Misty
> >
> > [1] The minutes have not yet posted at the time of this email, but will
> be
> > available at http://www.apache.org/foundation/records/minutes/2019/.
> > [2] https://www.apache.org/foundation/#who-runs-the-asf
> >
>

Re: Thank you Misty

[Zach York]

Thank you for all you have done as our Chair, Misty! Best of luck!

On Thu, Jul 18, 2019 at 10:54 AM Andrew Purtell  wrote:

> Thank you for serving as our Chair, Misty. Your reports were some of the
> best I've ever seen in my ten or so years at the ASF. Best of luck to you
> and yours in your future endeavors.
>
> On Thu, Jul 18, 2019 at 10:46 AM Misty Linville  wrote:
>
> > It's been my honor to serve as your PMC chair since 2017, when I took
> over
> > from Andrew Purtell. I've decided to step back from my volunteer ASF
> > activities to leave room in my life for other things.
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

Re: [ANNOUNCE] Please welcome Peter Somogyi to the HBase PMC

[Zach York]

Congrats Peter!

On Tue, Jan 22, 2019 at 11:04 AM Sergey Shelukhin
 wrote:

> Congrats!
>
> -Original Message-
> From: Abhishek Singh Chouhan 
> Sent: Tuesday, January 22, 2019 10:52 AM
> To: d...@hbase.apache.org
> Cc: Hbase-User 
> Subject: Re: [ANNOUNCE] Please welcome Peter Somogyi to the HBase PMC
>
> Congrats Peter!
>
> On Mon, Jan 21, 2019 at 10:19 PM ramkrishna vasudevan <
> ramkrishna.s.vasude...@gmail.com> wrote:
>
> > Congratulations Peter.
> >
> > On Tue, Jan 22, 2019 at 11:48 AM Tamas Penzes
> >  > >
> > wrote:
> >
> > > Congrats Peter!
> > >
> > > On Tue, Jan 22, 2019, 02:36 Duo Zhang  > >
> > > > On behalf of the Apache HBase PMC I am pleased to announce that
> > > > Peter Somogyi has accepted our invitation to become a PMC member
> > > > on the Apache HBase project.
> > > > We appreciate Peter stepping up to take more responsibility in the
> > HBase
> > > > project.
> > > >
> > > > Please join me in welcoming Peter to the HBase PMC!
> > > >
> > >
> >
>

Re: Does Dropping the Source HBase Table Affect Its Snapshots and Cloned Tables from Snapshots?

[Zach York]

Anil is right. Dropping/modifying source tables should not affect
snapshots/cloned tables. If a source table is dropped, HBase will retain
the HFiles referenced by the snapshot in the archive directory. Any HFile
referred to by a table or snapshot will not be deleted by the
HFileCleaner. Only when that snapshot/cloned table is deleted/dropped will
the HFiles be eligible for deletion.

On Wed, Nov 28, 2018 at 7:21 PM Anil Gupta  wrote:

> Cloned table and snapshots should not have any impact if you drop source
> table.
>
> Sent from my iPhone
>
> > On Nov 28, 2018, at 5:23 PM, William Shen 
> wrote:
> >
> > Hi,
> >
> > I understand that changes made to the tables cloned using snapshot will
> not
> > affect the snapshot nor the source data table the snapshot is based on.
> > However, I could not find information on whether or not a snapshot or a
> > cloned table will be affected by the source table getting dropped. Can
> > someone chime in on the HBase behavior in this case?
> >
> > Thank you!
>

Re: Any way to avoid HBASE-21069?

[Zach York]

Hey Jacob,

Sorry you hit this issue. Yes HBASE-20723 introduced this bug and it is
fixed in HBASE-20734.

As for on EMR, emr-5.18.0 contains HBASE-20734 and this bug is not present
there. Please try upgrading to emr-5.18.0 to avoid the error.

Thanks,
Zach

On Mon, Nov 26, 2018 at 12:39 PM LeBlanc, Jacob <
jacob.lebl...@microfocus.com> wrote:

> Hi,
>
> We've recently upgraded our production clusters to 1.4.6. We have jobs
> periodically run that take snapshots of some of our hbase tables and these
> jobs seem to be running into
> https://issues.apache.org/jira/browse/HBASE-21069. I understand there was
> a missing null check, but in the bug I don't really see any explanation of
> how the null occurs in the first place. For those of us running 1.4.6, is
> there anything we can do to avoid hitting the bug?
>
> This problem is made worse because we are running a cluster in AWS EMR,
> meaning our WAL is on a different filesystem (HDFS) and the hbase root
> directory (EMRFS), and we are hitting some sort of issue where sometimes
> the master gets stuck while splitting a WAL from the crashed region server:
>
> 2018-11-20 12:01:58,599 ERROR [split-log-closeStream-2] wal.WALSplitter:
> Couldn't rename
> s3://cmx-emr-hbase-us-west-2-oregon/hbase/data/default/upload_metadata_v2/3f98fcda5f711b29af28e9613d4b833b/recovered.edits/00165359708-ip-172-20-113-197.us-west-2.compute.internal%2C16020%2C1542620776146.1542673338055.temp
> to
> s3://cmx-emr-hbase-us-west-2-oregon/hbase/data/default/upload_metadata_v2/3f98fcda5f711b29af28e9613d4b833b/recovered.edits/00165359720
> java.io.IOException: Cannot get log reader
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:365)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:277)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:265)
> at
> org.apache.hadoop.hbase.wal.WALSplitter$LogRecoveredEditsOutputSink.deleteOneWithFewerEntries(WALSplitter.java:1363)
> at
> org.apache.hadoop.hbase.wal.WALSplitter$LogRecoveredEditsOutputSink.closeWriter(WALSplitter.java:1496)
> at
> org.apache.hadoop.hbase.wal.WALSplitter$LogRecoveredEditsOutputSink$2.call(WALSplitter.java:1448)
> at
> org.apache.hadoop.hbase.wal.WALSplitter$LogRecoveredEditsOutputSink$2.call(WALSplitter.java:1445)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: Wrong FS:
> s3://cmx-emr-hbase-us-west-2-oregon/hbase/data/default/upload_metadata_v2/3f98fcda5f711b29af28e9613d4b833b/recovered.edits/00165359720,
> expected: hdfs://ip-172-20-113-83.us-west-2.compute.internal:8020
> at
> org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:669)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:214)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$4.doCall(DistributedFileSystem.java:329)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$4.doCall(DistributedFileSystem.java:325)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:337)
> at
> org.apache.hadoop.fs.FileSystem.open(FileSystem.java:790)
> at
> org.apache.hadoop.hbase.wal.WALFactory.createReader(WALFactory.java:303)
> ... 12 more
>
> It seems like https://issues.apache.org/jira/browse/HBASE-20723 did not
> hit all use cases. My understanding is that in 1.4.8 the recovered edits
> are collocated with the WAL so this will no longer be an issue (
> https://issues.apache.org/jira/browse/HBASE-20734) but AWS has yet to
> release an EMR with 1.4.8 so this is causing us pain right now when we hit
> this situation (it doesn't seem to happen every time a region server
> crashes - only twice so far).
>
> Unfortunately because we are running an AWS EMR cluster, so we can't
> really just patch the region servers ourselves. We have the option of
> upgrading to 1.4.7 to get the fix for HBASE-21069,  but that will take us a
> little time to test, release, and schedule downtime for our application so
> any mitigating steps we could take in the meantime would be appreciated.
>
> Thanks,
>
> --Jacob LeBlanc
>
>
>

Re: [ANNOUNCE] New HBase committer Jingyun Tian

[Zach York]

Congratulations, Jingyun! Welcome!

On Tue, Nov 13, 2018 at 10:59 AM Peter Somogyi  wrote:

> Congratulations Jingyun!
>
> On Tue, Nov 13, 2018 at 8:54 AM 张铎(Duo Zhang) 
> wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that Jingyun
> > Tian has accepted the PMC's invitation to become a committer on the
> > project. We appreciate all of Jingyun's generous contributions thus far
> and
> > look forward to his continued involvement.
> >
> > Congratulations and welcome, Jingyun!
> >
>

Re: HA master on EMR

[Zach York]

Hey Austin,

It sounds like you are asking about read availability in the case where a
primary cluster becomes unhealthy?

In that case, you should look at the HBase on S3 Read Replica clusters
feature[1][2]. This allows for High availability reads if the primary
cluster becomes unhealthy.

Let me know if I misinterpreted your ask!

Thanks,
Zach

[1]
https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hbase-s3.html#emr-hbase-s3-read-replica
[2]
https://aws.amazon.com/blogs/big-data/setting-up-read-replica-clusters-with-hbase-on-amazon-s3/


> -- Forwarded message -
>> From: Austin Heyne 
>> Date: Thu, Aug 30, 2018 at 8:30 AM
>> Subject: HA master on EMR
>> To: 
>>
>>
>> HBase on EMR is fairly reliable but is still subject to hardware
>> failures (which has happened to me before). Is there a best practice for
>> adding backup masters to an EMR cluster?
>>
>> I know this isn't technically a supported feature from AWS but we're
>> already heavily invested into HBase on EMR and would like to investigate
>> options on mitigating the risk of a master failure. In EMR if the master
>> dies the entire cluster is terminated so we need fail over for HBase,
>> Hadoop/HDFS and Zookeeper. The one idea that I've had is to create a
>> second (or third) EMR cluster with its HBase, Zookeeper and Hadoop/HDFS
>> configuration pointed to the primary cluster. This would in effect add
>> the RegionServers and Datanodes to the primary cluster. I know that
>> loosing 1/3 to 1/2 of your Datanodes would most likely mean you would
>> loose some WALs but re-ingesting the last days worth of data is
>> acceptable trade off for us in exchange for not having downtime.
>>
>> I realize this is a slightly crazy idea and using something like
>> Kubernetes is the 'correct' solution but I have to work with what we
>> have and mitigate possible issues. My question is are there any big
>> issues that anyone would foresee us having with this idea?
>>
>> Thanks for the feedback,
>> Austin
>>
>>

Re: [ANNOUNCE] New HBase committer Zach York

[Zach York]

Thanks everyone!

I am excited to continue my work in HBase!

Thanks,
Zach

On Thu, Mar 8, 2018 at 9:03 AM, ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:

> Congratulations Zach !!!
>
> On Thu, Mar 8, 2018 at 11:03 AM, Yu Li <car...@gmail.com> wrote:
>
> > Congratulations, Zach!
> >
> > Best Regards,
> > Yu
> >
> > On 8 March 2018 at 06:13, Mike Drob <md...@apache.org> wrote:
> >
> > > Congratulations, Zach!
> > >
> > > On Wed, Mar 7, 2018 at 4:03 PM, Andrew Purtell <apurt...@apache.org>
> > > wrote:
> > >
> > > > Congratulations and welcome Zach!
> > > >
> > > >
> > > > On Wed, Mar 7, 2018 at 8:27 AM, Sean Busbey <bus...@apache.org>
> wrote:
> > > >
> > > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Zach
> > > > > York has accepted the PMC's invitation to become a committer on the
> > > > > project.
> > > > >
> > > > > We appreciate all of Zach's great work thus far and look forward to
> > > > > continued involvement.
> > > > >
> > > > > Please join me in congratulating Zach!
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrew
> > > >
> > > > Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > > > decrepit hands
> > > >- A23, Crosstalk
> > > >
> > >
> >
>

Re: Please congratulate our new PMC Chair Misty Stanley-Jones

[Zach York]

Congrats Misty!

On Thu, Sep 21, 2017 at 12:11 PM, Stack  wrote:

> Misty!
>
> On Thu, Sep 21, 2017 at 12:08 PM, Andrew Purtell 
> wrote:
>
> > At today's meeting of the Board, Special Resolution B changing the HBase
> > project Chair to Misty Stanley-Jones was passed unanimously.
> >
> > Please join me in congratulating Misty on her new role!
> >
> > ​(If you need any help or advice please don't hesitate to ping me, Misty,
> > but I suspect you'll do just fine and won't need it.)​
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>