[
https://issues.apache.org/jira/browse/SPARK-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-17917:
------------------------------
Priority: Minor (was: Major)
Maybe, I suppose it will be a little tricky to define what the event is here,
since the event is that something didn't happen. Still, whatever is triggering
the log might reasonably trigger an event. I don't have a strong feeling on
this partly because I'm not sure what the action then is -- kill the job?
> Convert 'Initial job has not accepted any resources..' logWarning to a
> SparkListener event
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-17917
> URL: https://issues.apache.org/jira/browse/SPARK-17917
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Mario Briggs
> Priority: Minor
>
> When supporting Spark on a multi-tenant shared large cluster with quotas per
> tenant, often a submitted taskSet might not get executors because quotas have
> been exhausted (or) resources unavailable. In these situations, firing a
> SparkListener event instead of just logging the issue (as done currently at
> https://github.com/apache/spark/blob/9216901d52c9c763bfb908013587dcf5e781f15b/core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala#L192),
> would give applications/listeners an opportunity to handle this more
> appropriately as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
