Affects Version/s: None
Fix Version/s: 0.13.0
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.
|Field||Original Value||New Value|
|Summary||heartbeat monitor thread goea away||heartbeat monitor thread goes away|
|Priority||Major [ 3 ]||Blocker [ 1 ]|
|Assignee||dhruba borthakur [ dhruba ]|
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Resolution||Fixed [ 1 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Fix Version/s||0.13.0 [ 12312348 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Component/s||dfs [ 12310710 ]|