Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 9 Feb 2012 05:14:00 +0000 (UTC)
From: "Eli Collins (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <820292803.18122.1328764440815.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2109195778.18105.1328764080327.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-2922) HA: close out operation categories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins updated HDFS-2922:
------------------------------

    Attachment: hdfs-2922.txt

Patch attached. Updates operations per the description (most are unchanged). Also:
- Remove warn in RetryInvocationHandler so it's just a debug so we don't log on every operation to an active that we failed over to
- Fix a couple spelling mistakes

                
> HA: close out operation categories
> ----------------------------------
>
>                 Key: HDFS-2922
>                 URL: https://issues.apache.org/jira/browse/HDFS-2922
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-2922.txt
>
>
> We need to close out the NN operations categories.
> The following operations should be left as is, ie not failover, as it's reasonable to call these on a standby, and we just need to update the TODO with a comment:
> - {{setSafeMode}} (Might want to force the standby out of safemode)
> - {{restoreFailedStorage}} (Might want to tell the standby to restore the shared edits dir)
> - {{saveNamespace}}, {{metaSave}} (Could imagine calling these on a standby eg in a recovery scenario)
> - {{refreshNodes}} (Decommissioning needs to refresh the standby)
> The following operations should be checked for READ, as neither should need to be called on standby, will failover unless stale reads are enabled:
> - {{getTransactionID}}, {{getEditLogManifest}} (we don't checkoint the standby)
> The following operations should be checked for WRITE, as they should not be called on a standby, ie should always failover:
> - {{finalizeUpgrade}}, {{distributedUpgradeProgress}} (should not be able to upgrade the standby)
> - {{setBalancerBandwidth}} (balancer should failover)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira