GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/1280
[FLINK-2878] [webmonitor] Fix unexpected leader address pattern
The HandlerRedirectUtils.getRedirectAddress decides whether the retrieved
leader address is equal to the local job manager address. The local job manager
address is, however, in the form akka.tcp://flink@url/user/jobmanager whereas
the leader address can be akka://flink/user/jobmanager if the local job manager
is the current leader. Such a case produced a warning which is not correct.
This PR checks for the local job manager address and signals that no
redirection has to be done if it receives akka://flink/user/jobmanager.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink
fixUnexpectedLeaderAddressPattern
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1280.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1280
----
commit c5e09728f48510100e741230903bd7f354f9770f
Author: Till Rohrmann <[email protected]>
Date: 2015-10-21T13:35:02Z
[FLINK-2878] [webmonitor] Fix unexpected leader address pattern
The HandlerRedirectUtils.getRedirectAddress decides whether the retrieved
leader address is equal to the local job manager address. The local job manager
address is, however, in the form akka.tcp://flink@url/user/jobmanager whereas
the leader address can be akka://flink/user/jobmanager if the local job manager
is the current leader. Such a case produced a warning which is not correct.
This PR checks for the local job manager address and signals that no
redirection has to be done if it receives akka://flink/user/jobmanager.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
