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 2020/03/04 15:56:00 UTC
[jira] [Commented] (HADOOP-16507) S3Guard fsck: Add option to
configure severity (level) for the scan
[ https://issues.apache.org/jira/browse/HADOOP-16507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051353#comment-17051353 ]
Gabor Bota commented on HADOOP-16507:
-------------------------------------
Maybe worth to do this jira as well: https://issues.apache.org/jira/browse/HADOOP-16745
> S3Guard fsck: Add option to configure severity (level) for the scan
> -------------------------------------------------------------------
>
> Key: HADOOP-16507
> URL: https://issues.apache.org/jira/browse/HADOOP-16507
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Gabor Bota
> Assignee: Mukund Thakur
> Priority: Major
>
> There's the severity of Violation (inconsistency) defined in {{org.apache.hadoop.fs.s3a.s3guard.S3GuardFsck.Violation}}.
> This flag is only for defining the severity of the Violation, but not used to filter the scan for issue severity.
> The task to do: Use the severity level to define which issue should be logged and/or fixed during the scan.
> Note: the best way to avoid possible code duplication would be to not even add the consistency violation pair to the list of violations during the scan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org