You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Currently what you can do is something like:
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 gets8889
. 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.
The text was updated successfully, but these errors were encountered: