[
https://issues.apache.org/jira/browse/HDFS-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171374#comment-14171374
]
Yongjun Zhang commented on HDFS-5194:
-------------------------------------
HI [~dep],
I was working on HDFS-7235 and found this jira, thanks for the great work you
have done here.
Some questions:
1. {{FsDatasetSpi}} currently has the {{@InterfaceAudience.Private}}
annotation, I assume it means we can still modify the FsDatasetSpi interface
and without breaking compatibility from external users' point of view, am I
correct?
2. For HDFS-7235, {{DataNode#transferBlock}} calls isValidBlock(), when it
returns false, DN reports the bad block to NN for some cases, and only send
error report back to NN for other cases. It failed to report bad block to NN
for the case described in HDFS-7235. I'm thinking about adding a new method
like {{needToReportInvalidBlock()}} to FsDatasetSpi, so when {{isValidBlock()}}
returns false, {{needToReportInvalidBlock()}} can be called to find out whether
DN need to report it as bad block. What do you think?
Thanks.
> Robust support for alternate FsDatasetSpi implementations
> ---------------------------------------------------------
>
> Key: HDFS-5194
> URL: https://issues.apache.org/jira/browse/HDFS-5194
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, hdfs-client
> Reporter: David Powell
> Assignee: David Powell
> Priority: Minor
> Attachments: HDFS-5194.design.01222014.pdf,
> HDFS-5194.design.09112013.pdf, HDFS-5194.patch.09112013
>
>
> The existing FsDatasetSpi interface is well-positioned to permit extending
> Hadoop to run natively on non-traditional storage architectures. Before this
> can be done, however, a number of gaps need to be addressed. This JIRA
> documents those gaps, suggests some solutions, and puts forth a sample
> implementation of some of the key changes needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
