[
https://issues.apache.org/jira/browse/HADOOP-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371339#comment-15371339
]
Ray Chiang commented on HADOOP-13254:
-------------------------------------
We're getting dangerously close to wanting a design document for all of this.
Initially, the {{DiskValidator}} functionality was designed for the following:
# Being pluggable
# Gathering one or more write/read style checks under one class
# Saving metrics based on the class
As it was initially designed, it was meant to be a blocking call in the sense
that "return bad if it's not okay to write to the disk".
How defensive should the design be? I'd be okay with separate
{{DiskValidator}} and {{DiskValidatorService}} interfaces.
> Create framework for configurable disk checkers
> -----------------------------------------------
>
> Key: HADOOP-13254
> URL: https://issues.apache.org/jira/browse/HADOOP-13254
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: HADOOP-13254.001.patch, HADOOP-13254.002.patch,
> HADOOP-13254.003.patch, HADOOP-13254.004.patch, HADOOP-13254.005.patch,
> HADOOP-13254.006.patch, HADOOP-13254.007.patch, HADOOP-13254.008.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
