[HDDS-733] Create container if not exist, as part of chunk write

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4.0
• Component/s: Ozone Datanode
• Target Version/s: 0.4.0
• Assignee: Lokesh Jain
• Reporter: Nandakumar
• Created: 25/Oct/18 08:50
• Updated: 09/Nov/18 19:03
• Resolved: 09/Nov/18 18:50

Description

The current implementation requires a container to be created in datanode before starting the chunk write. This can be optimized by creating the container on the first chunk write.
During chunk write, if the container is missing, we can go ahead and create the container.

Along with this change ALLOCATED and CREATING container states can be removed as they were used to track which containers have been successfully created. Also there is a shouldCreateContainer flag which is used by client to know if it needs to create container. This flag can be removed.

Issue Links

• is required by: HDDS-734 Remove create container logic from OzoneClient