There was an interesting thread a while back from I believe the netflix guys about running ThreadJobFactory in production.
> On Mar 2, 2016, at 4:20 PM, Robert Crim <rjc...@gmail.com> wrote: > > Hi, > > 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? > > Thanks, > Rob
signature.asc
Description: Message signed with OpenPGP using GPGMail
