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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2006/04/24 21:59:08 UTC

[jira] Updated: (HADOOP-162) concurrent modification exception in FSNamesystem.Lease.releaseLocks

     [ http://issues.apache.org/jira/browse/HADOOP-162?page=all ]

Owen O'Malley updated HADOOP-162:
---------------------------------

    Attachment: concurrent-mod-lease.patch

This patch moves the lease finding/updating code out of internalReleaseCreate and into abandonFileInProgress. releaseLocks clears the set itself.

> concurrent modification exception in FSNamesystem.Lease.releaseLocks
> --------------------------------------------------------------------
>
>          Key: HADOOP-162
>          URL: http://issues.apache.org/jira/browse/HADOOP-162
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Versions: 0.2
>     Reporter: Owen O'Malley
>     Assignee: Owen O'Malley
>  Attachments: concurrent-mod-lease.patch
>
> FSNameSystem.Lease.releaseLocks iterates through the creates set, calling InternalReleaseCreate on each element, which changes the creates set in the Lease. This causes a ConcurrentModificationException if you have more than two files that are owned by the lease that times out.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira