[GitHub] [arrow-ballista] yahoNanJing opened a new issue, #333: Executor get stopped unexpected

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

yahoNanJing opened a new issue, #333:
URL: https://github.com/apache/arrow-ballista/issues/333

   **Describe the bug**
   <!-- A clear and concise description of what the bug is. -->
   
   When restart an executor in a running ballista cluster, the executor's ip and port will not be changed. Only its id will be changed. After it gets started, the executor's old one will be detected of losing heartbeat and a stop executor request will be sent to this newly started executor. And this executor will be stopped unexpectedly.
   
   The executor should check whether the executor id in the request is the same as its id. If so, then stop itself. Otherwise, it should do nothing.
   
   **To Reproduce**
   <!-- Steps to reproduce the behavior: -->
   
   **Expected behavior**
   <!-- A clear and concise description of what you expected to happen. -->
   
   **Additional context**
   Add any other context about the problem here.
   


-- 
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: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-ballista] andygrove closed issue #333: Executor get stopped unexpected

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

andygrove closed issue #333: Executor get stopped unexpected
URL: https://github.com/apache/arrow-ballista/issues/333


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org