hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Moved) (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (HADOOP-8236) haadmin should have configurable timeouts for failover commands
Date Sat, 31 Mar 2012 02:27:26 GMT

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

Todd Lipcon moved HDFS-3072 to HADOOP-8236:
-------------------------------------------

          Component/s:     (was: ha)
                       ha
     Target Version/s: 2.0.0  (was: 0.24.0)
    Affects Version/s:     (was: 0.24.0)
                       0.23.3
                  Key: HADOOP-8236  (was: HDFS-3072)
              Project: Hadoop Common  (was: Hadoop HDFS)
    
> haadmin should have configurable timeouts for failover commands
> ---------------------------------------------------------------
>
>                 Key: HADOOP-8236
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8236
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 0.23.3
>            Reporter: Philip Zeyliger
>            Assignee: Todd Lipcon
>
> The HAAdmin failover could should time out reasonably aggressively and go onto the fencing
strategies if it's dealing with a mostly dead active namenode.  Currently it uses what's probably
the default, which is to say no timeout whatsoever.
> {code}
>   /**
>    * Return a proxy to the specified target service.
>    */
>   protected HAServiceProtocol getProtocol(String serviceId)
>       throws IOException {
>     String serviceAddr = getServiceAddr(serviceId);
>     InetSocketAddress addr = NetUtils.createSocketAddr(serviceAddr);
>     return (HAServiceProtocol)RPC.getProxy(
>           HAServiceProtocol.class, HAServiceProtocol.versionID,
>           addr, getConf());
>   }
> {code}

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

        

Mime
View raw message