samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Malcolm McFarland <mmcfarl...@cavulus.com>
Subject Re: Samza 1.1.0 on AWS EMR (emr - 5.13.0, amazon 2.8.3, zookeeper 3.4.10)
Date Thu, 18 Apr 2019 18:05:06 GMT
Hey folks,

We were also looking at running Samza in EMR, but couldn't find enough
information to get going with it, and, time crunches being what they are,
created our own Hadoop 2.7.6 cluster to run it (thanks again to Prateek for
the help on this!).

Has anybody on this list gotten Samza to run on EMR successfully, and if
so, do they have any tips or links to documentation for doing this? Is
there a minimum version of Samza and/or Kafka that's required?

Cheers,
Malcolm

On Thu, Apr 18, 2019 at 9:08 AM Hai Lu <lhaiesp@apache.org> wrote:

> +samza dev
>
> ApplicationRunnerMain should be there in the samza-core module. Are you
> seeing the samza-core jar in your lib folder? Make sure the scala version
> also match (2.10 vs. 2.11)
>
> Are you upgrading from 0.14 to 1.1 or from 1.0 to 1.1?
>
> Thanks,
> Hai
>
>
> On Wed, Apr 17, 2019 at 4:28 PM Majd F. Sakr <msakr@cs.cmu.edu> wrote:
>
> > Hello Hai,
> >
> > I hope you are doing well.  I'm writing you from Carnegie Mellon
> > University again.
> >
> > One of my TAs is trying to upgrade our project to use the latest Samza
> > distribution but is failing.  He describes the situation here:
> >
> >
> https://stackoverflow.com/questions/55737123/samza-1-1-0-run-app-sh-does-not-work-during-deployment-of-hello-samza
> >
> > Can someone on your team please help?
> >
> > Many thanks,
> >
> > Majd
> >
> >
>


-- 
Malcolm McFarland
Cavulus
1-800-760-6915
mmcfarland@cavulus.com


This correspondence is from HealthPlanCRM, LLC, d/b/a Cavulus. Any
unauthorized or improper disclosure, copying, distribution, or use of the
contents of this message is prohibited. The information contained in this
message is intended only for the personal and confidential use of the
recipient(s) named above. If you have received this message in error,
please notify the sender immediately and delete the original message.

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