You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2009/09/09 05:03:57 UTC

[jira] Updated: (HDFS-606) ConcurrentModificationException in invalidateCorruptReplicas()

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

Konstantin Shvachko updated HDFS-606:
-------------------------------------

    Attachment: CMEinCorruptReplicas.patch

This is a rather obvious patch, which makes a copy of the list before iterating.
Should not require any new tests, because this condition is hardly testable at all.

> ConcurrentModificationException in invalidateCorruptReplicas()
> --------------------------------------------------------------
>
>                 Key: HDFS-606
>                 URL: https://issues.apache.org/jira/browse/HDFS-606
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>             Fix For: 0.21.0
>
>         Attachments: CMEinCorruptReplicas.patch
>
>
> {{BlockManager.invalidateCorruptReplicas()}} iterates over DatanodeDescriptor-s while removing corrupt replicas from the descriptors. This causes {{ConcurrentModificationException}} if there is more than one replicas of the block. I ran into this exception debugging different scenarios in append, but it should be fixed in the trunk too.

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