A followup (in case anyone is interested): we worked around this by making a
request to the "/jars" endpoint of the UI. The response has an attribute called
"address" which includes the DNS name and port where the UI is accessible.
Hi Shannon,
the problem is that YARNs proxy only allows GET HTTP requests, but for
uploading files, a different request type is needed.
I've filed a JIRA for the problem you've reported:
https://issues.apache.org/jira/browse/FLINK-4432
Regards,
Robert
On Mon, Aug 15, 2016 at 6:03 PM, Shannon Ca
Thanks Ufuk. For now, we will use the Yarn AM proxy.
About uploading JARs: the JobManager UI that is exposed via the Yarn AM proxy
does not allow manually uploading Flink job jars for execution on the cluster
(look for "Yarn's AM proxy doesn't allow file uploads." in the code). As I
understand
I've verified this. I think this has likely accidentally changed with
the refactoring of the YARN setup for Flink 1.1. We probably wrote the
web monitor port explicitly to the config in 1.0 whereas we don't do
it in 1.1 anymore. I think this should be addressed with the next
bugfix release 1.1.2.
Hey Shannon! I just took a look at the code and it looks like the
Flink REST handler for the config did _not_ change since last year. It
could be that somehow the config is loaded differently. Can you verify
that using the same config with Flink 1.0 and Flink 1.1 the port is
printed correctly and a
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 fo
