[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

["Gabor Bota (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734126#comment-16734126 ] 

Gabor Bota commented on HADOOP-15999:
-------------------------------------

I'm going to fix geFileStatus: if S3Guard is not in authoritative mode, we should check S3 for filestatus as well. If the metadata from S3 is more recent than what we have on the MS, we should update the MS and return the fresher metadata from S3.
I will extend this with inconsistency detection metrics in HADOOP-15779. Also, if we are not running in authoritative mode, all operations will be slower.

If MS is authoritative, then we don't have to read S3. Adding more config knobs to this would make this thing over-complicated.

There should be an fsck op to sync things (you are right [~stevel@apache.org]), so if a customer runs with S3Guard auth mode and let's say they made some out-of-band operation like a delete without ms, there's a way to sync with the tool.

Note: if there's an out-of-band operation right now it's easier to remove the whole ms with prune then handling ms ddb records one by one.


> [s3a] Better support for out-of-band operations
> -----------------------------------------------
>
>                 Key: HADOOP-15999
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15999
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.0
>            Reporter: Sean Mackrory
>            Assignee: Gabor Bota
>            Priority: Major
>         Attachments: out-of-band-operations.patch
>
>
> S3Guard was initially done on the premise that a new MetadataStore would be the source of truth, and that it wouldn't provide guarantees if updates were done without using S3Guard.
> I've been seeing increased demand for better support for scenarios where operations are done on the data that can't reasonably be done with S3Guard involved. For example:
> * A file is deleted using S3Guard, and replaced by some other tool. S3Guard can't tell the difference between the new file and delete / list inconsistency and continues to treat the file as deleted.
> * An S3Guard-ed file is overwritten by a longer file by some other tool. When reading the file, only the length of the original file is read.
> We could possibly have smarter behavior here by querying both S3 and the MetadataStore (even in cases where we may currently only query the MetadataStore in getFileStatus) and use whichever one has the higher modified time.
> This kills the performance boost we currently get in some workloads with the short-circuited getFileStatus, but we could keep it with authoritative mode which should give a larger performance boost. At least we'd get more correctness without authoritative mode and a clear declaration of when we can make the assumptions required to short-circuit the process. If we can't consider S3Guard the source of truth, we need to defer to S3 more.
> We'd need to be extra sure of any locality / time zone issues if we start relying on mod_time more directly, but currently we're tracking the modification time as returned by S3 anyway.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org