[
https://issues.apache.org/jira/browse/YARN-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohith Sharma K S updated YARN-7662:
------------------------------------
Attachment: YARN-7662.02.patch
Updated patch with following changes
# changes is only for reader web app bind address so that both timeline server
and timeline reader can start in same machine. Rest all other configurations
can be reused!
# Introduced 3 additional configuration for timeline reader i.e
#* _yarn.timeline-service.reader.webapp.address_
#* _yarn.timeline-service.reader.webapp.https.address_ and
#* _yarn.timeline-service.reader.bind-host_.
# Default values for these configurations kept as same as older one to maintain
compatibility. These configurations can be used only when if someone wants to
use both TimelineServer and TimelineReader in same machine.
# I have also defined collector configurations but not *exposed* to user as of
now. These are defined as @Private.
#* _yarn.timeline-service.collector.webapp.address_
#* _yarn.timeline-service.collector.webapp.https.address_ and
#* _yarn.timeline-service.collector.bind-host_.
# For security login in reader and collector, hostname is considered from
webapp address rather rpc address because ATSv2 does not start RPC servers. So
it does not make sense to use RPC address configuration.
> [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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
