samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Crim <>
Subject ThreadJobFactory in production
Date Wed, 02 Mar 2016 21:20:52 GMT

We're currently working on a solution that allows us to run Samza jobs on
Mesos. This seems to be going well, and something we'd like to move away
from when native Mesos support is added to Samza.

While we're developing and testing our scheduler, I'm wondering about the
implications of running tasks with the ThreadJobFactory in "production".
The documentation advise against this, but it's not clear why.

If we were using the ThreadJobFactory inside of a docker container on Mesos
with Marathon for production, would be our main problem? These are not
particularly high-load tasks. Aside from not be able to get find-grained
resource scheduling per-task, it seems like the main issue the not being to
easily tell when a job stops due to error / exception.

In other words, what would be stop-stopping reasons to not use the
TreadJobFactory in production?


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