[
https://issues.apache.org/jira/browse/HIVE-14213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373913#comment-15373913
]
Siddharth Seth commented on HIVE-14213:
---------------------------------------
bq. Why do we need a separate set of config settings?
That's really only for the case where defaults are incorrect. A bunch of these
settings are common to multiple commands. e.g. the yarn logs command, or yarn
application -list would use the parameters for retry. Similarly various dfs
commands. I don't think the main config settings can be changed in
yarn-site/core-site just for this command - hence the new config variables.
bq. On the same note, if the component settings are already set, and the new
ones are not set, this will override them with defaults. Perhaps we can just
have the default constants for the original parameters (from YARN etc.), and
set them if not already set? If the user wants to change them they can just set
the originals too
Didn't quite understand this. If the new configs are set - they'll be used.
Otherwise the defaults will be used. The defaults are supposed to be good
enough.
> Add timeouts for various components in llap status check
> --------------------------------------------------------
>
> Key: HIVE-14213
> URL: https://issues.apache.org/jira/browse/HIVE-14213
> Project: Hive
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-14213.01.patch
>
>
> The llapstatus check connects to various compoennts - YARN, HDFS via Slider,
> ZooKeeper. If either of these components are down - the command can take a
> long time to exit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
