hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao Sun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13749) Use getServiceStatus to discover observer namenodes
Date Wed, 05 Sep 2018 22:12:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605002#comment-16605002
] 

Chao Sun commented on HDFS-13749:
---------------------------------

Attached patch v1. [~xkrogen]: turns out it's not easy to reuse {{NameNodeProxies}} since
it is in a different module. Here I still called {{HAServiceProtocolClientSideTranslatorPB}}
but it is semantically the same as what {{NameNodeProxies}} does.

> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message