Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overhaul jvm debug settings #162

Open
jvalkeal opened this issue Jun 28, 2019 · 0 comments
Open

Overhaul jvm debug settings #162

jvalkeal opened this issue Jun 28, 2019 · 0 comments

Comments

@jvalkeal
Copy link
Contributor

Currently what you can do is something like:

deployer.time.local.debugPort=8888
deployer.time.local.debugSuspend=n
deployer.log.local.debugPort=8889
deployer.log.local.debugSuspend=n

This has so many issues starting from a fact that each instance(if you deploy more than one) simply gets debug port by summing instance id. i.e. for time instance 0 it gets 8888 and instance 1 gets 8889. Then obviously first instance of log would fail as port is already in use. Behaviour is probably not documented at all.

Other thing is that these ports are not exposed anywhere other that what dataflow exposes as deployment properties. So it's impossible to know from dataflow rest api if debug was enabled for a particular instance and what was a port it was tried to assign. I think these debug settings needs to be exposed via runtime parameters so that we can query what is a possible debug target for a running app instances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant