You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "zhoukang (JIRA)" <ji...@apache.org> on 2019/06/06 05:15:00 UTC
[jira] [Commented] (SPARK-27068) Support failed jobs ui and
completed jobs ui use different queue
[ https://issues.apache.org/jira/browse/SPARK-27068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857291#comment-16857291 ]
zhoukang commented on SPARK-27068:
----------------------------------
[~srowen] Here is a use case in our cluster.
We have a long running spark sql thriftserver, and users use that as ad-hoc query engine and also for a online bi service.
Since failure number is not too large. But total query number will quickly increased as show in image below.
When we want to find the root cause for the failed query, currently is really not too convenience.
!屏幕快照 2019-06-06 下午1.12.04.png!
> Support failed jobs ui and completed jobs ui use different queue
> ----------------------------------------------------------------
>
> Key: SPARK-27068
> URL: https://issues.apache.org/jira/browse/SPARK-27068
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Affects Versions: 2.4.0
> Reporter: zhoukang
> Priority: Major
> Attachments: 屏幕快照 2019-06-06 下午1.12.04.png
>
>
> For some long running jobs,we may want to check out the cause of some failed jobs.
> But most jobs has completed and failed jobs ui may disappear, we can use different queue for this two kinds of jobs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org