[
https://issues.apache.org/jira/browse/HDFS-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606286#comment-16606286
]
Erik Krogen commented on HDFS-13749:
------------------------------------
Thanks for looking into the proxy initialization, I appreciate the second set
of eyes there.
{quote}
I'm also not particularly happy with the hard-coded 30 sec timeout, As a
improvement, we can re-use {{ipc.client.rpc-timeout.ms}}. The same is also done
in {{NameNodeProxiesClient#createProxyWithAlignmentContext}}. What do you think?
{quote}
This sounds reasonable to me
> Use getServiceStatus to discover observer namenodes
> ---------------------------------------------------
>
> Key: HDFS-13749
> URL: https://issues.apache.org/jira/browse/HDFS-13749
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Major
> Attachments: HDFS-13749-HDFS-12943.000.patch,
> HDFS-13749-HDFS-12943.001.patch
>
>
> In HDFS-12976 currently we discover NameNode state by calling
> {{reportBadBlocks}} as a temporary solution. Here, we'll properly implement
> this by using {{HAServiceProtocol#getServiceStatus}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
