+1 (binding). Let’s look into all concerns raised during the merge vote in post-merge phase.
Li Lu > On Jul 5, 2016, at 10:17, Wangda Tan <wheele...@gmail.com> wrote: > > +1 (Binding), > Looking forward to merge this into trunk! > > - Wangda > > On Tue, Jul 5, 2016 at 4:18 AM, Naganarasimha G R (Naga) < > garlanaganarasi...@huawei.com> wrote: > >> +1 (Binding), >> >> May be we need to further look into the points mentioned by Allen ! >> >> Regards, >> + Naga >> ________________________________________ >> From: Allen Wittenauer [a...@apache.org] >> Sent: Tuesday, July 05, 2016 11:40 >> To: yarn-dev@hadoop.apache.org >> Subject: Re: [VOTE] merge feature branch YARN-2928 >> >> -0: >> >> I haven't looked at the code changes (although the pom change in >> hadoop-aws seems pretty oddball). But I did do a quick pass through the >> documentation. It needs some formatting, cleanup, and consistency work done >> (e.g., not using toc macro, lack of language specific code formatting, >> usage of version numbers are gonna be awkward in the future, etc) . It's >> also using the wrong command for trunk, highlighting a problem of >> developing on branch-2 and then forward porting. (hint: daemon stuff has >> been handled by bin/yarn in trunk for almost 2 years now...) >> >> Not enough to stop a merge, IMHO, but definitely should be followed up on >> post-merge. >> >> On 2016-07-01 09:00 (-0700), Sangjin Lee <s...@apache.org> wrote: >>> Hi folks,> >>> >>> Per earlier discussion [1], I'd like to start a formal vote to merge> >>> feature branch YARN-2928 [2] (Timeline Service v.2) to trunk. The vote >> will> >>> run for 7 days, and will end July 8 9:00 AM PDT.> >>> >>> We have been developing the feature in a feature branch (YARN-2928 [3]) >> for> >>> a while, and we are reasonably confident that the state of the feature> >>> meets the criteria to be merged onto trunk and we'd love folks to get >> their> >>> hands on it in a test capacity and provide valuable feedback so that we >> can> >>> make it production-ready.> >>> >>> In a nutshell, Timeline Service v.2 delivers significant scalability and> >>> usability improvements based on a new architecture. You can browse the> >>> requirements/design doc, the storage schema doc, the new entity/data >> model,> >>> the YARN documentation, and also discussions on subsequent milestones on> >>> YARN-2928 [2].> >>> >>> What we would like to merge to trunk is termed "alpha 1" (milestone 1). >> The> >>> feature has a complete end-to-end read/write flow, and you should be >> able> >>> to start setting it up and testing it. At a high level, the following >> are> >>> the key features that have been implemented:> >>> >>> - distributed writers (collectors) as NM aux services> >>> - HBase storage> >>> - new entity model that includes flows> >>> - setting the flow context via YARN app tags> >>> - real time metrics aggregation to the application level and the flow >> level> >>> - rich REST API that supports filters, complex conditionals, limits,> >>> content selection, etc.> >>> - YARN generic events and system metrics> >>> - integration with Distributed Shell and MapReduce> >>> >>> There are a total of 139 subtasks that were completed as part of this> >>> effort.> >>> >>> We paid close attention to ensure that once disabled Timeline Service >> v.2> >>> does not impact existing functionality when disabled (by default).> >>> >>> Special thanks go to all the folks who worked real hard on this feature: >> Li> >>> Lu, Junping Du, Vinod Kumar Vavilapalli, Naga G. R., Varun Saxena, >> Vrushali> >>> C, and Joep Rottinghuis!> >>> >>> Regards,> >>> Sangjin> >>> >>> [1]> >>> >> https://lists.apache.org/thread.html/314288f399f5ef96b2f4f1fc055ac5d440310c8d98ace9a0045e8729@%3Cyarn-dev.hadoop.apache.org%3E >>> >>> [2] https://issues.apache.org/jira/browse/YARN-2928> >>> [3] https://github.com/apache/hadoop/commits/YARN-2928> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
