[
https://issues.apache.org/jira/browse/FLINK-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Pedersen updated FLINK-10449:
----------------------------------
Description:
After FLINK-8696, the second parameter of jobmanager.sh is interpreted as the
hostname. This ends up overriding the hostname in the docker entrypoint, making
the jobmanager reject all taskmanager messages as non-local recipients.
See also
[http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-1-5-4-issues-w-TaskManager-connecting-to-ResourceManager-td23298.html#a23310|http://example.com/]
was:
After FLINK-8696, the second parameter of jobmanager.sh is interpreted as the
hostname. This ends up overriding the hostname in the dockerfile, making the
jobmanager reject all taskmanager messages as non-local recipients.
See also
[http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-1-5-4-issues-w-TaskManager-connecting-to-ResourceManager-td23298.html#a23310|http://example.com]
> Docker flink hostname is locked to "cluster"
> --------------------------------------------
>
> Key: FLINK-10449
> URL: https://issues.apache.org/jira/browse/FLINK-10449
> Project: Flink
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.5.4
> Reporter: Mike Pedersen
> Priority: Major
>
> After FLINK-8696, the second parameter of jobmanager.sh is interpreted as
> the hostname. This ends up overriding the hostname in the docker entrypoint,
> making the jobmanager reject all taskmanager messages as non-local recipients.
> See also
> [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-1-5-4-issues-w-TaskManager-connecting-to-ResourceManager-td23298.html#a23310|http://example.com/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
