[
https://issues.apache.org/jira/browse/MESOS-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133524#comment-15133524
]
Till Toenshoff commented on MESOS-4598:
---------------------------------------
Yes, I like the idea of using {{subprocess}} default environment for triggering
the PORT-removal - much less intrusive and irritating than my option.
Yes, {{executorEnvironment}} should'nt really have to deal in all details with
this.
For warning / erroring - fixing the problem for the user with a warning seems
rather nice.
Great suggestions Joseph!
> Logrotate ContainerLogger should not remove IP from environment.
> ----------------------------------------------------------------
>
> Key: MESOS-4598
> URL: https://issues.apache.org/jira/browse/MESOS-4598
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.27.0
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: mesosphere
>
> The {{LogrotateContainerLogger}} starts libprocess-using subprocesses.
> Libprocess initialization will attempt to resolve the IP from the hostname.
> If a DNS service is not available, this step will fail, which terminates the
> logger subprocess prematurely.
> Since the logger subprocesses live on the agent, they should use the same
> {{LIBPROCESS_IP}} supplied to the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
