You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Bota (JIRA)" <ji...@apache.org> on 2019/08/06 11:03:00 UTC
[jira] [Commented] (HADOOP-16423) S3Guarld fsck: Check metadata
consistency from S3 to metadatastore (log)
[ https://issues.apache.org/jira/browse/HADOOP-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900897#comment-16900897 ]
Gabor Bota commented on HADOOP-16423:
-------------------------------------
Based on an offline discussion what's coming up:
* Severity added to the violation type enums (3 levels, defined in the enum)
* * eg. Etag mismatch is defined as serious but etag missing is defined as a warn
* Error messages added to the enums instead of the violation handler.
* Teardown in itests: close rawfs
> S3Guarld fsck: Check metadata consistency from S3 to metadatastore (log)
> ------------------------------------------------------------------------
>
> Key: HADOOP-16423
> URL: https://issues.apache.org/jira/browse/HADOOP-16423
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Gabor Bota
> Assignee: Gabor Bota
> Priority: Major
>
> This part is only for logging the inconsistencies.
> This issue only covers the part when the walk is being done in the S3 and compares all metadata to the MS.
> There will be no part where the walk is being done in the MS and compare it to the S3.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org