hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-7101) Add config parameter to allow JHS to alway scan user dir irrespective of modTime
Date Tue, 12 Jun 2018 23:29:00 GMT

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

Arun Suresh updated MAPREDUCE-7101:
       Resolution: Fixed
    Fix Version/s: 3.2.0
           Status: Resolved  (was: Patch Available)

Thanks again for the patch [~tmarquardt].
Fixed the comment and checked into trunk and branch-2. (The prev jenkins failure was because
it picked the updated patch after I committed it)

> Add config parameter to allow JHS to alway scan user dir irrespective of modTime
> --------------------------------------------------------------------------------
>                 Key: MAPREDUCE-7101
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7101
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Assignee: Thomas Marquardt
>            Priority: Critical
>             Fix For: 2.10.0, 3.2.0
>         Attachments: MAPREDUCE-7101.001.patch, MAPREDUCE-7101.001.patch
> Currently, the JHS scan directory if the modification of *directory* changed: 
> {code} 
>     public synchronized void scanIfNeeded(FileStatus fs) {
>       long newModTime = fs.getModificationTime();
>       if (modTime != newModTime) {
>         <... omitted some logics ...>
>         // reset scanTime before scanning happens
>         scanTime = System.currentTimeMillis();
>         Path p = fs.getPath();
>         try {
>           scanIntermediateDirectory(p);
> {code}
> This logic relies on an assumption that, the directory's modification time will be updated
if a file got placed under the directory.
> However, the semantic of directory's modification time is not consistent in different
FS implementations. For example, MAPREDUCE-6680 fixed some issues of truncated modification
time. And HADOOP-12837 mentioned on S3, the directory's modification time is always 0.
> I think we need to revisit behavior of this logic to make it to more robustly work on
different file systems.

This message was sent by Atlassian JIRA

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

View raw message