[ https://issues.apache.org/jira/browse/YARN-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295155#comment-16295155 ]
Varun Saxena commented on YARN-7662: ------------------------------------ [~rohithsharma], thanks for the latest patch. As we have already released ATSv2 and the addresses depend on yarn.timeline-service.bind-host, to maintain backward compatibility, we should fall back to it if yarn.timeline-service.reader/collector.bind-host is not set > [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, > YARN-7662.02.patch, YARN-7662.03.patch, YARN-7662.04.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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org