hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2922) HA: close out operation categories
Date Thu, 09 Feb 2012 05:31:59 GMT

     [ 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

Yup, I see your points. Updated patch.
> 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, 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
> - {{saveNamespace}}, {{metaSave}} (Could imagine calling these on a standby eg in a recovery
> - {{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


View raw message