[jira] [Created] (AMBARI-25574) Start/Stop All Button color are not displayed correctly

akiyamaneko created AMBARI-25574: Summary: Start/Stop All Button color are not displayed correctly Key: AMBARI-25574 URL: https://issues.apache.org/jira/browse/AMBARI-25574 Project: Ambari

[jira] [Updated] (AMBARI-25574) Start/Stop All Button color are not displayed correctly

[ https://issues.apache.org/jira/browse/AMBARI-25574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25574: - Attachment: (was: Start All icon fixes wrong color.png) > Start/Stop All Button color are

[jira] [Updated] (AMBARI-25574) Start/Stop All Button color are not displayed correctly

[ https://issues.apache.org/jira/browse/AMBARI-25574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25574: - Description: Start/Stop All Button color In ambari web page are not displayed correctly, The

[jira] [Updated] (AMBARI-25574) Start/Stop All Button color are not displayed correctly

[ https://issues.apache.org/jira/browse/AMBARI-25574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25574: - Attachment: Stop All icon shows wrong color.png > Start/Stop All Button color are not

[jira] [Created] (AMBARI-25573) Ambari Metrics save as JSON/CSV use metricName instead of default name.

akiyamaneko created AMBARI-25573: Summary: Ambari Metrics save as JSON/CSV use metricName instead of default name. Key: AMBARI-25573 URL: https://issues.apache.org/jira/browse/AMBARI-25573 Project:

[jira] [Created] (AMBARI-25592) Fix the problem that JVM related metrics in hbase and ams cannot be displayed

akiyamaneko created AMBARI-25592: Summary: Fix the problem that JVM related metrics in hbase and ams cannot be displayed Key: AMBARI-25592 URL: https://issues.apache.org/jira/browse/AMBARI-25592

[jira] [Created] (AMBARI-25600) The default widget name generated by the clone-widget is incorrect

akiyamaneko created AMBARI-25600: Summary: The default widget name generated by the clone-widget is incorrect Key: AMBARI-25600 URL: https://issues.apache.org/jira/browse/AMBARI-25600 Project:

[jira] [Updated] (AMBARI-25600) The default widget name generated by the clone-widget is incorrect

[ https://issues.apache.org/jira/browse/AMBARI-25600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25600: - Attachment: cloned widget.png > The default widget name generated by the clone-widget is

[jira] [Commented] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"

[ https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238251#comment-17238251 ] akiyamaneko commented on AMBARI-25591: -- [~dhire...@gmail.com] It is recommended that you login

[jira] [Comment Edited] (AMBARI-25591) org.postgresql.util.PSQLException: FATAL: password authentication failed for user "mapred"

[ https://issues.apache.org/jira/browse/AMBARI-25591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17238251#comment-17238251 ] akiyamaneko edited comment on AMBARI-25591 at 11/24/20, 4:49 PM: -

[jira] [Created] (AMBARI-25593) ambari-agent.log output prints password in plain text

akiyamaneko created AMBARI-25593: Summary: ambari-agent.log output prints password in plain text Key: AMBARI-25593 URL: https://issues.apache.org/jira/browse/AMBARI-25593 Project: Ambari

[jira] [Created] (AMBARI-25594) ambari-agent.log output prints password in plain text

akiyamaneko created AMBARI-25594: Summary: ambari-agent.log output prints password in plain text Key: AMBARI-25594 URL: https://issues.apache.org/jira/browse/AMBARI-25594 Project: Ambari

[jira] [Resolved] (AMBARI-25594) ambari-agent.log output prints password in plain text

[ https://issues.apache.org/jira/browse/AMBARI-25594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko resolved AMBARI-25594. -- Resolution: Duplicate > ambari-agent.log output prints password in plain text >

[jira] [Updated] (AMBARI-25593) ambari-agent.log output prints password in plain text

[ https://issues.apache.org/jira/browse/AMBARI-25593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25593: - Priority: Critical (was: Major) > ambari-agent.log output prints password in plain text >

[jira] [Issue Comment Deleted] (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:all-tabpanel ] akiyamaneko updated AMBARI-25543: - Comment: was deleted (was: I try to fix this with this pr: 

[jira] [Updated] (AMBARI-25583) The notes field in the config history page does not support UTF-8 characters such as Chinese/Japanese for filtering

[ https://issues.apache.org/jira/browse/AMBARI-25583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25583: - Attachment: filter_by_notes_expected_result.png filter_by_notes_screenshot.png

[jira] [Created] (AMBARI-25583) The notes field in the config history page does not support UTF-8 characters such as Chinese/Japanese for filtering

akiyamaneko created AMBARI-25583: Summary: The notes field in the config history page does not support UTF-8 characters such as Chinese/Japanese for filtering Key: AMBARI-25583 URL:

[jira] [Comment Edited] (AMBARI-25572) Metrics cannot be stored if mutation size is not set properly

[ https://issues.apache.org/jira/browse/AMBARI-25572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232545#comment-17232545 ] akiyamaneko edited comment on AMBARI-25572 at 11/16/20, 9:09 AM: -

[jira] [Issue Comment Deleted] (AMBARI-24855) Ambari does not prompt History Server restart upon modification in "yarn.log-aggregation.retain-seconds"

[ https://issues.apache.org/jira/browse/AMBARI-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-24855: - Comment: was deleted (was: [~itskrishspace] hi,guys, I tried to reproduce this problem

[jira] [Commented] (AMBARI-24855) Ambari does not prompt History Server restart upon modification in "yarn.log-aggregation.retain-seconds"

[ https://issues.apache.org/jira/browse/AMBARI-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232563#comment-17232563 ] akiyamaneko commented on AMBARI-24855: -- [~itskrishspace] hi,guys, I tried to reproduce this

[jira] [Commented] (AMBARI-24855) Ambari does not prompt History Server restart upon modification in "yarn.log-aggregation.retain-seconds"

[ https://issues.apache.org/jira/browse/AMBARI-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232562#comment-17232562 ] akiyamaneko commented on AMBARI-24855: -- [~itskrishspace] hi,guys, I tried to reproduce this

[jira] [Comment Edited] (AMBARI-25572) Metrics cannot be stored if mutation size is not set properly

[ https://issues.apache.org/jira/browse/AMBARI-25572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232545#comment-17232545 ] akiyamaneko edited comment on AMBARI-25572 at 11/16/20, 9:08 AM: -

[jira] [Updated] (AMBARI-25587) Metrics cannot be stored and the exception message is null when metric value is NaN

[ https://issues.apache.org/jira/browse/AMBARI-25587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25587: - Summary: Metrics cannot be stored and the exception message is null when metric value is NaN

[jira] [Created] (AMBARI-25587) metrics-timelineservice cannot handle special metric value: NaN correctly

akiyamaneko created AMBARI-25587: Summary: metrics-timelineservice cannot handle special metric value: NaN correctly Key: AMBARI-25587 URL: https://issues.apache.org/jira/browse/AMBARI-25587 Project:

[jira] [Created] (AMBARI-25586) The page will not refresh automatically after the permission was modified in the Files View page

akiyamaneko created AMBARI-25586: Summary: The page will not refresh automatically after the permission was modified in the Files View page Key: AMBARI-25586 URL:

[jira] [Updated] (AMBARI-25586) The page will not refresh automatically after the permission was modified in the Files View page

[ https://issues.apache.org/jira/browse/AMBARI-25586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25586: - Issue Type: Improvement (was: Bug) > The page will not refresh automatically after the

[jira] [Commented] (AMBARI-25572) Metrics cannot be stored if mutation size is not set properly

[ https://issues.apache.org/jira/browse/AMBARI-25572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17232545#comment-17232545 ] akiyamaneko commented on AMBARI-25572: -- [~payert] We have also encountered this problem. Is there

[jira] [Created] (AMBARI-25585) The functions related to remote cluster have some problems

akiyamaneko created AMBARI-25585: Summary: The functions related to remote cluster have some problems Key: AMBARI-25585 URL: https://issues.apache.org/jira/browse/AMBARI-25585 Project: Ambari

[jira] [Updated] (AMBARI-25585) There are some problems with the remote cluster management function

[ https://issues.apache.org/jira/browse/AMBARI-25585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25585: - Summary: There are some problems with the remote cluster management function (was: The

[jira] [Updated] (AMBARI-25585) There are some problems with the remote cluster management

[ https://issues.apache.org/jira/browse/AMBARI-25585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25585: - Summary: There are some problems with the remote cluster management (was: There are some

[jira] [Created] (AMBARI-25579) Historical configuration parameters display garbled characters

akiyamaneko created AMBARI-25579: Summary: Historical configuration parameters display garbled characters Key: AMBARI-25579 URL: https://issues.apache.org/jira/browse/AMBARI-25579 Project: Ambari

[jira] [Updated] (AMBARI-25578) HBase 'Num Scan Next Requests' metric in grafana always shows 'No datapoints'

[ https://issues.apache.org/jira/browse/AMBARI-25578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] akiyamaneko updated AMBARI-25578: - Attachment: screenshot.png > HBase 'Num Scan Next Requests' metric in grafana always shows 'No

[jira] [Created] (AMBARI-25578) HBase 'Num Scan Next Requests' metric in grafana always shows 'No datapoints'

akiyamaneko created AMBARI-25578: Summary: HBase 'Num Scan Next Requests' metric in grafana always shows 'No datapoints' Key: AMBARI-25578 URL: https://issues.apache.org/jira/browse/AMBARI-25578

[jira] [Commented] (AMBARI-25572) Metrics cannot be stored if mutation size is not set properly

[ https://issues.apache.org/jira/browse/AMBARI-25572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364138#comment-17364138 ] akiyamaneko commented on AMBARI-25572: -- Sorry for the delay, I've tried to update the