[SLIDER-1104] failed to track a outstanding request which was escalated

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Slider 0.81
• Component/s: appmaster
• Assignee: kyungwan nam
• Reporter: kyungwan nam
• Created: 27/Mar/16 04:27
• Updated: 11/May/17 17:38
• Resolved: 11/May/17 17:38

Description

when a outstanding request is escalated, the new container request, which has relaxed placement and a changed priority (the same node as the original one) will be sent.
because of relaxed placement, RM can allocate a container to a node which didn't specify in container request.
but, it is determined whether a outstanding request has been allocated only when the node in the allocated container is the same as the node in the outstanding request.
as a result, it will be failed to track the outstanding request, and Slider AM will keep the request which has already been allocated.
hear is Slider AM log when I met this problem.

2016-03-27 11:14:21,225 [AMRM Callback Handler Thread] INFO  appmaster.SliderAppMaster - onContainersAllocated(1)
2016-03-27 11:14:21,225 [AMRM Callback Handler Thread] DEBUG state.AppState - onContainersAllocated(): Total containers allocated = 1
2016-03-27 11:14:21,226 [AMRM Callback Handler Thread] DEBUG state.OutstandingRequestTracker - Processing allocation for role 1  on ContainerID=container_e14_1458884021812_0006_01_000004 nodeID=n1.mycompany.com:45454 http=n1.mycompany.com:8042 priority=1073741825 resource=<memory:1024, vCores:1>
2016-03-27 11:14:21,226 [AMRM Callback Handler Thread] WARN  state.OutstandingRequestTracker - No open request found for container ContainerID=container_e14_1458884021812_0006_01_000004 nodeID=n1.mycompany.com:45454 http=n1.mycompany.com:8042 priority=1073741825 resource=<memory:1024, vCores:1>, outstanding queue has 0 entries 
2016-03-27 11:14:21,226 [AMRM Callback Handler Thread] INFO  state.RoleHistory - Adding 1 hosts for role 1
2016-03-27 11:14:21,227 [AMRM Callback Handler Thread] WARN  state.AppState - Unexpected allocation of container ContainerID=container_e14_1458884021812_0006_01_000004 nodeID=n1.mycompany.com:45454 http=n1.mycompany.com:8042 priority=1073741825 resource=<memory:1024, vCores:1>
2016-03-27 11:14:21,227 [AMRM Callback Handler Thread] INFO  state.AppState - Assigning role HBASE_MASTER to container container_e14_1458884021812_0006_01_000004, on n1.mycompany.com:45454,

Issue Links

• duplicates: SLIDER-1224 the outstanding request that has been escalated is failed to cleanup