[HDFS-11888] Ozone: SCM: use state machine for open containers allocated for key/blocks

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDFS-7240
• Fix Version/s: HDFS-7240
• Component/s: ozone
• Target Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Xiaoyu Yao
• Reporter: Xiaoyu Yao
• Created: 26/May/17 04:48
• Updated: 26/Apr/18 21:53
• Resolved: 23/Aug/17 19:39

Description

SCM BlockManager provision a pool of containers upon block creation request that can't be satisfied with current open containers in the pool. However, only one container is returned with the creationFlag to the client. The other container provisioned in the same batch will not have this flag. Client can't assume to use these containers that has not been created on SCM datanodes,

This ticket is opened to fix the issue by persist the createContainerNeeded flag for the provisioned containers. The flag will be eventually cleared by processing container report from datanode when the container report handler is fully implemented on SCM.

For now, we will use a default batch size of 1 for ozone.scm.container.provision_batch_size so that the container will be created on demand upon the first block allocation into the container.

Issue Links

• is related to: HDFS-12178 Ozone: OzoneClient: Handling SCM container creationFlag at client side