hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (JIRA)" <>
Subject [jira] [Commented] (HIVE-17362) The MAX_PREWARM_TIME should be configurable on HoS
Date Tue, 05 Sep 2017 09:32:02 GMT


Peter Vary commented on HIVE-17362:

I will be honest with you [~leftylev]: I am a developer, so it might be better if someone
more user oriented decides on this :) Where would a user look for this info? The *hive.prewarm.spark.timeout*
does not effect Tez. It only effects Spark, but the other prewarm parameters are used by both.
What do you recommend? I would happy to do it :)

> The MAX_PREWARM_TIME should be configurable on HoS
> --------------------------------------------------
>                 Key: HIVE-17362
>                 URL:
>             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

View raw message