[ 
https://issues.apache.org/jira/browse/YARN-8774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tao Yang updated YARN-8774:
---------------------------
    Description: 
The cause is that the RMContainerImpl instance of reserved container lost its 
node label expression, when scheduler reserves containers for non-default 
node-label requests, it will be wrongly added into 
LeafQueue#ignorePartitionExclusivityRMContainers and never be removed.

To reproduce this memory leak:
(1) create reserved container
RegularContainerAllocator#doAllocation:  create RMContainerImpl instanceA 
(nodeLabelExpression="")
LeafQueue#allocateResource:  RMContainerImpl instanceA is put into  
LeafQueue#ignorePartitionExclusivityRMContainers
(2) allocate from reserved container
RegularContainerAllocator#doAllocation: create RMContainerImpl instanceB 
(nodeLabelExpression="test-label")
(3) From now on, RMContainerImpl instanceA will be left in memory (be kept in 
LeafQueue#ignorePartitionExclusivityRMContainers) forever until RM restarted

  was:
Reproduce memory leak:
(1) create reserved container
RegularContainerAllocator#doAllocation:  create RMContainerImpl instanceA 
(nodeLabelExpression="")
LeafQueue#allocateResource:  RMContainerImpl instanceA is put into  
LeafQueue#ignorePartitionExclusivityRMContainers
(2) allocate from reserved container
RegularContainerAllocator#doAllocation: create RMContainerImpl instanceB 
(nodeLabelExpression="test-label")
(3) From now on, RMContainerImpl instanceA will be left in memory (be kept in 
LeafQueue#ignorePartitionExclusivityRMContainers) forever until RM restarted


> Memory leak when CapacityScheduler allocates from reserved container with 
> non-default label
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-8774
>                 URL: https://issues.apache.org/jira/browse/YARN-8774
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Critical
>
> The cause is that the RMContainerImpl instance of reserved container lost its 
> node label expression, when scheduler reserves containers for non-default 
> node-label requests, it will be wrongly added into 
> LeafQueue#ignorePartitionExclusivityRMContainers and never be removed.
> To reproduce this memory leak:
> (1) create reserved container
> RegularContainerAllocator#doAllocation:  create RMContainerImpl instanceA 
> (nodeLabelExpression="")
> LeafQueue#allocateResource:  RMContainerImpl instanceA is put into  
> LeafQueue#ignorePartitionExclusivityRMContainers
> (2) allocate from reserved container
> RegularContainerAllocator#doAllocation: create RMContainerImpl instanceB 
> (nodeLabelExpression="test-label")
> (3) From now on, RMContainerImpl instanceA will be left in memory (be kept in 
> LeafQueue#ignorePartitionExclusivityRMContainers) forever until RM restarted



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to