Hi, Roger, In LinkedIn we have already moved to YARN 2.6 and is moving to YARN 2.7 now. I am not aware of any major issues in upgrading. I will let our team member Jon Bringhurst to chime in since he did all the upgrade and may have more insights.
@Jon, could you help to comment on this? Thanks! -Yi On Wed, Aug 19, 2015 at 9:12 AM, Roger Hoover <roger.hoo...@gmail.com> wrote: > We're using 2.4.0 in production. Are there any major incompatibilities to > watch out for when upgrading to 2.6.0? > > Thanks, > > Roger > > On Mon, Aug 17, 2015 at 4:41 PM, Yan Fang <yanfang...@gmail.com> wrote: > > > Hi guys, > > > > we have been discussing upgrading to Yarn 2.6.0 (SAMZA-536 > > <https://issues.apache.org/jira/browse/SAMZA-536>), because there are > some > > bug fixes after 2.4.0 and we can not enable the Yarn RM recovering > feature > > in Yarn 2.4.0 (SAMZA-750 < > https://issues.apache.org/jira/browse/SAMZA-750 > > >) > > . > > > > So we just want to make sure if any production users are still using Yarn > > 2.4.0 and do not plan to upgrade to 2.6.0+? > > > > If not further concern, I think we can go and upgrade to Yarn 2.6.0 in > > Samza 0.10.0 release. > > > > Thanks, > > > > Fang, Yan > > yanfang...@gmail.com > > >
