You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2009/01/07 03:45:44 UTC

[jira] Created: (HADOOP-4986) FSNamesystem.getBlockLocations sets access time without holding the namespace locks

FSNamesystem.getBlockLocations sets access time without holding the namespace locks
-----------------------------------------------------------------------------------

                 Key: HADOOP-4986
                 URL: https://issues.apache.org/jira/browse/HADOOP-4986
             Project: Hadoop Core
          Issue Type: Bug
          Components: dfs
    Affects Versions: 0.19.0
            Reporter: Tsz Wo (Nicholas), SZE
            Priority: Blocker


After the access time feature is added to HDFS, FSNamesystem.getBlockLocations(..) is no longer a read only namespace operation.  It changes the namespace by updating the access time.  However, the thread does not own namespace locks.  This may lead to namespace inconsistency.

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

[jira] Resolved: (HADOOP-4986) FSNamesystem.getBlockLocations sets access time without holding the namespace locks

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE resolved HADOOP-4986.
--------------------------------------------

    Resolution: Invalid

getBlockLocationsInternal is already synchronized.  How come I have missed this?

> FSNamesystem.getBlockLocations sets access time without holding the namespace locks
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-4986
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4986
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Priority: Blocker
>
> After the access time feature is added to HDFS, FSNamesystem.getBlockLocations(..) is no longer a read only namespace operation.  It changes the namespace by updating the access time.  However, the thread does not own namespace locks.  This may lead to namespace inconsistency.

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