[
https://issues.apache.org/jira/browse/HDDS-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793854#comment-16793854
]
Xiaoyu Yao commented on HDDS-1163:
----------------------------------
Thanks [~sdeka] for the work. Just have a question about the purpose of
inMemContainerData in KeyValueContainerCheck. I see it is passed in by the
production code and unit test with non-null value but never get used in the
actual checking process. This was flagged as a checkstyle warning in our
nightly run. Maybe we can remove it for now and add it back when it is ready to
be consumed? Feel free to reassign
https://issues.apache.org/jira/browse/HDDS-1292 for the fix.
> Basic framework for Ozone Data Scrubber
> ---------------------------------------
>
> Key: HDDS-1163
> URL: https://issues.apache.org/jira/browse/HDDS-1163
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Fix For: 0.5.0
>
> Attachments: HDDS-1163.000.patch, HDDS-1163.001.patch,
> HDDS-1163.002.patch, HDDS-1163.003.patch, HDDS-1163.004.patch,
> HDDS-1163.005.patch, HDDS-1163.006.patch, HDDS-1163.007.patch
>
>
> Included in the scope:
> 1. Background scanner thread to iterate over container set and dispatch check
> tasks for individual containers
> 2. Fixed rate scheduling - dispatch tasks at a pre-determined rate (for
> example 1 container/s)
> 3. Check disk layout of Container - basic check for integrity of the
> directory hierarchy inside the container, include chunk directory and
> metadata directories
> 4. Check container file - basic sanity checks for the container metafile
> 5. Check Block Database - iterate over entries in the container block
> database and check for the existence and accessibility of the chunks for each
> block.
> Not in scope (will be done as separate subtasks):
> 1. Dynamic scheduling/pacing of background scan based on system load and
> available resources.
> 2. Detection and handling of orphan chunks
> 3. Checksum verification for Chunks
> 4. Corruption handling - reporting (to SCM) and subsequent handling of any
> corruption detected by the scanner. The current subtask will simply log any
> corruption which is detected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
