You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2017/09/05 05:08:00 UTC
[jira] [Commented] (HIVE-17362) The MAX_PREWARM_TIME should be
configurable on HoS
[ https://issues.apache.org/jira/browse/HIVE-17362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153112#comment-16153112 ]
Lefty Leverenz commented on HIVE-17362:
---------------------------------------
Doc note: This adds the configuration parameter *hive.prewarm.spark.timeout* to HiveConf.java. Thanks for documenting it in the wiki, [~pvary].
* [hive.prewarm.spark.timeout | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.prewarm.spark.timeout]
Question: Does it have anything to do with Tez? You put it in the Tez section because it belongs with *hive.prewarm.enabled* and *hive.prewarm.numcontainers* which are both Tez/Spark parameters but perhaps it belongs in the Spark section with just a crossreference from the Tez section.
> The MAX_PREWARM_TIME should be configurable on HoS
> --------------------------------------------------
>
> Key: HIVE-17362
> URL: https://issues.apache.org/jira/browse/HIVE-17362
> Project: Hive
> Issue Type: Improvement
> Components: Spark
> Affects Versions: 3.0.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Fix For: 3.0.0
>
> Attachments: HIVE-17362.2.patch, HIVE-17362.patch
>
>
> When using HIVE_PREWARM_ENABLED, we are waiting MAX_PREWARM_TIME for the containers to warm up. This is currently set to 5s. This is often not enough for a spark session to initialize the executors. We should be able to configure this, so we can set a value which has an effect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)