[
https://issues.apache.org/jira/browse/HADOOP-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-1205:
----------------------------------
Priority: Major (was: Blocker)
I hesitate to add a global lock to open since it will slowdown map/reduce jobs
when all tasks open a file in the beginning. I'd like to mark this issue as a
non-blocker for two reasons. First I do not think that the chance of getting
inconsistent data is high. Even if open may return inconsistent data, dfsClient
has a retry mechanism which allows it to recover from any error. Second Dhruba
is working on adding fine grain locks to dfs. This issue can be easily resolved
after his work is done.
> The open method of FSNamesystem should be synchronized
> ------------------------------------------------------
>
> Key: HADOOP-1205
> URL: https://issues.apache.org/jira/browse/HADOOP-1205
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.12.2
> Reporter: Hairong Kuang
> Fix For: 0.13.0
>
> Attachments: open.patch
>
>
> Method open accesses a shared data structure blockMap. If synchronization
> access is not enforced, open might return inconsistent results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
