Yup, I was building and running tests in the branch.
ALL CLEAR now. YARN-321 merged. I could build branch-2. Ran all the YARN tests
successfully.
Let me know if any more issues blow up and/or file JIRA tickets.
+Vinod
On Jan 28, 2014, at 1:08 PM, Sandy Ryza wrote:
> It looks like Vinod just
It looks like Vinod just fixed this. Thanks!
On Tue, Jan 28, 2014 at 1:00 PM, Sandy Ryza wrote:
> I'm getting build errors on branch-2 because the pom for the new module
> still refers to 3.0.0-SNAPSHOT:
>
>
> hadoop-yarn-server
> org.apache.hadoop
> 3.0.0-SNAPSHOT
>
> 4.0.
I'm getting build errors on branch-2 because the pom for the new module
still refers to 3.0.0-SNAPSHOT:
hadoop-yarn-server
org.apache.hadoop
3.0.0-SNAPSHOT
4.0.0
org.apache.hadoop
hadoop-yarn-server-applicationhistoryservice
3.0.0-SNAPSHOT
hadoop-yarn-server-application
Trunk build seems stable now after the merge. A couple of yarn trunk builds
also ran fine (https://builds.apache.org/job/Hadoop-Yarn-trunk/462/ and
https://builds.apache.org/job/Hadoop-Yarn-trunk/463/). Branch 2.3 is also cut
and is out of the way.
I'm now merging this into branch-2 so as to m
Done. Ran trunk compilation and the new module's (small number of) YARN tests.
Seems fine. Please let Zhijie/Mayank or me know if something major is broken.
And/or file tickets.
Thanks,
+Vinod
On Jan 25, 2014, at 8:21 PM, Vinod Kumar Vavilapalli
wrote:
> With 5 binding +1s, one non-binding +
With 5 binding +1s, one non-binding +1 and no -1s, this vote passes. I'm
merging YARN-321 into trunk now.
Thanks everyone for voting!
+Vinod
On Jan 22, 2014, at 3:29 AM, Devaraj K wrote:
> +1
>
>
>
> Thanks
> Devaraj K
>
>
> On Wed, Jan 22, 2014 at 1:05 AM, Mayank Bansal wrote:
>
>> +1
+1
Thanks,
Mayank
On Tue, Jan 21, 2014 at 11:11 AM, Arun C Murthy wrote:
> +1 (binding)
>
> Arun
>
> On Jan 17, 2014, at 12:53 PM, Zhijie Shen wrote:
>
> > Hi folks,
> >
> > As previously discussed here (
> http://markmail.org/message/iscvp7cedrtvmd6p),
> > I would like to call a vote to merg
+1 (binding)
Arun
On Jan 17, 2014, at 12:53 PM, Zhijie Shen wrote:
> Hi folks,
>
> As previously discussed here (http://markmail.org/message/iscvp7cedrtvmd6p),
> I would like to call a vote to merge the YARN-321 branch for Generic
> Application History Server into trunk.
>
> *Scope of the cha
Thanks Zhijie!
I've been involved in its design. And reviewed almost every patch. Contributed
a little w.r.t tests etc.
The code is in a decent shape bar some bugs and security. The merge should let
us avoid the maintenance burden.
Tested the latest code on my single node setup. It mostly loo
As a cluster resource management platform, generic history service is
necessary for job-tracing, troubleshooting, fault tolerance, and
performance tuning.
Like StarterLog in Condor, accounting logs in Torque, and so on. However,
generic history service should avoid getting involved into too many de
Hi folks,
As previously discussed here (http://markmail.org/message/iscvp7cedrtvmd6p),
I would like to call a vote to merge the YARN-321 branch for Generic
Application History Server into trunk.
*Scope of the changes*
The changes enable ResourceManager to record the historic information of
the
11 matches
Mail list logo
