hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4225) FSEditLog logs modification time instead of access time.
Date Sat, 20 Sep 2008 01:29:46 GMT

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

Konstantin Shvachko updated HADOOP-4225:

    Attachment: LogATime.patch

I am not arguing about the semantics of the access time field, I am saying that when saving
it into the edits log you should save exactly that field rather than another one.
So, if you want to set accessTime to the value of the modificationTime you assign that value
to that field. But when you serialize accessTime in {{logOpenFile()}} to the disk you should
serialize that field rather than something else. I cannot even understand which of them (the
first or the second) corresponds to which time until I look at the loading code.
This is what I mean.

> FSEditLog logs modification time instead of access time.
> --------------------------------------------------------
>                 Key: HADOOP-4225
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4225
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Konstantin Shvachko
>            Priority: Blocker
>             Fix For: 0.19.0
>         Attachments: LogATime.patch
> ((FSEditLog.logOpenFile()}} does not persist accessTime but modificationTime instead.
Should be {{getAccessTime()}}.
> Introduced in HADOOP-1869.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message