[jira] [Created] (AMBARI-25570) Some RPC metrics are lost in the Grafana NameNode page, shows: No Data Points
echohlne created AMBARI-25570:
-
Summary: Some RPC metrics are lost in the Grafana NameNode page,
shows: No Data Points
Key: AMBARI-25570
URL: https://issues.apache.org/jira/browse/AMBARI-25570
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.7.4
Reporter: echohlne
Fix For: 2.7.6
Attachments: RPC Service Port metrics shows No datapoints.png
Some RPC Service Point metrics are lost in the Grafana NameNode page, shows:
'No Data Points', as the attachment shows.
Ambari Version:2.7.4
Grafana URL: http://${Grafana_HOST}:3000/dashboard/db/hdfs-namenodes
The abnormal metrics are shown as follows:
||metric||widget name||
|rpc.rpc.datanode.RpcQueueTimeAvgTime|RPC Service Port Queue Time|
|rpc.rpc.datanode.RpcQueueTimeNumOps|RPC Service Port Queue Num Ops|
|rpc.rpc.datanode.RpcProcessingTimeAvgTime|RPC Service Port Processing Time|
|rpc.rpc.datanode.RpcProcessingTimeNumOps|RPC Service Port Processing Num Ops|
|rpc.rpc.datanode.CallQueueLength|RPC Service Port Call Queue Length|
|rpc.rpc.datanode.RpcSlowCalls|RPC Service Port Slow Calls|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25543) hdfs heatmap "DataNode Process Disk I/O Utilization" showed incorrect high
[ https://issues.apache.org/jira/browse/AMBARI-25543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211531#comment-17211531 ] echohlne commented on AMBARI-25543: --- I try to fix this with this pr: [https://github.com/apache/ambari/pull/3237] > hdfs heatmap "DataNode Process Disk I/O Utilization" showed incorrect high > --- > > Key: AMBARI-25543 > URL: https://issues.apache.org/jira/browse/AMBARI-25543 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 > Environment: HDP release version Version 2.7.4.0 >Reporter: mmuuooaa >Priority: Major > Attachments: Disk_IO_Utilization.png > > Time Spent: 40m > Remaining Estimate: 0h > > hdfs heatmap "DataNode Process Disk I/O Utilization" showed incorrect high, > which is 36,000,000%, see attached picture -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25566) HBase 'Mutate Latencies-Average' metric in grafana always shows 'No datapoints'
echohlne created AMBARI-25566: - Summary: HBase 'Mutate Latencies-Average' metric in grafana always shows 'No datapoints' Key: AMBARI-25566 URL: https://issues.apache.org/jira/browse/AMBARI-25566 Project: Ambari Issue Type: Bug Affects Versions: 2.7.4 Reporter: echohlne Attachments: HBase Mutate Latencies shows No dataPoints.png I checked in ambari2.7.3 and 2.7.4, all have the problem.see attached picture -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25568) The 'NodeManager RAM Utilized' metric in the heatmap of YARN does not show the unit
echohlne created AMBARI-25568: - Summary: The 'NodeManager RAM Utilized' metric in the heatmap of YARN does not show the unit Key: AMBARI-25568 URL: https://issues.apache.org/jira/browse/AMBARI-25568 Project: Ambari Issue Type: Improvement Affects Versions: 2.7.4 Reporter: echohlne Fix For: 2.7.6 Attachments: NodeManager RAM Utilized no unit.png The 'NodeManager RAM Utilized' metric in the heatmap of YARN does not show the unit，as the attachment shows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178264#comment-17178264 ] echohlne edited comment on AMBARI-25545 at 8/26/20, 6:50 AM: - I create a pr: [https://github.com/apache/ambari/pull/3220 |https://github.com/apache/ambari/pull/3220] and have tested the patch in my environment, the result screenshot is in the attachment. was (Author: echohlne): I create a pr: [https://github.com/apache/ambari/pull/3220 |https://github.com/apache/ambari/pull/3220] and have tested the patch in my environment. [~hapylestat] could you please help me review? Thank you! > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-fixed-screenshot.png, question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > # create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > # Select a directory just created in step 1, then click download button, and > you can see that the name of the generated zip file is incorrect. > > The problem screenshot is shown in the attachment. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Attachment: question-fixed-screenshot.png > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-fixed-screenshot.png, question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > # create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > # Select a directory just created in step 1, then click download button, and > you can see that the name of the generated zip file is incorrect. > > The problem screenshot is shown in the attachment. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) fix downloaded zip-file name shows empty in the fileview page.
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Summary: fix downloaded zip-file name shows empty in the fileview page. (was: If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly) > fix downloaded zip-file name shows empty in the fileview page. > -- > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-fixed-screenshot.png, question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > # create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > # Select a directory just created in step 1, then click download button, and > you can see that the name of the generated zip file is incorrect. > > The problem screenshot is shown in the attachment. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap-metrics-negative-fixed-screenshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap-metrics-negative-screentshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap-metrics-negative-fixed-screenshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap--metrics-NaN-fixed-screentshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: (was: heatmap-negative-screentshot.png) > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: (was: heatmap-NaN-screentshot.png) > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap--metrics-NaN-fixed-screentshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: (was: heatmap--metrics-NaN-fixed-screentshot.png) > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: (was: heatmap-metrics-negative-fixed-screenshot.png) > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Attachment: heatmap--metrics-NaN-screentshot.png > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179710#comment-17179710 ] echohlne edited comment on AMBARI-25546 at 8/26/20, 5:28 AM: - we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3223] please help to review it thanks a lot. was (Author: echohlne): we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3221] please help to review it thanks a lot. > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179710#comment-17179710 ] echohlne edited comment on AMBARI-25546 at 8/26/20, 5:45 AM: - we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3223] the test result screenshot is in the attachment please help to review it thanks a lot. was (Author: echohlne): we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3223] please help to review it thanks a lot. > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap--metrics-NaN-fixed-screentshot.png, > heatmap--metrics-NaN-screentshot.png, > heatmap-metrics-negative-fixed-screenshot.png, > heatmap-metrics-negative-screentshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing
echohlne created AMBARI-25546: - Summary: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing Key: AMBARI-25546 URL: https://issues.apache.org/jira/browse/AMBARI-25546 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.4 Reporter: echohlne Fix For: 2.7.5 Attachments: heatmap-NaN-screentshot.png, heatmap-negative-screentshot.png It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing. examples has been shown in the attachment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Description: Steps to Reproduce: # create a directory contains non-ascii characters such as create a Chinese directory or a Japanese directory. # Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. The problem screenshot is shown in the attachment. was: Steps to Reproduce: 1. create a directory contains non-ascii characters such as create a Chinese directory or a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > # create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > # Select a directory just created in step 1, then click download button, and > you can see that the name of the generated zip file is incorrect. > > The problem screenshot is shown in the attachment. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Description: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing which is not very kindly. examples has been shown in the attachment. was: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing. examples has been shown in the attachment. > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Summary: The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing) > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Summary: the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing) > the maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- External issue URL: (was: https://github.com/apache/ambari/pull/3221) Fix Version/s: (was: 2.7.5) 2.7.6 > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- External issue URL: https://github.com/apache/ambari/pull/3221 > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Summary: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing) > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers after parsing. > examples has been shown in the attachment -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25546) The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179710#comment-17179710 ] echohlne commented on AMBARI-25546: --- we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3221] please help to review it thanks a lot. > The maximum parameter on the heapmap page still supports negative numbers And > NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Description: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing. examples has been shown in the attachment. was: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing. examples has been shown in the attachment > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25545) If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly
echohlne created AMBARI-25545: - Summary: If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly Key: AMBARI-25545 URL: https://issues.apache.org/jira/browse/AMBARI-25545 Project: Ambari Issue Type: Bug Components: contrib Affects Versions: 2.7.4 Environment: ambari 2.7.4 Reporter: echohlne Fix For: 2.7.6 Steps to Reproduce: 1. create a Chinese directory and a Japanese directory. 2. Select a directory just created in step 1,and then click download button, you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Attachment: question-screenshot.png > If the file directory name in HDFS contains non-ASCII characters, the zip > file name generated by downloading will be displayed incorrectly > -- > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to Reproduce: > > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1,and then click download button, > you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25545) If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178264#comment-17178264 ] echohlne commented on AMBARI-25545: --- I create a pr: [https://github.com/apache/ambari/pull/3219] I have tested the patch in my environment. > If the file directory name in HDFS contains non-ASCII characters, the zip > file name generated by downloading will be displayed incorrectly > -- > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to Reproduce: > > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1,and then click download button, > you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Priority: Major (was: Minor) > If the file directory name in HDFS contains non-ASCII characters, the zip > file name generated by downloading will be displayed incorrectly > -- > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to Reproduce: > > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1,and then click download button, > you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Summary: If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly (was: If the file directory name in HDFS contains non-ASCII characters, the zip file name generated by downloading will be displayed incorrectly) > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to Reproduce: > > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1,and then click download button, > you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Description: Steps to Reproduce: 1. create a directory contains non-ascii characters such as create a Chinese directory or a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. was: Steps to Reproduce: 1. create a directory contains non-ascii characters such as Chinese directory and a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > 1. create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > 2. Select a directory just created in step 1, then click download button, > and you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Description: Steps to Reproduce: 1. create a directory contains non-ascii characters such as Chinese directory and a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. was: Steps to Reproduce: 1. create a Chinese directory and a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > 1. create a directory contains non-ascii characters such as Chinese > directory and a Japanese directory. > 2. Select a directory just created in step 1, then click download button, > and you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Description: Steps to Reproduce: 1. create a Chinese directory and a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. was: Steps to Reproduce: 1. create a Chinese directory and a Japanese directory. 2. Select a directory just created in step 1,and then click download button, you can see that the name of the generated zip file is incorrect. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > Steps to Reproduce: > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1, then click download button, > and you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178264#comment-17178264 ] echohlne edited comment on AMBARI-25545 at 8/15/20, 3:47 PM: - I create a pr: [https://github.com/apache/ambari/pull/3220 |https://github.com/apache/ambari/pull/3220] and have tested the patch in my environment. was (Author: echohlne): I create a pr: [https://github.com/apache/ambari/pull/3219] I have tested the patch in my environment. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > 1. create a Chinese directory and a Japanese directory. > 2. Select a directory just created in step 1, then click download button, > and you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178264#comment-17178264 ] echohlne edited comment on AMBARI-25545 at 8/16/20, 8:28 AM: - I create a pr: [https://github.com/apache/ambari/pull/3220 |https://github.com/apache/ambari/pull/3220] and have tested the patch in my environment. [~hapylestat] could you please help me review? Thank you! was (Author: echohlne): I create a pr: [https://github.com/apache/ambari/pull/3220 |https://github.com/apache/ambari/pull/3220] and have tested the patch in my environment. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > 1. create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > 2. Select a directory just created in step 1, then click download button, > and you can see that the name of the generated zip file is incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
