Hi Malcolm,

Based on the following log

INFO [org.apache.samza.zk.ZkJobCoordinator] New JobModel does not contain
> pid=a3e86ddf-8d18-40c9-8063-1efd588cec56. Stopping this processor. New
> JobModel: JobModel [..]
>

I'd have to guess that the processor isn't part of the quorum (list of
processors) that was used by the leader to generate the job model in the
first place and hence it is expected to ignore the job model change and
shut itself down.

I'd suggest

   1. Take a pass at whether this processor is part of the quorum and what
   happened to its membership.
   2. Take a pass at the leader's log to get some insights into what set of
   processors it started out with when generating the job model.

We will need more details to investigate the issue. If you can attach the
failed processor and leader logs, I can take a stab at it.

Thanks,
Bharath


On Mon, Dec 14, 2020 at 10:05 AM Malcolm McFarland <mmcfarl...@cavulus.com>
wrote:

> Hey all,
>
> We have an app that's been running on v0.14.1 for the last few years, and
> we're trying to drag it forward into the present with v1.5.1. I've tried a
> few different approaches at updating it, including creating a
> TaskApplication via the low-level API and also following the "Legacy
> Applications" deploy instructions. Thus far, the legacy approach seems most
> promising, but the application isn't fully starting up. It _seems_ to be an
> issue with creating the JobModel; although there are no explicit errors, I
> do see these log messages:
>
> INFO [org.apache.samza.zk.ZkJobCoordinator] Got a notification for new
> JobModel version. Path = ..
> INFO [org.apache.samza.zk.ZkJobCoordinator]
> pid=a3e86ddf-8d18-40c9-8063-1efd588cec56: new JobModel is available.
> Version =9; JobModel = JobModel [..]
> INFO [org.apache.samza.zk.ZkJobCoordinator] New JobModel does not contain
> pid=a3e86ddf-8d18-40c9-8063-1efd588cec56. Stopping this processor. New
> JobModel: JobModel [..]
>
> At this point the ThreadJob shuts down cleanly. Afaict, the legacy
> configuration is set up correctly, and mirrors our functional build under
> 0.14.1. Any thoughts?
>
> 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.
>

Reply via email to