Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 10 Nov 2017 05:06:01 +0000 (UTC)
From: "Brahma Reddy Battula (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13116311.1509946670000.203917.1510290361214@Atlassian.JIRA>
In-Reply-To: <JIRA.13116311.1509946670000@Atlassian.JIRA>
References: <JIRA.13116311.1509946670000@Atlassian.JIRA> <JIRA.13116311.1509946670061@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12781) After Datanode down, In Namenode UI
 Datanode tab is throwing warning message.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 10 Nov 2017 05:06:09 -0000


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

Brahma Reddy Battula commented on HDFS-12781:
---------------------------------------------

bq.It seems the workaround() function is trying to get the LiveNodes and return them as an array that DataTables.js can consume
It's return all the nodes.Please see the following snippet when it's called workaround().
   {code}
      r.LiveNodes = node_map_to_array(JSON.parse(r.LiveNodes));
      augment_live_nodes(r.LiveNodes);
      r.DeadNodes = node_map_to_array(JSON.parse(r.DeadNodes));
      augment_dead_nodes(r.DeadNodes);
      r.DecomNodes = node_map_to_array(JSON.parse(r.DecomNodes));
      r.EnteringMaintenanceNodes = node_map_to_array(JSON.parse(r.EnteringMaintenanceNodes));
      return r;
	{code}
	So,Following will be nodes info after calling the {{workaround()}}.
{noformat}
<tr><td ng-value="alive-BLR1000006586:50076" class="dfshealth-node-icon dfshealth-node-alive">BLR1000006586:50076 (*.*.105.92:50076)</td><td ng-value="alive-BLR1000006586:50076"><a href='http://BLR1000006586:9864'>http://BLR1000006586:9864</a></td><td ng-value="2">2s</td><td ng-value="5">5m</td><td ng-value="62"><div><div style="display:inline-block; float: left; padding-right: 10px;">147.65 GB</div><div class="clearfix progress dfshealth-node-capacity-bar" title="Non DFS: 89.59 GB, Used: 1.68 GB"><div class="progress-bar progress-bar-success" style="width: 62%"></div></div></div></td><td title="Blocks Scheduled : 0">247</td><td ng-value="1.1375871">1.68 GB (1.14%)</td><td>3.0.0-beta1</td></tr>

<tr><td ng-value="alive-BLR1000006596:50076" class="dfshealth-node-icon dfshealth-node-alive">BLR1000006596:50076 (*.*.109.205:50076)</td><td ng-value="alive-BLR1000006596:50076"><a href='http://BLR1000006596:50075'>http://BLR1000006596:50075</a></td><td ng-value="2">2s</td><td ng-value="4">4m</td><td ng-value="65"><div><div style="display:inline-block; float: left; padding-right: 10px;">147.65 GB</div><div class="clearfix progress dfshealth-node-capacity-bar" title="Non DFS: 93.63 GB, Used: 1.68 GB"><div class="progress-bar progress-bar-success" style="width: 65%"></div></div></div></td><td title="Blocks Scheduled : 0">247</td><td ng-value="1.1375792">1.68 GB (1.14%)</td><td>2.7.4</td></tr>

<tr class="danger"><td ng-value="down-BLR1000006554:50076" class="dfshealth-node-icon dfshealth-node-down">BLR1000006554:50076 (*.*.97.117:50076)</td><td></td><td>Thu Nov 02 19:57:09 +0530 2017</td><td></td><td></td><td></td><td></td></tr></table>
{noformat}

bq.If it is only recently dead, which coloumn of data doesn't exist?
As we can't get the metrics, {{Http Address}},{{Last Block Report}},{{Capacity}},{{Blocks}},{{Block pool used}},{{Version}} will be null. Check following Json and {{data}} after workaround call.
{noformat}
 "DeadNodes" : "{\"BLR1000006554:50076\":{\"lastContact\":594774,\"decommissioned\":false,\"adminState\":\"In Service\",\"xferaddr\":\"*.*.97.117:50076\"}}",

<tr class="danger"><td ng-value="down-BLR1000006554:50076" class="dfshealth-node-icon dfshealth-node-down">BLR1000006554:50076 (*.*.97.117:50076)</td><td></td><td>Thu Nov 02 19:57:09 +0530 2017</td><td></td><td></td><td></td><td></td></tr></table>
 {noformat}

> After Datanode down, In Namenode UI Datanode tab is throwing warning message.
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-12781
>                 URL: https://issues.apache.org/jira/browse/HDFS-12781
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.9.0, 3.0.0-alpha1
>            Reporter: Harshakiran Reddy
>            Assignee: Brahma Reddy Battula
>         Attachments: HDFS-12781-001.patch
>
>
> Scenario:
> Stop one Datanode
> Refresh or click on the Datanode tab in namenode UI.
> Actual Output:
> ==============
> it's throwing the warning message. please find the bellow warning message.
> DataTables warning: table id=table-datanodes - Requested unknown parameter '7' for row 2. For more information about this error, please see http://datatables.net/tn/4
> Expected Output:
> ================
> whenever you click on Datanode tab,it should be display the datanodes information.


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