Executor get stopped unexpected

[yahoNanJing]

Describe the bug

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

Expected behavior

Additional context
Add any other context about the problem here.