samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Malcolm McFarland <mmcfarl...@cavulus.com>
Subject Re: Where does task.class actually matter?
Date Fri, 19 Jul 2019 05:49:00 GMT
Here's another twist: I'm attempting to create a "start-only" instance of
my Samza app by pulling the existing, functional tarball down from S3,
expanding it, and using the run-app.sh and the *.properties file within it
to start the YARN task. This all seems to work just fine, but when I start
the task in this manner, I'm seeing a bunch of failed attempts on YARN with
a 'Exception in thread "main" java.lang.ClassNotFoundException' error. This
seems bonkers, since all I'm doing is using exactly the same config file to
point YARN at exactly the same tarball in exactly the same place. I'm even
killing the previous process before restarting it, just in case there's
some sort of conflict there. How on Earth could the same sequence of steps
produce these two different results? Does the JAVA_PATH variable from the
box I *start* the task from affect the box that *runs* the task?

Cheers,
Malcolm McFarland
Cavulus


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.


On Wed, Jul 17, 2019 at 8:46 PM Malcolm McFarland <mmcfarland@cavulus.com>
wrote:

> Hey Folks,
>
> I'm trying to setup a load-only installation of Samza -- in other words, a
> process that starts a Samza processor task on YARN, but isn't using the
> actual config file that's bundled into the YARN package -- and I'm getting
> some flack from run-app.sh that the task.class doesn't exist in the
> generic hello-samza installation I'm using. I'd really like to just be able
> to load an already-existing Samza bundle (in this case, it's stored on S3)
> without having to do an entire build of the bundle. Is this possible? If
> so, why would run-app.sh care if the bundle is built locally or not?
>
> Cheers,
> Malcolm McFarland
> Cavulus
>
>
> 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