[ https://issues.apache.org/jira/browse/HADOOP-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HADOOP-3503: ------------------------------------------- Hadoop Flags: [Reviewed] +1 codes look good. Are you sure you want to change several calls from LOG.debug(...) to LOG.info(...)? > Race condition when client and namenode start block recovery simultaneously > --------------------------------------------------------------------------- > > Key: HADOOP-3503 > URL: https://issues.apache.org/jira/browse/HADOOP-3503 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.18.0 > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: pingPong.patch > > > When a client detects a error while writing to a block, it starts the > generation-stamp-protocol to remove stale replicas. At the same time, if the > namenode experiences a lease expiry event for that file, the namenode starts > the generation-stamp-protocol for the same block. Now, the client and thr > namenode ping-pongs trying to stamp the block replicas. This ping-pong can > continue for a long time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.