I have deployed a trivial cluster and ran some MapReduce example and everything worked!
The bad news: I found some bugs in the Ignite's deployment (or rather the discrepancies in 1.9's expectations for the configuration files). It isn't perhaps a blocker, but I would like to spend a bit of time (hopefully over the weekend) to fix it. I would be ok if we don't consider this as a blocker though. Cos -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Fri, Mar 31, 2017 at 11:16 AM, Evans Ye <[email protected]> wrote: > Roman, > > Sounds reasonable. I can recall that discussing thread. > So we don't need to build arch independent component on ppc or arm. > Instead, the deployment and testing for components on those platforms would > be much more important than builds. > > Revoke my -1, but I'd like to take more time for evaluation. > Thanks for the putting up for a RC. > > > 2017-04-01 2:05 GMT+08:00 Roman Shaposhnik <[email protected]>: > >> On Fri, Mar 31, 2017 at 11:02 AM, Olaf Flebbe <[email protected]> wrote: >> > Hi, >> > >> > That's the infamous frontend-maven-plugin, downloading and trying to >> execute "node" for amd64 on each arch. Amir, you patched around these >> issues in the past ? >> >> That's one problem -- but I'm pretty sure its not the only one. >> >> Like I said -- for 1.2 we're just side-stepping this and providing >> packages built elsewhere. >> >> For past 1.2 we should fix it for real -- but fixing it for real will >> require much more than >> the workaround we currently have in do-component-builds. >> >> Thanks, >> Roman. >>
