hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinayakumar B <vinayakum...@apache.org>
Subject Re: 2.7.1 status
Date Wed, 27 May 2015 07:36:43 GMT
Hi Vinod,

https://issues.apache.org/jira/browse/HDFS-8270 seems to create some issue
for the downstream projects in NonHA case.
I will try to get it in for 2.7.1 if everyone agrees to remove IPC level
retries only in case of NonHA for *create() *request.

-Vinay

On Wed, May 27, 2015 at 12:34 PM, Nijel s f <nijel.sf@huawei.com> wrote:

>
> Hi,
>
> Thanks for the update
> We are using 2.7.0 for our platform, and testing it per our scenarios.
>
> Overall the test result looks fine. Basic performance test is done and no
> degradation observed in our scenarios.
> Functional scenarios are working fine and no issue reported in
> compatibility with the usage scenarios
>
> Ran into few major issues,
>
> https://issues.apache.org/jira/browse/YARN-3558
> https://issues.apache.org/jira/browse/HADOOP-11628
> https://issues.apache.org/jira/browse/YARN-3585
>
> As per the discussion with some of the members, YARN-3558 seems like not a
> regression bug.
>
> Looking forward to get these fixed in 2.7.1
>
>
> Regards
> Nijel
>
> -----Original Message-----
> From: Vinod Kumar Vavilapalli [mailto:vinodkv@hortonworks.com]
> Sent: 23 May 2015 01:02
> To: Hadoop Common; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org
> Cc: Vinod Kumar Vavilapalli
> Subject: Re: 2.7.1 status
>
> Been a while since 2.7.0 release.
>
> I am going to do a scan of outstanding issues this weekend and start the
> push. There are 7 blockers/criticals as of now:
> https://issues.apache.org/jira/issues/?filter=12331550
>
> I couldn't send notes to downstream projects as I originally anticipated.
> But from our internal testing with the latest releases/branches of other
> ecosystem projects like Hive, Pig, Oozie, I haven't yet seen any
> incompatible issues being reported. We also have done one preliminary round
> of rolling-upgrades testing which seems to have gone well.
>
> Will post more results over this and next week. Has anyone else done any
> testing on 2.7.0? If so, please update here of your findings.
>
> Hoping to get a release candidate out next week.
>
> Thanks
> +Vinod
>
> On Apr 23, 2015, at 11:58 AM, Vinod Kumar Vavilapalli <vinodkv@apache.org
> <mailto:vinodkv@apache.org>> wrote:
>
> As we talked before [1], I am going to start the push for 2.7.1 [2].
>
> Here are the things I am going to do, with help from others in the
> community
>  - Review current 2.7.1 content to make sure only bug fixes went in
>  - Review 2.8 to see if any important bug fixes didn't get merged into
> 2.7.1
>  - Send notes to downstream projects to see if they can pick up 2.7.0
> mainly with a view of catching incompatibilities/critical issues
>
> If you feel like there is an important fix that you need in 2.7.1, please
> mark it so on JIRA so we can coordinate the release timeline.
>
> Also, it will be great if other community members share their testing
> results on 2.7.0 +, so that we can settle on a stable 2.7.1.
>
> Thanks
> +Vinod
>
>
> [1]: A 2.7.1 release to follow up 2.7.0
> http://markmail.org/thread/zwzze6cqqgwq4rmw
>
> [2] JIRA filter I am using to track blockers/criticals:
> https://issues.apache.org/jira/issues/?filter=12331550
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message