That would be pretty neat, in fact by modifying bin/flink-daemon.sh you'd
end up having all managers listening for a remote debugger and it would be
a problem if you want the JVM to suspend on start.

On Tue, May 17, 2016 at 2:22 PM, Greg Hogan <c...@greghogan.com> wrote:

> I also just modify the startup scripts but would it be better to have
> variants of env.java.opts specific to the JobManager, TaskManager, client,
> etc.?
>
> On Tue, May 17, 2016 at 5:24 AM, Stephan Ewen <se...@apache.org> wrote:
>
> > Hey Stefano!
> >
> > I think that question is bound to come up again. I created a page in the
> > Flink Wiki to document this.
> >
> > If you have a few moments, would be great if you could add your
> description
> > there:
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Remote+Debugging+of+Flink+Clusters
> > (it is linked from the front page
> > https://cwiki.apache.org/confluence/display/FLINK/Apache+Flink+Home )
> >
> > Greetings,
> > Stephan
> >
> >
> > On Tue, May 17, 2016 at 4:26 AM, Vijay Srinivasaraghavan <
> > vijikar...@yahoo.com.invalid> wrote:
> >
> > > Awesome, thanks Stefano!!
> > >
> > >     On Monday, May 16, 2016 9:57 AM, Stefano Baghino <
> > > stefano.bagh...@radicalbit.io> wrote:
> > >
> > >
> > >  I had to do it a couple of times. Wonderful experience to understand
> the
> > > inner workings of Flink and explore it while running.
> > > I don't know if there's a preferred way to do this but this is how I
> did
> > > it:
> > >
> > > Edit the run configurations in IntelliJ, click the + icon in the upper
> > left
> > > corner, choose the "Remote" preset.
> > > Under the "Settings" pane, fill in the remote host where you'll run
> > Flink.
> > > Copy the "Command line arguments for running remote JVM".
> > > Go to the machine running Flink, choose the launch script you need to
> > > "hijack" and append the copied arguments after the "java" command. Make
> > > sure to set "suspend=y" if you want to make sure Flink doesn't start
> > > without your debugger attached.
> > >
> > > Now simply run Flink with the script you tampered with and run the
> > > debugger. Please note that if you set "suspend=y" Flink won't start
> until
> > > the debugger is attached to the process. Also beware that if the
> machine
> > > running Flink is far away from the remote debugger you may suffer from
> > > increased latency when debugging.
> > >
> > > Hope I've been helpful, happy hacking. :)
> > >
> > > On Mon, May 16, 2016 at 6:43 PM, Vijay Srinivasaraghavan <
> > > vijikar...@yahoo.com.invalid> wrote:
> > >
> > > > How do I attach remote debugger to running Flink cluster from
> IntelliJ?
> > > > Appreciate if anyone could share the steps?
> > > > RegardsVijay
> > >
> > >
> > >
> > >
> > > --
> > > BR,
> > > Stefano Baghino
> > >
> > > Software Engineer @ Radicalbit
> > >
> > >
> > >
> > >
> >
>



-- 
BR,
Stefano Baghino

Software Engineer @ Radicalbit

Reply via email to