Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 4 May 2017 16:33:04 +0000 (UTC)
From: "Xuefu Zhang (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13067494.1493323623000.128208.1493915584136@Atlassian.JIRA>
In-Reply-To: <JIRA.13067494.1493323623000@Atlassian.JIRA>
References: <JIRA.13067494.1493323623000@Atlassian.JIRA> <JIRA.13067494.1493323623469@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HIVE-16552) Limit the number of tasks a Spark
 job may contain
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 May 2017 16:33:10 -0000


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

Xuefu Zhang commented on HIVE-16552:
------------------------------------

Committed to master. Thanks to Rui for the review.

> Limit the number of tasks a Spark job may contain
> -------------------------------------------------
>
>                 Key: HIVE-16552
>                 URL: https://issues.apache.org/jira/browse/HIVE-16552
>             Project: Hive
>          Issue Type: Improvement
>          Components: Spark
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16552.1.patch, HIVE-16552.2.patch, HIVE-16552.3.patch, HIVE-16552.4.patch, HIVE-16552.patch
>
>
> It's commonly desirable to block bad and big queries that takes a lot of YARN resources. One approach, similar to mapreduce.job.max.map in MapReduce, is to stop a query that invokes a Spark job that contains too many tasks. The proposal here is to introduce hive.spark.job.max.tasks with a default value of -1 (no limit), which an admin can set to block queries that trigger too many spark tasks.
> Please note that this control knob applies to a spark job, though it's possible that one query can trigger multiple Spark jobs (such as in case of map-join). Nevertheless, the proposed approach is still helpful.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)