[jira] [Updated] (SPARK-22123) Add latest failure reason for task set blacklist
[
https://issues.apache.org/jira/browse/SPARK-22123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao updated SPARK-22123:
Priority: Minor (was: Major)
> Add latest failure reason for task set blacklist
>
>
> Key: SPARK-22123
> URL: https://issues.apache.org/jira/browse/SPARK-22123
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler, Spark Core
>Affects Versions: 2.1.0, 2.2.0
>Reporter: zhoukang
>Assignee: zhoukang
>Priority: Minor
> Fix For: 2.3.0
>
>
> Till now , every job which aborted by completed blacklist just show log like
> below which has no more information:
> {code:java}
> Aborting $taskSet because task $indexInTaskSet (partition $partition) cannot
> run anywhere due to node and executor blacklist. Blacklisting behavior cannot
> run anywhere due to node and executor blacklist.Blacklisting behavior can be
> configured via spark.blacklist.*."
> {code}
> We could add most recent failure reason for taskset blacklist which can be
> showed on spark ui to let user know failure reason directly.
> An example after modifying:
> {code:java}
> Aborting TaskSet 0.0 because task 0 (partition 0) cannot run anywhere due to
> node and executor blacklist.
> Most recent failure:
> Some(Lost task 0.1 in stage 0.0 (TID 3,xxx, executor 1):
> java.lang.Exception: Fake error!
> at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:73)
> at org.apache.spark.scheduler.Task.run(Task.scala:99)
> at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:305)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> ).
> Blacklisting behavior can be configured via spark.blacklist.*.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-22123) Add latest failure reason for task set blacklist
[
https://issues.apache.org/jira/browse/SPARK-22123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhoukang updated SPARK-22123:
-
Description:
Till now , every job which aborted by completed blacklist just show log like
below which has no more information:
{code:java}
Aborting $taskSet because task $indexInTaskSet (partition $partition) cannot
run anywhere due to node and executor blacklist. Blacklisting behavior cannot
run anywhere due to node and executor blacklist.Blacklisting behavior can be
configured via spark.blacklist.*."
{code}
We could add most recent failure reason for taskset blacklist which can be
showed on spark ui to let user know failure reason directly.
An example after modifying:
{code:java}
Aborting TaskSet 0.0 because task 0 (partition 0) cannot run anywhere due to
node and executor blacklist.
Most recent failure:
Some(Lost task 0.1 in stage 0.0 (TID 3,xxx, executor 1): java.lang.Exception:
Fake error!
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:73)
at org.apache.spark.scheduler.Task.run(Task.scala:99)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:305)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
).
Blacklisting behavior can be configured via spark.blacklist.*.
{code}
was:
Till now , every job which aborted by completed blacklist just show log like
below which has no more information:
{code:java}
Aborting $taskSet because task $indexInTaskSet (partition $partition) cannot
run anywhere due to node and executor blacklist. Blacklisting behavior cannot
run anywhere due to node and executor blacklist.Blacklisting behavior can be
configured via spark.blacklist.*."
{code}
We could add most recent failure reason for taskset blacklist which can be
showed on spark ui to let user know failure reason directly.
An example after modifying:
{code:java}
User class threw exception: org.apache.spark.SparkException: Job aborted due to
stage failure: Aborting TaskSet 0.0 because task 0 (partition 0) cannot run
anywhere due to node and executor blacklist. **Latest failure reason is**
Some(Lost task 0.1 in stage 0.0 (TID 3,xxx, executor 1): java.lang.Exception:
Fake error! at
org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:73) at
org.apache.spark.scheduler.Task.run(Task.scala:99) at
org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:305) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) ). Blacklisting behavior can be
configured via spark.blacklist.*. at
org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1458)
at
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1446)
at
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1445)
at
scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) at
org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1445) at
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
at
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
at scala.Option.foreach(Option.scala:257) at
org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:808)
at
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1681)
at
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1636)
at
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1625)
at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48) at
org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:634) at
org.apache.spark.SparkContext.runJob(SparkContext.scala:1922) at
org.apache.spark.SparkContext.runJob(SparkContext.scala:1935) at
org.apache.spark.SparkContext.runJob(SparkContext.scala:1948) at
org.apache.spark.SparkContext.runJob(SparkContext.scala:1962) at
org.apache.spark.rdd.RDD.count(RDD.scala:1157) at
org.apache.spark.examples.GroupByTest$.main(GroupByTest.scala:50) at
org.apache.spark.examples.GroupByTest.main(GroupByTest.scala) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
[jira] [Updated] (SPARK-22123) Add latest failure reason for task set blacklist
[
https://issues.apache.org/jira/browse/SPARK-22123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imran Rashid updated SPARK-22123:
-
Component/s: Scheduler
> Add latest failure reason for task set blacklist
>
>
> Key: SPARK-22123
> URL: https://issues.apache.org/jira/browse/SPARK-22123
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler, Spark Core
>Affects Versions: 2.1.0, 2.2.0
>Reporter: zhoukang
>
> Till now , every job which aborted by completed blacklist just show log like
> below which has no more information:
> {code:java}
> Aborting $taskSet because task $indexInTaskSet (partition $partition) cannot
> run anywhere due to node and executor blacklist. Blacklisting behavior cannot
> run anywhere due to node and executor blacklist.Blacklisting behavior can be
> configured via spark.blacklist.*."
> {code}
> We could add most recent failure reason for taskset blacklist which can be
> showed on spark ui to let user know failure reason directly.
> An example after modifying:
> {code:java}
> User class threw exception: org.apache.spark.SparkException: Job aborted due
> to stage failure: Aborting TaskSet 0.0 because task 0 (partition 0) cannot
> run anywhere due to node and executor blacklist. **Latest failure reason is**
> Some(Lost task 0.1 in stage 0.0 (TID 3,xxx, executor 1): java.lang.Exception:
> Fake error! at
> org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:73) at
> org.apache.spark.scheduler.Task.run(Task.scala:99) at
> org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:305) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745) ). Blacklisting behavior can be
> configured via spark.blacklist.*. at
> org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1458)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1446)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1445)
> at
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) at
> org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1445)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
> at scala.Option.foreach(Option.scala:257) at
> org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:808)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1681)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1636)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1625)
> at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48) at
> org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:634) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1922) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1935) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1948) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1962) at
> org.apache.spark.rdd.RDD.count(RDD.scala:1157) at
> org.apache.spark.examples.GroupByTest$.main(GroupByTest.scala:50) at
> org.apache.spark.examples.GroupByTest.main(GroupByTest.scala) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.spark.deploy.yarn.ApplicationMaster$$anon$2.run(ApplicationMaster.scala:653)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-22123) Add latest failure reason for task set blacklist
[
https://issues.apache.org/jira/browse/SPARK-22123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imran Rashid updated SPARK-22123:
-
Summary: Add latest failure reason for task set blacklist (was: Add latest
failure reason for task set blacklis)
> Add latest failure reason for task set blacklist
>
>
> Key: SPARK-22123
> URL: https://issues.apache.org/jira/browse/SPARK-22123
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
>Affects Versions: 2.1.0, 2.2.0
>Reporter: zhoukang
>
> Till now , every job which aborted by completed blacklist just show log like
> below which has no more information:
> {code:java}
> Aborting $taskSet because task $indexInTaskSet (partition $partition) cannot
> run anywhere due to node and executor blacklist. Blacklisting behavior cannot
> run anywhere due to node and executor blacklist.Blacklisting behavior can be
> configured via spark.blacklist.*."
> {code}
> We could add most recent failure reason for taskset blacklist which can be
> showed on spark ui to let user know failure reason directly.
> An example after modifying:
> {code:java}
> User class threw exception: org.apache.spark.SparkException: Job aborted due
> to stage failure: Aborting TaskSet 0.0 because task 0 (partition 0) cannot
> run anywhere due to node and executor blacklist. **Latest failure reason is**
> Some(Lost task 0.1 in stage 0.0 (TID 3,xxx, executor 1): java.lang.Exception:
> Fake error! at
> org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:73) at
> org.apache.spark.scheduler.Task.run(Task.scala:99) at
> org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:305) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745) ). Blacklisting behavior can be
> configured via spark.blacklist.*. at
> org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1458)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1446)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1445)
> at
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) at
> org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1445)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
> at
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:808)
> at scala.Option.foreach(Option.scala:257) at
> org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:808)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1681)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1636)
> at
> org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1625)
> at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48) at
> org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:634) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1922) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1935) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1948) at
> org.apache.spark.SparkContext.runJob(SparkContext.scala:1962) at
> org.apache.spark.rdd.RDD.count(RDD.scala:1157) at
> org.apache.spark.examples.GroupByTest$.main(GroupByTest.scala:50) at
> org.apache.spark.examples.GroupByTest.main(GroupByTest.scala) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.spark.deploy.yarn.ApplicationMaster$$anon$2.run(ApplicationMaster.scala:653)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
