me pain to anybody with clusters on those
> >> versions.
> >>
> >> Eric
> >>
> >> On Tue, Sep 24, 2019 at 2:42 PM Jonathan Hung
> >> wrote:
> >>
> >>> Sorry, let me edit my first point. We can just create addendums f
point. We can just create addendums for
>>> YARN-6616 in branch-2.7 and branch-2.8 to edit the submitTime field to the
>>> correct id 28. We don’t need to revert YARN-6616 from these branches
>>> completely.
>>>
>>> Jonathan
>>>
>>>
t;
>> ____________________
>> From: Jonathan Hung
>> Sent: Tuesday, September 24, 2019 11:38 AM
>> To: Eric Badger
>> Cc: Hadoop Common; yarn-dev; mapreduce-dev; Hdfs-dev
>> Subject: Re: Incompatible changes between branch-2.8 and branch-2.9
>>
>>
t;
>
> From: Jonathan Hung
> Sent: Tuesday, September 24, 2019 11:38 AM
> To: Eric Badger
> Cc: Hadoop Common; yarn-dev; mapreduce-dev; Hdfs-dev
> Subject: Re: Incompatible changes between branch-2.8 and branch-2.9
>
> Hi Eric, thanks for th
: Tuesday, September 24, 2019 11:38 AM
To: Eric Badger
Cc: Hadoop Common; yarn-dev; mapreduce-dev; Hdfs-dev
Subject: Re: Incompatible changes between branch-2.8 and branch-2.9
Hi Eric, thanks for the investigation.
* For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6
Hi Eric, thanks for the investigation.
- For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
revert YARN-6616 from branch-2.7 and branch-2.8.
- For YARN-6050, there's a bit here:
https://develop
