Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 77322 invoked from network); 5 Jun 2008 23:15:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jun 2008 23:15:14 -0000 Received: (qmail 95443 invoked by uid 500); 5 Jun 2008 23:15:10 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 95409 invoked by uid 500); 5 Jun 2008 23:15:10 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 95398 invoked by uid 99); 5 Jun 2008 23:15:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 16:15:10 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 23:14:29 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4D27F234C132 for ; Thu, 5 Jun 2008 16:14:47 -0700 (PDT) Message-ID: <920367991.1212707687315.JavaMail.jira@brutus> Date: Thu, 5 Jun 2008 16:14:47 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3503) Race condition when client and namenode start block recovery simultaneously In-Reply-To: <1413233275.1212692384970.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602843#action_12602843 ] dhruba borthakur commented on HADOOP-3503: ------------------------------------------ This LOG calls occur only when the lease is recovered. This shud not happen too frequently. I would like to have some log messages to debug this code when it it occurs. Do you see a LOG message that occurs outside of lease recovery? > 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.