[
https://issues.apache.org/jira/browse/HDFS-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618153#comment-16618153
]
Chao Sun commented on HDFS-13749:
---------------------------------
Thanks [~xkrogen]!
bq. is there any rational behind using 3 retries with 200ms sleep?
I basically cloned this from
[NameNodeProxies#createNNProxyWithNamenodeProtocol|https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/NameNodeProxies.java#L258]
but changed the retries from 5 to 3, since I found that the later increased
the latency a lot which might affect performance of DFS client reading from NN
when some NN node is not available. Let me know if this makes sense.
uploaded patch v4 to address the comments.
> 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, HDFS-13749-HDFS-12943.002.patch,
> HDFS-13749-HDFS-12943.003.patch, HDFS-13749-HDFS-12943.004.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]
