[ 
https://issues.apache.org/jira/browse/SPARK-26288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716298#comment-16716298
 ] 

ASF GitHub Bot commented on SPARK-26288:
----------------------------------------

dongjoon-hyun edited a comment on issue #23243: 
[SPARK-26288][ExternalShuffleService]add initRegisteredExecutorsDB
URL: https://github.com/apache/spark/pull/23243#issuecomment-446083308
 
 
   Hi, @weixiuli . You can use `[CORE]` instead of `[ExternalShuffleService]` 
in the PR title.

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


> add initRegisteredExecutorsDB in ExternalShuffleService
> -------------------------------------------------------
>
>                 Key: SPARK-26288
>                 URL: https://issues.apache.org/jira/browse/SPARK-26288
>             Project: Spark
>          Issue Type: New Feature
>          Components: Kubernetes, Shuffle
>    Affects Versions: 2.4.0
>            Reporter: weixiuli
>            Priority: Major
>             Fix For: 2.4.0
>
>
> As we all know that spark on Yarn uses DB to record RegisteredExecutors 
> information which can be reloaded and used again when the 
> ExternalShuffleService is restarted .
> The RegisteredExecutors information can't be recorded both in the mode of 
> spark's standalone and spark on k8s , which will cause the 
> RegisteredExecutors information to be lost ,when the ExternalShuffleService 
> is restarted.
> To solve the problem above, a method is proposed and is committed .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to