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

[宾莉金（binlijin）]

Congratulations!

Tao Li  于2023年10月18日周三 10:02写道：

> Congratulations!!!
>
> Georry Huang  于2023年10月18日周三 09:49写道：
>
> > Congratulations!
> >
> > Xiaolin Ha  于2023年10月18日周三 09:43写道：
> >
> > > Congratulations, Bryan! Impressed and well deserved.
> > >
> > > Duo Zhang  于2023年10月17日周二 09:32写道：
> > >
> > > > 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！
> > > >
> > >
> >
>


-- 
*Best Regards,*
 lijin bin

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

[宾莉金（binlijin）]

Congratulations and welcome!

张铎(Duo Zhang)  于2023年9月15日周五 17:08写道：

> 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 项目
> 做出的贡献，并期待他在未来继续承担更多的责任。
>
> 欢迎阮辉！
>


-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New HBase Committer Liangjun He

[宾莉金（binlijin）]

Congratulations!

张铎(Duo Zhang)  于2022年12月3日周六 22:28写道：

> Congratulations!
>
> Yu Li  于2022年12月3日周六 21:51写道：
> >
> > 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
>


-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New HBase Committer Zheng Wang(王正)

[宾莉金（binlijin）]

Congratulations and welcome!

张铎(Duo Zhang)  于2020年9月24日周四 上午10:24写道：

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


-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] Please welcome Lijin Bin to the HBase PMC

[宾莉金（binlijin）]

Thanks everybody. It’s an honor to join the PMC and I’ll try to do my best
to help the project and the community.

Jan Hentschel  于2020年5月26日周二 上午1:37写道：

> Congratulations and welcome!
>
> From: Guanghao Zhang 
> Reply-To: "dev@hbase.apache.org" 
> Date: Monday, May 25, 2020 at 4:40 PM
> To: HBase Dev List , Hbase-User <
> u...@hbase.apache.org>
> Subject: [ANNOUNCE] Please welcome Lijin Bin to the HBase PMC
>
> On behalf of the Apache HBase PMC I am pleased to announce that Lijin Bin
> has accepted our invitation to become a PMC member on the Apache HBase
> project. We appreciate Lijin Bin stepping up to take more responsibility in
> the HBase project.
>
> Please join me in welcoming Lijin Bin to the HBase PMC!
>
>

-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New HBase committer Bharath Vissapragada

[宾莉金（binlijin）]

Congratulations and welcome!

Jan Hentschel  于2020年2月6日周四 下午4:12写道：

> Congratulations and welcome!
>
> From: Pankaj kr 
> Reply-To: "u...@hbase.apache.org" 
> Date: Thursday, February 6, 2020 at 6:23 AM
> To: "u...@hbase.apache.org" , HBase Dev List <
> dev@hbase.apache.org>
> Subject: RE: [ANNOUNCE] New HBase committer Bharath Vissapragada
>
> Congratulations Bharath
>
> Regards,
> Pankaj
>
>
> -Original Message-
> From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com]
> Sent: 06 February 2020 10:49
> To: HBase Dev List mailto:dev@hbase.apache.org>>
> Cc: hbase-user mailto:u...@hbase.apache.org>>
> Subject: Re: [ANNOUNCE] New HBase committer Bharath Vissapragada
>
> Congratulations!
>
> Sukumar Maddineni  smaddin...@salesforce.com.invalid>> 于2020年2月6日周四
> 下午12:58写道：
>
> Congrats Bharat...
>
> --
> Sukumar
>
> On Wed, Feb 5, 2020 at 8:17 PM Geoffrey Jacoby  gjac...@apache.org>> wrote:
>
> > Congratulations, Bharath!
> >
> > On Wed, Feb 5, 2020 at 7:41 PM Viraj Jasani  >
> > wrote:
> >
> > > 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
> > >
> >
>
>
> --
>
>  http://smart.salesforce.com/sig/smaddineni/us_mb/default/link.html>>
>
>
>

-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New HBase committer Viraj Jasani

[宾莉金（binlijin）]

Welcome and Congratulations, Viraj!

张铎(Duo Zhang)  于2019年12月30日周一 下午1:18写道：

> Congratulations!
>
> 李响  于2019年12月30日周一 上午10:12写道：
>
> >- Congratulations and warmly welcome \^o^/
> >
> >
> > On Sun, Dec 29, 2019 at 2:14 AM Jan Hentschel <
> > jan.hentsc...@ultratendency.com> wrote:
> >
> > > Congrats and welcome, Viraj! Well deserved.
> > >
> > > From: Peter Somogyi 
> > > Reply-To: "dev@hbase.apache.org" 
> > > Date: Friday, December 27, 2019 at 2:02 PM
> > > To: HBase Dev List , hbase-user <
> > > u...@hbase.apache.org>
> > > Subject: [ANNOUNCE] New HBase committer Viraj Jasani
> > >
> > > 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!
> > >
> > >
> >
> > --
> >
> >李响 Xiang Li
> >
> > 手机 cellphone ：+86-136-8113-8972
> > 邮件 e-mail  ：wate...@gmail.com
> >
>


-- 
*Best Regards,*
 lijin bin

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

[宾莉金（binlijin）]

Congratulations!

Duo Zhang  于2019年12月9日周一 下午5:47写道：

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


-- 
*Best Regards,*
 lijin bin

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

[宾莉金（binlijin）]

Congratulations Duo!  and thanks Misty.

Anoop Sam John  于2019年7月21日周日 上午9:26写道：

> Congrats Duo.
>
> Thanks Misty for your great work as the PMC chair.
>
> Anoop
>
> On Sat, Jul 20, 2019 at 12:07 AM Xu Cang  wrote:
>
> > Thank you Misty!
> > Congratulations Duo, thanks for taking extra work!
> >
> > On Fri, Jul 19, 2019 at 11:23 AM Zach York  >
> > wrote:
> >
> > > 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
> > > > >
> > > >
> > >
> >
>


-- 
*Best Regards,*
 lijin bin

Re: [VOTE] The first HBase 1.4.3 release candidate (RC0) is available

[宾莉金（binlijin）]

+1 non-binding


- Built from source: ok (8u162)

- RAT check: ok (8u162)

- Unit tests pass: ok (8u66)

- Loaded 1M rows with LTT: ok (8u162), all keys verified, latency and logs

looks good

- Shell commands: ok (8u162), ran DDL/flush/compact/split commands,

everything looks good

- Web UI: OK

2018-03-27 3:55 GMT+08:00 Umesh Agashe :

> +1 non-binding
>
> download src & bin tar ball   - OK
> signatures & sums- OK
> build from source (openjdk version "1.8.0_151")  - OK
> rat check   -
> OK
> start local instance from bin & CRUD from shell  - OK
> LTT write, read1 million rows, 2 cols/row  - OK
> check logs - OK
>
>
> On Mon, Mar 26, 2018 at 9:38 AM, Artem Ervits 
> wrote:
>
> > the only thing I did was
> > start from bin tarball
> > ran some shell commands
> > some java
> > then took snapshot
> > dropped the table
> > restored from snapshot
> > more shell commands
> > stopped hbase
> > built from source and installed
> > that's pretty much where I saw the error in the UI
> >
> > On Mon, Mar 26, 2018 at 12:24 PM, Andrew Purtell <
> andrew.purt...@gmail.com
> > >
> > wrote:
> >
> > > Thanks for testing the RC!
> > >
> > > Can you say more about the circumstances that lead to the
> > > CorruptHFileException?
> > >
> > >
> > > > On Mar 26, 2018, at 9:22 AM, Artem Ervits 
> > wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > signatures:
> > > >  src: OK
> > > >  bin: OK
> > > > sha512:
> > > >  src: OK
> > > >  bin: OK
> > > >
> > > > hbase shell: OK
> > > > logs: OK
> > > >
> > > > Hadoop Pseudo-distrbibuted: 2.7.5
> > > > Java 1.8.0_161 1M rows - 1.4.2 client: OK
> > > > HBase PE: OK
> > > >
> > > > Source Release:
> > > >
> > > > Build and install: OK
> > > > tests: OK
> > > >  ran tests and still encounterederrors on hbase-server for
> > > > TestSpnegoHttpServer
> > > >
> > > > HBase UI: NOK
> > > >  splits/merges OK
> > > >  see this for the first timed
> > > >  org.apache.hadoop.hbase.io.hfile.CorruptHFileException: Problem
> > reading
> > > > HFile Trailer from file hdfs://
> > > > hadoop.example.com:9000/apps/hbase/data/default/table1/
> > > 23fb9fe7c999be282e1bbb86d6cdb999/cf/table1=
> > 23fb9fe7c999be282e1bbb86d6cdb9
> > > 99-3b61a7574888488b8e35b64b3fa15f2f
> > > >
> > > >
> > > > On Mon, Mar 26, 2018 at 8:48 AM, Balazs Meszaros <
> > > > balazs.mesza...@cloudera.com> wrote:
> > > >
> > > >> +1
> > > >>
> > > >> - built from source: OK
> > > >> - unit tests passed: OK
> > > >> - rat check: OK
> > > >> - LTT with 1M rows: OK
> > > >> - ran basic shell commands: OK
> > > >> - web UI: OK
> > > >>
> > > >>> On Sat, Mar 24, 2018 at 4:37 AM, Ted Yu 
> wrote:
> > > >>>
> > > >>> +1
> > > >>>
> > > >>> Ran test suite with Java 1.8.0_151 - passed
> > > >>> Ran RAT check - passed
> > > >>>
> > > >>> LoadTestTool loaded 1M rows
> > > >>>
> > > >>> On Fri, Mar 23, 2018 at 5:09 PM, Andrew Purtell <
> apurt...@apache.org
> > >
> > > >>> wrote:
> > > >>>
> > >  The first HBase 1.4.3 release candidate (RC0) is available for
> > > download
> > > >>> at
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.3RC0/ and
> > > Maven
> > >  artifacts are available in the temporary repository
> > >  https://repository.apache.org/content/repositories/
> > > >> orgapachehbase-1207/
> > > >>> .
> > > 
> > >  The git tag corresponding to the candidate is '1.4.3RC0'
> > (172373d1f0).
> > > 
> > >  A detailed source and binary compatibility report for this release
> > is
> > >  available for your review at
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.3RC0/
> > >  compat-check-report.html
> > >  .
> > > 
> > >  A list of the 36 issues resolved in this release can be found at
> > >  https://s.apache.org/FM08 .
> > > 
> > >  Please try out the candidate and vote +1/0/-1.
> > > 
> > >  This vote will be open for at least 72 hours. Unless objection I
> > will
> > > >> try
> > >  to close it Friday March 30, 2018 if we have sufficient votes.
> > > 
> > >  Prior to making this announcement I made the following preflight
> > > >> checks:
> > > 
> > > RAT check passes (7u80)
> > > Unit test suite passes (7u80)
> > > LTT load 1M rows with 100% verification and 20% updates (8u152)
> > > ITBLL Loop 1 1B rows (8u152)
> > > 
> > > 
> > >  --
> > >  Best regards,
> > >  Andrew
> > > 
> > > >>>
> > > >>
> > >
> >
>



-- 
*Best Regards,*
 lijin bin

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

[宾莉金（binlijin）]

HBASE-19338 has committed, do you want to update the master branch and test
it again?

2017-11-29 10:32 GMT+08:00 张铎(Duo Zhang) :

> And one thing may effect performance is that, now we rely on
> CompletableFuture more and more in our code base, but at least before
> jdk8u131 there is a performance regression for CompletableFuture. So
> consider moving to the newest jdk if you are still on an older version.
>
> Thanks.
>
> 2017-11-29 3:35 GMT+08:00 Mike Drob :
>
> > Ted,
> >
> > To clarify, I'm talking about a hypothetical bugfix that impacted
> > performance, not to imply that I know of a specific such change.
> >
> > I've seen it often enough before that performance is blazing fast at the
> > expense of accuracy and people are surprised when correctness takes
> longer.
> >
> >
> > Mike
> >
> > On Tue, Nov 28, 2017 at 1:01 PM, Ted Yu  wrote:
> >
> > > Mike:
> > > Which JIRA was the important bug-fix ?
> > >
> > > Thanks
> > >
> > > On Tue, Nov 28, 2017 at 9:16 AM, Mike Drob  wrote:
> > >
> > > > Eshcar - do you have time to try the other alpha releases and see
> where
> > > > exactly we introduced the regressions?
> > > >
> > > > Also, I'm worried that the performance regression may be related to
> an
> > > > important bug-fix, where before we may have had fast writes but also
> > > risked
> > > > incorrect behavior somehow.
> > > >
> > > > Mike
> > > >
> > > > On Tue, Nov 28, 2017 at 2:48 AM, Eshcar Hillel
>  > >
> > > > wrote:
> > > >
> > > > > I agree, so will wait till we focus on performance.
> > > > > Just one more update, I also ran the same experiment (write-only)
> > with
> > > > > banch-2 beta-1.Here is a summary of the throughput I see in each
> > > > tag/branch:
> > > > > ---  | BASIC | NONE  |
> > > > > ---2-alpha-1| 110K   | 80K |
> > > > > 2-beta-1 |  81K| 62K |
> > > > > master| 60K | 55K |---
> > > > > This means there are multiple sources for the regression.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Saturday, November 25, 2017, 7:44:01 AM GMT+2, 张铎(Duo
> Zhang) <
> > > > > palomino...@gmail.com> wrote:
> > > > >
> > > > >  I think first we need a release plan on when we will begin to
> focus
> > on
> > > > the
> > > > > performance issue?
> > > > >
> > > > > I do not think it is a good time to focus on performance issue now
> as
> > > we
> > > > > haven’t stabilized our build yet. The performance regression may
> come
> > > > back
> > > > > again after some bug fixes and maybe we use a wrong way to increase
> > > > > performance and finally we find that it is just a bug...
> > > > >
> > > > > Of course I do not mean we can not do any performance related
> issues
> > > now,
> > > > > for example, HBASE-19338 is a good catch and can be fixed right
> now.
> > > > >
> > > > > And also, for AsyncFSWAL and in memory compaction, we need to
> > consider
> > > > the
> > > > > performance right now as they are born for performance, but let’s
> > focus
> > > > on
> > > > > the comparison to other policies, not a previous release so we can
> > find
> > > > the
> > > > > correct things to fix.
> > > > >
> > > > > Of course, if there is a big performance downgrading comparing to
> the
> > > > > previous release and we find it then we should tell others, just
> like
> > > > this
> > > > > email. An earlier notification is always welcomed.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > Stack 于2017年11月25日 周六13:22写道：
> > > > >
> > > > > > On Thu, Nov 23, 2017 at 7:35 AM, Eshcar Hillel
> > >  > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Happy Thanksgiving all,
> > > > > > >
> > > > > >
> > > > > > And to you Eshcar.
> > > > > >
> > > > > >
> > > > > >
> > > > > > > In recent benchmarks I ran in HBASE-18294 I discovered major
> > > > > performance
> > > > > > > degradation of master code w.r.t 2-alpha-1 code.I am running
> > > > write-only
> > > > > > > workload (similar to the one reported in HBASE-16417). I am
> using
> > > the
> > > > > > same
> > > > > > > hardware and same configuration settings (specifically, I
> testes
> > > both
> > > > > > basic
> > > > > > > memstore compaction with optimal parameters, and no memsore
> > > > > > > compaction).While in 2-alpha-1 code I see throughput of
> ~110Kops
> > > for
> > > > > > basic
> > > > > > > compaction and ~80Kops for no compaction, in the master code I
> > get
> > > > only
> > > > > > > 60Kops and 55Kops, respectively. *This is almost 50% reduction
> in
> > > > > > > performance*.
> > > > > > > (1) Did anyone else noticed such degradation?(2) Do we have any
> > > > > > systematic
> > > > > > > automatic/semi-automatic method to track the sources of this
> > > > > performance
> > > > > > > issue?
> > > > > > > Thanks,Eshcar
> > > > > > >
> > > > > >
> > > > > >
> > 

Re: [DISCUSS] Should flush decisions be made based on data size (key-value only) or based on heap size (including metadata overhead)?

[宾莉金（binlijin）]

I like to use the former, heap occupancy, so we not need to worry about the
OOM and FullGc，and change configuration to adapted to new policy.

2017-07-06 14:03 GMT+08:00 Stack :

> On Wed, Jul 5, 2017 at 9:59 PM, ramkrishna vasudevan <
> ramkrishna.s.vasude...@gmail.com> wrote:
>
> >
> > >>Sounds like we should be doing the former, heap occupancy
> > Stack, so do you mean we need to roll back this new change in trunk? The
> > background is https://issues.apache.org/jira/browse/HBASE-16747.
> >
> >
> I remember that issue. It seems good to me (as it did then) where we have
> the global tracking in RS of all data and overhead so we shouldn't OOME and
> we keep accounting of overhead and data distinct because now data can be
> onheap or offheap.
>
> We shouldn't be doing blocking updates -- not when there is probably loads
> of memory still available -- but that is a different (critical) issue.
> Sounds like current configs can 'surprise' -- see Yu Li note -- given the
> new accounting.
>
> Looks like I need to read HBASE-18294
>  to figure what the
> pivot/problem w/ the new policy is.
>
> Thanks,
> St.Ack
>
>
>
>
>
> > Regards
> > Ram
> >
> >
> > On Thu, Jul 6, 2017 at 8:40 AM, Yu Li  wrote:
> >
> > > We've also observed more blocking updates happening with the new policy
> > > (flush decision made on data size), but could work-around it by
> reducing
> > > the hbase.hregion.memstore.flush.size setting. The advantage of
> current
> > > policy is we could control the flushed file size more accurately, but
> > > meanwhile losing some "compatibility" (requires configuration updating
> > > during rolling upgrade).
> > >
> > > I'm not sure whether we should rollback, but if stick on current policy
> > > there should be more documents, metrics (monitoring heap/data occupancy
> > > separately) and log message refinements, etc. Attaching some of the
> logs
> > we
> > > observed, which is pretty confusing w/o knowing the details of
> > > implementation:
> > >
> > > 2017-07-03 16:11:54,724 INFO
> > >  [B.defaultRpcServer.handler=182,queue=11,port=16020]
> > > regionserver.MemStoreFlusher: Blocking updates on
> > > hadoop0528.et2.tbsite.net,16020,1497336978160:
> > > global memstore heapsize 7.2 G is >= than blocking 7.2 G size
> > > 2017-07-03 16:11:54,754 INFO
> > >  [B.defaultRpcServer.handler=186,queue=15,port=16020]
> > > regionserver.MemStoreFlusher: Blocking updates on
> > > hadoop0528.et2.tbsite.net,16020,1497336978160:
> > > global memstore heapsize 7.2 G is >= than blocking 7.2 G size
> > > 2017-07-03 16:11:57,571 INFO  [MemStoreFlusher.0]
> > > regionserver.MemStoreFlusher: Flush of region
> > > mainv7_main_result_c,1496,1499062935573.02adfa7cbdc606dce5b79a516e1649
> > 2a.
> > > due to global heap pressure. Total Memstore size=3.2 G, Region memstore
> > > size=331.4 M
> > > 2017-07-03 16:11:57,571 WARN
> > >  [B.defaultRpcServer.handler=49,queue=11,port=16020]
> > > regionserver.MemStoreFlusher: Memstore is above high water mark and
> block
> > > 2892ms
> > >
> > > Best Regards,
> > > Yu
> > >
> > > On 6 July 2017 at 00:56, Stack  wrote:
> > >
> > > > On Wed, Jul 5, 2017 at 6:30 AM, Eshcar Hillel
> > >  > > > >
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > > I opened a new Jira https://issues.apache.org/
> > jira/browse/HBASE-18294
> > > to
> > > > > discuss this question.
> > > > > Flush decisions are taken at the region level and also at the
> region
> > > > > server level - there is the question of when to trigger a flush and
> > > then
> > > > > which region/store to flush.Regions track both their data size
> > > (key-value
> > > > > size only) and their total heap occupancy (including index and
> > > additional
> > > > > metadata).One option (which was the past policy) is to trigger
> > flushes
> > > > and
> > > > > choose flush subjects based on regions heap size - this gives a
> > better
> > > > > estimation for sysadmin of how many regions can a RS carry.Another
> > > option
> > > > > (which is the current policy) is to look at the data size - this
> > gives
> > > a
> > > > > better estimation of the size of the files that are created by the
> > > flush.
> > > > >
> > > >
> > > >
> > > > Sounds like we should be doing the former, heap occupancy. An
> > > > OutOfMemoryException puts a nail in any benefit other accountings
> might
> > > > have.
> > > >
> > > > St.Ack
> > > >
> > > >
> > > >
> > > > > I see this is as critical to HBase performance and usability,
> namely
> > > > > meeting the user expectation from the system, hence I would like to
> > > hear
> > > > as
> > > > > many voices as possible.Please join the discussion in the Jira and
> > let
> > > us
> > > > > know what you think.
> > > > > Thanks,Eshcar
> > > > >
> > > > >
> > > >
> > >
> >
>



-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New Apache HBase committer Ashu Pachauri

[宾莉金（binlijin）]

Congratulations, Ashu !

2017-06-17 7:27 GMT+08:00 Gary Helmling :

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



-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] New HBase committer Allan Yang

[宾莉金（binlijin）]

Congratulations, Allan !

2017-06-09 11:49 GMT+08:00 Yu Li :

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



-- 
*Best Regards,*
 lijin bin

Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky

[宾莉金（binlijin）]

Congratulations!

2017-03-28 22:16 GMT+08:00 Kahlil Oppenheimer :

> Congrats Anastasia!
>
> On Tue, Mar 28, 2017 at 9:50 AM Nick Dimiduk  wrote:
>
> > Thank you for all your contributions Anastasia!
> >
> > On Mon, Mar 27, 2017 at 5:38 AM ramkrishna vasudevan <
> > ramkrishna.s.vasude...@gmail.com> wrote:
> >
> > > Hi All
> > >
> > > Welcome Anastasia Braginsky, one more female committer to HBase. She
> has
> > > been active now for a while with her Compacting memstore feature and
> she
> > > along with Eshcar have done lot of talks in various meetups and
> HBaseCon
> > on
> > > their feature.
> > >
> > > Welcome onboard and looking forward to work with you Anastasia !!!
> > >
> > > Regards
> > > Ram
> > >
> >
>



-- 
*Best Regards,*
 lijin bin