[HDFS-12382] Ozone: SCM: BlockManager creates a new container for each allocateBlock call

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: HDFS-7240
• Component/s: ozone
• Target Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Nandakumar
• Reporter: Nandakumar
• Created: 31/Aug/17 20:11
• Updated: 26/Apr/18 21:53
• Resolved: 01/Sep/17 00:09

Description

StorageContainerManager's block protocol creates a new container for each allocate block call instead of using existing open containers. This behavior is not seen once the cluster is restarted.

When createContainer flag is set, the container state is changed from ALLOCATED to CREATING. But in refreshContainers call only ALLOCATED state is handled.

During restart loadAllocatedContainers loads the containers map properly, which fixes the issue after restart. But we will face the same issue later when we allocate new containers.

Issue Links

• is duplicated by: HDFS-12367 Ozone: Too many open files error while running corona