hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koji Noguchi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1312) heartbeat monitor thread goes away
Date Tue, 01 May 2007 23:30:15 GMT

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

Koji Noguchi updated HADOOP-1312:

    Priority: Blocker  (was: Major)

Namenode  just prints to stderr(.out file)  and keeps on running without HeartbeatMonitor
As a result, namenode tries to assign blocks to the dead datanodes.

> heartbeat monitor thread goes away
> ----------------------------------
>                 Key: HADOOP-1312
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1312
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Priority: Blocker
> The heartbeat monitor thread encounters a ConcurrentModificationException while iterating
over the "heartbeats" data structure. This occurs when the namenode was getting restarted.
There are actuallt two bugs here:
> 1. The Heartbeat Monitor thread needs to catch Exceptions and continue, instead of exiting.
> 2. The heartbeats data structures is protected by the heartbeats lock. The registerDatanode()
method invokes removeDatanode() without acquiring the heartbeats monitor lock. This causes
the ConcurrentModificationException.

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

View raw message