Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 26 Aug 2017 06:53:02 +0000 (UTC)
From: "Elek, Marton (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13096465.1503331280000.127849.1503730382212@Atlassian.JIRA>
In-Reply-To: <JIRA.13096465.1503331280000@Atlassian.JIRA>
References: <JIRA.13096465.1503331280000@Atlassian.JIRA> <JIRA.13096465.1503331280266@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12333) Ozone: Extend Datanode web
 interface with SCM information
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 26 Aug 2017 06:53:11 -0000


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

Elek, Marton commented on HDFS-12333:
-------------------------------------

Just to calirify: this page exists even now, I just added the two middle Ozone related section to that.

> Ozone: Extend Datanode web interface with SCM information
> ---------------------------------------------------------
>
>                 Key: HDFS-12333
>                 URL: https://issues.apache.org/jira/browse/HDFS-12333
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: HDFS-7240
>    Affects Versions: HDFS-7240
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>         Attachments: HDFS-12333-HDFS-7240.001.patch, ozonedatanode.png
>
>
> Current Datanode web interface shows information about the Block Pools:
> * Namenode Address
> * BlockPoolID
> * ActorState
> * Last Heartbeat
> * Last Block Report
> I propose in this jira to add the same information about the SCM (if the datanode is a member of ozone cluster). It would help to check the current state of the datanode (is ozone enabled? Is there an active connection to the SCM?)
> 1. Suggested information to display:
> * SCM hostname/address
> * EndpointState (GETVERSION, REGISTER, HEARTBEAT, SHUTDOWN)
> * version (from the VersoinResponse)
> * missedCount
> They could be displayed with publishing JMX information from SCMConnectionManager or EndpointStateMachines.
> 2. StorageLocationReport[] from the ContainerLocationManager also should be exposed over JMX and displayed on the web interface:
> * id
> * failed (bool)
> * capacity
> * scmUsed
> * remaining
> 3. Possible report of Last Heartbeat/Container report should be investigated.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org