[
https://issues.apache.org/jira/browse/HDFS-15028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986070#comment-16986070
]
Masatake Iwasaki edited comment on HDFS-15028 at 12/2/19 2:09 PM:
------------------------------------------------------------------
The capacity is given by statvfs via java.io.File#getTotalSpace. It would be
nice if you have a number how much the overhead is reduced by the change.
Currently we can change the size of volume and underlying file system without
restarting DataNode (e.g. running on Amazon EC2 with EBS volumes). Should the
fix be configurable and disabled by default to keep current behavior?
was (Author: iwasakims):
The capacity is given by statvfs system call via java.io.File#getTotalSpace. It
would be nice if you have a number how much the overhead is reduced by the
change.
Currently we can change the size of volume and underlying file system without
restarting DataNode (e.g. running on Amazon EC2 with EBS volumes). Should the
fix be configurable and disabled by default to keep current behavior?
> Keep the capacity of volume and reduce a system call
> ----------------------------------------------------
>
> Key: HDFS-15028
> URL: https://issues.apache.org/jira/browse/HDFS-15028
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Yang Yun
> Assignee: Yang Yun
> Priority: Minor
> Attachments: HDFS-15028.patch
>
>
> The local volume is not changed. so keep the first value of the capacity and
> reuse for each heartbeat．
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
