[jira] [Created] (HBASE-25087) Splittable Meta: Generalize handling of meta regions to support splittable meta

Francis Christopher Liu created HBASE-25087: --- Summary: Splittable Meta: Generalize handling of meta regions to support splittable meta Key: HBASE-25087 URL: https://issues.apache.org/jira/browse/HBASE

[jira] [Resolved] (HBASE-25056) Splittable Meta: foward port fixes from hbase-2 branch and stabilize unit tests

[ https://issues.apache.org/jira/browse/HBASE-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Christopher Liu resolved HBASE-25056. - Resolution: Fixed > Splittable Meta: foward port fixes from hbas

[jira] [Created] (HBASE-25056) Splittable Meta: foward port fixes from hbase-2 branch and stabilize unit tests

Francis Christopher Liu created HBASE-25056: --- Summary: Splittable Meta: foward port fixes from hbase-2 branch and stabilize unit tests Key: HBASE-25056 URL: https://issues.apache.org/jira/browse/HBASE

[jira] [Resolved] (HBASE-25028) Rebase Splittable Meta Master branch

[ https://issues.apache.org/jira/browse/HBASE-25028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Christopher Liu resolved HBASE-25028. - Resolution: Fixed > Rebase Splittable Meta Master bra

[jira] [Created] (HBASE-25028) Rebase Splittable Meta Master branch

Francis Christopher Liu created HBASE-25028: --- Summary: Rebase Splittable Meta Master branch Key: HBASE-25028 URL: https://issues.apache.org/jira/browse/HBASE-25028 Project: HBase

[jira] [Created] (HBASE-25027) Generalize MasterRegistry, etc to support both Master and Regionserver

Francis Christopher Liu created HBASE-25027: --- Summary: Generalize MasterRegistry, etc to support both Master and Regionserver Key: HBASE-25027 URL: https://issues.apache.org/jira/browse/HBASE-25027

Re: [DISCUSS] Merge "HBASE-22514 Move rsgroup feature into core of HBase" back to master

I have not looked at the patch. But I think it's a great idea to have RSGroup part of core. It will make a lot of things easier. Thanks, Francis On Thu, Feb 13, 2020 at 5:36 PM 张铎(Duo Zhang) wrote: > This depends on you, the release manager of 2.3 :) > > If you want this, we could have a try.

Re: [DISCUSS] EOM branch-1.3

Hi Guys, We are still on 1.3 so it would be in our interest if I can continue to rollout 1.3.z releases. Having said that it is the oldest release branch and I understand the effort it takes to maintain another branch hence I didn't push for it unless there are other reasons than our own for

Re: [VOTE] Second Release Candidate for HBase 1.3.6 is available for download

+1 (Binding) Checked: - Signature & checksums - built from source - ran unit tests - web ui - some shell commands Oddly enough org.apache.hadoop.hbase.ipc.TestIPC fails when run in the docker container, even when run individually but passes when I ran it individually on my mac. Also thanks for

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

Thanks a lot Misty! And congratulations Duo! Francis On Sun, Jul 21, 2019 at 8:27 PM Yu Li wrote: > Congratulations Duo! And thank you Misty! > > Best Regards, > Yu > > > On Sun, 21 Jul 2019 at 11:21, Allan Yang wrote: > > > Congratulations Duo! > > Best Regards > > Allan Yang > > > > > >

Re: Roll a 1.3.5 for PHOENIX-5269 ?

Hi Andy, I won't have time to roll one this week. Please go ahead and roll 1.3.5. Francis On Fri, May 24, 2019 at 11:52 AM Andrew Purtell wrote: > PHOENIX-5269 cannot be committed to the 4.14-HBase-1.3 code line until > 1.3.5 is released including HBASE-22374. If there is no objection I would

Re: [DISCUSS] HBase 3

I'd also like to get "Splittable Meta" HBASE-12233 in. Apart from scalability this would help spread the load on meta access across a bunch of servers. We have a branch-1.3 implementation, I'll put it up got sidetracked a bit when I was cleaning it up. Then after that a trunk patch. Thanks,

[ANNOUNCE] Apache HBase 1.3.4 is now available for download

The HBase team is happy to announce the immediate availability of Apache HBase 1.3.4 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

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

With three binding +1's this vote passes. Thanks a lot Andy, Sean and Josh! Francis On Wed, Apr 24, 2019 at 1:13 PM Sean Busbey wrote: > +1 > > Good: > * checksums, signatures > * LICENSE/NOTICE > * staged maven repo looks fine > > > On Mon, Apr 15, 2019 at 4:10 AM Francis Liu wrote: > > > >

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

This RC still needs one more binding vote. I'm extending the deadline to until friday (4/26). Please vote. Thanks, Francis On Fri, Apr 19, 2019 at 1:12 PM Francis Christopher Liu < toffer@gmail.com> wrote: > Just a reminder need one more binding vote for this release. So far it

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

Just a reminder need one more binding vote for this release. So far it's mine and Andy's. Here's my +1 Thanks, Francis On Mon, Apr 15, 2019 at 2:49 PM Andrew Purtell wrote: > +1 > > Checked sums and signatures: ok > RAT check passes: ok (7u80) > Built from source: ok (7u80) > Unit tests pass:

Working on 1.3.4 release

Hi, As promised working on cutting a 1.3 release for this quarter. Should hopefully have an RC up next week. Thanks, Francis

Re: [DISCUSS] EOL branch-1.3

have > >> limited bandwidth so stuff gets missed. just doing it as a part of the > >> release takes quite some time if one hasn't been keeping an eye out. > >> > >> FWIW, I agree that effort towards getting your deployment onto a future > >> branch-

Re: [DISCUSS] EOL branch-1.3

er. It'd be nice if that could include > discussing what it would take for periodic updates to future branch-1 minor > releases to become your plan instead of e.g. sticking to branch-1.4.z > > On Mon, Dec 17, 2018, 18:38 Francis Christopher Liu wrote: > > > > How about we have

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

+1 (Binding) I checked the following: 1. Checksums and signatures 2. Rat 3. Built From Source and Ran unit tests 4. Some shell commands 5. Web UI 6. LTT with 1M rows Thanks, Francis On Fri, Dec 14, 2018 at 10:43 PM Sakthi wrote: > (+1 Non-Binding) > >1. Checksums and signatures(both src

Re: [DISCUSS] EOL branch-1.3

hly (usually, monthly) and Sean has > been > > releasing 1.2 every quarter. So maybe quarterly releases would be good? > > What do others think? What is the minimum release schedule to make it > worth > > your while for commits/backports to a branch? At least once every half >

Re: [DISCUSS] EOL branch-1.3

ity. Committers have to deal with > > > > effectively a dead branch. Users get no releases. Given the consensus > > > > expressed on this thread we don’t want this deal. It’s great that > > you’ve > > > > stepped forward to offer ongoing RM activi

Re: [DISCUSS] EOL branch-1.3

ee that I stepped forward to make a release? There is a VOTE > thread now for 1.3.3RC0. Perhaps we can start there? Would you use it? > Would you +1? Or are there changes in there that are of concern? Please > consider commenting on the VOTE. > > > > On Dec 17, 2018, at 8:31 AM, Franc

Re: [DISCUSS] EOL branch-1.3

Hi, Apologies a bit late to this discussion. I would still like to continue making 1.3 releases. If the concern is having a better cadence of releases let me know how often the community would like (quarterly, every other month, etc) and I'll make sure to carve out time with my employer. We will

Re: [VOTE] First release candidate for HBase 1.3.2 (RC1) is available

Thanks Chia-Ping! I'll make sure to build with my username next time. On Tue, Mar 27, 2018 at 6:32 AM Chia-Ping Tsai wrote: > +1 (binding) > > unit tests (oracle 8u161) - pass > deploy src and binary - LGTM > shell command - LGTM > put|delete|get|scan 100W rows - LGTM >

Re: [VOTE] First release candidate for HBase 1.3.2 (RC1) is available

publishing the artifacts stay tuned for the release announcement. Thanks, Francis On Tue, Mar 27, 2018 at 4:00 PM Francis Christopher Liu < toffer@gmail.com> wrote: > Thanks Chia-Ping! I'll make sure to build with my username next time. > > > On Tue, Mar 27, 2018 at 6:32 AM Chi

Re: [VOTE] First release candidate for HBase 1.3.2 (RC1) is available

> The value of "HBase Compiled" is weird. see the following screenshot. Chia-Ping, I was running the build as root in a docker container. Is this a concern? > Just a notice: according to our make_rc.sh script, the sha files should be named as .sha512. Balazs, thanks for pointing this out. I was

Re: Flush requires global ADMIN permission on 2.0

Not a fan of allowing users (including table and namespace admins) access to HBase apis that directly allow them to create new files, etc. There's potential for misuse spamming the NN, broadening the issue. My 2 cents. Francis On Tue, Mar 13, 2018 at 1:49 PM Josh Elser

Re: [DISCUSS] our stable release pointer and EOM

> I think Francis Liu might be wanting to make more releases of 1.3. If so, and for as long as he wants to do it, we shouldn't mark it EOM obviously. Thanks! Yes, I'd like to continue cutting releases for 1.3 as long as we are on it which may be a while. > As for moving the stable pointer to

Re: Going to roll 1.3.2 RC in next few weeks

rt...@gmail.com> > wrote: > >> Ok. Great! >> >> Will revisit this next month. >> >> On Jan 5, 2018, at 9:35 AM, Francis Christopher Liu <toffer@gmail.com> >> wrote: >> >> I'm interested in picking it up if that's ok. Tho I'm out till

Re: Going to roll 1.3.2 RC in next few weeks

I'm interested in picking it up if that's ok. Tho I'm out till mid next week. Thanks, Francis On Thu, Jan 4, 2018 at 12:00 PM Andrew Purtell wrote: > Ok, I’ll start work on a 1.3.2 RC > > > > > On Jan 3, 2018, at 12:13 PM, Andrew Purtell wrote: >

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

Just some high-level thoughts on rolling upgradeability (I'm repeating a few things already said). 1. No service interruption for 1.x clients while a cluster is being ugpraded to 2.x. - This includes support for apis commonly used in a running system: delegation tokens, getting region

Re: NumTables/regions Quota management and RS groups - Core or coprocessors

Thanks for the response guys. Can I take it this is an affirmative for region server groups as well? HBASE-6721 -Francis On Fri, Dec 5, 2014 at 10:17 AM, Ted Yu yuzhih...@gmail.com wrote: bq. something like quotas is a core issue +1 On Fri, Dec 5, 2014 at 10:09 AM, Andrew Purtell