[
https://issues.apache.org/jira/browse/HADOOP-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur resolved HADOOP-4866.
--------------------------------------
Resolution: Invalid
After reading the comments on this JIRA and aftrer some discussion with
Nicholas, we gathered that the infinite loop was probably created by a client
application that continuously tried to open/append to the file. A code
walk-through revealed that the DFSClient will attempt lease recovery 5 times
per replica for that node. After that, it throws an IO error to the
application. We also determined that the current patch is not required.
I am closing this issue for now, please feel free to reopen if you see it occur
again.
> NameNode error in commitBlockSynchronization
> --------------------------------------------
>
> Key: HADOOP-4866
> URL: https://issues.apache.org/jira/browse/HADOOP-4866
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Brian Bockelman
> Attachments: 4866_20081215.patch, 4866_20081216.patch,
> 4866_20081217.patch
>
>
> The NameNode continuously has an error in the commitBlockSynchronization.
> This happens for ~5 blocks at a rate of 5-10Hz. I have no idea when this
> started happening because this has been going on for days, well past the
> start of our current logs.
> This appears to be a new symptom in 0.19.0, but I have no idea what could be
> causing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
