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 "Nigel Daley (JIRA)" <ji...@apache.org> on 2008/03/31 23:58:24 UTC

[jira] Created: (HADOOP-3141) periodic ConcurrentModificationException in IPC Server

periodic ConcurrentModificationException in IPC Server
------------------------------------------------------

                 Key: HADOOP-3141
                 URL: https://issues.apache.org/jira/browse/HADOOP-3141
             Project: Hadoop Core
          Issue Type: Bug
          Components: ipc
    Affects Versions: 0.16.1
            Reporter: Nigel Daley


Seeing this exception in the Namenode log (429 of them yesterday alone)

2008-03-30 00:00:32,332 WARN org.apache.hadoop.ipc.Server: Exception in Responder java.util.ConcurrentModificationException
        at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
        at java.util.HashMap$KeyIterator.next(HashMap.java:827)
        at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010)
        at org.apache.hadoop.ipc.Server$Responder.run(Server.java:475)

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


[jira] Resolved: (HADOOP-3141) periodic ConcurrentModificationException in IPC Server

Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amar Kamat resolved HADOOP-3141.
--------------------------------

    Resolution: Duplicate

Duplicate of HADOOP-3010.

> periodic ConcurrentModificationException in IPC Server
> ------------------------------------------------------
>
>                 Key: HADOOP-3141
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3141
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.16.1
>            Reporter: Nigel Daley
>
> Seeing this exception in the Namenode log (429 of them yesterday alone)
> 2008-03-30 00:00:32,332 WARN org.apache.hadoop.ipc.Server: Exception in Responder java.util.ConcurrentModificationException
>         at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
>         at java.util.HashMap$KeyIterator.next(HashMap.java:827)
>         at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010)
>         at org.apache.hadoop.ipc.Server$Responder.run(Server.java:475)

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


[jira] Commented: (HADOOP-3141) periodic ConcurrentModificationException in IPC Server

Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583909#action_12583909 ] 

Raghu Angadi commented on HADOOP-3141:
--------------------------------------

I think this should be fixed in 0.16.3. It does look scary to the user though for now it does not do any harm.

> periodic ConcurrentModificationException in IPC Server
> ------------------------------------------------------
>
>                 Key: HADOOP-3141
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3141
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.16.1
>            Reporter: Nigel Daley
>
> Seeing this exception in the Namenode log (429 of them yesterday alone)
> 2008-03-30 00:00:32,332 WARN org.apache.hadoop.ipc.Server: Exception in Responder java.util.ConcurrentModificationException
>         at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
>         at java.util.HashMap$KeyIterator.next(HashMap.java:827)
>         at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010)
>         at org.apache.hadoop.ipc.Server$Responder.run(Server.java:475)

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