Application Moved Back to the Original Queue After the ResourceManager Is Restarted?

Symptom

If an application is moved from one queue to another, the application moved back to the original queue after the ResourceManager is restarted.

Answer

This is a usage restriction of the ResourceManager. If an application is moved to another queue during running, the RM restarts and does not store the information about the new queue.

Assume that a user submits a MapReduce task to the leaf queue test11. The leaf queue test11 is deleted when the task is running. In this case, the submission queue automatically changes to the lost_and_found queue (tasks that are not included in queues are placed in the lost_and_found queue) and the task is suspended. To start the task, the user moves the task to the leaf queue test21. If the ResourceManager restarts, the displayed submission queue is lost_and_found instead of test21.

If the task is not complete, the ResourceManager only stores the queue information before the task is moved. To solve this problem, move the application again after the ResourceManager is restarted to write information about the new queue to the ResourceManager.