hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17362) The MAX_PREWARM_TIME should be configurable on HoS
Date Tue, 05 Sep 2017 15:33:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153843#comment-16153843
] 

Xuefu Zhang commented on HIVE-17362:
------------------------------------

I think it's probably better to document  those params separately for tez and spark. First,
not all params are applicable to each engine. Secondly, the semantics of each param might
be slightly different for different engines.

> 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)

Mime
View raw message