You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2017/01/25 09:55:29 UTC
[jira] [Reopened] (FLINK-5492) BootstrapTools log wrong address of
started ActorSystem
[ https://issues.apache.org/jira/browse/FLINK-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger reopened FLINK-5492:
-----------------------------------
I need to reopen this issue because one of the changes in this JIRA are not correct.
I now see the following in the TaskManager logs:
{code}
2017-01-25 09:45:41,289 INFO org.apache.flink.runtime.taskmanager.TaskManager - (Starting TaskManager actor system at {}:{}.,permanent-qa-cluster-master,0)
{code}
> BootstrapTools log wrong address of started ActorSystem
> -------------------------------------------------------
>
> Key: FLINK-5492
> URL: https://issues.apache.org/jira/browse/FLINK-5492
> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
>
> When starting an {{ActorSystem}} via the {{Bootstrap}} tools, then the {{startActorSystem}} function logs the IP resolved from the provided hostname as the {{ActorSystem}} address. However, then the function uses the unresolved hostname to start the {{ActorSystem}}. Since Akka matches the ActorSystem's address and the destination address of the incoming message we should log the URL which is used to start the {{ActorSystem}} and not the resolved IP (messages with the IP will usually be rejected).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)