[
https://issues.apache.org/jira/browse/HDFS-12333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141497#comment-16141497
]
Elek, Marton edited comment on HDFS-12333 at 8/25/17 11:18 AM:
---------------------------------------------------------------
Screenshot of the web interface is included.
was (Author: elek):
Screenshot of the web interface.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
