Guys,
I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as I am trying to prep for the webinar this week. It seems that if even this bug is fixed we won't be able to use it in bigtop stack with Hadoop 2.6 at the base as it requires yarn 2.7.1 (if I am reading this right?) Hence, the question: how can I disable the build of ignite-yarn (which I can not care less for) to have a working Ignite cluster on top of Hadoop 2.6? Appreciate the timely reply if anyone has the info! Thanks! Cos |
On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik <[hidden email]> wrote:
> Guys, > > I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as I am > trying to prep for the webinar this week. It seems that if even this bug is > fixed we won't be able to use it in bigtop stack with Hadoop 2.6 at the > base > as it requires yarn 2.7.1 (if I am reading this right?) Hence, the > question: > how can I disable the build of ignite-yarn (which I can not care less for) > to > have a working Ignite cluster on top of Hadoop 2.6? > Or yet another approach is to fix the yarn 2.7.1 build if possible. > > Appreciate the timely reply if anyone has the info! Thanks! > Cos > |
Hi,
>Hence, the question: how can I disable the build of ignite-yarn (which I can not care less for) to >have a working Ignite cluster on top of Hadoop 2.6? You can disable the build of ignite-yarn using the following maven command: *mvn clean package -DskipTests -pl \!modules/yarn -Dhadoop.version=2.6.0 -Dignite.edition=hadoop * |
In reply to this post by dsetrakyan
On Mon, Aug 17, 2015 at 07:39PM, Dmitriy Setrakyan wrote:
> On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik <[hidden email]> wrote: > > > Guys, > > > > I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as I am > > trying to prep for the webinar this week. It seems that if even this bug is > > fixed we won't be able to use it in bigtop stack with Hadoop 2.6 at the > > base > > as it requires yarn 2.7.1 (if I am reading this right?) Hence, the > > question: > > how can I disable the build of ignite-yarn (which I can not care less for) > > to > > have a working Ignite cluster on top of Hadoop 2.6? > > > > Or yet another approach is to fix the yarn 2.7.1 build if possible. I so didn't catch your drift. Could you elaborate? |
In reply to this post by Nikolay Tikhonov
On Tue, Aug 18, 2015 at 09:43AM, Nikolay Tikhonov wrote:
> Hi, > > >Hence, the question: how can I disable the build of ignite-yarn (which I > can not care less for) to > >have a working Ignite cluster on top of Hadoop 2.6? > > You can disable the build of ignite-yarn using the following maven command: > > *mvn clean package -DskipTests -pl \!modules/yarn -Dhadoop.version=2.6.0 > -Dignite.edition=hadoop * Ah, that's helpful - I will try it in the morning. Thanks Nikolay! |
In reply to this post by Konstantin Boudnik-2
On Tue, Aug 18, 2015 at 12:45 AM, Konstantin Boudnik <[hidden email]> wrote:
> On Mon, Aug 17, 2015 at 07:39PM, Dmitriy Setrakyan wrote: > > On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik <[hidden email]> > wrote: > > > > > Guys, > > > > > > I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as > I am > > > trying to prep for the webinar this week. It seems that if even this > bug is > > > fixed we won't be able to use it in bigtop stack with Hadoop 2.6 at the > > > base > > > as it requires yarn 2.7.1 (if I am reading this right?) Hence, the > > > question: > > > how can I disable the build of ignite-yarn (which I can not care less > for) > > > to > > > have a working Ignite cluster on top of Hadoop 2.6? > > > > > > > Or yet another approach is to fix the yarn 2.7.1 build if possible. > > I so didn't catch your drift. Could you elaborate? > I was suggesting that we fix the yarn 2.7.1 compatibility in Ignite. |
On Tue, Aug 18, 2015 at 12:59AM, Dmitriy Setrakyan wrote:
> On Tue, Aug 18, 2015 at 12:45 AM, Konstantin Boudnik <[hidden email]> wrote: > > > On Mon, Aug 17, 2015 at 07:39PM, Dmitriy Setrakyan wrote: > > > On Mon, Aug 17, 2015 at 6:54 PM, Konstantin Boudnik <[hidden email]> > > wrote: > > > > > > > Guys, > > > > > > > > I am looking at https://issues.apache.org/jira/browse/IGNITE-1195 as > > I am > > > > trying to prep for the webinar this week. It seems that if even this > > bug is > > > > fixed we won't be able to use it in bigtop stack with Hadoop 2.6 at the > > > > base > > > > as it requires yarn 2.7.1 (if I am reading this right?) Hence, the > > > > question: > > > > how can I disable the build of ignite-yarn (which I can not care less > > for) > > > > to > > > > have a working Ignite cluster on top of Hadoop 2.6? > > > > > > > > > > Or yet another approach is to fix the yarn 2.7.1 build if possible. > > > > I so didn't catch your drift. Could you elaborate? > > > > I was suggesting that we fix the yarn 2.7.1 compatibility in Ignite. Oh yeah, that'd be the best! But if 1.3.+ version is relying on certain APIs from 2.7.+ it might be hard. Arguably, that could be one of those yarn backward incompatibilities, but I haven't looked into it - really don't have time nor enough interest for it. Cos |
In reply to this post by Nikolay Tikhonov
Unfortunately, it won't work in Bigtop 1.0 as it is using Maven 3.0.+ where's
your suggestion only applies to v 3.2.1 and later. At any rate I hacked around it by explicitly removing the module from the top-level pom file. I have opened BIGTOP-1968 to see it through... Cos On Tue, Aug 18, 2015 at 09:43AM, Nikolay Tikhonov wrote: > Hi, > > >Hence, the question: how can I disable the build of ignite-yarn (which I > can not care less for) to > >have a working Ignite cluster on top of Hadoop 2.6? > > You can disable the build of ignite-yarn using the following maven command: > > *mvn clean package -DskipTests -pl \!modules/yarn -Dhadoop.version=2.6.0 > -Dignite.edition=hadoop * |
Free forum by Nabble | Edit this page |