[
https://issues.apache.org/jira/browse/HIVE-16000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanth Jayachandran updated HIVE-16000:
-----------------------------------------
Description:
Follow up for HIVE-15971 (based on
https://issues.apache.org/jira/browse/HIVE-15971?focusedCommentId=15876814&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15876814)
1) Make NodeManager web address port available via ServiceInstance or something
better (other than reading from configuration)
2) When llap node goes down log URL cannot be constructed since we rely on
information from service registry. Instead YARN NodeId can be extended to
provided necessary information (container id) for constructing the log url.
was:
Follow up for HIVE-15971
1) Make NodeManager web address port available via ServiceInstance or something
better (other than reading from configuration)
2) When llap node goes down log URL cannot be constructed since we rely on
information from service registry. Instead YARN NodeId can be extended to
provided necessary information (container id) for constructing the log url.
> LLAP: LLAP log urls improvements
> --------------------------------
>
> Key: HIVE-16000
> URL: https://issues.apache.org/jira/browse/HIVE-16000
> Project: Hive
> Issue Type: Bug
> Components: llap
> Affects Versions: 2.2.0
> Reporter: Prasanth Jayachandran
>
> Follow up for HIVE-15971 (based on
> https://issues.apache.org/jira/browse/HIVE-15971?focusedCommentId=15876814&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15876814)
> 1) Make NodeManager web address port available via ServiceInstance or
> something better (other than reading from configuration)
> 2) When llap node goes down log URL cannot be constructed since we rely on
> information from service registry. Instead YARN NodeId can be extended to
> provided necessary information (container id) for constructing the log url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
