[
https://issues.apache.org/jira/browse/HIVE-16552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996025#comment-15996025
]
Rui Li commented on HIVE-16552:
-------------------------------
[~xuefuz] thanks for the update. I think you can exclude the new test for
TestNegativeCliDriver because it's only for Spark. You should be able to do it
in:
{code}
public static class NegativeCliConfig extends AbstractCliConfig {
public NegativeCliConfig() {
super(CoreNegativeCliDriver.class);
try {
setQueryDir("ql/src/test/queries/clientnegative");
excludesFrom(testConfigProps, "minimr.query.negative.files");
excludeQuery("authorization_uri_import.q");
setResultsDir("ql/src/test/results/clientnegative");
setLogDir("itests/qtest/target/qfile-results/clientnegative");
setInitScript("q_test_init.sql");
setCleanupScript("q_test_cleanup.sql");
setHiveConfDir("");
setClusterType(MiniClusterType.none);
} catch (Exception e) {
throw new RuntimeException("can't construct cliconfig", e);
}
}
}
{code}
> 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
> Attachments: HIVE-16552.1.patch, HIVE-16552.2.patch,
> HIVE-16552.3.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)
