[
https://issues.apache.org/jira/browse/HADOOP-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628376#action_12628376
]
rangadi edited comment on HADOOP-1869 at 9/4/08 9:50 AM:
--------------------------------------------------------------
Edit : its fine. getBlockLocations calls internal dir.setTimes().
Regd setTimes() implementation : We should have a private setTimes that does
not do security checks and audit logging since most common use is internal (as
in getBlockLocations()) . Security checks and logging is needed only when user
actively invokes setTimes().. btw, should it be setUTimes()? I haven't looked
at rest of the patch thoroughly.
was (Author: rangadi):
Regd setTimes() implementation : We should have a private setTimes that
does not do security checks and audit logging since most common use is internal
(as in getBlockLocations()) . Security checks and logging is needed only when
user actively invokes setTimes().. btw, should it be setUTimes()? I haven't
looked at rest of the patch thoroughly.
> access times of HDFS files
> --------------------------
>
> Key: HADOOP-1869
> URL: https://issues.apache.org/jira/browse/HADOOP-1869
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.19.0
>
> Attachments: accessTime1.patch, accessTime4.patch, accessTime5.patch,
> accessTime6.patch
>
>
> HDFS should support some type of statistics that allows an administrator to
> determine when a file was last accessed.
> Since HDFS does not have quotas yet, it is likely that users keep on
> accumulating files in their home directories without much regard to the
> amount of space they are occupying. This causes memory-related problems with
> the namenode.
> Access times are costly to maintain. AFS does not maintain access times. I
> thind DCE-DFS does maintain access times with a coarse granularity.
> One proposal for HDFS would be to implement something like an "access bit".
> 1. This access-bit is set when a file is accessed. If the access bit is
> already set, then this call does not result in a transaction.
> 2. A FileSystem.clearAccessBits() indicates that the access bits of all files
> need to be cleared.
> An administrator can effectively use the above mechanism (maybe a daily cron
> job) to determine files that are recently used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
