{"push_id":1573889664,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4661d30b988bf773ab45a15b143efb2908d33743","before":"37112fcfcd64db8f84f437e5c54cc3ea039c68f6","commits":[{"sha":"4661d30b988bf773ab45a15b143efb2908d33743","author":{"name":"Marcelo Vanzin","email":"31a02c4d82e3479e776883a3423bc52579c6a1cf@cloudera.com"},"message":"[SPARK-19554][UI,YARN] Allow SHS URL to be used for tracking in YARN RM.\n\nAllow an application to use the History Server URL as the tracking\nURL in the YARN RM, so there's still a link to the web UI somewhere\nin YARN even if the driver's UI is disabled. This is useful, for\nexample, if an admin wants to disable the driver UI by default for\napplications, since it's harder to secure it (since it involves non\ntrivial ssl certificate and auth management that admins may not want\nto expose to user apps).\n\nThis needs to be opt-in, because of the way the YARN proxy works, so\na new configuration was added to enable the option.\n\nThe YARN RM will proxy requests to live AMs instead of redirecting\nthe client, so pages in the SHS UI will not render correctly since\nthey'll reference invalid paths in the RM UI. The proxy base support\nin the SHS cannot be used since that would prevent direct access to\nthe SHS.\n\nSo, to solve this problem, for the feature to work end-to-end, a new\nYARN-specific filter was added that detects whether the requests come\nfrom the proxy and redirects the client appropriatly. The SHS admin has\nto add this filter manually if they want the feature to work.\n\nTested with new unit test, and by running with the documented configuration\nset in a test cluster. Also verified the driver UI is used when it's\nenabled.\n\nAuthor: Marcelo Vanzin <vanzin@cloudera.com>\n\nCloses #16946 from vanzin/SPARK-19554.","distinct":true,"url":"https://api.github.com/repos/apache/spark/commits/4661d30b988bf773ab45a15b143efb2908d33743"}]}
{"actor":{"display_login":"asfgit"}}