[GitHub] [spark] Ngone51 commented on issue #24375: [SPARK-25250][CORE] try best to not submit tasks when the partitions are already completed

[GitBox <gi...@apache.org>]

Ngone51 commented on issue #24375: [SPARK-25250][CORE] try best to not submit tasks when the partitions are already completed
URL: https://github.com/apache/spark/pull/24375#issuecomment-483499062
 
 
   > The issue cannot be 100% eliminated. Let's say task set 1.0 (zombie) has a running task for a partition, and task set 1.1 (active) has already submitted the task for the same partition and completed. Then there is nothing we can do.
   
   Though we have nothing to do with finding `1`, but what's wrong with it ?
   
   task in TSM 1.1(active) submitted and completed successfully, and TSM 1.0(zombie) has a running task for the same partition. So, task in TSM 1.0 (zombie) would fail later, but it do not have any impact on TSM 1.1(active), and TSM 1.0/1.1 would both finished normally.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org