Details
-
New Feature
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
3.0.0-beta1
-
None
-
None
Description
As discussed in HADOOP-13650, we want to add an S3Guard CLI command which compares S3 with MetadataStore, and returns a failure status if any invariants are violated.
Attachments
Issue Links
- is depended upon by
-
HADOOP-14936 S3Guard: remove "experimental" from documentation
- Resolved
-
HADOOP-15619 Über-JIRA: S3Guard Phase IV: Hadoop 3.3 features
- Resolved
- is related to
-
HADOOP-13936 S3Guard: DynamoDB can go out of sync with S3AFileSystem.delete()
- Resolved
- links to
1.
|
S3Guard fsck: Export MetadataStore and S3 bucket hierarchy | Open | Unassigned | |
2.
|
S3Guard fsck: Implement fixing mechanism for inconsistencies between S3 and MetadataStore | Open | Unassigned | |
3.
|
S3Guard fsck: Check metadata consistency from metadatastore to S3 (log) | Open | Unassigned | |
4.
|
Add fsck to S3A tests where additional diagnosis is needed | Open | Unassigned | |
5.
|
S3Guard fsck: Detect if a directory if authoritative and highlight errors if detected in it | Open | Unassigned | |
6.
|
S3Guarld fsck: Add docs to the first iteration (S3->ddbMS, -verify) | Open | Unassigned | |
7.
|
S3Guard fsck: Use enum instead of int for severity in violations | Open | Unassigned |