Description
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
Attachments
Attachments
Issue Links
- is depended upon by
-
YARN-7674 Update Timeline Reader web app address in UI2
- Resolved