[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180084#comment-16180084 ] steven-wugang commented on HDFS-12353: -- [~eddyxu] Hi,I have added a test for this patch.Can you help me review it?Thank you very much. > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353-4.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164317#comment-16164317 ] steven-wugang commented on HDFS-12353: -- [~eddyxu] Sorry, I study the unit testing framework for a few days . Now I have added a test for this patch.Please help me review this patch again,Thank you very much. By the way, I looked at the failure of the above unit test ，which should have nothing to do with this patch。 > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353-4.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Patch Available (was: Open) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353-4.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Open (was: Patch Available) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353-4.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353-4.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353-4.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353-3.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, > HDFS-12353-3.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Patch Available (was: Open) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353-2.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353-2.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Open (was: Patch Available) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353-1.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Patch Available (was: Open) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Open (was: Patch Available) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: (was: HDFS-12353-1.patch) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353-1.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353-1.patch, HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16156817#comment-16156817 ] steven-wugang commented on HDFS-12353: -- [~eddyxu]ok,thanks for your review. I will add a test for this patch as soon as possible! > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154703#comment-16154703 ] steven-wugang commented on HDFS-12353: -- [~drankye] Hello,Excuse me,can you help me review this patch?Thank you very much! > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Issue Comment Deleted] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Comment: was deleted (was: [~brahmareddy]hi,can you help me review this issue?Thank you!) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141257#comment-16141257 ] steven-wugang commented on HDFS-12353: -- [~brahmareddy]hi,can you help me review this issue?Thank you! > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Assigned] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang reassigned HDFS-12353: Assignee: steven-wugang > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Status: Patch Available (was: Open) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Attachment: HDFS-12353.patch > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12353.patch > > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23908322375185 (21.74 TB) > Non DFS Used: 618808670703 (576.31 GB) > DFS Remaining: 14847212859392 (13.50 TB) > DFS Used%: 60.72% > DFS Remaining%: 37.71% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 38 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.2:50010 (zhd2-2) > Hostname: zhd2-2 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 21142153003941 (19.23 TB) > Non DFS Used: 7107518921819 (6.46 TB) > DFS Remaining: 11124671979520 (10.12 TB) > DFS Used%: 53.70% > DFS Remaining%: 28.25% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 22 > Last contact: Fri Aug 25 10:06:50 CST 2017 > The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS > Used%" value in other live datanode reports is DFS Used/Configured Capacity. > The two calculation methods are inconsistent,misunderstanding may arise. -- 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
[jira] [Issue Comment Deleted] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Comment: was deleted (was: use command "hdfs dfsadmin -report",as follows: [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report Configured Capacity: 157497375621120 (143.24 TB) Present Capacity: 148541284228197 (135.10 TB) DFS Remaining: 56467228499968 (51.36 TB) DFS Used: 92074055728229 (83.74 TB) DFS Used%: 61.99% Under replicated blocks: 1 Blocks with corrupt replicas: 3 Missing blocks: 0 Missing blocks (with replication factor 1): 0 - Live datanodes (4): Name: 172.168.129.1:50010 (zhd2-1) Hostname: zhd2-1 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23560170107046 (21.43 TB) Non DFS Used: 609684660058 (567.81 GB) DFS Remaining: 15204489138176 (13.83 TB) DFS Used%: 59.84% DFS Remaining%: 38.62% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 36 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.3:50010 (zhd2-3) Hostname: zhd2-3 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23463410242057 (21.34 TB) Non DFS Used: 620079140343 (577.49 GB) DFS Remaining: 15290854522880 (13.91 TB) DFS Used%: 59.59% DFS Remaining%: 38.83% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 30 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.4:50010 (zhd2-4) Hostname: zhd2-4 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23908322375185 (21.74 TB) Non DFS Used: 618808670703 (576.31 GB) DFS Remaining: 14847212859392 (13.50 TB) DFS Used%: 60.72% DFS Remaining%: 37.71% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 38 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.2:50010 (zhd2-2) Hostname: zhd2-2 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 21142153003941 (19.23 TB) Non DFS Used: 7107518921819 (6.46 TB) DFS Remaining: 11124671979520 (10.12 TB) DFS Used%: 53.70% DFS Remaining%: 28.25% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 22 Last contact: Fri Aug 25 10:06:50 CST 2017 The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS Used%" value in other live datanode reports is DFS Used/Configured Capacity.The two calculation methods are inconsistent,misunderstanding may arise.) > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) >
[jira] [Updated] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12353: - Description: use command "hdfs dfsadmin -report",as follows: [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report Configured Capacity: 157497375621120 (143.24 TB) Present Capacity: 148541284228197 (135.10 TB) DFS Remaining: 56467228499968 (51.36 TB) DFS Used: 92074055728229 (83.74 TB) DFS Used%: 61.99% Under replicated blocks: 1 Blocks with corrupt replicas: 3 Missing blocks: 0 Missing blocks (with replication factor 1): 0 - Live datanodes (4): Name: 172.168.129.1:50010 (zhd2-1) Hostname: zhd2-1 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23560170107046 (21.43 TB) Non DFS Used: 609684660058 (567.81 GB) DFS Remaining: 15204489138176 (13.83 TB) DFS Used%: 59.84% DFS Remaining%: 38.62% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 36 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.3:50010 (zhd2-3) Hostname: zhd2-3 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23463410242057 (21.34 TB) Non DFS Used: 620079140343 (577.49 GB) DFS Remaining: 15290854522880 (13.91 TB) DFS Used%: 59.59% DFS Remaining%: 38.83% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 30 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.4:50010 (zhd2-4) Hostname: zhd2-4 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23908322375185 (21.74 TB) Non DFS Used: 618808670703 (576.31 GB) DFS Remaining: 14847212859392 (13.50 TB) DFS Used%: 60.72% DFS Remaining%: 37.71% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 38 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.2:50010 (zhd2-2) Hostname: zhd2-2 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 21142153003941 (19.23 TB) Non DFS Used: 7107518921819 (6.46 TB) DFS Remaining: 11124671979520 (10.12 TB) DFS Used%: 53.70% DFS Remaining%: 28.25% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 22 Last contact: Fri Aug 25 10:06:50 CST 2017 The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS Used%" value in other live datanode reports is DFS Used/Configured Capacity. The two calculation methods are inconsistent,misunderstanding may arise. > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > > use command "hdfs dfsadmin -report",as follows: > [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report > Configured Capacity: 157497375621120 (143.24 TB) > Present Capacity: 148541284228197 (135.10 TB) > DFS Remaining: 56467228499968 (51.36 TB) > DFS Used: 92074055728229 (83.74 TB) > DFS Used%: 61.99% > Under replicated blocks: 1 > Blocks with corrupt replicas: 3 > Missing blocks: 0 > Missing blocks (with replication factor 1): 0 > - > Live datanodes (4): > Name: 172.168.129.1:50010 (zhd2-1) > Hostname: zhd2-1 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23560170107046 (21.43 TB) > Non DFS Used: 609684660058 (567.81 GB) > DFS Remaining: 15204489138176 (13.83 TB) > DFS Used%: 59.84% > DFS Remaining%: 38.62% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 36 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.3:50010 (zhd2-3) > Hostname: zhd2-3 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used: 23463410242057 (21.34 TB) > Non DFS Used: 620079140343 (577.49 GB) > DFS Remaining: 15290854522880 (13.91 TB) > DFS Used%: 59.59% > DFS Remaining%: 38.83% > Configured Cache Capacity: 60 (5.59 GB) > Cache Used: 0 (0 B) > Cache Remaining: 60 (5.59 GB) > Cache Used%: 0.00% > Cache Remaining%: 100.00% > Xceivers: 30 > Last contact: Fri Aug 25 10:06:50 CST 2017 > Name: 172.168.129.4:50010 (zhd2-4) > Hostname: zhd2-4 > Decommission Status : Normal > Configured Capacity: 39374343905280 (35.81 TB) > DFS Used:
[jira] [Commented] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
[ https://issues.apache.org/jira/browse/HDFS-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141084#comment-16141084 ] steven-wugang commented on HDFS-12353: -- use command "hdfs dfsadmin -report",as follows: [hdfs@zhd2-3 sbin]$ hdfs dfsadmin -report Configured Capacity: 157497375621120 (143.24 TB) Present Capacity: 148541284228197 (135.10 TB) DFS Remaining: 56467228499968 (51.36 TB) DFS Used: 92074055728229 (83.74 TB) DFS Used%: 61.99% Under replicated blocks: 1 Blocks with corrupt replicas: 3 Missing blocks: 0 Missing blocks (with replication factor 1): 0 - Live datanodes (4): Name: 172.168.129.1:50010 (zhd2-1) Hostname: zhd2-1 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23560170107046 (21.43 TB) Non DFS Used: 609684660058 (567.81 GB) DFS Remaining: 15204489138176 (13.83 TB) DFS Used%: 59.84% DFS Remaining%: 38.62% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 36 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.3:50010 (zhd2-3) Hostname: zhd2-3 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23463410242057 (21.34 TB) Non DFS Used: 620079140343 (577.49 GB) DFS Remaining: 15290854522880 (13.91 TB) DFS Used%: 59.59% DFS Remaining%: 38.83% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 30 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.4:50010 (zhd2-4) Hostname: zhd2-4 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 23908322375185 (21.74 TB) Non DFS Used: 618808670703 (576.31 GB) DFS Remaining: 14847212859392 (13.50 TB) DFS Used%: 60.72% DFS Remaining%: 37.71% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 38 Last contact: Fri Aug 25 10:06:50 CST 2017 Name: 172.168.129.2:50010 (zhd2-2) Hostname: zhd2-2 Decommission Status : Normal Configured Capacity: 39374343905280 (35.81 TB) DFS Used: 21142153003941 (19.23 TB) Non DFS Used: 7107518921819 (6.46 TB) DFS Remaining: 11124671979520 (10.12 TB) DFS Used%: 53.70% DFS Remaining%: 28.25% Configured Cache Capacity: 60 (5.59 GB) Cache Used: 0 (0 B) Cache Remaining: 60 (5.59 GB) Cache Used%: 0.00% Cache Remaining%: 100.00% Xceivers: 22 Last contact: Fri Aug 25 10:06:50 CST 2017 The first "DFS Used%" value on the top is DFS Used/Present Capacity,but "DFS Used%" value in other live datanode reports is DFS Used/Configured Capacity.The two calculation methods are inconsistent,misunderstanding may arise. > Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of > datanode reports. > -- > > Key: HDFS-12353 > URL: https://issues.apache.org/jira/browse/HDFS-12353 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > -- 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
[jira] [Created] (HDFS-12353) Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports.
steven-wugang created HDFS-12353: Summary: Modify Dfsuse percent of dfsadmin report inconsistent with Dfsuse percent of datanode reports. Key: HDFS-12353 URL: https://issues.apache.org/jira/browse/HDFS-12353 Project: Hadoop HDFS Issue Type: Bug Reporter: steven-wugang -- 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
[jira] [Commented] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091042#comment-16091042 ] steven-wugang commented on HDFS-12067: -- [~brahma]I only modified some help hint information, and nothing related to code logical changes. The above error should have nothing to do with this commit. Please review it again，thank you！ > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS_12067.006.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.006.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS_12067.006.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS_12067.006.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.005.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS_12067.005.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Commented] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089207#comment-16089207 ] steven-wugang commented on HDFS-12067: -- [~brahma]Thanks for your review,I'd be happy to do it. > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Commented] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089206#comment-16089206 ] steven-wugang commented on HDFS-12067: -- [~brahma] ok > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.004.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS_12067.004.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.003.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: (was: HDFS_12067.003.patch) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Commented] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16069298#comment-16069298 ] steven-wugang commented on HDFS-12067: -- [~vagarychen] thank you for your review,I have revised it. > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.003.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS_12067.003.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.002.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS_12067.002.patch, > HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Open (was: Patch Available) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS_12067.001.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS_12067.001.patch, HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12068) Modify judgment condition in function computeVolumeDataDensity,otherwise maybe divided by zero
[
https://issues.apache.org/jira/browse/HDFS-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
steven-wugang updated HDFS-12068:
-
Status: Patch Available (was: Open)
> Modify judgment condition in function computeVolumeDataDensity,otherwise
> maybe divided by zero
> --
>
> Key: HDFS-12068
> URL: https://issues.apache.org/jira/browse/HDFS-12068
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: steven-wugang
>Assignee: steven-wugang
> Attachments: HDFS-12068.patch
>
>
> IN function computeVolumeDataDensity,there is a piece of code,as follow:
> public void computeVolumeDataDensity() {
> ...
>if (volume.computeEffectiveCapacity() < 0) {
> skipMisConfiguredVolume(volume);
> continue;
> }
>
> double dfsUsedRatio =
> truncateDecimals(volume.getUsed() /
> (double) volume.computeEffectiveCapacity());
>
>
> }
> Did not filter out the case that volume.computeEffectiveCapacity() is
> zero，maybe divided by zero behind.
--
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
[jira] [Updated] (HDFS-12068) Modify judgment condition in function computeVolumeDataDensity,otherwise maybe divided by zero
[
https://issues.apache.org/jira/browse/HDFS-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
steven-wugang updated HDFS-12068:
-
Attachment: HDFS-12068.patch
> Modify judgment condition in function computeVolumeDataDensity,otherwise
> maybe divided by zero
> --
>
> Key: HDFS-12068
> URL: https://issues.apache.org/jira/browse/HDFS-12068
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: steven-wugang
>Assignee: steven-wugang
> Attachments: HDFS-12068.patch
>
>
> IN function computeVolumeDataDensity,there is a piece of code,as follow:
> public void computeVolumeDataDensity() {
> ...
>if (volume.computeEffectiveCapacity() < 0) {
> skipMisConfiguredVolume(volume);
> continue;
> }
>
> double dfsUsedRatio =
> truncateDecimals(volume.getUsed() /
> (double) volume.computeEffectiveCapacity());
>
>
> }
> Did not filter out the case that volume.computeEffectiveCapacity() is
> zero，maybe divided by zero behind.
--
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
[jira] [Assigned] (HDFS-12068) Modify judgment condition in function computeVolumeDataDensity,otherwise maybe divided by zero
[
https://issues.apache.org/jira/browse/HDFS-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
steven-wugang reassigned HDFS-12068:
Assignee: steven-wugang
> Modify judgment condition in function computeVolumeDataDensity,otherwise
> maybe divided by zero
> --
>
> Key: HDFS-12068
> URL: https://issues.apache.org/jira/browse/HDFS-12068
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: steven-wugang
>Assignee: steven-wugang
>
> IN function computeVolumeDataDensity,there is a piece of code,as follow:
> public void computeVolumeDataDensity() {
> ...
>if (volume.computeEffectiveCapacity() < 0) {
> skipMisConfiguredVolume(volume);
> continue;
> }
>
> double dfsUsedRatio =
> truncateDecimals(volume.getUsed() /
> (double) volume.computeEffectiveCapacity());
>
>
> }
> Did not filter out the case that volume.computeEffectiveCapacity() is
> zero，maybe divided by zero behind.
--
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
[jira] [Created] (HDFS-12068) Modify judgment condition in function computeVolumeDataDensity,otherwise maybe divided by zero
steven-wugang created HDFS-12068:
Summary: Modify judgment condition in function
computeVolumeDataDensity,otherwise maybe divided by zero
Key: HDFS-12068
URL: https://issues.apache.org/jira/browse/HDFS-12068
Project: Hadoop HDFS
Issue Type: Bug
Reporter: steven-wugang
IN function computeVolumeDataDensity,there is a piece of code,as follow:
public void computeVolumeDataDensity() {
...
if (volume.computeEffectiveCapacity() < 0) {
skipMisConfiguredVolume(volume);
continue;
}
double dfsUsedRatio =
truncateDecimals(volume.getUsed() /
(double) volume.computeEffectiveCapacity());
}
Did not filter out the case that volume.computeEffectiveCapacity() is
zero，maybe divided by zero behind.
--
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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Status: Patch Available (was: Open) > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang > Attachments: HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Updated] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12067: - Attachment: HDFS-12067.patch > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang > Attachments: HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Assigned] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
[ https://issues.apache.org/jira/browse/HDFS-12067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang reassigned HDFS-12067: Assignee: steven-wugang > Add command help description about 'hdfs dfsadmin -help getVolumeReport' > command. > - > > Key: HDFS-12067 > URL: https://issues.apache.org/jira/browse/HDFS-12067 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12067.patch > > > When I use the command,I see the command help description,but the help > description doesn't make it clear,especially the argument 'port',It's easy to > mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order > to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Created] (HDFS-12067) Add command help description about 'hdfs dfsadmin -help getVolumeReport' command.
steven-wugang created HDFS-12067: Summary: Add command help description about 'hdfs dfsadmin -help getVolumeReport' command. Key: HDFS-12067 URL: https://issues.apache.org/jira/browse/HDFS-12067 Project: Hadoop HDFS Issue Type: Improvement Reporter: steven-wugang When I use the command,I see the command help description,but the help description doesn't make it clear,especially the argument 'port',It's easy to mistake for port (default 9866) in 'dfs.datanode.address'.Therefore, in order to use this command better,I add some descriptions about the arguments. -- 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
[jira] [Commented] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064467#comment-16064467 ] steven-wugang commented on HDFS-12025: -- [~anu]ok, I know it。thank you！ > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug > Components: diskbalancer >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Comment Edited] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064453#comment-16064453 ] steven-wugang edited comment on HDFS-12025 at 6/27/17 8:24 AM: --- [~anu] sorry,I don't really know it.I'll follow the rule next time.Thank you for reminding me! was (Author: steven-wugang): sorry,I don't really know it.I'll follow the rule next time.Thank you for reminding me! > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug > Components: diskbalancer >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Commented] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064453#comment-16064453 ] steven-wugang commented on HDFS-12025: -- sorry,I don't really know it.I'll follow the rule next time.Thank you for reminding me! > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug > Components: diskbalancer >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Commented] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064421#comment-16064421 ] steven-wugang commented on HDFS-12025: -- [~anu] Could you please help me with this commit? Some of the descriptions in log are not appropriate, may cause misunderstanding > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Commented] (HDFS-12045) Add log when Diskbalancer volume is transient storage type
[ https://issues.apache.org/jira/browse/HDFS-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064404#comment-16064404 ] steven-wugang commented on HDFS-12045: -- [~anu] thank you very much! > Add log when Diskbalancer volume is transient storage type > -- > > Key: HDFS-12045 > URL: https://issues.apache.org/jira/browse/HDFS-12045 > Project: Hadoop HDFS > Issue Type: Improvement > Components: diskbalancer >Reporter: steven-wugang >Assignee: steven-wugang > Attachments: HDFS-12045.patch > > > When dskbalancer volume is transient storage type,should add log to explain > that unable to support transient storage type。 -- 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
[jira] [Commented] (HDFS-12045) Add log when Diskbalancer volume is transient storage type
[ https://issues.apache.org/jira/browse/HDFS-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064380#comment-16064380 ] steven-wugang commented on HDFS-12045: -- [~anu] This genkins mistake has nothing to do with my commit. I only add log about it,but not change code logic。 thank you for adding me to the contributors list. > Add log when Diskbalancer volume is transient storage type > -- > > Key: HDFS-12045 > URL: https://issues.apache.org/jira/browse/HDFS-12045 > Project: Hadoop HDFS > Issue Type: Improvement > Components: diskbalancer >Reporter: steven-wugang >Assignee: Anu Engineer > Attachments: HDFS-12045.patch > > > When dskbalancer volume is transient storage type,should add log to explain > that unable to support transient storage type。 -- 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
[jira] [Updated] (HDFS-12045) Add log when Diskbalancer volume is transient storage type
[ https://issues.apache.org/jira/browse/HDFS-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12045: - Attachment: HDFS-12045.patch > Add log when Diskbalancer volume is transient storage type > -- > > Key: HDFS-12045 > URL: https://issues.apache.org/jira/browse/HDFS-12045 > Project: Hadoop HDFS > Issue Type: Improvement >Reporter: steven-wugang > Attachments: HDFS-12045.patch > > > When dskbalancer volume is transient storage type,should add log to explain > that unable to support transient storage type。 -- 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
[jira] [Created] (HDFS-12045) Add log when Diskbalancer volume is transient storage type
steven-wugang created HDFS-12045: Summary: Add log when Diskbalancer volume is transient storage type Key: HDFS-12045 URL: https://issues.apache.org/jira/browse/HDFS-12045 Project: Hadoop HDFS Issue Type: Improvement Reporter: steven-wugang When dskbalancer volume is transient storage type,should add log to explain that unable to support transient storage type。 -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Status: Patch Available (was: Open) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Attachment: (was: HDFS-12025.001.patch) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Attachment: HDFS-12025.002.patch > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Status: Open (was: Patch Available) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.002.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Attachment: HDFS-12025.001.patch > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.001.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Status: Patch Available (was: Open) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.001.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Status: Open (was: Patch Available) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Attachment: (was: HDFS-12025.patch) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Status: Patch Available (was: Open) > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Updated] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
[ https://issues.apache.org/jira/browse/HDFS-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] steven-wugang updated HDFS-12025: - Attachment: HDFS-12025.patch > Modify help instructions of Plan command and Execute command about > DiskBalancer > --- > > Key: HDFS-12025 > URL: https://issues.apache.org/jira/browse/HDFS-12025 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: steven-wugang > Attachments: HDFS-12025.patch > > > There are some inaccurate descriptions in help descriptions about PlanCommand > and ExecuteCommand of DiskBalancer. > For example, in ExecuteCommand help description, "Execute command runs a > submits a plan for execution on the given data node" should be modify > modified to "Execute command runs a submitted plan for execution on the given > data node". -- 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
[jira] [Created] (HDFS-12025) Modify help instructions of Plan command and Execute command about DiskBalancer
steven-wugang created HDFS-12025: Summary: Modify help instructions of Plan command and Execute command about DiskBalancer Key: HDFS-12025 URL: https://issues.apache.org/jira/browse/HDFS-12025 Project: Hadoop HDFS Issue Type: Bug Reporter: steven-wugang There are some inaccurate descriptions in help descriptions about PlanCommand and ExecuteCommand of DiskBalancer. For example, in ExecuteCommand help description, "Execute command runs a submits a plan for execution on the given data node" should be modify modified to "Execute command runs a submitted plan for execution on the given data node". -- 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
