You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2017/12/16 14:26:00 UTC
[jira] [Commented] (YARN-7662) [Atsv2] Define new set of
configurations for reader and collectors to bind.
[ https://issues.apache.org/jira/browse/YARN-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293825#comment-16293825 ]
Rohith Sharma K S commented on YARN-7662:
-----------------------------------------
I updated this JIRA summary to reflect to define new set of configurations for readers and collectors to bind.
> [Atsv2] Define new set of configurations for reader and collectors to bind.
> ---------------------------------------------------------------------------
>
> Key: YARN-7662
> URL: https://issues.apache.org/jira/browse/YARN-7662
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Attachments: YARN-7662.01.patch, YARN-7662.01.patch
>
>
> While starting Timeline Reader in secure mode, login happens using timeline.service.address even though timeline.service.bindhost is configured with 0.0.0.0. This causes exact principal name that matches address name to be present in keytabs.
> It is always better to login using getLocalHost that gives machine hostname which is configured in /etc/hosts unlike NodeManager does in serviceStart.
> And timeline.service.address is not required in non-secure mode, so its better to keep consistent in secure and non-secure mode
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org