Added them all, tx Rohit.

+Vinod

> On Aug 5, 2015, at 9:51 PM, Rohith Sharma K S <rohithsharm...@huawei.com> 
> wrote:
> 
> Can we add following fixes to 2.6.1?
> 
> YARN-3733 
> YARN-2865
> YARN-3990
> YARN-2894
> 
> 
> Thanks & Regards
> Rohith Sharma K S
> 
> 
> -----Original Message-----
> From: Allan Wilson [mailto:awils...@pandora.com] 
> Sent: 05 August 2015 23:25
> To: common-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org; 
> yarn-...@hadoop.apache.org
> Cc: hdfs-...@hadoop.apache.org
> Subject: Re: Planning Hadoop 2.6.1 release
> 
> Another +1 to add those fixes.
> 
> YARN-3487 bug can grind a large cluster to a halt repeatedly
> 
> 
> 
> -Allan
> 
> ----
> Allan Wilson | Sr. Software Engineer | Pandora m 919.841.2449 |  
> awils...@pandora.com
> 
> 
> 
> 
> 
> On 8/5/15, 1:52 PM, "Rich Haase" <rha...@pandora.com> wrote:
> 
>> +1 to add those fixes.
>> 
>> 
>> Rich Haase | Sr. Software Engineer | Pandora m 303.887.1146 | 
>> rha...@pandora.com
>> 
>> 
>> 
>> 
>> On 8/5/15, 11:42 AM, "Wangda Tan" <wheele...@gmail.com> wrote:
>> 
>>> Can we add following two fixes to 2.6.1?
>>> 
>>> https://issues.apache.org/jira/browse/YARN-2922 and 
>>> https://issues.apache.org/jira/browse/YARN-3487.
>>> 
>>> They're not fatal issue, but they can cause lots of issue in a large 
>>> cluster.
>>> 
>>> Thanks,
>>> Wangda
>>> 
>>> 
>>> On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee <sj...@apache.org> wrote:
>>> 
>>>> See my later update in the thread. HDFS-7704 is in the list.
>>>> 
>>>> Thanks,
>>>> Sangjin
>>>> 
>>>> On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli < 
>>>> vino...@hortonworks.com> wrote:
>>>> 
>>>>> Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only 
>>>>> and
>>>> is
>>>>> not part of the candidate list. Removed HDFS-7916 from the list.
>>>>> 
>>>>> Thanks
>>>>> +Vinod
>>>>> 
>>>>>> On Jul 24, 2015, at 6:32 PM, Sangjin Lee <sj...@apache.org> wrote:
>>>>>> 
>>>>>> Out of the JIRAs we proposed, please remove HDFS-7916. I don't
>>>> think it
>>>>>> applies to 2.6.
>>>>>> 
>>>>>> Thanks,
>>>>>> Sangjin
>>>>> 
>>>>> 
>>>> 
>> 
> 
> 

Reply via email to