[jira] [Resolved] (HADOOP-16382) Clock skew can cause S3Guard to think object metadata is out of date

["Steve Loughran (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-16382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-16382.
-------------------------------------
    Resolution: Won't Fix

we just don't get enough information back. Be nice if an http response header always included clock time, but, well...

> Clock skew can cause S3Guard to think object metadata is out of date
> --------------------------------------------------------------------
>
>                 Key: HADOOP-16382
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16382
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When a S3Guard entry is added for an object, its last updated flag is taken from the local clock: if a getFileStatus is made immediately afterwards, the timestamp of the file from the HEAD may be > than the local time, so the DDB entry updated.
> This is even if the clocks are *close*. When updating an entry from S3, the actual timestamp of the file should be used to fix it, not local clocks



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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