On Thu, Mar 9, 2017 at 10:25 PM, Stack <st...@duboce.net> wrote: > On Tue, Mar 7, 2017 at 1:51 PM, Josh Elser <els...@apache.org> wrote: > >> Thanks for pulling in the FS Quotas work, Stack. I'm trying to cross the >> last T's and dot the last I's. >> >> The biggest thing I know I need to do still is to write a new chapter to >> the book. After that, I'd start entertaining larger reviews/discussions to >> merge the feature into master. Anyone with free time (giggles) is more than >> welcome to start perusing :) >> >> > Out of interest, this could come in after 2.0 Josh? Any 2.0 specific needs > to make this work? > > nvm Josh. I have it in the Ancillaries section so its not blocker. Fix it if I have it wrong. St.Ack
> Meantime, updated the 2.0 doc 1. > > Thanks Josh, > St.Ack > > 1. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ > ktczrlKHK8N4SZzs/edit# > > > >> >> Stack wrote: >> >>> Just a quick update (Please feel free to amend your own status in our >>> hbase-2.0 doc [1]). >>> >>> On the criticals: >>> >>> + Little progress on the blocker AMv2. A month or more necessary still >>> before code complete (Estimate) >>> + Accordion (inmemory compaction) progressing nicely as is the offheap >>> read/write path. Both are almost done. >>> + Rolling upgrade testing. No work done. >>> + No recent work on core decision tasks (clean-up narrative around RPC >>> timeout, hbase:meta on master or not, batch vs partial semantic, etc.) >>> >>> Non-criticals/Ancillaries >>> >>> + Async client and C++ client are both making good progress. Not done. >>> + Backup/Restore is making good progress >>> + RegionServer-based assignment got a bunch of scrutiny lately and is now >>> 'done'. >>> + FileSystem Quotas making good progress. >>> >>> I'm seeing another month or two at least before branch and probably >>> three. >>> See doc [1] for more detail. >>> >>> Yours, >>> St.Ack >>> >>> 1. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ >>> ktczrlKHK8N4SZzs/edit# >>> >>> >>> >>> >>> >>> On Sun, Jan 29, 2017 at 9:16 PM, Stack<st...@duboce.net> wrote: >>> >>> On Thu, Jan 26, 2017 at 11:49 PM, ramkrishna vasudevan< >>>> ramkrishna.s.vasude...@gmail.com> wrote: >>>> >>>> Hi All >>>>> >>>>> Thanks Stack. The doc looks great. The offheap write path/read path- I >>>>> think from the read path perspective we have some good feedback from >>>>> Alibaba folks. >>>>> >>>>> Agree. >>>> >>>> >>>> The write path subtasks are all done. We are currently working on some >>>>> perf >>>>> results that would help us to come up with some docs that suggests best >>>>> configs and tunings for the offheap write path configurations. >>>>> >>>>> >>>>> Thanks Ram. Would be good to hear what configs you are looking to >>>> implement as default so those of us also starting to test can enable >>>> them >>>> to get you feedback. >>>> >>>> Also suggest you fill the above short status into the doc (You are >>>> keeping >>>> up full status elsewhere). I've been trying to add status as I see it >>>> popping up; e.g. Enis did a nice state-of-the-C++ client recently up in >>>> JIRA and I added pointer to the 2.0 doc. Anyone else working on 2.0 >>>> features, would be good if you kept a short state in this overview doc; >>>> just ask for edit perms. >>>> >>>> Thanks, >>>> St.Ack >>>> >>>> >>>> >>>> >>>> >>>> Regards >>>>> Ram >>>>> >>>>> On Thu, Jan 19, 2017 at 5:37 AM, Andrew Purtell<andrew.purtell@gmail.c >>>>> om >>>>> wrote: >>>>> >>>>> I'm interested in both split meta and rsgroups. Good news. I'd like to >>>>>> help test. >>>>>> >>>>>> >>>>>> On Jan 18, 2017, at 2:53 PM, Stack<st...@duboce.net> wrote: >>>>>>> >>>>>>> On Wed, Jan 18, 2017 at 2:26 PM, Francis Liu<tof...@apache.org> >>>>>>>> >>>>>>> wrote: >>>>> >>>>>> Hi Stack, >>>>>>>> I'd like to get split meta (HBASE-112288) in 2.x as well. I can have >>>>>>>> >>>>>>> a >>>>> >>>>>> 2.x >>>>>> >>>>>>> draft up next week. Was working on the 1.x version internally. >>>>>>>> Also if you'd like I can be the owner for rsgroups as well. >>>>>>>> Thanks,Francis >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I added splitting meta as a possible and had you and I as owner on >>>>>>>> >>>>>>> rsgroups (I was doing to do a bit of testing and doc for this >>>>>>> >>>>>> feature). >>>>> >>>>>> Would love to see splittable meta show up. Needs to be rolling >>>>>>> >>>>>> upgradeable >>>>>> >>>>>>> though. Lets chat up on the issue. >>>>>>> St.Ack >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> On Wednesday, January 18, 2017 11:29 AM, Stack<st...@duboce.net >>>>>>>> > >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> Done Thiruvel (And thanks Guanghao for adding hbase-replication). >>>>>>>> St.Ack >>>>>>>> >>>>>>>> On Tue, Jan 17, 2017 at 6:11 PM, Thiruvel Thirumoolan< >>>>>>>> thiru...@yahoo-inc.com.invalid> wrote: >>>>>>>> >>>>>>>> Hi Stack, >>>>>>>>> I would like to add Favored Nodes to the ancillary section. >>>>>>>>> HBASE-15531: Favored Nodes EnhancementsStatus: Active >>>>>>>>> >>>>>>>> development.Owner: >>>>>> >>>>>>> Thiruvel Thanks!-Thiruvel >>>>>>>>> >>>>>>>>> On Monday, January 16, 2017 2:10 PM, Stack<st...@duboce.net> >>>>>>>>> >>>>>>>> wrote: >>>>> >>>>>> >>>>>>>>> On Mon, Jan 16, 2017 at 3:01 AM, Guanghao Zhang<zghao...@gmail.com >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> For 6. Significant contirbs in master only, there are some issues >>>>>>>>>> >>>>>>>>> about >>>>>> >>>>>>> replication operations routed through master. They are sub-task >>>>>>>>>> of HBASE-10504. And there are other umbrella issue for >>>>>>>>>> replication, >>>>>>>>>> >>>>>>>>> like >>>>>>>> >>>>>>>>> HBase-14379 Replication V2 and HBASE-15867 Moving HBase Replication >>>>>>>>>> tracking from Zookeeper to HBase. So i thought we can add a new >>>>>>>>>> >>>>>>>>> section >>>>>> >>>>>>> named >>>>>>>>>> hbase-replication to possible 2.0.0s. This will help us to track >>>>>>>>>> >>>>>>>>> the >>>>> >>>>>> state. >>>>>>>>> >>>>>>>>>> Thanks. >>>>>>>>>> >>>>>>>>>> Thanks Guanghao Zhang. I agree. I made you an editor. If you want >>>>>>>>> to >>>>>>>>> >>>>>>>> have a >>>>>>>> >>>>>>>>> go at a first cut, be my guest. If nothing done in the next day or >>>>>>>>> >>>>>>>> so, >>>>> >>>>>> I'll >>>>>>>> >>>>>>>>> add this section Sir. >>>>>>>>> Thanks, >>>>>>>>> M >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>> >>> >
