Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <320070519.1212704685173.JavaMail.jira@brutus>
Date: Thu, 5 Jun 2008 15:24:45 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (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


     [ 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.