[YARN-9807] ContainerAllocator re-creates RMContainer instance when allocate for ReservedContainer

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Target Version/s: 3.5.0
• Assignee: Yicong Cai
• Reporter: Yicong Cai
• Created: 02/Sep/19 12:55
• Updated: 04/Jan/24 08:36

Description

The ContainerAllocator re-creates the RMContainer instance when it is allocated to the ReservedContainer. This will cause the RMContainer to lose information from NEW to RESERVED.

RM Log

2019-08-28 18:42:30,320 [10645451] - INFO [SchedulerEventDispatcher:Event Processor:RMContainerImpl@486] - container_e47_1566978597856_2831_01_000007 Container Transitioned from NEW to RESERVED
2019-08-28 18:42:38,055 [10653186] - INFO [SchedulerEventDispatcher:Event Processor:AbstractContainerAllocator@126] - assignedContainer application attempt=appattempt_1566978597856_2831_000001 container=container_e47_1566978597856_2831_01_000007 queue=org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.allocator.RegularContainerAllocator@69f543b5 clusterResource=<memory:229806080, vCores:42240> type=NODE_LOCAL requestedPartition=label_ndir_2
2019-08-28 18:42:38,055 [10653186] - INFO [SchedulerEventDispatcher:Event Processor:RMContainerImpl@486] - container_e47_1566978597856_2831_01_000007 Container Transitioned from NEW to ALLOCATED