dongjoon-hyun commented on PR #44280: URL: https://github.com/apache/spark/pull/44280#issuecomment-1848903044
For this part, you are right. The driver recovery and app recovery are two additional separate issues which we need to address later. > But the worker doesn't send WorkerSchedulerStateResponse as expected to the master (because it doesn't receive MasterChanged correctly). When the recovering master receives WorkerSchedulerStateResponse, looks like it has some important steps to do like adding executor to application, etc. > I'm wondering, is it okay to skip WorkerSchedulerStateResponse and all these steps? This PR focuses only on `Worker recovery` and there is no regression from the `Driver or App` perspective because they will be deleted like the existing behavior, @viirya . -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
