Currently when schedule execution to request to allocate slot from SlotPool, the TaskManagerLocation parameter is empty collection. So for task fail over scenario, the new execution attempt may be deployed to different task managers. If setting rockDB as state backend, the performance is better if the data can be restored from local machine. So we try to reuse the TaskManagerLocation of prior execution attempt when allocating slot from SlotPool. If the TaskManagerLocation is empty from prior executions, the behavior is the same with current status.