[
https://issues.apache.org/jira/browse/HDDS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470104#comment-16470104
]
Shashikant Banerjee commented on HDDS-38:
-----------------------------------------
Thanks [~anu], for the review comments.
Datanode currently sends the list of volumes with usage and free space info.
At SCM, even if we detect that a certain volume is full, there is no corrective
action to be taken at SCM for this. If a volume gets full, once the particular
datanode is choosen, the decision to not place a container on the disk can be
taken at the datanode itself. Also, diskBalancing decision should to be taken
at dataNode.
I think while sending the storage report, datanode itself can send list of full
volumes as well as failed volumes in case we want to display these on SCM UI
and adjust the overall scmNodeStat accordingly. The problem here i see is, for
each storage we use storageUUID as the identifier for the particular volume
currently and SCM is not aware of the mapping between the storageUUIDs and the
data dirs these UUIDs map to. In case, we want to display full volumes or
failed volumes, we should show up the actual data dir paths instead of
storageUUIDs at SCM.
Let me know your thoughts on this.
> Add SCMNodeStorage map in SCM class to store storage statistics per Datanode
> ----------------------------------------------------------------------------
>
> Key: HDDS-38
> URL: https://issues.apache.org/jira/browse/HDDS-38
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-38.00.patch
>
>
> Currently , the storage stats per Datanode are maintained inside
> scmNodeManager. This will
> move the scmNodeStats for storage outside SCMNodeManager to simplify
> refactoring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
