Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 15 Jul 2013 22:52:49 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12657184.1373502431589.54079.1373928769995@arcas>
In-Reply-To: <JIRA.12657184.1373502431589@arcas>
References: <JIRA.12657184.1373502431589@arcas>
Subject: [jira] [Commented] (HDFS-4979) Implement retry cache on the
 namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709105#comment-13709105 ] 

Suresh Srinivas commented on HDFS-4979:
---------------------------------------

I noticed that where I am setting boolean {{success}} to true in try blocks is susceptible to issues related to reordered writes. I am going to change them to AtomicBoolean in my next patch. Any one wants to take a stab at reviewing this patch?

bq. The above two cases are different because the return type is a comprehensive object. Hence instead of storing the object in retry cache, it is generated during retry attempts. In the following cases, return type is a simple object. Hence it results in simple handling with just void, string or boolean returned.
In order to save some memory, should we order complexity or just hold on to the previous response? Thoughts?

                
> Implement retry cache on the namenode
> -------------------------------------
>
>                 Key: HDFS-4979
>                 URL: https://issues.apache.org/jira/browse/HDFS-4979
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-4979.1.patch, HDFS-4979.2.patch, HDFS-4979.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira