[FLINK-9351] RM stop assigning slot to Job because the TM killed before connecting to JM successfully

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Component/s: Runtime / Coordination
• Assignee: Sihua Zhou
• Reporter: Sihua Zhou
• Created: 14/May/18 05:40
• Updated: 02/Jul/18 16:25
• Resolved: 02/Jul/18 14:54

Description

The steps are the following(copied from Stephan's comments in 5931):

• JobMaster / SlotPool requests a slot (AllocationID) from the ResourceManager
• ResourceManager starts a container with a TaskManager
• TaskManager registers at ResourceManager, which tells the TaskManager to push a slot to the JobManager.
• TaskManager container is killed
• The ResourceManager does not queue back the slot requests (AllocationIDs) that it sent to the previous TaskManager, so the requests are lost and need to time out before another attempt is tried.

Issue Links

• links to: GitHub Pull Request #6133