Re: [ANNOUNCE] New HBase Committer Liangjun He

Congrats and welcome ! On Tue, Dec 6, 2022 at 2:21 AM Andrew Purtell wrote: > Congratulations, and welcome! > > 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

Re: [VOTE] First release candidate for HBase 1.7.2 is available for download

+1 binding. Here are my test steps: 1. Download the source tarball, signature (.asc), and checksum (.sha512): OK 2. Import gpg keys: download KEYS and run gpg --import /path/to/downloaded/KEYS : OK 3. Verify the signature by running: - gpg --verify hbase-1.7.2-src.tar.gz.asc: OK - gpg

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download

+1 (binding) 1. Download the source tarball, signature (.asc), and checksum (.sha512): OK 2. Import gpg keys: download KEYS and run gpg --import /path/to/downloaded/KEYS : OK 3. Verify the signature by running: gpg --verify hbase-thirdparty-4.1.1-src.tar.gz.asc : OK 4. Verify the checksum by

Re: [DISCUSS]HBase2.1.0 is slower than HBase1.2.0

Hi Zheng wang. Hope this issue will be helpful for you. https://issues.apache.org/jira/browse/HBASE-21657 Thanks. On Tue, Jun 9, 2020 at 5:53 PM Anoop John wrote: > Thanks for the detailed analysis and update zheng wang. > >The code line below in StoreScanner.next() cost about 100ms in v2.1,

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

One of the most important issue for branch-2.3 is HBASE-21879, which means reading block offheap from fs to save GC. There's one remaining open issue which need to upgrade the Hadoop version to make the offheap reading really work, I will finish that issue in the next few days. BTW, I was

Re: [ANNOUNCE] New HBase committer Ankit Singhal

Congratulations Ankit. On Wed, Nov 13, 2019 at 9:57 AM Guangxu Cheng wrote: > Congratulations and welcome, Ankit! > > Toshihiro Suzuki 于2019年11月13日周三 上午6:46写道： > > > Congratulations! Ankit > > > > On Wed, Nov 13, 2019 at 6:56 AM Esteban Gutierrez > > wrote: > > > > > Congrats, Ankit! > > > --

Re: [DISCUSS] branch-1 versioning and the need for a 1.5.1

+1 Thanks Seen. On Sat, Nov 2, 2019 at 9:56 AM Andrew Purtell wrote: > +1 > > Sounds good Sean. > > As discussed earlier we should all feel free to bump the minor version on > branch-1 whenever a compatibility guideline requires it. > > If we ever need to make a 1.5.1 or 1.5.2 for a user who

Re: The fifth HBase 1.5.0 release candidate (RC4) is available

+1 (binding) Run the hbase-vote.sh under dev-support directory, the results are following: * Signature: ok * Checksum : ok * Rat check (1.8.0_221): ok - mvn clean apache-rat:check * Built from source (1.8.0_221): ok - mvn clean install -DskipTests * Unit tests pass

Re: [DISCUSS] Moving towards a branch-2 line that can get the 'stable' pointer.

> Let's gather a few stories on it working for folks in production and move the pointer then. Agree, XiaoMi is making parts of the online clusters upgrade to HBase2.2.x, I think Guanghao will share the practices some time later. Thanks. On Sun, Sep 15, 2019 at 12:09 AM Stack wrote: > On Fri,

Re: Documenting how to do cluster operations when things have gone wrong

Nice to see those, Yeah I think we need some ref-guide or cases to show hbase2.x admin how to fix their RIT regions or other problems. It's a very urgent task (based on feedback from some hbase2.x users). Thanks. On Sat, Sep 14, 2019 at 2:59 AM Sean Busbey wrote: > Hi folks! > > Was chatting

Re: [VOTE] The second HBase 2.2.1 release candidate (RC1) is available

Agree, give my +1 (binding). BTW Peter Somogyi also have commit the fix to related branches. Thanks. On Mon, Sep 9, 2019 at 5:40 PM 张铎(Duo Zhang) wrote: > Seems to be a UT issue? I do not think it is sufficient to sink an RC? > > OpenInx 于2019年9月9日周一 下午4:35写道： &g

Re: [VOTE] The second HBase 2.2.1 release candidate (RC1) is available

Seems the TestHRegionWithInMemoryFlush is always failed under my host, filed issue to address this: https://issues.apache.org/jira/browse/HBASE-22995 * Signature: ok * Checksum : ok * Rat check (1.8.0_202): ok - mvn clean apache-rat:check * Built from

Re: [VOTE] The second release candidate for hbase-2.0.6 is up and available for download

+1 (binding) The HBASE-22874 don't affect the 2.0.6, so it should be OK now. The vote result here under my host are: * Signature: ok * Checksum : ok * Rat check (1.8.0_202): ok - mvn clean apache-rat:check * Built from source (1.8.0_202): ok - mvn

Re: [VOTE] First release candidate for HBase 2.1.6 is available for download

See the previous failed UT, it says address already bind. And run the UT several times under a new host again, seems all works fine. So +1. On Sun, Aug 18, 2019 at 3:56 PM OpenInx wrote: > Let me try the TestJMXConnectorServer locally again, although it failed > now, it should not

Re: [VOTE] First release candidate for HBase 2.1.6 is available for download

Let me try the TestJMXConnectorServer locally again, although it failed now, it should not effect the rc vote. Give my +1, will take a look about that UT. On Sun, Aug 18, 2019 at 3:15 PM OpenInx wrote: > > * Signature: ok > * Checksum : ok > * Rat check (1.

Re: [VOTE] First release candidate for HBase 2.1.6 is available for download

* Signature: ok * Checksum : ok * Rat check (1.8.0_202): ok - mvn clean apache-rat:check * Built from source (1.8.0_202): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_202): failed - mvn test -P runAllTests The

Re: [NOTICE] Reid Chan has been added to the HBASE PMC!

Congrats Reid! On Sat, Aug 17, 2019 at 4:28 AM Esteban Gutierrez wrote: > Congrats, Reid! > > -- > Cloudera, Inc. > > > > On Fri, Aug 16, 2019 at 1:36 PM Andrew Purtell > wrote: > > > Congratulations, Reid! > > > > > > On Fri, Aug 16, 2019 at 10:30 AM Stack wrote: > > > > > The mighty Reid

Re: [ANNOUNCE] New HBase committer Tak-Lon (Stephen) Wu

Congratulations! Stephen. On Tue, Aug 6, 2019 at 10:30 AM Toshihiro Suzuki wrote: > Congratulations! Stephen > > On Tue, Aug 6, 2019 at 6:11 AM Xu Cang > wrote: > > > Congratulations and welcome Tak-Lon! > > > > On Mon, Aug 5, 2019 at 1:08 PM Zach York > > wrote: > > > > > Congratulations and

Re: Re: [ANNOUNCE] Please welcome Zheng Hu to the HBase PMC

I'm so glad to join the PMC, Apache HBase is a great open source project and the community is also very nice and friendly. In the comming days, will do more to make the project & community forward, also we need more work to attract people to enhance and expand the community: blog/post/book/talk

Re: [ANNOUNCE] new HBase committer Sakthi

Congratulations, Sakthi. On Thu, Aug 1, 2019 at 3:09 PM Jan Hentschel < jan.hentsc...@ultratendency.com> wrote: > Congrats Sakthi > > From: Reid Chan > Reply-To: "u...@hbase.apache.org" > Date: Thursday, August 1, 2019 at 9:04 AM > To: "u...@hbase.apache.org" , dev < > dev@hbase.apache.org> >

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

Congratulations Duo! and thanks Misty. On Fri, Jul 19, 2019 at 9:34 AM Guanghao Zhang wrote: > Congratulations! > > Duo Zhang 于2019年7月19日周五 上午9:33写道： > > > Thanks Misty for the great job you have done these years. > > > > And thanks all for trusting me. Will try my best. > > > > Jan Hentschel

Re: Backport pre/post Grant/Revoke events to branch-2.1

ch-2.1. Looks like it’s not, but I’m quite new to HBase and wanted to get confirmation. The branch-2.1 would like to accept the patches of bug fix as I said above. Thanks. On Mon, Jul 15, 2019 at 5:57 PM Andor Molnar wrote: > Hi OpenInx, > > I meant RegionObserver, but it doesn’t really mat

Re: Backport pre/post Grant/Revoke events to branch-2.1

Hi Andor: > to branch-2.1 to make pre/post Grant and Revoke events available in RegionObserver. I think you mean MasterObserver. This feature was contributed by our XiaoMi HBase team. we did not port those patches to branch-2.1 before because we thought the most priority of the branch at that

Re: Integration Test - and running them

Skipped: 0 On Thu, Jul 11, 2019 at 10:51 AM OpenInx wrote: > Hi Norbert Kalmar > > You mean run the test by the command: mvn test > -Dtest=IntegrationTestBigLinkedList ? > Then I think it should have some detail logs under your directory: > /hbase-it/target/surefire-reports &g

Re: Integration Test - and running them

Hi Norbert Kalmar You mean run the test by the command: mvn test -Dtest=IntegrationTestBigLinkedList ? Then I think it should have some detail logs under your directory: /hbase-it/target/surefire-reports Aslo there should be some logs under you hbase-it/target/MiniCluster-xxx directory... On

Re: Please help to review patch of the HDFS-14585 (backport Byte

statement valid, if you use Ozone API ? > > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature> > > On Thu, Jun 27, 2019 at 9:20 AM, OpenInx

Please help to review patch of the HDFS-14585 (backport ByteBuffer pread to branch-2.9)

Dear HDFS Team: I'm apache HBase member and working on HBASE-21879 [1]: it's a feature which help to optimize the HBase GC issues, we redesigned the HBase read(Scan/Get) path by reading HDFS block into offheap ByteBuffers and it had great performance improvement in our benchmark test [2]. While

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

Merged the HBASE-21879 back to master branch, Thanks all. On Sun, Jun 23, 2019 at 10:40 AM OpenInx wrote: > Now we have four +1 votes ( all binding). > Will wait a day before the merge, if no objections I will do the merge. > Thanks all for reviewing & checking. > > On Sat,

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

amkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > > > +1 to merge to master. Great job Zheng > > > > On Sat, Jun 22, 2019, 8:41 AM Guanghao Zhang wrote: > > > > > +1 for merge this to master. > > > > > > OpenInx 于2019年6月2

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

.9.3 in future. Thanks. On Wed, Jun 19, 2019 at 10:41 PM OpenInx wrote: > Thanks for your reviewing and flaky test checking, Duo. > Will file a separate issue to address your comment if necessary. > > Thanks. > > On Wed, Jun 19, 2019 at 9:55 PM 张铎(Duo Zhang) > wrote: > >

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

6月18日周二 下午9:48写道： > > > Good. Will take a look soon. > > > > OpenInx 于2019年6月18日周二 下午9:41写道： > > > >> > Could please open a PR, just like what I have done for HBASE-21512, so > >> that others could have a overall view on the modified code? > >>

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

ote: > The performance number is great. > > Could please open a PR, just like what I have done for HBASE-21512, so that > others could have a overall view on the modified code? > > Thanks. > > OpenInx 于2019年6月18日周二 下午6:58写道： > > > BTW, when testing this branch, we

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

?focusedCommentId=16866472=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16866472 Thanks. On Tue, Jun 18, 2019 at 12:05 PM OpenInx wrote: > The HBASE-21879 has lots of changes: 123 files changed, 5833 > insertions(+), 3015 deletions(-). > Currently we developed this is

Re: [VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

. Thanks for your suggestion, Guanghao ! On Tue, Jun 18, 2019 at 11:39 AM Guanghao Zhang wrote: > This is a improvement not a new feature? So backport to branch-2, too? > > OpenInx 于2019年6月17日周一 下午2:45写道： > > > Dear HBase dev: > > > > In HBASE-21879[1], we redesign

[VOTE] Merge branch HBASE-21879 (Reading HFile's Block to ByteBuffer directly) back to master.

Dear HBase dev: In HBASE-21879[1], we redesigned the offheap read path: read the HFileBlock from HDFS to pooled offheap ByteBuffers directly, while before HBASE-21879 we just read the HFileBlock to heap which would still lead to high GC pressure. After few months of development and testing, all

Re: [ANNOUNCE] New Committer: Wellington Chevreuil

Congratulations Wellington! On Sat, Jun 8, 2019 at 5:01 AM Xu Cang wrote: > Congrats Wellington and welcome! > > > On Fri, Jun 7, 2019 at 1:21 PM Sakthi wrote: > > > Hurray! Congrats Wellington. Well deserved one! > > > > Sakthi > > > > On Fri, Jun 7, 2019 at 12:58 PM Wei-Chiu Chuang > >

Re: Flame Graphs

There's also a doc here: http://hbase.apache.org/book.html#profiler Thanks. On Mon, Jun 3, 2019 at 9:25 PM OpenInx wrote: > Hi : > > In HBASE-21926, Andrew introduced the great profile tool (async-profiler > ) into our HBase. > It's very easy to use this: > 1. you need to d

Re: Flame Graphs

Hi : In HBASE-21926, Andrew introduced the great profile tool (async-profiler ) into our HBase. It's very easy to use this: 1. you need to download the binary of async-profier from here: https://github.com/jvm-profiling-tools/async-profiler 2. then you need to set a java option which point to

Re: [VOTE] The first HBase 2.1.5 release candidate (RC1) is available for test

+1 (non-binding) Run the hbase-vote.sh, looks good to me. * Signature: ok * Checksum : ok * Rat check (1.8.0_202): ok - mvn clean apache-rat:check * Built from source (1.8.0_202): ok - mvn clean install -DskipTests * Unit tests pass

Re: [ANNOUNCE] New HBase committer Yi Mei

Congratulations! On Fri, May 24, 2019 at 3:12 PM Guanghao Zhang wrote: > On behalf of the Apache HBase PMC, I am pleased to announce that Yi Mei has > accepted the PMC's invitation to become a committer on the project. We > appreciate all of Yi Mei's generous contributions thus far and look

Re: [ANNOUNCE] Please welcome Jan Hentschel to the Apache HBase PMC

Congratulation, Jan! Thanks for your work. On Thu, May 9, 2019 at 6:08 AM Artem Ervits wrote: > Well deserved Jan! > > On Wed, May 8, 2019, 5:37 PM Sean Busbey wrote: > > > On behalf of the Apache HBase PMC I am pleased to announce that Jan > > Hentschel has accepted our invitation to become a

Re: [DISCUSS] EOL 2.0 release line

I'v checked the issues in version 2.0.6 [1], seems no critial issues, so for me +1. 1. https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20AND%20fixVersion%20%3D%202.0.6 On Wed, Apr 24, 2019 at 8:37 PM Sean Busbey wrote: > Hi folks! > > Tomorrow will be a month since the 2.0.5

Re: [DISCUSS] switch from "Ammending-Author" to "Co-authored-by" in commit messages

+1, thanks Sean. On Wed, Apr 24, 2019 at 2:15 AM Josh Elser wrote: > sgtm. > > On 4/23/19 10:55 AM, Sean Busbey wrote: > > Hi Folks! > > > > We have an established practice of using a git commit message trailer > > of "Amending-Author" when there's multiple authors for a commit[1]. > > > > For

Re: Are we ready to accept PR commit from github?

gives us. I'll confirm by > checking how the two projects I know to have this set up (Hadoop and > Yetus). > > On Mon, Mar 25, 2019, 21:23 OpenInx wrote: > > > @stack boss, Can you see the settings also the jenkins config ? If so, > > mind you grant those permissions? >

Re: Are we ready to accept PR commit from github?

@stack boss, Can you see the settings also the jenkins config ? If so, mind you grant those permissions? On Tue, Mar 26, 2019 at 10:17 AM 张铎(Duo Zhang) wrote: > I can not see the settings tab on github either... > > OpenInx 于2019年3月26日周二 上午10:11写道： > >> So the current prob

Re: Are we ready to accept PR commit from github?

So the current problem is: github PR can not trigger hadoop QA ? I will take some time to let this work, but seems I've no setting permissions in github repo, also no permission to view the jenkins config. @Sean Busby, @Josh Elser @张铎(Duo Zhang) Could you help to grant those permission to me

Re: [VOTE] The second HBase 2.1.4 Release Candidate is available for download

(+1 non-Binding) 1. Checksums and signatures(both src and bin): OK 2. Rat Check: OK 3. Built from source: OK 4. Unit Tests: OK 5. Basic Shell commands: OK 6. Web UI: OK 7. LTT with 10^5 rows: OK Thanks stack. On Wed, Mar 20, 2019 at 10:44 PM Stack wrote: > Please vote on

Re: [DISCUSS] what's our biggest source of friction for getting new contributors going?

Good question, some points in my opinion: 1. The current workflow is quite complex compared to github PR workflow. For ex, creating a JIRA while new contributors has no permission to assign it to self ? Github PR will help a lot. 2. Long PR merge cycle, the hadoop QA take a long time,

Re: [DISCUSS] HBASE-14850 C++ client implementation

+1 for creating a new hbse-native-client project, about the compatibility, I think we can add an night test ? such as it'll clone the latest HBase repo and use the native client to request the HBase Minicluster. On Wed, Mar 13, 2019 at 3:54 PM Guanghao Zhang wrote: > Hi, all, we plan to pick

Re: [ANNOUNCE] New HBase committer Xu Cang

Congratulations! On Fri, Feb 8, 2019 at 7:42 PM 张铎(Duo Zhang) wrote: > Congratulations! > > Allan Yang 于2019年2月8日周五 下午7:40写道： > > > Congratulations, Xu! > > Best Regards > > Allan Yang > > > > > > Xu Cang 于2019年2月7日周四 上午3:06写道： > > > > > Thank you all! Looking forward to contributing more and

About the performance of In-Memory Compaction.

Hi Recently, I made some performance tests for evaluating DefaultMemstore and CompactintMemstore. *Performance when using the DefaultMemstore.* [image: image.png] *Performance when using the CompactingMemstore.* [image: image.png] We can see that the latency control of CompactingMemstore

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

Congrats Peter! You deserve it ! On Tue, Jan 22, 2019 at 9:44 AM Sakthi wrote: > Congrats Peter! > > Sakthi > > On Mon, Jan 21, 2019 at 5:36 PM Duo Zhang wrote: > > > On behalf of the Apache HBase PMC I am pleased to announce that Peter > > Somogyi > > has accepted our invitation to become a

Re: Did the branch-2.1 need the patch HBASE-21657 ?

e to start old HMaster again to > finish them first. > If we want to release 2.2.0, at least we need to document this out. > > > > > On Mon, Jan 14, 2019, 20:07 OpenInx > > > > bq. For me, I would say that let's start the 2.2.x release line soon? > So

Re: Did the branch-2.1 need the patch HBASE-21657 ?

bq. For me, I would say that let's start the 2.2.x release line soon? So user could benefit from the change after they upgrade to 2.2.x. Sound good. On Tue, Jan 15, 2019 at 11:05 AM OpenInx wrote: > b > > On Tue, Jan 15, 2019 at 10:54 AM 张铎(Duo Zhang) > wrote: > >>

Re: Did the branch-2.1 need the patch HBASE-21657 ?

b On Tue, Jan 15, 2019 at 10:54 AM 张铎(Duo Zhang) wrote: > For me, I would say that let's start the 2.2.x release line soon? So user > could benefit from the change after they upgrade to 2.2.x. > > OpenInx 于2019年1月15日周二 上午10:21写道： > > > Sorry, here is a typo. > &g

Re: Did the branch-2.1 need the patch HBASE-21657 ?

Sorry, here is a typo. > but not quite sure for branch-1 . Discussion are welcome (smile). but not quite sure for branch-2.1 On Tue, Jan 15, 2019 at 10:17 AM OpenInx wrote: > Hi: > > In HBASE-21657, I simplified the path of estimatedSerialiedSize() & > estimatedSerialiedSiz

Did the branch-2.1 need the patch HBASE-21657 ?

Hi: In HBASE-21657, I simplified the path of estimatedSerialiedSize() & estimatedSerialiedSizeOfCell() by moving the general getSerializedSize() and heapSize() from ExtendedCell to Cell interface. It's a incompatible change in some case, such as if the upstream user implemented their own Cells,

Re: [DISCUSS] EOL branch-1.3

> As mentioned in a few different DISCUSS threads, we have too many branches active and committers have limited bandwidth so stuff gets missed. Agreed, Some critial bugs , which need to commit to 8 branches now (branch-1.2/branch-1.3/branch-1.4/branch-1/branch-2/branch-2.1/branch-2.2/master). The

Re: Rolling 2.1.2 and 2.0.4

> Wondering if anyone has a bit of time to take a look at the flakeys? For2.1, they cause a fail every other time... Let me take a look. On Thu, Dec 6, 2018 at 1:56 PM Zach York wrote: > Do we have a process for deprecating releases with critical bugs? I'm not > sure this particular bug would

Re: The child procedure is scheduled in the reversed order in Procedure V2 Framework

ter HBASE-21375 > <https://issues.apache.org/jira/browse/HBASE-21375> checked in all 2.x > branch, the worker thread will execute every possible procedure in the > queue, so the front ones won't block, so this won't be a problem. > Best Regards > Allan Yang > > > OpenInx 于201

Re: [ANNOUNCE] Allan Yang joins the Apache HBase PMC

Congratulations, Allan! On Thu, Nov 29, 2018 at 6:58 AM Zach York wrote: > Congratulations and welcome Allan! > > > On Wed, Nov 28, 2018 at 10:21 AM Esteban Gutierrez > wrote: > > > Congratulations, Allan! > > > > -- > > Cloudera, Inc. > > > > > > > > On Wed, Nov 28, 2018 at 10:11 AM Yu Li

The child procedure is scheduled in the reversed order in Procedure V2 Framework

Hi : I read parts of the procedure v2 framework, and found that if a procedure has 3 added child procedure, then it's children will be schedued in the reversed order. Let me give an example. if a procedure A added 3 child procedure: B, C , D. a.addChildProcedure(B, C, D) The procedure

Re: [VOTE] First release candidate for HBase 1.2.9 is available

+1 (non-binding) - Checksums and signatures: OK - Basic shell command test: OK - Started binary in pseudo distributed mode: OK - WEB UI: OK - create table & put & delete & scan & list : OK - Build from source(jdk8u091): OK - mvn clean package -DskipTests - mvn clean install

Re: Re: [ANNOUNCE] New HBase committer Jingyun Tian

Congratulations Jingyun :) On Tue, Nov 13, 2018 at 5:47 PM Guanghao Zhang wrote: > Congratulations! > > Guangxu Cheng 于2018年11月13日周二 下午5:19写道： > > > Congratulations and welcome, Jingyun! > > > > Best Regards, > > Guangxu > > > > > > > > Tencent/Guangxu Cheng > > > > From: Nihal Jain > > Date:

Hadoop QA always says VM crash or System.exit called?

Hi All The latest successful Hadoop QA is https://builds.apache.org/job/PreCommit-HBASE-Build/14897, After that all jenkins build failed because of saying VM crash or System.exit called.. For example:

Re: [ANNOUNCE] Please welcome Zach York to the HBase PMC

Congratulations Zach! On Wed, Oct 17, 2018 at 8:14 PM ramkrishna vasudevan < ramkrishna.s.vasude...@gmail.com> wrote: > Congratulations Zach!!! > > On Wed, Oct 17, 2018 at 11:15 AM Yu Li wrote: > > > Congratulations and welcome, Zach! > > > > Best Regards, > > Yu > > > > > > On Wed, 17 Oct 2018

Re: [ANNOUNCE] New Committer: Toshihiro Suzuki

Congratulations and welcome ! On Wed, Aug 1, 2018 at 10:51 PM, Reid Chan wrote: > Congratulations and welcome, Toshihiro. > > > R.C > > > > > > From: Ted Yu > Sent: 01 August 2018 22:48:56 > To: dev@hbase.apache.org > Subject: Re: [ANNOUNCE] New

Re: HBase 1.4.6 RC next week

go into any patch releases 2.0.x > or 2.1.x either. I have updated fix versions accordingly to { 3.0.0, 2.2.0, > 1.5.0 } > > HBASE-20565 looks like review has completed and we are just waiting on a > patch for branch-1, which requires Java 7 compatible code. > > > > >

Re: HBase 1.4.6 RC next week

HBASE-20565 & HBASE-20151 are two bugs related to FilterList, I and Reid Chan have prepared patches for them. I think we can include those fix in 1.4.6. A quick review will help push this up... Thanks. On Fri, Jul 20, 2018 at 7:10 AM, Andrew Purtell wrote: > ​We have about 25 changes on

Re: [RESULT][VOTE] Merge branch HBASE-19064 back to master

+1. > >> > > >> > As the performance test shows that there is no performance downgrading > >> if > >> > we do not enable sync replication, and the feature basically works, I > >> think > >> > it is OK to merge it back to master branc

Re: [ANNOUNCE] New HBase committer Reid Chan

Congratulations and welcome ! On Tue, Jun 26, 2018 at 2:48 PM, 张铎(Duo Zhang) wrote: > Congratulations! > > 2018-06-26 14:44 GMT+08:00 Pankaj kr : > > > Congratulations Reid Chan..!! > > > > Regards, > > Pankaj Kumar > > Technical Project Leader > > Enterprise Intelligence, IT BU > > > > Huawei

Re: [VOTE] Merge branch HBASE-19064 back to master

Hi guys I've tested the write performance on both master branch and HBASE-19064 branch. Here's the JIRA [1]. The conclusion(Pasted from the comment): The QPS & AVG latency are similar when comparing the master branch with async replication and HBASE-19064 with async replication. BTW the QPS of

Re: [ANNOUNCE] New HBase committer Guangxu Cheng

Congratulations! On Mon, Jun 4, 2018 at 6:16 PM, ashish singhi wrote: > Congrats and Welcome! > > Regards, > Ashish > -Original Message- > From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com] > Sent: Monday, June 04, 2018 12:30 PM > To: HBase Dev List ; hbase-user < >

Re: [ANNOUNCE] HBaseConAsia 2018 CFP now open!

r.org/cfp/hbaseconasia-2018>* > [2] https://easychair.org/conferences/?conf=hbaseconasia2018 > [3] https://hbase.apache.org/hbaseconasia-2018/ > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: [ANNOUNCE] Please welcome Francis Liu to the HBase PMC

more > > > responsibility in the HBase project. He has been an active contributor > to > > > HBase for many years and recently took over responsibilities as branch > RM > > > for branch-1.3. > > > > > > Please join me in welcoming Franci

Re: [DISCUSS] A Problem When Start HBase Cluster Using Table Based Replication

t; > > > > 'region server' seems a bad smell to me. What's the advantage > > comparing > > > > to > > > > > zk? > > > > > > > > > > BTW, I believe that we only need the ReplicationPeerStorage to be > >

Re: [DISCUSS] A Problem When Start HBase Cluster Using Table Based Replication

; > BTW, I believe that we only need the ReplicationPeerStorage to be > > available when starting a region server, so we can keep this data in zk, > > and storage the queue related data to hbase:replication table? The > > replication related data is small so I think this is OK. >

[DISCUSS] A Problem When Start HBase Cluster Using Table Based Replication

Hi : (Paste from https://issues.apache.org/jira/browse/HBASE-20166? focusedCommentId=16399886=com.atlassian.jira. plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16399886) There's a really big problem here if we use table based replication to start a hbase cluster: For HMaster process,

Re: Re: [ANNOUNCE] Please welcome Mike Drob to the HBase PMC

e.apache.org to > >> let us know! > >> > >> - busbey > >> > > > > > > > >-- > >Best regards, > >Andrew > > > >Words like orphans lost among the crosstalk, meaning torn from truth's > >decrepit hands > > - A23, Crosstalk > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: 回复：Re: [ANNOUNCE] Please welcome Ashish Singhi to the HBase PMC

w! > >> > > >> > - busbey > >> > > >> > >> > >> > >> -- > >> Best regards, > >> Andrew > >> > >> Words like orphans lost among the crosstalk, meaning torn from truth's > >> decrepit hands > >>- A23, Crosstalk > >> > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: Re: [ANNOUNCE] Please welcome Guanghao Zhang to the HBase PMC

e.org to > >> > let us know! > >> > > >> > - busbey > >> > > >> > >> > >> > >> -- > >> Best regards, > >> Andrew > >> > >> Words like orphans lost among the crosstalk, meaning torn from truth's > >> decrepit hands > >>- A23, Crosstalk > >> > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: [ANNOUNCE] New HBase committer Peter Somogyi

gt; > > > > We appreciate all of Peter's great work thus far and look forward to > > > continued involvement. > > > > > > Please join me in congratulating Peter! > > > > > > > > > > > -- > > Best regards, > > Andrew

Re: [VOTE] Merge branch HBASE-19397 back to master and branch-2.

the work. > > > > > >>> > > > > > >>> The procedure will hold an exclusive lock on the peer id, so > now > > > > there > > > > > is > > > > > >>> no concurrent modifications on a single peer. > > > > > >>> > > > > > >>> And now it is guaranteed that once the procedure is done, the > > peer > > > > > >>> modification has already taken effect on all RSes. > > > > > >>> > > > > > >>> Abstracte a storage layer for replication peer/queue > manangement, > > > and > > > > > >>> refactored the upper layer to remove zk related > > > naming/code/comment. > > > > > >>> > > > > > >>> Add pre/postExecuteProcedures CP hooks to RegionServerObserver, > > and > > > > add > > > > > >>> permission check for executeProcedures method which requires > the > > > > caller > > > > > >>> to > > > > > >>> be system user or super user. > > > > > >>> > > > > > >>> On rolling upgrade: just do not do any replication peer > > > modifications > > > > > >>> during the rolling upgrading. There is no pb/layout changes on > > the > > > > > >>> peer/queue storage on zk. > > > > > >>> > > > > > >>> > > > > > >> And there are other benefits. > > > > > >> First, we have introduced a general procedure framework to send > > > tasks > > > > to > > > > > >> RS > > > > > >> and report the report back to Master. It can be used to > implement > > > > other > > > > > >> operations such as ACL change. > > > > > >> Second, zk is used as a external storage now since we do not > > depend > > > on > > > > > zk > > > > > >> watcher any more, it will be much easier to implement a 'table > > > based' > > > > > >> replication peer/queue storage. > > > > > >> > > > > > >> Please vote: > > > > > >> [+1] Agree > > > > > >> [-1] Disagree > > > > > >> [0] Neutral > > > > > >> > > > > > >> Thanks. > > > > > >> > > > > > >> > > > > > > > > > > > > > > > -- > > > > > > > > > > -- Appy > > > > > > > > > > > > > > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands >- A23, Crosstalk > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: [ANNOUNCE] Please welcome new HBase committer YI Liang

that > > Yi Liang has accepted the PMC's invitation to become a committer > > on the project. > > > > We appreciate all of Yi's great work thus far and look forward to > > his continued involvement. > > > > Please join me in congratulating Yi! > > &g

Re: Re: [ANNOUNCE] New HBase Committer Jan Hentschel

> >> Please join me in congratulating Jan! (One of us!) > > > >> > > > >> S > > > >> > > > > > > > > > > > > > > > >-- > > > >Best regards, > > > >Andrew > > > > > > > >Words like orphans lost among the crosstalk, meaning torn from truth's > > > >decrepit hands > > > > - A23, Crosstalk > > > > > > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: Branch 1.4 update

> > > -- > > Best regards, > > Andrew > > > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands >- A23, Crosstalk > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: [ANNOUNCE] New HBase committer Zheng Hu

> We > > > appreciate all of Zheng's generous contributions thus far and look > > forward > > > to his continued involvement. > > > > > > Congratulations and welcome, Zheng! > > > > > > -- == Openinx blog : http://openinx.github.io TO BE A GREAT HACKER ! ==

Re: [DISCUSS] Merge FilterList Improvement - Branch HBASE-18410

com> > wrote: > > Open a issue to track the merging work? Let's do a rebase and more > testing > > in that issue. And then come back and open a vote. > > > > 2017-10-20 11:48 GMT+08:00 OpenInx <open...@gmail.com>: > > > >> > I believe ther

Re: [DISCUSS] Merge FilterList Improvement - Branch HBASE-18410

are several UTs which we want them to be the guard of > > > merging? What is the situation of these UTs? > > > > > > Thanks. > > > > > > 2017-10-20 8:33 GMT+08:00 OpenInx <open...@gmail.com>: > > > > > > > Hi All : > > > > > &g

[DISCUSS] Merge FilterList Improvement - Branch HBASE-18410

Hi All : All subtasks have been resolved except HBASE-18993 , I think it's time to merge HBASE-18410 branch to master now. Any concerns ? Thanks.

Re: Hadoop QA failed to build in branch-1 & branch-1.3

do support java 7. the master branch already doesn't > do > > >> > any java 7, which is why the failures don't happen on it. > > >> > > > >> > On Sat, May 27, 2017 at 11:58 AM, Dima Spivak < > dimaspi...@apache.org> > > >> wrote

Hadoop QA failed to build in branch-1 & branch-1.3

Hi Guys Seems like we always fail to install jdk7 for Hadoop QA currently. ( RUN apt-get -q update && apt-get -q install -y oracle-java7-installer failed) I'm not familiar with Hadoop QA environment, Could anyone help to (or tell how to) fix it ? 1.