Thanks Chesnay. I had a look at how the JMX representation looks like when I look at a Task Manager which has one of the example Jobs deployed (https://ci.apache.org/projects/flink/flink-docs-release-1.1/quickstart/run_example_quickstart.html) and this looks correct. I assume at this point that the naming gets confused because I am having multiple sinks in my Job and more than one operator on the same stream. Maybe this is not expected and I should only have one operator and one sink per Job ? However the job itself does what it is supposed to so I would only change this for the monitoring as it stands right now. Also it seems to make a difference when things are happening in the job. I had a print (sink) of the wikipedia source stream right at after the source is read and after moving this print statement to the very end of the job class the representation in JMX changes. I would expect the naming of sinks and operators to be always the same regardless of when they happen, no ?
Thanks Philipp -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Task-and-Operator-Monitoring-via-JMX-naming-tp9560p9600.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
