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
