+1 for including the YARN-7190 patch in 3.0.3 release. This is a fix that
will enable HBase to use Hadoop 3.0.x in the production line.
thanks
Vrushali
On Tue, May 8, 2018 at 10:24 AM, Yongjun Zhang wrote:
> Thanks Wei-Chiu and Haibo for the feedback!
>
> Good thing is that I have made the fol
Hi Vinod,
bq. (b) We need to figure out if this V1 TimelineService should even be
support given ATSv2.
Yes, I am following this discussion. Let me chat with Rohith and Varun
about this and we will respond on this thread. As such, my preliminary
thoughts are that we should continue to support Time
Hi Allen,
I have filed https://issues.apache.org/jira/browse/YARN-7380 for the
timeline service findbugs warnings.
thanks
Vrushali
On Mon, Oct 23, 2017 at 11:14 AM, Allen Wittenauer wrote:
>
> I’m really confused why this causes the Yahoo! QA boxes to go catatonic
> (!?!) during the run. As
Timeline Service v2 should be landing on branch2 shortly.
thanks
Vrushali
On Thu, Sep 7, 2017 at 4:57 PM, Vrushali C wrote:
> Thanks everyone.
>
> It has been over a week (~9 days) since TSv2 has been merged to trunk with
> no problems thus far. We are now thinking about merg
As I mentioned in the [VOTE] thread at [1], for Timeline Service v2, we
are thinking about merging to branch2 some time in the next couple of weeks.
So far, we have been maintaining a branch2 based YARN-5355_branch2 along
with our trunk based feature branch YARN-5355. Varun Saxena has been
dilig
who had contributed what
>> > without having to go back to the branch.
>> >
>> > Regards,
>> > Varun Saxena.
>> >
>> > On Thu, Aug 31, 2017 at 3:56 AM, Vrushali C
>> > wrote:
>> >
>> > > Thanks Sangjin for the link to the pr
history
>> of a build.
>>
>> What should our policy/process be here?
>>
>> I do currently plan to merge the s3guard in as one single squashed patch;
>> just getting HADOOP-14809 sorted first.
>>
>>
>> > On 30 Aug 2017, at 07:09, Vrushali C wro
I'm adding my +1 (binding) to conclude the vote.
With 13 +1's (11 binding) and no -1's, the vote passes. We'll get on with
the merge to trunk shortly. Thanks everyone!
Regards
Vrushali
On Tue, Aug 29, 2017 at 10:54 AM, varunsax...@apache.org <
varun.saxena.apa...@gmail.com> wrote:
> +1 (bindin
bq. I don't think it's a lot to ask that feature leads shoot an email to
the release manager of their target version. DISCUSS emails right before a
proposed merge VOTE are way too late, it ends up being a fire drill where
we need to scramble on many fronts.
Yes, I have been thinking about this too
Hi Andrew,
As Rohith mentioned, if you are good with it, from the TSv2 side, we are
ready to go for merge tonight itself (Pacific time) right after the voting
period ends. Varun Saxena has been diligently rebasing up until now so most
likely our merge should be reasonably straightforward.
@Wangda
Hi Subru,
Thanks for your vote and your response!
Regarding your question about merging to branch2, I think, after the merge
to trunk is done, it will be good to merge to branch-2 as soon as we can.
A lot of testing with trunk has been done presently and it will be good to
repeat the same with th
Vrushali C created MAPREDUCE-5550:
-
Summary: Job Status message not shown in UI with Hadoop 2.0
Key: MAPREDUCE-5550
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5550
Project: Hadoop Map/Reduce
Vrushali C created MAPREDUCE-5502:
-
Summary: History link in resource manager is broken for KILLED jobs
Key: MAPREDUCE-5502
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502
Project: Hadoop
Vrushali C created MAPREDUCE-5432:
-
Summary: JobHistoryParser does not fetch clockSplits, cpuUsages,
vMemKbytes, physMemKbytes from history file
Key: MAPREDUCE-5432
URL: https://issues.apache.org/jira/browse
Vrushali C created MAPREDUCE-5309:
-
Summary: 2.0.4 JobHistoryParser can't parse certain failed job
history files generated by 2.0.3 history server
Key: MAPREDUCE-5309
URL: https://issues.apache.org/jira/b
15 matches
Mail list logo
