Hi Yan - I think this is slightly different. From the docs: "In the case of LocalJobRunner, it uses a run-container.sh script to execute the TaskRunner in a separate process, which will start one TaskRunner locally on the machine that you ran run-job.sh on.”
which means it will be in a separate jvm, although it will be local to the host where the job is running afaik. It still means that I would not be able to debug multiple tasks in the same debugger session, I think? Thanks Tyson On Apr 10, 2014, at 1:26 PM, Yan Fang <[email protected]> wrote: > Hi Tyson, > > If you change the YarnJobFactory to LocalJobRunner in configuration file, > Samza will run in local mode. > > http://samza.incubator.apache.org/learn/documentation/0.7.0/jobs/job-runner.html > > Thanks, > Fang, Yan > [email protected] > +1 (206) 849-4108 > > > On Thu, Apr 10, 2014 at 12:58 PM, Tyson Norris <[email protected]> wrote: > >> Hi - >> Is there an easy way to run tasks locally all within the same jvm to ease >> debugging? Or else, is there a good way to attach a debugger to separate >> task processes? >> >> I’m thinking something along the lines of Storm’s LocalCluster, where >> there is some emulation of separate processes but using threads within the >> same jvm. >> >> Thanks >> Tyson
