[jira] [Updated] (HDFS-9142) Separating Configuration object for namenode(s) in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142-branch-2.v1.patch > Separating Configuration object for namenode(s) in MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142-branch-2.v1.patch, HDFS-9142.v1.patch, > HDFS-9142.v2.patch, HDFS-9142.v3.patch, HDFS-9142.v4.patch, > HDFS-9142.v5.patch, HDFS-9142.v6.patch, HDFS-9142.v7.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Separating Configuration object for namenode(s) in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Summary: Separating Configuration object for namenode(s) in MiniDFSCluster (was: Update MiniDFSCluster to use separate Configuration object for each namenode ) > Separating Configuration object for namenode(s) in MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, > HDFS-9142.v6.patch, HDFS-9142.v7.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Separating Configuration object for cluster with more than 1 namenode in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Summary: Separating Configuration object for cluster with more than 1 namenode in MiniDFSCluster (was: Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster) > Separating Configuration object for cluster with more than 1 namenode in > MiniDFSCluster > --- > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, > HDFS-9142.v6.patch, HDFS-9142.v7.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949152#comment-14949152 ] Siqi Li commented on HDFS-9142: --- ok. I have removed "System.out.println" in patch v7 > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, > HDFS-9142.v6.patch, HDFS-9142.v7.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v7.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, > HDFS-9142.v6.patch, HDFS-9142.v7.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949116#comment-14949116 ] Siqi Li commented on HDFS-9142: --- [~mingma], it seems that patch v6 doesn't have a test report. Is there a way to start a test? > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, HDFS-9142.v6.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Status: Open (was: Patch Available) > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, HDFS-9142.v6.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Status: Patch Available (was: Open) > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, HDFS-9142.v6.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v6.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch, HDFS-9142.v6.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v5.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch, HDFS-9142.v5.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v4.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch, HDFS-9142.v4.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908843#comment-14908843 ] Siqi Li commented on HDFS-9142: --- Test failures seem to be unrelated > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v3.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch, > HDFS-9142.v3.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907125#comment-14907125 ] Siqi Li commented on HDFS-9142: --- Thanks for the review, I have updated the javadoc in patch v2 > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v2.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch, HDFS-9142.v2.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Description: When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode should have its own configuration object, and the configuration should have "dfs.namenode.http-address--" set up correctly for all pair > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li > Attachments: HDFS-9142.v1.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Assignee: Siqi Li Status: Patch Available (was: Open) > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-9142.v1.patch > > > When setting up simpleHAFederatedTopology in MiniDFSCluster, each Namenode > should have its own configuration object, and the configuration should have > "dfs.namenode.http-address--" set up correctly for > all pair -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
[ https://issues.apache.org/jira/browse/HDFS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-9142: -- Attachment: HDFS-9142.v1.patch > Namenode Http address is not configured correctly for federated cluster in > MiniDFSCluster > - > > Key: HDFS-9142 > URL: https://issues.apache.org/jira/browse/HDFS-9142 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li > Attachments: HDFS-9142.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HDFS-9142) Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster
Siqi Li created HDFS-9142: - Summary: Namenode Http address is not configured correctly for federated cluster in MiniDFSCluster Key: HDFS-9142 URL: https://issues.apache.org/jira/browse/HDFS-9142 Project: Hadoop HDFS Issue Type: Bug Reporter: Siqi Li -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744512#comment-14744512 ] Siqi Li commented on HDFS-6744: --- No, HDFS-6407 did not solve this issue. > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6744.v1.patch, deadnodespage.png, > decomnodespage.png, livendoespage.png > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Release Note: getSoftwareVersion method would replace original getVersion method, which returns the version string. The new getVersion method would return both version string and revision string > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch, > HDFS-8981.v3.patch, HDFS-8981.v4.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729598#comment-14729598 ] Siqi Li commented on HDFS-8981: --- thanks [~mingma] for the review, I have uploaded patch v4. > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch, > HDFS-8981.v3.patch, HDFS-8981.v4.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: HDFS-8981.v4.patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch, > HDFS-8981.v3.patch, HDFS-8981.v4.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: HDFS-8981.v3.patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch, > HDFS-8981.v3.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727985#comment-14727985 ] Siqi Li commented on HDFS-8981: --- checkstyle and test failures seems to be not related to this patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: HDFS-8981.v2.patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: (was: HDFS-8981.v2.patch) > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: HDFS-8981.v2.patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch, HDFS-8981.v2.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Assignee: Siqi Li Status: Patch Available (was: Open) > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Attachment: HDFS-8981.v1.patch > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Priority: Minor > Attachments: HDFS-8981.v1.patch > > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8981) Adding revision to data node jmx getVersion() method
[ https://issues.apache.org/jira/browse/HDFS-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8981: -- Description: to be consistent with namenode jmx, datanode jmx should also output revision number > Adding revision to data node jmx getVersion() method > > > Key: HDFS-8981 > URL: https://issues.apache.org/jira/browse/HDFS-8981 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Priority: Minor > > to be consistent with namenode jmx, datanode jmx should also output revision > number -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HDFS-8981) Adding revision to data node jmx getVersion() method
Siqi Li created HDFS-8981: - Summary: Adding revision to data node jmx getVersion() method Key: HDFS-8981 URL: https://issues.apache.org/jira/browse/HDFS-8981 Project: Hadoop HDFS Issue Type: Bug Reporter: Siqi Li Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Attachment: HDFS-6244.v6.patch > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch, HDFS-6244.v6.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Status: Patch Available (was: Open) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch, HDFS-6244.v6.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700204#comment-14700204 ] Siqi Li commented on HDFS-6244: --- I think Ming is talking about cloning the conf instead of reading the namespace specific property. Because for trash object, it should not be aware the concept of namespace. Also, I have tried to create a constructor for trash to take namespace as a parameter. However, this namespace also needs to pass to TrashPolicyDefault and Emptier, in order for them to read the namespace specific property. Which makes a lot of changes. Therefore, I think passing a clone conf is a cleaner approach. > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Status: Open (was: Patch Available) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Status: Patch Available (was: Open) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Attachment: HDFS-6244.v5.patch > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Attachment: (was: HDFS-6244.v5.patch) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Attachment: HDFS-6244.v5.patch > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch, HDFS-6244.v5.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Status: Open (was: Patch Available) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Status: Patch Available (was: Open) > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6244) Make Trash Interval configurable for each of the namespaces
[ https://issues.apache.org/jira/browse/HDFS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6244: -- Attachment: HDFS-6244.v4.patch > Make Trash Interval configurable for each of the namespaces > --- > > Key: HDFS-6244 > URL: https://issues.apache.org/jira/browse/HDFS-6244 > Project: Hadoop HDFS > Issue Type: Improvement >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-6244.v1.patch, HDFS-6244.v2.patch, > HDFS-6244.v3.patch, HDFS-6244.v4.patch > > > Somehow we need to avoid the cluster filling up. > One solution is to have a different trash policy per namespace. However, if > we can simply make the property configurable per namespace, then the same > config can be rolled everywhere and we'd be done. This seems simple enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
[ https://issues.apache.org/jira/browse/HDFS-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680446#comment-14680446 ] Siqi Li commented on HDFS-8868: --- Hi [~mingma] and [~jira.shegalov], can you guys take a look at this jira. > Trash Emptier stop working in cluster with federated namenodes > -- > > Key: HDFS-8868 > URL: https://issues.apache.org/jira/browse/HDFS-8868 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-8868.v1.patch > > > when we have federation set up, the default file system would become viewfs, > trash emptier is going to scan viewfs://namespace/user. However, if we don't > have a link in the mounttable.xml (viewfs://namespace/user ---> > hdfs://namespace/user), then trash emptier cannot find the user directory. > Therefore, we should have namenode use hdfs as its default filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
[ https://issues.apache.org/jira/browse/HDFS-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8868: -- Description: when we have federation set up, the default file system would become viewfs, trash emptier is going to scan viewfs://namespace/user. However, if we don't have a link in the mounttable.xml (viewfs://namespace/user ---> hdfs://namespace/user), then trash emptier cannot find the user directory. Therefore, we should have namenode use hdfs as its default filesystem > Trash Emptier stop working in cluster with federated namenodes > -- > > Key: HDFS-8868 > URL: https://issues.apache.org/jira/browse/HDFS-8868 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-8868.v1.patch > > > when we have federation set up, the default file system would become viewfs, > trash emptier is going to scan viewfs://namespace/user. However, if we don't > have a link in the mounttable.xml (viewfs://namespace/user ---> > hdfs://namespace/user), then trash emptier cannot find the user directory. > Therefore, we should have namenode use hdfs as its default filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
[ https://issues.apache.org/jira/browse/HDFS-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8868: -- Component/s: federation > Trash Emptier stop working in cluster with federated namenodes > -- > > Key: HDFS-8868 > URL: https://issues.apache.org/jira/browse/HDFS-8868 > Project: Hadoop HDFS > Issue Type: Bug > Components: federation >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-8868.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
[ https://issues.apache.org/jira/browse/HDFS-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8868: -- Assignee: Siqi Li Status: Patch Available (was: Open) > Trash Emptier stop working in cluster with federated namenodes > -- > > Key: HDFS-8868 > URL: https://issues.apache.org/jira/browse/HDFS-8868 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-8868.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
[ https://issues.apache.org/jira/browse/HDFS-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-8868: -- Attachment: HDFS-8868.v1.patch > Trash Emptier stop working in cluster with federated namenodes > -- > > Key: HDFS-8868 > URL: https://issues.apache.org/jira/browse/HDFS-8868 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Siqi Li > Attachments: HDFS-8868.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HDFS-8868) Trash Emptier stop working in cluster with federated namenodes
Siqi Li created HDFS-8868: - Summary: Trash Emptier stop working in cluster with federated namenodes Key: HDFS-8868 URL: https://issues.apache.org/jira/browse/HDFS-8868 Project: Hadoop HDFS Issue Type: Bug Reporter: Siqi Li -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597916#comment-14597916 ] Siqi Li commented on HDFS-7214: --- Sure, I will add it to the webUI based on the existing jmx results > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch, > HDFS-7214.v3.patch, HDFS-7214.v4.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596608#comment-14596608 ] Siqi Li commented on HDFS-7214: --- It looks like HDFS-7257 has already checked in a similar feature as of this jira. I feel like we could resolve this one by marking it as a duplicate > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch, > HDFS-7214.v3.patch, HDFS-7214.v4.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Attachment: HDFS-7214.v4.patch > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch, > HDFS-7214.v3.patch, HDFS-7214.v4.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596372#comment-14596372 ] Siqi Li commented on HDFS-7214: --- [~wheat9], Thanks for your feedback. 1. for suggestion of changing long to AtomicLong, I am not quite sure what the improvement would be. 2. I am not sure returning the timestamp is a good idea. Since getNNStarted method returns a Date object and the UI just displays it. I am just simply following that pattern. > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch, > HDFS-7214.v3.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Attachment: HDFS-7214.v3.patch > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch, > HDFS-7214.v3.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Attachment: HDFS-7214.v2.patch > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Labels: BB2015-05-TBR > Attachments: HDFS-7214.v1.patch, HDFS-7214.v2.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5296) DFS usage gets doubled in the WebUI of federated namenode
[ https://issues.apache.org/jira/browse/HDFS-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5296: -- Resolution: Won't Fix Status: Resolved (was: Patch Available) Since old HDFS WebUI has retired, close this jira > DFS usage gets doubled in the WebUI of federated namenode > - > > Key: HDFS-5296 > URL: https://issues.apache.org/jira/browse/HDFS-5296 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 2.0.5-alpha >Reporter: Siqi Li >Assignee: Siqi Li >Priority: Minor > Labels: BB2015-05-TBR > Attachments: BBF12817-B83E-4CC5-B0B8-4FA322E87FB7.png, > HDFS-5296-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184608#comment-14184608 ] Siqi Li commented on HDFS-5928: --- Thanks [~wheat9], the patch LGTM > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.007.patch, HDFS-5928.v2.patch, > HDFS-5928.v3.patch, HDFS-5928.v4.patch, HDFS-5928.v5.patch, > HDFS-5928.v6.patch, HDFS－5928.v1.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183667#comment-14183667 ] Siqi Li commented on HDFS-5928: --- thank you > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS-5928.v5.patch, HDFS-5928.v6.patch, > HDFS－5928.v1.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183602#comment-14183602 ] Siqi Li commented on HDFS-5928: --- [~wheat9] I have updated the patch with a screenshot, the test failures should be irrelevant for this patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS-5928.v5.patch, HDFS-5928.v6.patch, > HDFS－5928.v1.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181758#comment-14181758 ] Siqi Li commented on HDFS-6744: --- [~wheat9] the state of nodes are changing constantly, therefore, we should load them every time when people click a link, instead of load all info once and populate it to DOM when it is requested > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch, deadnodespage.png, > decomnodespage.png, livendoespage.png > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: HDFS-5928.v6.patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS-5928.v5.patch, HDFS-5928.v6.patch, > HDFS－5928.v1.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: screenshot-1.png > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS-5928.v5.patch, HDFS－5928.v1.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6742) Support sorting datanode list on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180743#comment-14180743 ] Siqi Li commented on HDFS-6742: --- [~airbots] Hi Chen, any updates on this jira? It would be extremely helpful when dealing with cluster with thousands of nodes > Support sorting datanode list on the new NN webUI > - > > Key: HDFS-6742 > URL: https://issues.apache.org/jira/browse/HDFS-6742 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Chen He > > The legacy webUI allows sorting datanode list based on specific column such > as hostname. It is handy for admins can find pattern more quickly, especially > for big clusters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: HDFS-5928.v5.patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS-5928.v5.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180524#comment-14180524 ] Siqi Li commented on HDFS-5928: --- I don't think this is going to work, if the cluster doesn't have HA or federation. Also, it's good to let people know what is namespace and what namenodeID > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180474#comment-14180474 ] Siqi Li commented on HDFS-5928: --- [~wheat9] I have added the check for both namespace and namenodeID > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177607#comment-14177607 ] Siqi Li commented on HDFS-5928: --- I have added the check for both namespace and namenodeID > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: HDFS-5928.v4.patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS-5928.v4.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177262#comment-14177262 ] Siqi Li commented on HDFS-6744: --- I have attached 3 screenshots of each page(livenodes, deadnodes, decomnodes) > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch, deadnodespage.png, > decomnodespage.png, livendoespage.png > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6744: -- Attachment: decomnodespage.png deadnodespage.png livendoespage.png > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch, deadnodespage.png, > decomnodespage.png, livendoespage.png > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174072#comment-14174072 ] Siqi Li commented on HDFS-6744: --- Hi [~wheat9], can you take a look at this patch? > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Issue Type: Sub-task (was: Improvement) Parent: HDFS-6751 > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6744: -- Status: Patch Available (was: Open) > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6744: -- Attachment: HDFS-6744.v1.patch > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6744.v1.patch > > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HDFS-6744) Improve decommissioning nodes and dead nodes access on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned HDFS-6744: - Assignee: Siqi Li > Improve decommissioning nodes and dead nodes access on the new NN webUI > --- > > Key: HDFS-6744 > URL: https://issues.apache.org/jira/browse/HDFS-6744 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > > The new NN webUI lists live node at the top of the page, followed by dead > node and decommissioning node. From admins point of view: > 1. Decommissioning nodes and dead nodes are more interesting. It is better to > move decommissioning nodes to the top of the page, followed by dead nodes and > decommissioning nodes. > 2. To find decommissioning nodes or dead nodes, the whole page that includes > all nodes needs to be loaded. That could take some time for big clusters. > The legacy web UI filters out the type of nodes dynamically. That seems to > work well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167192#comment-14167192 ] Siqi Li commented on HDFS-5928: --- [~wheat9] Hi Haohui, I have attached a patch that uses conf to parse namespace and namenodeID. I don't think the release audit warning and core test failure are related to this patch, can you get this patch committed? > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Status: Open (was: Patch Available) > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Status: Patch Available (was: Open) > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: HDFS-5928.v3.patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS-5928.v3.patch, > HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Attachment: HDFS-5928.v3.patch > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-5928.v3.patch, HDFS-6743.v1.patch, > HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Status: Patch Available (was: Open) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-5928.v3.patch, HDFS-6743.v1.patch, > HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Attachment: (was: HDFS-5928.v3.patch) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch, HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Status: Open (was: Patch Available) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-5928.v3.patch, HDFS-6743.v1.patch, > HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Attachment: HDFS-6743.v2.patch > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch, HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Status: Open (was: Patch Available) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch, HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Status: Patch Available (was: Open) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch, HDFS-6743.v2.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Status: Patch Available (was: Open) > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned HDFS-6743: - Assignee: Siqi Li > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6743) Put IP address into a new column on the new NN webUI
[ https://issues.apache.org/jira/browse/HDFS-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-6743: -- Attachment: HDFS-6743.v1.patch > Put IP address into a new column on the new NN webUI > > > Key: HDFS-6743 > URL: https://issues.apache.org/jira/browse/HDFS-6743 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Ming Ma >Assignee: Siqi Li > Attachments: HDFS-6743.v1.patch > > > The new NN webUI combines hostname and IP into one column in datanode list. > It is more convenient for admins if the IP address can be put to a separate > column, as in the legacy NN webUI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[
https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164113#comment-14164113
]
Siqi Li commented on HDFS-5928:
---
I think using MXBean is the way to pass information to the new NN webUI, I am
just following the pattern. Even if it is possible to get the information from
{http://Addr/conf}, there are other information that are not available from
{http://Addr/conf}.
For example, https://issues.apache.org/jira/browse/HDFS-7214
> show namespace and namenode ID on NN dfshealth page
> ---
>
> Key: HDFS-5928
> URL: https://issues.apache.org/jira/browse/HDFS-5928
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Siqi Li
>Assignee: Siqi Li
> Attachments: HDFS-5928.v2.patch, HDFS－5928.v1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Status: Patch Available (was: Open) > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-7214.v1.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Attachment: HDFS-7214.v1.patch > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-7214.v1.patch > > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-7214: -- Description: The currently NN webUI displayed JVM start up. It will be useful to show when NN became active. > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > > The currently NN webUI displayed JVM start up. It will be useful to show when > NN became active. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HDFS-7214) Display the time when NN became active on the webUI
[ https://issues.apache.org/jira/browse/HDFS-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned HDFS-7214: - Assignee: Siqi Li > Display the time when NN became active on the webUI > --- > > Key: HDFS-7214 > URL: https://issues.apache.org/jira/browse/HDFS-7214 > Project: Hadoop HDFS > Issue Type: Sub-task >Reporter: Siqi Li >Assignee: Siqi Li > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HDFS-7214) Display the time when NN became active on the webUI
Siqi Li created HDFS-7214: - Summary: Display the time when NN became active on the webUI Key: HDFS-7214 URL: https://issues.apache.org/jira/browse/HDFS-7214 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Siqi Li -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162811#comment-14162811 ] Siqi Li commented on HDFS-5928: --- [~wheat9] Hi Haohui, I don't think the findbugs and core test failure are related to this patch, can you get this patch committed? > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Status: Patch Available (was: Open) > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: HDFS-5928.v2.patch > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Status: Open (was: Patch Available) > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS-5928.v2.patch, HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-5928) show namespace and namenode ID on NN dfshealth page
[ https://issues.apache.org/jira/browse/HDFS-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated HDFS-5928: -- Attachment: (was: HDFS-5928.v2.patch) > show namespace and namenode ID on NN dfshealth page > --- > > Key: HDFS-5928 > URL: https://issues.apache.org/jira/browse/HDFS-5928 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: Siqi Li >Assignee: Siqi Li > Attachments: HDFS－5928.v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
