Bharat Viswanadham commented on HDDS-156:

+1 LGTM.( Check style issues need to be fixed)

> Implement HDDSVolume to manage volume state
> -------------------------------------------
>                 Key: HDDS-156
>                 URL: https://issues.apache.org/jira/browse/HDDS-156
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>             Fix For: 0.2.1
>         Attachments: HDDS-156-HDDS-48.001.patch, HDDS-156-HDDS-48.002.patch, 
> HDDS-156-HDDS-48.003.patch, HDDS-156-HDDS-48.004.patch
> This Jira proposes the following:
>  # Implement HDDSVolume to encompass VolumeInfo along with other HDDS 
> specific fields.
>  ** VolumeInfo container disk specific information such as capacity, usage, 
> storageType. HddsVolume has hdds specific fields for volume such as 
> VolumeState, VolumeStats (will be added later).
>  # Write volume level Version file 
>  ** clusterID, storageID, datanodeUUID, creationTime and layoutVersion.
>  # Read Version file while instantiating HDDSVolumes.
>  ** When the volume Version file already exists (for example, when a DN is 
> restarted), then the version file is read for the stored clusterID, 
> datanodeUuid, lahyoutVersion etc. Some checks will be performed to verify the 
> sanity of the volume.
>  ** When a fresh Datanode is started, the Version file is not written to the 
> volume uptill the clusterID is received from the SCM.

This message was sent by Atlassian JIRA

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

Reply via email to