hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13749) Use getServiceStatus to discover observer namenodes
Date Thu, 30 Aug 2018 22:37:00 GMT

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

Konstantin Shvachko commented on HDFS-13749:
--------------------------------------------

Hey [~csun], this should probably go on top of Erik's changes in HDFS-13779. I believe with
that you will need only to change the implementation of {{getServiceState()}}. Team work :-)

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