It appears that when running Flink 1.1.1 on Yarn, my previous method of making a request to the yarn AM proxy on the master node at http://{master_node}:20888/proxy/{app_id}/jobmanager/config doesn't work the same as it did.
Previously, the returned JSON value would include an accurate value for "jobmanager.web.port". Now, however, it appears to return a zero. As a result, I cannot expose the JobManager UI itself. I can use the Yarn proxy but it does not support the useful feature of uploading JARs. Is there another way of determining which port the JobManager is running on? Thanks! -Shannon
