[jira] [Updated] (AMBARI-26027) no data is available for monitoring indicators of components such as hdfs and yarn on the web page
[ https://issues.apache.org/jira/browse/AMBARI-26027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-26027: Labels: pull-request-available (was: ) > no data is available for monitoring indicators of components such as hdfs and > yarn on the web page > -- > > Key: AMBARI-26027 > URL: https://issues.apache.org/jira/browse/AMBARI-26027 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7 >Reporter: zhilong.deng >Priority: Major > Labels: pull-request-available > Attachments: image-2023-11-20-09-56-56-068.png, > image-2023-11-20-09-57-27-880.png, image-2023-11-20-10-00-56-139.png > > > When we look at the monitoring indicators through the ambari page, we can > only see the following picture: > !image-2023-11-20-09-56-56-068.png! > !image-2023-11-20-09-57-27-880.png! > I have fixed this issue and the link is : > [https://github.com/452926826/ambari-metrics/tree/AMBARI-26027|http://example.com/] > The effect is as follows: > !image-2023-11-20-10-00-56-139.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26022) Ambari Metrics Subporject supports Python3 environment
[ https://issues.apache.org/jira/browse/AMBARI-26022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-26022: Labels: pull-request-available (was: ) > Ambari Metrics Subporject supports Python3 environment > -- > > Key: AMBARI-26022 > URL: https://issues.apache.org/jira/browse/AMBARI-26022 > Project: Ambari > Issue Type: Improvement >Affects Versions: metrics-3.0.0 >Reporter: lucas >Assignee: lucas >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > Hi, > I create this issue to make a pull request for adding Python support to > ambari-metrics subproject > I have modified the code as in AMBARI-26000 and run maven unit tests with the > following command. > mvn -Dmaven.test.failure.ignore=true test -Dmaven.artifact.threads=10 > -Drat.skip -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-26020) upgrade Ambari Metrics to python3
[ https://issues.apache.org/jira/browse/AMBARI-26020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-26020: Labels: pull-request-available (was: ) > upgrade Ambari Metrics to python3 > - > > Key: AMBARI-26020 > URL: https://issues.apache.org/jira/browse/AMBARI-26020 > Project: Ambari > Issue Type: Improvement >Reporter: caijialiang >Assignee: caijialiang >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25998) Host uuid is not getting synced to other collectors, causing NPE while accessing metric
[ https://issues.apache.org/jira/browse/AMBARI-25998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25998: Labels: pull-request-available (was: ) > Host uuid is not getting synced to other collectors, causing NPE while > accessing metric > --- > > Key: AMBARI-25998 > URL: https://issues.apache.org/jira/browse/AMBARI-25998 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > Host uuid is not getting synced with other collectors, causing NPE while > accessing metric > {code:java} > java.lang.NullPointerException > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457) > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150) > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966) > at > org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294) > at > org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267) > {code} > *Steps to reproduce the issue* > 1. Push below metrics through collector-1 > {noformat} > { > "metrics": [ > { > "metricname": "cpu1", > "appid": "app1", > "hostname": "host1", > "starttime": 1693294119309, > "metrics": { > "1693294119309": 100, > "1693294129309": 200 > } > } > ] > } > {noformat} > After metadata sync interval elapsed, performed following operations > 2. GET http://COLLECTOR-1-HOST:6188/ws/v1/timeline/metrics/hosts returned > {noformat} > { > "host1": [ > "app1" > ], > ... > } > {noformat} > 3. GET http://COLLECTOR-2-HOST:6188/ws/v1/timeline/metrics/hosts returned > { > "host1": [ > "app1" > ], > ... > } > 4. GET > http://COLLECTOR-1-HOST:6188/ws/v1/timeline/metrics?metricNames=cpu1=app1=host1 > returned > { > "metrics": [ > { > "metricname": "cpu1", > "appid": "app1", > "hostname": "host1", > "timestamp": 0, > "starttime": 1693294119309, > "metrics": { > "1693294129309": 200.0 > }, > "metadata": {} > } > ] > } > 5. GET > http://COLLECTOR-2-HOST:6188/ws/v1/timeline/metrics?metricNames=cpu1=app1=host1 > returned > {noformat} > { > "exception": "NullPointerException", > "javaClassName": "java.lang.NullPointerException" > } > {noformat} > When host name is being synced, host id also should be synced to fix this > issue. > Similar to this issue another issue > https://issues.apache.org/jira/browse/AMBARI-25963 was raised, but that NPE > was because metrics uuid was not synced, this issue is because of host uuid > is not synced. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25995) Resolve mutate related graphs for hbase & ams-hbase
[ https://issues.apache.org/jira/browse/AMBARI-25995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25995: Labels: pull-request-available (was: ) > Resolve mutate related graphs for hbase & ams-hbase > --- > > Key: AMBARI-25995 > URL: https://issues.apache.org/jira/browse/AMBARI-25995 > Project: Ambari > Issue Type: Story >Reporter: Sandeep Kumar >Assignee: Sandeep Kumar >Priority: Major > Labels: pull-request-available > Attachments: image-2023-08-22-00-51-53-101.png, > image-2023-08-22-00-55-55-893.png, image-2023-08-22-00-56-40-536.png, > image-2023-08-22-00-58-18-615.png, image-2023-08-22-00-58-26-998.png, > image-2023-08-22-00-59-35-889.png, image-2023-08-22-01-00-22-674.png > > Time Spent: 10m > Remaining Estimate: 0h > > These graphs are showing no data > AMS-hbase home: > !image-2023-08-22-00-51-53-101.png|width=451,height=148! > ams-hbase-regionserver: > !image-2023-08-22-00-55-55-893.png|width=444,height=162! > !image-2023-08-22-00-56-40-536.png|width=450,height=195! > HBase-home: > !image-2023-08-22-00-58-26-998.png|width=445,height=127! > Hbase-regionserver: > !image-2023-08-22-01-00-22-674.png|width=406,height=148! > !image-2023-08-22-00-59-35-889.png|width=408,height=177! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25992) logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25992: Labels: pull-request-available (was: ) > logsearch-portal cannot startup due to spring-boot-autoconfigure upgrade > > > Key: AMBARI-25992 > URL: https://issues.apache.org/jira/browse/AMBARI-25992 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Labels: pull-request-available > > ambari-logsearch-portal server cannot startup. > After spring-boot upgrade from 2.0.6.RELEASE to 2.1.5.RELEASE, due to the > change of class LdapAutoConfiguration, spring need the LdapTemplate bean > during startup. > Without the LdapTemplate bean, logsearch-portal server report the following > error: > 2023-08-11 06:28:24,471 [main] WARN org.eclipse.jetty.webapp.WebAppContext > (WebAppContext.java:554) - Failed startup of context > o.s.b.w.e.j.JettyEmbeddedWebAppContext@6e8fdd19\{application,/,[file:///tmp/jetty-docbase.7488131157696980871.61888/, > > jar:file:/usr/lib/ambari-logsearch-portal/libs/swagger-ui-3.19.0.jar!/META-INF/resources],UNAVAILABLE} > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'servletEndpointRegistrar' defined in class path resource > [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]: > Bean instantiation via factory method failed; nested exception is > org.springframework.beans.BeanInstantiationException: Failed to instantiate > [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: > Factory method 'servletEndpointRegistrar' threw exception; nested exception > is org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name 'healthEndpoint' defined in class path resource > [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: > Unsatisfied dependency expressed through method 'healthEndpoint' parameter > 1; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'healthIndicatorRegistry' defined in class path resource > [org/springframework/boot/actuate/autoconfigure/health/HealthIndicatorAutoConfiguration.class]: > Bean instantiation via factory method failed; nested exception is > org.springframework.beans.BeanInstantiationException: Failed to instantiate > [org.springframework.boot.actuate.health.HealthIndicatorRegistry]: Factory > method 'healthIndicatorRegistry' threw exception; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.boot.actuate.autoconfigure.ldap.LdapHealthIndicatorAutoConfiguration': > Unsatisfied dependency expressed through constructor parameter 0; nested > exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name 'ldapTemplate' defined in class path resource > [org/springframework/boot/autoconfigure/ldap/LdapAutoConfiguration.class]: > Unsatisfied dependency expressed through method 'ldapTemplate' parameter 0; > nested exception is > org.springframework.beans.factory.NoSuchBeanDefinitionException: No > qualifying bean of type 'org.springframework.ldap.core.ContextSource' > available: expected at least 1 bean which qualifies as autowire candidate. > Dependency annotations: {} > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25993) logsearch-logfeeder cannot startup due to lake of configuration
[ https://issues.apache.org/jira/browse/AMBARI-25993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25993: Labels: pull-request-available (was: ) > logsearch-logfeeder cannot startup due to lake of configuration > --- > > Key: AMBARI-25993 > URL: https://issues.apache.org/jira/browse/AMBARI-25993 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Assignee: Robin Zuo >Priority: Major > Labels: pull-request-available > > logsearch-logfeeder fail to start and report the following error: > 2023-08-19 14:20:40,835 [main] INFO > org.springframework.boot.StartupInfoLogger (StartupInfoLogger.java:50) - > Starting LogFeeder on hadoop-1 with PID 78570 > (/usr/lib/ambari-logsearch-logfeeder/libs/ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar > started by root in /var/lib/ambari-agent) > 2023-08-19 14:20:40,861 [main] INFO > org.springframework.boot.SpringApplication (SpringApplication.java:675) - No > active profile set, falling back to default profiles: default > 2023-08-19 14:20:43,187 [main] ERROR > org.springframework.boot.SpringApplication (SpringApplication.java:858) - > Application run failed > java.lang.IllegalArgumentException: String 'null' cannot be converted to > LogFeederMode enum > at > org.apache.ambari.logfeeder.conf.LogFeederMode.fromString(LogFeederMode.java:48) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.apache.ambari.logfeeder.conf.condition.NonCloudStorageCondition.matches(NonCloudStorageCondition.java:34) > ~[ambari-logsearch-logfeeder-3.0.0.0-SNAPSHOT.jar:?] > at > org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:108) > ~[spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[ https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25984: Labels: pull-request-available (was: ) > Ambari metrics summary API missing daily aggregator info > > > Key: AMBARI-25984 > URL: https://issues.apache.org/jira/browse/AMBARI-25984 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Attachments: screenshot-1.png > > > API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following > {noformat} > { > "timestamp": 1691405233095, > "metadata": { > "timeline_metric_store_watcher": "2", > "datanode": "329", > "HOST": "154", > "jobhistoryserver": "67", > "namenode": "457", > "ambari_server": "79", > "hiveserver2": "116", > "amssmoketestfake": "2", > "hivemetastore": "438", > "resourcemanager": "257", > "Number of Hosts": "7", > "applicationhistoryserver": "108", > "nodemanager": "366", > "hbase": "1950", > "ams-hbase": "5583" > }, > "aggregation": { > "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023", > "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023", > "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023", > "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023", > "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023" > } > } > {noformat} > In above aggregation information TimelineMetricHostAggregatorDaily and > TimelineClusterAggregatorDaily are missing. Summary API should return these > aggregation detail also. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25975: Labels: pull-request-available (was: ) > Grafana upgrade to 9.x caused many issues in metrics grafana dashboards. > > > Key: AMBARI-25975 > URL: https://issues.apache.org/jira/browse/AMBARI-25975 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png, > screenshot-2.png, screenshot-3.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes > etc. template loading is failing with error > {noformat} > An unexpected error happened > Details > TypeError: Cannot read properties of null (reading 'text') > at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025) > at g > (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468) > at div > at en > (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150) > at div > at nn > (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022) > at form > at div > at _a > (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395) > {noformat} > # datasource.js is throwing error while populating data. for example > yarn-queue dashboard logs below error in browser console > !image-2023-07-24-23-52-31-437.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25976) Upgrade grafana to remediate CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25976: Labels: pull-request-available (was: ) > Upgrade grafana to remediate CVEs > - > > Key: AMBARI-25976 > URL: https://issues.apache.org/jira/browse/AMBARI-25976 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > Grafana Security Advisory > https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ > Upgrade grafana to latest 9.x available version 9.5.6 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25963) Metrics metadata sync problem, accessing metrics which got created though other collector throws NPE
[ https://issues.apache.org/jira/browse/AMBARI-25963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25963: Labels: pull-request-available (was: ) > Metrics metadata sync problem, accessing metrics which got created though > other collector throws NPE > > > Key: AMBARI-25963 > URL: https://issues.apache.org/jira/browse/AMBARI-25963 > Project: Ambari > Issue Type: Bug >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Critical > Labels: pull-request-available > > Metrics metadata sync problem, accessing metrics which got created though > other collector throws NPE > *Steps to reproduce the issue:* > # Install ambari metrics with two collectors C1 and C2 > # Submit following metrics through collector C1 > {code:java} > { > "metrics": [ > { > "metricname": "cpu", > "appid": "skywalking", > "hostname": "hostXYZ", > "starttime": 1687944230477, > "metrics": { > "1687944230477": 100, > "1687944430477": 200 > } > } > ] > } > {code} > # > http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics?metricNames=cpu=skywalking=hostXYZ > API call returns > {noformat} > { > "exception": "NullPointerException", > "javaClassName": "java.lang.NullPointerException" > } > {noformat} > In collector C2 log file following message is logged > {code} > 2023-06-28 09:40:24,592 ERROR > org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager: > TimelineMetricMetadataKey is null for : [7, 73, 67, -94, 19, -102, 82, 114, > 100, -66, -22, 79, -51, -107, -73, 64, -36, -72, -42, -103] > 2023-06-28 09:40:24,594 WARN > org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR > java.lang.NullPointerException > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457) > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150) > at > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966) > at > org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294) > at > org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267) > {code} > Same behaviour is there even after 5 minutes which is the default ambari > metrics metadata sync interval. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25962) Host apps metadata is not synced to other collectors when multiple collectors are installed
[ https://issues.apache.org/jira/browse/AMBARI-25962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25962: Labels: pull-request-available (was: ) > Host apps metadata is not synced to other collectors when multiple collectors > are installed > --- > > Key: AMBARI-25962 > URL: https://issues.apache.org/jira/browse/AMBARI-25962 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Critical > Labels: pull-request-available > > Host apps metadata is not synced to other collectors when multiple metrics > collectors are installed. > *Steps to reproduce the issue:* > # Install ambari metrics with two collector C1 and C2 > # Submit following metrics through collector C1 > {code:java} > { > "metrics": [ > { > "metricname": "cpu", > "appid": "skywalking", > "hostname": "hostXYZ", > "starttime": 1687849289558, > "metrics": { > "1687849289558": 100, > "1687849295558": 200 > } > } > ] > } > {code} > # http://COLLECTOR_C1_HOST:6188/ws/v1/timeline/metrics/hosts API call returns > {noformat} > { > "hostXYZ": [ > "datanode", > "HOST", > "namenode", > "skywalking", > "ams-hbase" > ], > ... > } > {noformat} > This is as expected. > # http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics/hosts API call returns > {noformat} > { > "hostXYZ": [ > "datanode", > "HOST", > "namenode", > "ams-hbase" > ], > ... > } > {noformat} > This output indicates that new appid skywalking is not getting synced to > other collector C2. This new appid is not getting synced even after 5 minutes > which is the default ambari metrics metadata sync interval. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25959) Ambari Metrics Grafana rpm missing some grafana tarball files
[ https://issues.apache.org/jira/browse/AMBARI-25959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25959: Labels: pull-request-available (was: ) > Ambari Metrics Grafana rpm missing some grafana tarball files > - > > Key: AMBARI-25959 > URL: https://issues.apache.org/jira/browse/AMBARI-25959 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > grafana-9.3.2.linux-amd64.tar.gz is extracted in folder > ambari-metrics-grafana/target/grafana/grafana-9.3.2 then all files inside > grafana-9.3.2 are used while building the rpm. But while extracting > grafana-9.3.2.linux-amd64.tar.gz some files are getting extracted in inside > ambari-metrics-grafana/target/grafana which then are not part of the rpm > > Grafana tarball extraction script to be changed so all files are placed > inside correct folder. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25958) Ambari metrics returns Infinity when rate transformation is used
[ https://issues.apache.org/jira/browse/AMBARI-25958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25958: Labels: pull-request-available (was: ) > Ambari metrics returns Infinity when rate transformation is used > > > Key: AMBARI-25958 > URL: https://issues.apache.org/jira/browse/AMBARI-25958 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give > value as Infinity. This is incorrect. > For example invoking below URL returned Infinity along with other values > http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate=seconds=true=1686815115333=hbase=1686815945333 > > Output: > {noformat} > 1686796983505:679 > 1686797040051: 0.8214285714285714 > 1686797040144:"Infinity" > 1686797042427:55 > 1686797043504:2027 > 1686797100144:"Infinity" > 1686797102426:55{noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25957) Ambari Metrics Grafana Datasource is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25957: Labels: pull-request-available (was: ) > Ambari Metrics Grafana Datasource is not working > > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25954) Upgrade ignite-core to 2.1.0 to 2.15.0
[ https://issues.apache.org/jira/browse/AMBARI-25954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25954: Labels: pull-request-available (was: ) > Upgrade ignite-core to 2.1.0 to 2.15.0 > -- > > Key: AMBARI-25954 > URL: https://issues.apache.org/jira/browse/AMBARI-25954 > Project: Ambari > Issue Type: Improvement >Reporter: Sand Shreeya >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25935) Upgrade Ambari Infra Solr to version 8 and ensure it is consistent with the Solr version in Ambari 2.8 stack
[ https://issues.apache.org/jira/browse/AMBARI-25935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25935: Labels: pull-request-available (was: ) > Upgrade Ambari Infra Solr to version 8 and ensure it is consistent with the > Solr version in Ambari 2.8 stack > > > Key: AMBARI-25935 > URL: https://issues.apache.org/jira/browse/AMBARI-25935 > Project: Ambari > Issue Type: Technical task >Reporter: caijialiang >Priority: Major > Labels: pull-request-available > > Upgrade Ambari Infra Solr to version 8 and ensure it is consistent with the > Solr version in Ambari 2.8 stack. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25710) Update Ambari website
[ https://issues.apache.org/jira/browse/AMBARI-25710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25710: Labels: pull-request-available (was: ) > Update Ambari website > - > > Key: AMBARI-25710 > URL: https://issues.apache.org/jira/browse/AMBARI-25710 > Project: Ambari > Issue Type: Task >Reporter: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > > Several items on the website needs a revamp. > (1) instead of IRC, we now use Slack. > (2) Announce that Ambari is back in "what's New" > (3) "The Team" page. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25880) For hadoop_logs collection of Infra-solr, indexed log_message field is too large to copy to key_log_message field
[ https://issues.apache.org/jira/browse/AMBARI-25880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25880: Labels: pull-request-available (was: ) > For hadoop_logs collection of Infra-solr, indexed log_message field is too > large to copy to key_log_message field > - > > Key: AMBARI-25880 > URL: https://issues.apache.org/jira/browse/AMBARI-25880 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.3 >Reporter: guluo >Priority: Critical > Labels: pull-request-available > > The hadoop_logs collection of Infra-solr is used to store logs generated by > services, such as hadoop、spark, etc. > However, Infra-solr will report an error when the length of the single-line > log generated by services exceeds 2^15-2, Because Infra-solr cannot copy the > data of field log_message to field key_log_messag > {code:java} > //代码占位符 > org.apache.solr.common.SolrException: Exception writing document id > 54d786cd-f6a7-4746-9b17-e9b2b0fe389a to the index; possible analysis error: > Document contains at least one immense term in field="action" (whose UTF8 > encoding is longer than the max length 32766), all of which were skipped. > Please correct the analyzer to not produce such terms. The prefix of the > first immense term is: '[98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, > 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98, 98]...', > original message: bytes can be at most 32766 in length; got 32767. Perhaps > the document has an indexed string field (solr.StrField) which is too large > {code} > *Reproduce Step:* > 1 Create a json File named data.json > [ > { > "log_message": "", > "id": "54d786cd-f6a7-4746-9b17-e9b2b0fe3efa" > } > ] > Note: the content of field log_message is a randomly generated string with a > length exceeding 2^15-2 > 2 Update the hadoop_logs > curl http://ip:port/solr/hadoop_logs/update?commit=true -H > 'Content-type:application/json' --data-binary @data.json > 3 Get the error message mentioned above > > *similar issue:* > AMBARI-24067: Log Search: indexed string field could be too large for > audit_logs > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25876) Define next version number for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25876: Labels: pull-request-available (was: ) > Define next version number for Ambari Metrics > - > > Key: AMBARI-25876 > URL: https://issues.apache.org/jira/browse/AMBARI-25876 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > When ambari-metrics is a module of ambari, it uses all versions before 2.8.0, > and the version number contains 5 digits, x.x.x.x.x, which also contains the > release version number. > If we merge AMBARI-25875, then the version number will only be 3 digits and > will no longer contain the release version number, I think this is a big > change for identifying versions, so I prefer to upgrade the major version and > set the next version to 3.0.0 for ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25875) Use separate property for release version for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25875: Labels: pull-request-available (was: ) > Use separate property for release version for Ambari Metrics > > > Key: AMBARI-25875 > URL: https://issues.apache.org/jira/browse/AMBARI-25875 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > > In AMBARI-25859, we use *x.y.z-p* for version number and *p* stands for > release version, but this may confused for people, so I'd like to split *p* > into a separate property -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25867) Introduce CI build for Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25867: Labels: pull-request-available (was: ) > Introduce CI build for Ambari Metrics > - > > Key: AMBARI-25867 > URL: https://issues.apache.org/jira/browse/AMBARI-25867 > Project: Ambari > Issue Type: Improvement >Reporter: Kengo Seki >Assignee: Kengo Seki >Priority: Major > Labels: pull-request-available > > It would be better if we had CI build for Ambari Metrics so that we could > notice unit test failures before merging PR. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25866) Fix an unit test failure on ambari-metrics-kafka-sink
[ https://issues.apache.org/jira/browse/AMBARI-25866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25866: Labels: pull-request-available (was: ) > Fix an unit test failure on ambari-metrics-kafka-sink > - > > Key: AMBARI-25866 > URL: https://issues.apache.org/jira/browse/AMBARI-25866 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Kengo Seki >Priority: Major > Labels: pull-request-available > > I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the > following error: > {code} > $ mvn test -f ambari-metrics-kafka-sink/pom.xml > ... > Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 1.519 sec <<< > FAILURE! - in > org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest > testReporterStartStop(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest) > Time elapsed: 0.817 sec <<< FAILURE! > java.lang.AssertionError: > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > at > org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testReporterStartStop(KafkaTimelineMetricsReporterTest.java:102) > testReporterStartStopHttps(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest) > Time elapsed: 0.022 sec <<< FAILURE! > java.lang.AssertionError: > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > at > org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testReporterStartStopHttps(KafkaTimelineMetricsReporterTest.java:131) > testMetricsExclusionPolicy(org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest) > Time elapsed: 0.021 sec <<< FAILURE! > java.lang.AssertionError: > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > at > org.apache.hadoop.metrics2.sink.kafka.KafkaTimelineMetricsReporterTest.testMetricsExclusionPolicy(KafkaTimelineMetricsReporterTest.java:151) > Results : > Failed tests: > KafkaTimelineMetricsReporterTest.testMetricsExclusionPolicy:151 > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > KafkaTimelineMetricsReporterTest.testReporterStartStop:102 > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > KafkaTimelineMetricsReporterTest.testReporterStartStopHttps:131 > Expectation failure on verify: > Metrics.defaultRegistry(): expected: 2, actual: 0 > Tests run: 5, Failures: 3, Errors: 0, Skipped: 0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 4.238 s > [INFO] Finished at: 2023-02-24T09:46:44+09:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on > project ambari-metrics-kafka-sink: There are test failures. > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25865) Fix an unit test failure on ambari-metrics-host-monitoring
[ https://issues.apache.org/jira/browse/AMBARI-25865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25865: Labels: pull-request-available (was: ) > Fix an unit test failure on ambari-metrics-host-monitoring > -- > > Key: AMBARI-25865 > URL: https://issues.apache.org/jira/browse/AMBARI-25865 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Kengo Seki >Priority: Major > Labels: pull-request-available > > I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the > following error: > {code} > $ mvn test -f ambari-metrics-host-monitoring/pom.xml > ... > [INFO] --- exec-maven-plugin:1.2.1:exec (python-test) @ > ambari-metrics-host-monitoring --- > Running tests > No handlers could be found for logger "root" > Traceback (most recent call last): > File "unitTests.py", line 137, in > sys.exit(main()) > File "unitTests.py", line 106, in main > modules] > File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName > module = __import__('.'.join(parts_copy)) > File > "/home/sekikn/repos/ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestMetricCollector.py", > line 24, in > from core.application_metric_map import ApplicationMetricMap > File > "/home/sekikn/repos/ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/__init__.py", > line 29, in > for dir in os.walk(path).next()[1]: > StopIteration > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 1.126 s > [INFO] Finished at: 2023-02-24T09:45:36+09:00 > [INFO] > > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec > (python-test) on project ambari-metrics-host-monitoring: Command execution > failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1] > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25864) Fix an unit test failure on ambari-metrics-common
[ https://issues.apache.org/jira/browse/AMBARI-25864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25864: Labels: pull-request-available (was: ) > Fix an unit test failure on ambari-metrics-common > - > > Key: AMBARI-25864 > URL: https://issues.apache.org/jira/browse/AMBARI-25864 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Kengo Seki >Priority: Major > Labels: pull-request-available > > I tried to run unit tests on the release-2.0.0-rc0 branch and ran into the > following error: > {code} > $ mvn test -f ambari-metrics-common/pom.xml > ... > Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<< > FAILURE! - in > org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest > testEmbeddedModeCollectorZK(org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest) > Time elapsed: 0.007 sec <<< ERROR! > java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory > at > org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest.testEmbeddedModeCollectorZK(MetricCollectorHATest.java:88) > Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory > at > org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHATest.testEmbeddedModeCollectorZK(MetricCollectorHATest.java:88) > Results : > Tests in error: > MetricCollectorHATest.testEmbeddedModeCollectorZK:88 » NoClassDefFound > org/slf... > Tests run: 20, Failures: 0, Errors: 1, Skipped: 0 > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 35.496 s > [INFO] Finished at: 2023-02-24T09:54:00+09:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19:test (default-test) on > project ambari-metrics-common: There are test failures. > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25859) Correct Ambari Metrics version parsing logic
[ https://issues.apache.org/jira/browse/AMBARI-25859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25859: Labels: pull-request-available (was: ) > Correct Ambari Metrics version parsing logic > > > Key: AMBARI-25859 > URL: https://issues.apache.org/jira/browse/AMBARI-25859 > Project: Ambari > Issue Type: Bug >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: pull-request-available > Attachments: image-2023-02-22-16-49-06-587.png > > > Currently Ambari Metrics uses *2.0.0.0-SNAPSHOT* as its version number, and > the regex > *^([0-9]{+})\.([0-9]{+})\.([0-9]{+})\.([0-9]{+})((\.|-)(([0-9]+)|(SNAPSHOT)|(techwin)).)?** > and get *$7* as its release version number, but when we remove *SNAPSHOT* > suffix, the parse will return empty value cause build rpm package fails. > > If I understand it correctly, the old logic is trying to get number(or word > *SNAPSHOT* or {*}techwin{*}) after the symbol "-" as its release version, so > I'd like to change the version format to *x.y.z-p* where *x.y.z* means ambari > version and *p* means patch version in SPEC file.(if the branch is under > development, we can use *SNAPSHOT* for {*}p{*}) > > Like this: > !image-2023-02-22-16-49-06-587.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25815) upgrade gson-2.2.2.jar to 2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25815: Labels: pull-request-available (was: ) > upgrade gson-2.2.2.jar to 2.9.0 > --- > > Key: AMBARI-25815 > URL: https://issues.apache.org/jira/browse/AMBARI-25815 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > > |[CVE-2022-25647 > |http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25647]| > upgrade gson in ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25814) upgrade commons-io-2.4.jar to 2.8.0
[ https://issues.apache.org/jira/browse/AMBARI-25814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25814: Labels: pull-request-available (was: ) > upgrade commons-io-2.4.jar to 2.8.0 > --- > > Key: AMBARI-25814 > URL: https://issues.apache.org/jira/browse/AMBARI-25814 > Project: Ambari > Issue Type: Story >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > > |[CVE-2021-29425|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29425]| > upgrade commons-io in ambari- metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25840: Labels: pull-request-available (was: ) > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25834) Fix syntax errors for ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25834: Labels: pull-request-available (was: ) > Fix syntax errors for ambari-metrics-collector > -- > > Key: AMBARI-25834 > URL: https://issues.apache.org/jira/browse/AMBARI-25834 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-05-21-40-59-872.png > > > Fix the syntax errors shown in the image below. > !image-2023-01-05-21-40-59-872.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25830: Labels: pull-request-available (was: ) > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Upgrade grafana from 6.7.4 to 9.3.2. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25828) Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6
[ https://issues.apache.org/jira/browse/AMBARI-25828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25828: Labels: pull-request-available (was: ) > Upgrade ambari-metrics-kafka-sink to be compatible with kafka>=2.6 > -- > > Key: AMBARI-25828 > URL: https://issues.apache.org/jira/browse/AMBARI-25828 > Project: Ambari > Issue Type: Sub-task > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7(x86_64) > Ambari-2.8 > Ambari-Metrics-2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2022-12-26-21-25-54-719.png > > > 1. As KAFKA-9106 > https://issues.apache.org/jira/browse/KAFKA-9106 > and > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+configurable > said. > Any code currently using will switch to using > com.yammer.metrics.Metrics.defaultRegistry()KafkaYammerMetrics.defaultRegistry() > This change started with kafka-2.6. > Reference: > !image-2022-12-26-21-25-54-719.png! > 2. This issue also fix NPE because of > https://issues.apache.org/jira/browse/AMBARI-24797. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25825) Port BIGTOP-3872 to fix Ambari-Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25825: Labels: pull-request-available (was: ) > Port BIGTOP-3872 to fix Ambari-Metrics > -- > > Key: AMBARI-25825 > URL: https://issues.apache.org/jira/browse/AMBARI-25825 > Project: Ambari > Issue Type: Sub-task > Components: metrics >Affects Versions: 2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > As discussed in following > https://github.com/apache/ambari-metrics/pull/79#issuecomment-1362638692 > I will > 1. Port BIGTOP-3872 to Ambari-Metrics. > 2. Add dependency phoenix-hbase-compat-2.4.1 for ambari-metrics-timeline. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25822) Remove invalid relocations in pom.xml for ambari-metrics-common
[ https://issues.apache.org/jira/browse/AMBARI-25822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25822: Labels: pull-request-available (was: ) > Remove invalid relocations in pom.xml for ambari-metrics-common > --- > > Key: AMBARI-25822 > URL: https://issues.apache.org/jira/browse/AMBARI-25822 > Project: Ambari > Issue Type: Sub-task > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25821) Fixed syntax error that caused OOM in the ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-25821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25821: Labels: pull-request-available (was: ) > Fixed syntax error that caused OOM in the ambari-metrics-collector > -- > > Key: AMBARI-25821 > URL: https://issues.apache.org/jira/browse/AMBARI-25821 > Project: Ambari > Issue Type: Sub-task > Components: metrics >Affects Versions: 2.8.0 > Environment: Centos7 >Reporter: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25806) Upgrade kafka clients to resolve CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25806: Labels: pull-request-available (was: ) > Upgrade kafka clients to resolve CVEs > - > > Key: AMBARI-25806 > URL: https://issues.apache.org/jira/browse/AMBARI-25806 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep Kumar >Priority: Major > Labels: pull-request-available > > CVE-2018-17196: > In Apache Kafka versions between 0.11.0.0 and 2.1.0, it is possible to > manually craft a Produce request which bypasses transaction/idempotent ACL > validation. Only authenticated clients with Write permission on the > respective topics are able to exploit this vulnerability. Users should > upgrade to 2.1.1 or later where this vulnerability has been fixed. > CVE-2021-38153: > Some components in Apache Kafka use `Arrays.equals` to validate a password or > key, which is vulnerable to timing attacks that make brute force attacks for > such credentials more likely to be successful. Users should upgrade to 2.8.1 > or higher, or 3.0.0 or higher where this vulnerability has been fixed. The > affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, > 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, > 2.7.0, 2.7.1, and 2.8.0. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25807) Upgrade Guava version to resolve CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25807: Labels: pull-request-available (was: ) > Upgrade Guava version to resolve CVEs > - > > Key: AMBARI-25807 > URL: https://issues.apache.org/jira/browse/AMBARI-25807 > Project: Ambari > Issue Type: Bug >Reporter: Sandeep Kumar >Priority: Major > Labels: pull-request-available > > *[CVE-2020-8908|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-8908]* > A temp directory creation vulnerability exists in all versions of Guava, > allowing an attacker with access to the machine to potentially access data in > a temporary directory created by the Guava API > com.google.common.io.Files.createTempDir(). By default, on unix-like systems, > the created directory is world-readable (readable by an attacker with access > to the system). The method in question has been marked @Deprecated in > versions 30.0 and later and should not be used. For Android developers, we > recommend choosing a temporary directory API provided by Android, such as > context.getCacheDir(). For other Java developers, we recommend migrating to > the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly > configures permissions of 700, or configuring the Java runtime's > java.io.tmpdir system property to point to a location whose permissions are > appropriately configured. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25811) Optimize ambari metrics build time
[ https://issues.apache.org/jira/browse/AMBARI-25811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25811: Labels: pull-request-available (was: ) > Optimize ambari metrics build time > -- > > Key: AMBARI-25811 > URL: https://issues.apache.org/jira/browse/AMBARI-25811 > Project: Ambari > Issue Type: Improvement > Components: metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > > Currently in ambari metrics build, most of the time is taken by > ambari-metrics-assembly. > Looks maven-assembly-plugin is taking lot of time in stitching the artifacts. > Upgrading maven-assembly-plugin from 2.2-beta-5 to 3.4.2(latest version) > reduces the build time significantly > *Before change:* > {noformat} > 15:58:46,215 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT: > 15:58:46,215 [INFO] > 15:58:46,218 [INFO] ambari-metrics . > SUCCESS [ 3.960 s] > 15:58:46,220 [INFO] Ambari Metrics Common .. > SUCCESS [ 11.492 s] > 15:58:46,220 [INFO] Ambari Metrics Hadoop Sink . > SUCCESS [ 7.655 s] > 15:58:46,220 [INFO] Ambari Metrics Flume Sink .. > SUCCESS [ 4.045 s] > 15:58:46,220 [INFO] Ambari Metrics Kafka Sink .. > SUCCESS [ 3.465 s] > 15:58:46,220 [INFO] Ambari Metrics Storm Sink .. > SUCCESS [ 2.887 s] > 15:58:46,220 [INFO] Ambari Metrics Collector ... > SUCCESS [ 19.416 s] > 15:58:46,220 [INFO] Ambari Metrics Monitor . > SUCCESS [ 4.791 s] > 15:58:46,220 [INFO] Ambari Metrics Grafana . > SUCCESS [ 2.838 s] > 15:58:46,220 [INFO] Ambari Metrics Host Aggregator . > SUCCESS [ 8.363 s] > 15:58:46,220 [INFO] Ambari Metrics Assembly > SUCCESS [09:09 min] > 15:58:46,220 [INFO] > > 15:58:46,220 [INFO] BUILD SUCCESS > 15:58:46,220 [INFO] > > 15:58:46,221 [INFO] Total time: 10:18 min > 15:58:46,221 [INFO] Finished at: 2022-12-14T15:58:46+05:30 > {noformat} > *After Change:* > {noformat} > 16:18:22,667 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT: > 16:18:22,667 [INFO] > 16:18:22,670 [INFO] ambari-metrics . > SUCCESS [ 3.897 s] > 16:18:22,671 [INFO] Ambari Metrics Common .. > SUCCESS [ 10.880 s] > 16:18:22,671 [INFO] Ambari Metrics Hadoop Sink . > SUCCESS [ 4.681 s] > 16:18:22,671 [INFO] Ambari Metrics Flume Sink .. > SUCCESS [ 2.184 s] > 16:18:22,671 [INFO] Ambari Metrics Kafka Sink .. > SUCCESS [ 2.949 s] > 16:18:22,671 [INFO] Ambari Metrics Storm Sink .. > SUCCESS [ 3.071 s] > 16:18:22,671 [INFO] Ambari Metrics Collector ... > SUCCESS [ 18.471 s] > 16:18:22,671 [INFO] Ambari Metrics Monitor . > SUCCESS [ 5.416 s] > 16:18:22,671 [INFO] Ambari Metrics Grafana . > SUCCESS [ 2.458 s] > 16:18:22,671 [INFO] Ambari Metrics Host Aggregator . > SUCCESS [ 8.963 s] > 16:18:22,671 [INFO] Ambari Metrics Assembly > SUCCESS [ 57.413 s] > 16:18:22,671 [INFO] > > 16:18:22,671 [INFO] BUILD SUCCESS > 16:18:22,671 [INFO] > > 16:18:22,671 [INFO] Total time: 02:00 min > 16:18:22,673 [INFO] Finished at: 2022-12-14T16:18:22+05:30 > {noformat} > *As shown above, in my build environment, build time is reduced from 10 > minute to 2 minute.* -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25810) Allow skipping Python unit tests in ambari-metrics
[ https://issues.apache.org/jira/browse/AMBARI-25810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25810: Labels: pull-request-available (was: ) > Allow skipping Python unit tests in ambari-metrics > -- > > Key: AMBARI-25810 > URL: https://issues.apache.org/jira/browse/AMBARI-25810 > Project: Ambari > Issue Type: Bug > Components: metrics >Reporter: Mohammad Arshad >Priority: Minor > Labels: pull-request-available > Fix For: 2.0.0 > > > Currently skipPythonTests flag is available in ambari but not in metrics. > Lets add in metrics too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25809) ambari-metrics-host-monitoring project build creates temp folder outside of target folder
[ https://issues.apache.org/jira/browse/AMBARI-25809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25809: Labels: pull-request-available (was: ) > ambari-metrics-host-monitoring project build creates temp folder outside of > target folder > - > > Key: AMBARI-25809 > URL: https://issues.apache.org/jira/browse/AMBARI-25809 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Priority: Minor > Labels: pull-request-available > Fix For: 2.0.0 > > > ambari-metrics-host-monitoring project creates > ambari-metrics-host-monitoring\target\psutil_build_temp folder under ambari > folder > it should be created under the target folder > Run mvn clean install -DskipTests then run git status to know the folder > creation status > {noformat} > user1@host1 ambari-metrics-host-monitoring % git status > On branch master > Your branch is up to date with 'origin/master'. > Untracked files: > (use "git add ..." to include in what will be committed) > "../ambari-metrics-host-monitoring\\target\\psutil_build_temp/" > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25808) Metrics data simulator throws NPE
[ https://issues.apache.org/jira/browse/AMBARI-25808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25808: Labels: pull-request-available (was: ) > Metrics data simulator throws NPE > - > > Key: AMBARI-25808 > URL: https://issues.apache.org/jira/browse/AMBARI-25808 > Project: Ambari > Issue Type: Bug >Reporter: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: 2.7.8 > > > {noformat} > user@host1 bin % ./start.sh localhost:6188 2 > {noformat} > {code:java} > 2022-12-10 00:00:15,245 INFO [main] loadsimulator.MetricsLoadSimulator > (MetricsLoadSimulator.java:parseArgs(110)) - Recognized options: > baseHostName=host1 hosts#=2 trafficMode=burst metricsHostName=localhost:6188 > collectIntervalMillis=15000 sendIntervalMillis=6 simulateMaster=false > 2022-12-10 00:00:15,250 INFO [main] data.MetricsGeneratorConfigurer > (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading > metrics_def/HOST.dat > 2022-12-10 00:00:15,269 INFO [main] data.MetricsGeneratorConfigurer > (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading > metrics_def/DATANODE.dat > 2022-12-10 00:00:15,270 INFO [main] data.MetricsGeneratorConfigurer > (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading > metrics_def/NODEMANAGER.dat > 2022-12-10 00:00:15,272 INFO [main] data.MetricsGeneratorConfigurer > (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading > metrics_def/SLAVE_HBASE.dat > Exception in thread "main" java.lang.NullPointerException > at java.io.Reader.(Reader.java:78) > at java.io.InputStreamReader.(InputStreamReader.java:72) > at > org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.readMetrics(MetricsGeneratorConfigurer.java:72) > at > org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.createMetricsForHost(MetricsGeneratorConfigurer.java:57) > at > org.apache.ambari.metrics.core.loadsimulator.LoadRunner.createApplicationMetrics(LoadRunner.java:112) > at > org.apache.ambari.metrics.core.loadsimulator.LoadRunner.addMetricsWorkers(LoadRunner.java:100) > at > org.apache.ambari.metrics.core.loadsimulator.LoadRunner.prepareWorkers(LoadRunner.java:88) > at > org.apache.ambari.metrics.core.loadsimulator.LoadRunner.(LoadRunner.java:69) > at > org.apache.ambari.metrics.core.loadsimulator.MetricsLoadSimulator.main(MetricsLoadSimulator.java:48) > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[ https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25803: Labels: pull-request-available (was: ) > ambari and ambari-metrics repo cloning logs warning because of case sensitive > files > --- > > Key: AMBARI-25803 > URL: https://issues.apache.org/jira/browse/AMBARI-25803 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: 2.7.8 > > > {noformat} > git clone https://github.com/apache/ambari-metrics.git > {noformat} > above command logs following warning > {noformat} > warning: the following paths have collided (e.g. case-sensitive paths > on a case-insensitive filesystem) and only one from the same > colliding group is in the working tree: > > 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT' > > 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat' > > 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT' > > 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat' > {noformat} > I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same. > Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and > TIMELINE_METRIC_STORE_WATCHER.dat is same. > There is no reason to keep both the files. we should delete .DAT files. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25801) Fix the Ambari-Metrics rpm package deployment failure
[ https://issues.apache.org/jira/browse/AMBARI-25801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25801: Labels: pull-request-available (was: ) > Fix the Ambari-Metrics rpm package deployment failure > - > > Key: AMBARI-25801 > URL: https://issues.apache.org/jira/browse/AMBARI-25801 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25790) HBase put metrics are not populated
[ https://issues.apache.org/jira/browse/AMBARI-25790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25790: Labels: pull-request-available (was: ) > HBase put metrics are not populated > > > Key: AMBARI-25790 > URL: https://issues.apache.org/jira/browse/AMBARI-25790 > Project: Ambari > Issue Type: Bug > Components: metrics >Reporter: Rajeshbabu Chintaguntla >Assignee: Rajeshbabu Chintaguntla >Priority: Major > Labels: pull-request-available > > Currently the HBase put metrics are defined as > {noformat} > regionserver.Server.Mutate_75th_percentile > regionserver.Server.Mutate_95th_percentile > regionserver.Server.Mutate_99th_percentile > regionserver.Server.Mutate_max > regionserver.Server.Mutate_mean > regionserver.Server.Mutate_median > ipc.IPC.receivedBytes > regionserver.Server.Mutate_min > regionserver.Server.Mutate_num_ops > {noformat} > But actual metrics need to be defined for writes should be Put as below. > {noformat} > "Put_num_ops": 12007275, > "Put_min": 0, > "Put_max": 0, > "Put_mean": 0, > "Put_25th_percentile": 0, > "Put_median": 0, > "Put_75th_percentile": 0, > "Put_90th_percentile": 0, > "Put_95th_percentile": 0, > "Put_98th_percentile": 0, > "Put_99th_percentile": 0, > "Put_99.9th_percentile": 0, > {noformat} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25782) Fix Ambari Metrics build failure
[ https://issues.apache.org/jira/browse/AMBARI-25782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25782: Labels: pull-request-available (was: ) > Fix Ambari Metrics build failure > > > Key: AMBARI-25782 > URL: https://issues.apache.org/jira/browse/AMBARI-25782 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: lucas >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Fix syntax, refactor and versions after forwarding from Ambari to > ambari-metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25780) Ambari metrics should upgrade hadoop and hbase for known CVE issues
[ https://issues.apache.org/jira/browse/AMBARI-25780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25780: Labels: pull-request-available (was: ) > Ambari metrics should upgrade hadoop and hbase for known CVE issues > --- > > Key: AMBARI-25780 > URL: https://issues.apache.org/jira/browse/AMBARI-25780 > Project: Ambari > Issue Type: Bug >Reporter: Lei Yao >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25717) Fix broken build on branch-2.7
[ https://issues.apache.org/jira/browse/AMBARI-25717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25717: Labels: pull-request-available (was: ) > Fix broken build on branch-2.7 > -- > > Key: AMBARI-25717 > URL: https://issues.apache.org/jira/browse/AMBARI-25717 > Project: Ambari > Issue Type: Bug >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Major > Labels: pull-request-available > Fix For: 2.7.7 > > Time Spent: 0.5h > Remaining Estimate: 0h > > {code:java} > [INFO] Reactor Summary: > [INFO] > [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 23.248 > s] > [INFO] ambari-metrics 2.7.6.0.0 ... SUCCESS [ 0.465 > s] > [INFO] Ambari Metrics Common 2.7.6.0.0 SUCCESS [ 50.696 > s] > [INFO] Ambari Metrics Hadoop Sink 2.7.6.0.0 ... SUCCESS [ 25.005 > s] > [INFO] Ambari Metrics Flume Sink 2.7.6.0.0 SUCCESS [ 10.208 > s] > [INFO] Ambari Metrics Kafka Sink 2.7.6.0.0 SUCCESS [ 8.929 > s] > [INFO] Ambari Metrics Storm Sink 2.7.6.0.0 SUCCESS [ 6.106 > s] > [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.6.0.0 ... SUCCESS [ 6.340 > s] > [INFO] Ambari Metrics Collector 2.7.6.0.0 . FAILURE [ 28.853 > s] > [INFO] Ambari Metrics Monitor 2.7.6.0.0 ... SKIPPED > [INFO] Ambari Metrics Grafana 2.7.6.0.0 ... SKIPPED > [INFO] Ambari Metrics Host Aggregator 2.7.6.0.0 ... SKIPPED > [INFO] Ambari Metrics Assembly 2.7.6.0.0 .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 02:40 min > [INFO] Finished at: 2022-08-16T01:29:20Z > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.7:run (phoenix_download) on > project ambari-metrics-timelineservice: An Ant BuildException has occured: > Can't get > https://downloads.apache.org/phoenix/apache-phoenix-5.0.0-HBase-2.0/bin/apache-phoenix-5.0.0-HBase-2.0-bin.tar.gz > to > /home/jenkins/jenkins-home/workspace/Ambari_Ambari-Nightly_branch-2.7/ambari-metrics/ambari-metrics-timelineservice/target/embedded/phoenix.tar.gz > [ERROR] around Ant part ... src="https://downloads.apache.org/phoenix/apache-phoenix-5.0.0-HBase-2.0/bin/apache-phoenix-5.0.0-HBase-2.0-bin.tar.gz; > > dest="/home/jenkins/jenkins-home/workspace/Ambari_Ambari-Nightly_branch-2.7/ambari-metrics/ambari-metrics-timelineservice/target/embedded/phoenix.tar.gz"/>... > @ 5:303 in > /home/jenkins/jenkins-home/workspace/Ambari_Ambari-Nightly_branch-2.7/ambari-metrics/ambari-metrics-timelineservice/target/antrun/build-Download > Phoenix.xml > [ERROR] -> [Help 1] {code} > phoenix-5.0.0-HBase-2.0-bin.tar.gz is no longer available on the mentioned > downloads.apache.org url. We should bump hbase and phoenix versions to > resolve this build issue. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[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 ] ASF GitHub Bot updated AMBARI-25587: Labels: pull-request-available (was: ) > Metrics cannot be stored and the exception message is null when metric value > is NaN > > > Key: AMBARI-25587 > URL: https://issues.apache.org/jira/browse/AMBARI-25587 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.4, 2.7.5 > Environment: Ambari:2.7.4 >Reporter: huangkunlun >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > > The exception information frequently appeared in ambari-metrics-collector.log > as follows: > {code:java} > 2020-11-12 12:28:11,200 WARN > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on > insert records to store : null > 2020-11-12 12:28:11,200 WARN > org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that > cannot be stored : > [default.General.hs2_avg_active_session_time,hiveserver2]{1605155168235=NaN, > 1605155198236=NaN, 1605155228235=NaN, 1605155258235=NaN} > {code} > The exception message of metrics written to HBase is directly displayed as > null. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25727) Update slf4j version to 2.0.0
[ https://issues.apache.org/jira/browse/AMBARI-25727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25727: Labels: pull-request-available (was: ) > Update slf4j version to 2.0.0 > - > > Key: AMBARI-25727 > URL: https://issues.apache.org/jira/browse/AMBARI-25727 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.6 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0, 2.7.7 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update slf4j version to 2.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25722) Remediation of log4j dependency’s
[ https://issues.apache.org/jira/browse/AMBARI-25722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25722: Labels: pull-request-available (was: ) > Remediation of log4j dependency’s > -- > > Key: AMBARI-25722 > URL: https://issues.apache.org/jira/browse/AMBARI-25722 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Affects Versions: 2.7.6 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0, 2.7.7 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Remediation of log4j dependency’s from Ambari code -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25668) Integrate the Apache released HBase as back store of Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25668: Labels: apache hbase metrics pull-request-available (was: apache hbase metrics) > Integrate the Apache released HBase as back store of Ambari Metrics > --- > > Key: AMBARI-25668 > URL: https://issues.apache.org/jira/browse/AMBARI-25668 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.7.5 >Reporter: Tamas Payer >Assignee: Tamas Payer >Priority: Major > Labels: apache, hbase, metrics, pull-request-available > Fix For: 2.7.6 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Since the non managed HDP tarballs are not accessible anymore publicly > AMBARI-25599 is an attempt to replace those dependencies of Ambari Metrics > with the open source versions. > However, the Apache version of HBase ( > [https://archive.apache.org/dist/hbase/2.0.2/hbase-2.0.2-bin.tar.gz] ) does > not starting up and failing with: > {code:java} > [root@c7401 ambari-metrics-collector]# less > hbase-ams-master-c7401.ambari.apache.org.log{code} > {code:java} > 2021-02-10 08:19:01,953 ERROR [main] master.HMasterCommandLine: Master exiting > java.lang.NoClassDefFoundError: > org/apache/commons/configuration/Configuration > at > org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.(DefaultMetricsSystem.java:38) > at > org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.(DefaultMetricsSystem.java:36) > at > org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:159) > at > org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:140) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at > org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:149) > at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2964) > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.configuration.Configuration{code} > The missing class '_org.apache.commons.configuration.Configuration_' is > located in _'commons-configuration2'_ but strangely that is not present in > '_/usr/lib/ams-hbase/lib/'_ if the Apache version of HBase is used for the > build. > * *Investigate why HBase fails to start up ?* > * *Why is commons-configuration2 lib missing ?* > * *Integrate the Apache released HBase as back store of Ambari Metrics* -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25635) Clear Cluster and METRIC_AGGREGATORS MBeans upon shutdown
[ https://issues.apache.org/jira/browse/AMBARI-25635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25635: Labels: HA helix metric-collector pull-request-available (was: HA helix metric-collector) > Clear Cluster and METRIC_AGGREGATORS MBeans upon shutdown > - > > Key: AMBARI-25635 > URL: https://issues.apache.org/jira/browse/AMBARI-25635 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.4, 2.7.5 >Reporter: Tamas Payer >Assignee: Tamas Payer >Priority: Major > Labels: HA, helix, metric-collector, pull-request-available > Fix For: 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > > Following warnings appear in metrics-collector.log upon startup. > {code:java} > javax.management.InstanceAlreadyExistsException: ClusterStatus: > cluster=ambari-metrics-cluster,instanceName=ctr-e153-1613480641811-87570-01-57.hwx.site_12001 > at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.register(ClusterStatusMonitor.java:172) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.registerInstances(ClusterStatusMonitor.java:498) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.setClusterInstanceStatus(ClusterStatusMonitor.java:220) > at > org.apache.helix.controller.stages.ReadClusterDataStage.process(ReadClusterDataStage.java:91) > at org.apache.helix.controller.pipeline.Pipeline.handle(Pipeline.java:48) > at > org.apache.helix.controller.GenericHelixController.handleEvent(GenericHelixController.java:295) > at > org.apache.helix.controller.GenericHelixController$ClusterEventProcessor.run(GenericHelixController.java:595) > {code} > and > {code:java} > 2021-03-09 23:15:53,450 INFO > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor: Register MBean: > ClusterStatus: > cluster=ambari-metrics-cluster,instanceName=ctr-e153-1613480641811-87570-01-57.hwx.site_12001,resourceName=METRIC_AGGREGATORS > 2021-03-09 23:15:53,450 INFO > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor: Register MBean: > ClusterStatus: > cluster=ambari-metrics-cluster,instanceName=ctr-e153-1613480641811-87570-01-57.hwx.site_12001,resourceName=METRIC_AGGREGATORS > 2021-03-09 23:15:53,450 WARN > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor: Could not register > MBean: ClusterStatus: > cluster=ambari-metrics-cluster,instanceName=ctr-e153-1613480641811-87570-01-57.hwx.site_12001,resourceName=METRIC_AGGREGATORS > javax.management.InstanceAlreadyExistsException: ClusterStatus: > cluster=ambari-metrics-cluster,instanceName=ctr-e153-1613480641811-87570-01-57.hwx.site_12001,resourceName=METRIC_AGGREGATORS > at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.register(ClusterStatusMonitor.java:172) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.registerPerInstanceResources(ClusterStatusMonitor.java:537) > at > org.apache.helix.monitoring.mbeans.ClusterStatusMonitor.setPerInstanceResourceStatus(ClusterStatusMonitor.java:307) > at > org.apache.helix.controller.stages.BestPossibleStateCalcStage.process(BestPossibleStateCalcStage.java:74) > at > org.apache.helix.controller.pipeline.Pipeline.handle(Pipeline.java:48) > at > org.apache.helix.controller.GenericHelixController.handleEvent(GenericHelixController.java:295) > at >
[jira] [Updated] (AMBARI-25599) Consider to eliminate HDP public binary references
[ https://issues.apache.org/jira/browse/AMBARI-25599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25599: Labels: pull-request-available (was: ) > Consider to eliminate HDP public binary references > -- > > Key: AMBARI-25599 > URL: https://issues.apache.org/jira/browse/AMBARI-25599 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Éberhardt Péter >Assignee: Szilárd Antal >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Public HDP binaries will no longer available: > [https://my.cloudera.com/knowledge/Cloudera-Customer-Advisory-Paywall-Update-External?id=306085] > Please analyse and eliminate(replace) the necessary references from the > codebase where rpms and tarballs of HDP are accessible. > Additionally non managed HDP tarballs should be replaced with open source > ones. For example: > [https://github.com/apache/ambari/blob/branch-2.7/ambari-metrics/pom.xml#L43] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25582) Change the way AMS Grafana datasource discovers the Kafka topics
[ https://issues.apache.org/jira/browse/AMBARI-25582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25582: Labels: ambari-metrics grafana pull-request-available (was: ambari-metrics grafana) > Change the way AMS Grafana datasource discovers the Kafka topics > - > > Key: AMBARI-25582 > URL: https://issues.apache.org/jira/browse/AMBARI-25582 > Project: Ambari > Issue Type: Task >Reporter: Tamas Payer >Assignee: Dmytro Grinenko >Priority: Major > Labels: ambari-metrics, grafana, pull-request-available > Fix For: 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > > Currently the available Kafka topics are discovered by extracting them from > the kafka.log.Log.* > metrics in the AMS Datasource to show them on the Kafka-Topics dashboard. > This means that if whitelisting is used the kafka.log.Log.* metrics must be > enabled and must not be excluded by 'external.kafka.metrics.exclude.prefix' > Kafka property either. > However, in some cases the large amount of kafka.log.Log.* metrics can be a > burden to AMS, so excluding them would be welcomed. > The possibility to discover the Kafka topics should be assessed! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25563) Storm dashboards are not showing metrics
[ https://issues.apache.org/jira/browse/AMBARI-25563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25563: Labels: grafana pull-request-available storm (was: grafana storm) > Storm dashboards are not showing metrics > > > Key: AMBARI-25563 > URL: https://issues.apache.org/jira/browse/AMBARI-25563 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.5 >Reporter: Tamas Payer >Assignee: Tamas Payer >Priority: Major > Labels: grafana, pull-request-available, storm > Fix For: 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > > All the Storm dashboards are failing to show metric data. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25562) Nightly test is failing due to Ambari Metrics Host Aggregator
[ https://issues.apache.org/jira/browse/AMBARI-25562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25562: Labels: pull-request-available (was: ) > Nightly test is failing due to Ambari Metrics Host Aggregator > - > > Key: AMBARI-25562 > URL: https://issues.apache.org/jira/browse/AMBARI-25562 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.6 >Reporter: Dmytro Grinenko >Assignee: Szilárd Antal >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > {code:java} > Results :Tests in error: > > AggregatorWebServiceTest.:45->JerseyTest.:217->JerseyTest.getContainer:335 > » ArrayIndexOutOfBounds > > AggregatorWebServiceTest.:45->JerseyTest.:217->JerseyTest.getContainer:335 > » ArrayIndexOutOfBounds > > AggregatorWebServiceTest.:45->JerseyTest.:217->JerseyTest.getContainer:335 > » ArrayIndexOutOfBoundsTests run: 18, Failures: 0, Errors: 3, Skipped: > 0[INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 10.591 > s] > [INFO] ambari-metrics 2.7.5.0.0 ... SUCCESS [ 0.525 > s] > [INFO] Ambari Metrics Common 2.7.5.0.0 SUCCESS [ 57.949 > s] > [INFO] Ambari Metrics Hadoop Sink 2.7.5.0.0 ... SUCCESS [ 18.953 > s] > [INFO] Ambari Metrics Flume Sink 2.7.5.0.0 SUCCESS [ 14.128 > s] > [INFO] Ambari Metrics Kafka Sink 2.7.5.0.0 SUCCESS [ 11.566 > s] > [INFO] Ambari Metrics Storm Sink 2.7.5.0.0 SUCCESS [ 7.246 > s] > [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.5.0.0 ... SUCCESS [ 6.247 > s] > [INFO] Ambari Metrics Collector 2.7.5.0.0 . SUCCESS [05:12 > min] > [INFO] Ambari Metrics Monitor 2.7.5.0.0 ... SUCCESS [ 2.775 > s] > [INFO] Ambari Metrics Grafana 2.7.5.0.0 ... SUCCESS [ 4.479 > s] > [INFO] Ambari Metrics Host Aggregator 2.7.5.0.0 ... FAILURE [ 5.123 > s] > [INFO] Ambari Metrics Assembly 2.7.5.0.0 .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 07:32 min > [INFO] Finished at: 2020-09-28T23:07:17Z > [INFO] > > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25549) NegativeArraySizeException thrown when invoking CurrentCollectorHost
[ https://issues.apache.org/jira/browse/AMBARI-25549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25549: Labels: pull-request-available (was: ) > NegativeArraySizeException thrown when invoking CurrentCollectorHost > > > Key: AMBARI-25549 > URL: https://issues.apache.org/jira/browse/AMBARI-25549 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1, 2.7.3, 2.7.4, 2.7.5 >Reporter: Tamas Payer >Assignee: Tamas Payer >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 0.5h > Remaining Estimate: 0h > > SMM is using *AbstractTimelineMetricsSink* class to fetch and push metrics to > Ambari Metric Collector in multi-threaded manner. > When all the AMS live nodes are > down([http://localhost:6188/ws/v1/timeline/metrics/livenodes]), the method > [getCurrentCollectorHost|https://github.com/apache/ambari-metrics/blob/c7dcf2b25241e2cfe6931d6261a43be97e0deaba/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java#L273] > throws _NegativeArraySizeException_. > {code:java} > java.lang.NegativeArraySizeException: null at > java.util.AbstractCollection.toArray(AbstractCollection.java:136) > at java.util.ArrayList.(ArrayList.java:178) > at > org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:460) > at > org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink$1.get(AbstractTimelineMetricsSink.java:450) > at > org.apache.hadoop.metrics2.sink.relocated.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:192) > at > org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getCurrentCollectorHost(AbstractTimelineMetricsSink.java:264) > at > com.hortonworks.smm.kafka.services.metric.ams.AMSMetricsFetcher.getCollectorAPIUri(AMSMetricsFetcher.java:231) > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25516) Missing @Override on methods
[ https://issues.apache.org/jira/browse/AMBARI-25516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25516: Labels: pull-request-available (was: ) > Missing @Override on methods > > > Key: AMBARI-25516 > URL: https://issues.apache.org/jira/browse/AMBARI-25516 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: trunk >Reporter: RickyMa >Assignee: Dmytro Grinenko >Priority: Trivial > Labels: pull-request-available > Fix For: trunk, 2.7.6 > > Attachments: AMBARI-25516-for-branch-2.7.patch, > AMBARI-25516-for-trunk.patch > > Time Spent: 3h 10m > Remaining Estimate: 0h > > Missing @Override on 91 methods. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25775) Failed to compile Ambari-Infra because of invalid url
[ https://issues.apache.org/jira/browse/AMBARI-25775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25775: Labels: pull-request-available (was: ) > Failed to compile Ambari-Infra because of invalid url > - > > Key: AMBARI-25775 > URL: https://issues.apache.org/jira/browse/AMBARI-25775 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-infra-2.8.0 >Reporter: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2022-11-04-10-05-46-029.png > > > http://central.maven.org/maven2 has been unable to access > !image-2022-11-04-10-05-46-029.png! > {code} > kage/code/ambari-infra/ambari-infra-solr-client/target/migrate/lucene-core-6.6.2.jar > [INFO] > > [INFO] Reactor Summary for ambari-infra 3.0.0.0-SNAPSHOT: > [INFO] > [INFO] ambari-infra ... SUCCESS [ 6.914 > s] > [INFO] Ambari Infra Solr Client ... FAILURE [ 7.090 > s] > [INFO] Ambari Infra Solr Plugin ... SKIPPED > [INFO] Ambari Infra Manager ... SKIPPED > [INFO] Ambari Infra Assembly .. SKIPPED > [INFO] Ambari Infra Manager Integration Tests . SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 14.279 s > [INFO] Finished at: 2022-11-04T10:04:29+08:00 > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project > ambari-infra-solr-client: An Ant BuildException has occured: The following > error occurred while executing this line: > [ERROR] /opt/package/code/ambari-infra/ambari-infra-solr-client/build.xml:39: > java.net.UnknownHostException: central.maven.org > [ERROR] around Ant part .. @ 4:28 in > /opt/package/code/ambari-infra/ambari-infra-solr-client/target/antrun/build-main.xml: > Unknown host central.maven.org > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :ambari-infra-solr-client > make: *** [rpm] Error 1 > {code} -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25723) Enable squash and merge in GitHub PR
[ https://issues.apache.org/jira/browse/AMBARI-25723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25723: Labels: pull-request-available (was: ) > Enable squash and merge in GitHub PR > > > Key: AMBARI-25723 > URL: https://issues.apache.org/jira/browse/AMBARI-25723 > Project: Ambari > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Minor > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > Reference: > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Mergebuttons -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25596) Multiple Ambari Unit Tests failing due to Address already in use
[ https://issues.apache.org/jira/browse/AMBARI-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25596: Labels: pull-request-available (was: ) > Multiple Ambari Unit Tests failing due to Address already in use > > > Key: AMBARI-25596 > URL: https://issues.apache.org/jira/browse/AMBARI-25596 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Suraj Naik >Priority: Minor > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Issue: > > {{Running org.apache.ambari.metrics.webapp.TestTimelineWebServicesTests run: > 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.294 sec <<< FAILURE! - > in > org.apache.ambari.metrics.webapp.TestTimelineWebServicestestAbout(org.apache.ambari.metrics.webapp.TestTimelineWebServices) > > Time elapsed: 0.005 sec > <<< ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException: > java.net.BindException: Address already in use > at > org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77) > Caused by: java.net.BindException: Address already in useat > org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77) > testGetMetrics(org.apache.ambari.metrics.webapp.TestTimelineWebServices) > Time elapsed: 0.001 sec <<< > ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException: > java.net.BindException: Address already in use > at > org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77) > Caused by: java.net.BindException: Address already in use > at > org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77) > Results :Tests in > error:TestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342 > » > TestContainerTestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342 > » TestContainer}} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25595) Maven throws 403 while attempting to download from http://repo.spring.io/milestone
[ https://issues.apache.org/jira/browse/AMBARI-25595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25595: Labels: pull-request-available (was: ) > Maven throws 403 while attempting to download from > http://repo.spring.io/milestone > -- > > Key: AMBARI-25595 > URL: https://issues.apache.org/jira/browse/AMBARI-25595 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Reporter: Suraj Naik >Priority: Minor > Labels: pull-request-available > > mvn clean install package throws 403 Forbidden due to the spring-milestones > not supporting http. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25514) Build fails on missing javax.el
[ https://issues.apache.org/jira/browse/AMBARI-25514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25514: Labels: pull-request-available (was: ) > Build fails on missing javax.el > --- > > Key: AMBARI-25514 > URL: https://issues.apache.org/jira/browse/AMBARI-25514 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.5 > Environment: Test it on Debian 9 with a clean Maven dependecies cache >Reporter: Carlos Saltos >Priority: Major > Labels: pull-request-available > Attachments: missing-javax.el-error.log, missing-javax.el-fix.patch > > > CURRENT BEHAVIOR: > When trying to build Ambari with ambari-metrics it fails for a missing > org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT dependancy (more info at the > attached error log file) > DESIRED BEHAVIOR: > The build succeeds > POSSIBLE SOLUTION: > Exclude the javax.el dependency since it is already provided by the jee > containers servers (please refer to the patch file to see an option of the > fix) > > NOTE: some builds might look they work but it is just because they cached > this dependancy in a point in time but now it is no more available -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25500) Hive Service Check Fails if the trustStorePassword has Special character $
[ https://issues.apache.org/jira/browse/AMBARI-25500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25500: Labels: pull-request-available (was: ) > Hive Service Check Fails if the trustStorePassword has Special character $ > -- > > Key: AMBARI-25500 > URL: https://issues.apache.org/jira/browse/AMBARI-25500 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: Akhil Naik >Assignee: Akhil Naik >Priority: Major > Labels: pull-request-available > > Problem statement : Hive Service Check Fails if the trustStorePassword has > Special character $ > the error logs say : > {code:java} > 2020-04-10 08:20:14,748 - Execute['! (beeline -u > 'jdbc:hive2://c4229-node3.coelab.cloudera.com:1/;transportMode=binary;ssl=true;sslTrustStore=/tmp/keystore1.jks;trustStorePassword=[PROTECTED]' > -n hive -e ';' 2>&1 | awk '{print}' | grep -vz -i -e 'Connected to:' -e > 'Transaction isolation:' -e 'inactive HS2 instance; use service discovery')'] > {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], > 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'} > 2020-04-10 08:20:19,509 - Connection to c4229-node3.coelab.cloudera.com on > port 1 failed > 2020-04-10 08:20:24,513 - Execute['! (beeline -u > 'jdbc:hive2://c4229-node3.coelab.cloudera.com:1/;transportMode=binary;ssl=true;sslTrustStore=/tmp/keystore1.jks;trustStorePassword=[PROTECTED]' > -n hive -e ';' 2>&1 | awk '{print}' | grep -vz -i -e 'Connected to:' -e > 'Transaction isolation:' -e 'inactive HS2 instance; use service discovery')'] > {'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], > 'timeout_kill_strategy': 2, 'timeout': 30, 'user': 'ambari-qa'} > 2020-04-10 08:20:28,927 - Connection to c4229-node3.coelab.cloudera.com on > port 1 failed > {code} > Root cause : the trustStorePassword should idaelly be passed in single quotes > to ignore the $ sign, the fix lies in : > https://github.com/apache/ambari/blob/a4b2901a9a16e356c230fb647471e099b2d965ba/ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py#L61 > changing > {code:java} > beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}', > 'trustStorePassword={ssl_password!p}']) > {code} > to : > {code:java} > beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}', > "trustStorePassword='{ssl_password!p}'"]) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25495) Extend the set of headers from server's response
[ https://issues.apache.org/jira/browse/AMBARI-25495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25495: Labels: pull-request-available (was: ) > Extend the set of headers from server's response > > > Key: AMBARI-25495 > URL: https://issues.apache.org/jira/browse/AMBARI-25495 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.6 >Reporter: Dmytro Vitiuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > > Extend the set of headers from server's response. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25494) Ambari - Unsafe third-party link (target="_blank")
[ https://issues.apache.org/jira/browse/AMBARI-25494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25494: Labels: pull-request-available (was: ) > Ambari - Unsafe third-party link (target="_blank") > -- > > Key: AMBARI-25494 > URL: https://issues.apache.org/jira/browse/AMBARI-25494 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25493) Ambari - Application Test Script Detected
[ https://issues.apache.org/jira/browse/AMBARI-25493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25493: Labels: pull-request-available (was: ) > Ambari - Application Test Script Detected > - > > Key: AMBARI-25493 > URL: https://issues.apache.org/jira/browse/AMBARI-25493 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25492) Ambari Sends Empty metrics_collector_hosts parameters after AMS service is deleted
[ https://issues.apache.org/jira/browse/AMBARI-25492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25492: Labels: pull-request-available (was: ) > Ambari Sends Empty metrics_collector_hosts parameters after AMS service is > deleted > -- > > Key: AMBARI-25492 > URL: https://issues.apache.org/jira/browse/AMBARI-25492 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: Akhil Naik >Assignee: Akhil Naik >Priority: Major > Labels: pull-request-available > > I am having an cluster where Ambari metrics collector was installed and > removed later as they dont use it . Now there Nifi fails to start due to > script error : > {code:java} > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/nifi.py", > line 304, in > Master().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 352, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/nifi.py", > line 139, in start > import params > File > "/var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/params.py", > line 302, in > metrics_collector_host = > str(config['clusterHostInfo']['metrics_collector_hosts'][0]) > IndexError: list index out of range > > {code} > Issue is easy to reproduce > 1) Deploy a fresh cluster with HDF > 2) Remove AMS service > 3) try to start/stop or restart nifi service. it will fail with abouve error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25491) newline characters are ignored on custom property
[ https://issues.apache.org/jira/browse/AMBARI-25491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25491: Labels: pull-request-available (was: ) > newline characters are ignored on custom property > - > > Key: AMBARI-25491 > URL: https://issues.apache.org/jira/browse/AMBARI-25491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: YUBI LEE >Priority: Minor > Labels: pull-request-available > > If I add a custom property of which value has new line characters, new line > characters are ignored after UI reloads. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25489) On adding new VDF the Base URLs are not auto populated
[ https://issues.apache.org/jira/browse/AMBARI-25489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25489: Labels: pull-request-available (was: ) > On adding new VDF the Base URLs are not auto populated > -- > > Key: AMBARI-25489 > URL: https://issues.apache.org/jira/browse/AMBARI-25489 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.6 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25487) Change authentication method from get to post
[ https://issues.apache.org/jira/browse/AMBARI-25487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25487: Labels: pull-request-available (was: ) > Change authentication method from get to post > - > > Key: AMBARI-25487 > URL: https://issues.apache.org/jira/browse/AMBARI-25487 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25486) Configs page not loading after Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-25486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25486: Labels: pull-request-available (was: ) > Configs page not loading after Ambari upgrade > - > > Key: AMBARI-25486 > URL: https://issues.apache.org/jira/browse/AMBARI-25486 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25479) Set Keytab: Kerberos Client operation takes lot of time and timing out
[ https://issues.apache.org/jira/browse/AMBARI-25479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25479: Labels: pull-request-available (was: ) > Set Keytab: Kerberos Client operation takes lot of time and timing out > -- > > Key: AMBARI-25479 > URL: https://issues.apache.org/jira/browse/AMBARI-25479 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.6 > > > During HDP upgrade re-generate keytabs operations the steps is timing out. > "Set Keytab: Kerberos Client" is taking more than hour and in the process > ambari agents are loosing the heart beat and step is getting failed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25485) Change authentication method from get to post
[ https://issues.apache.org/jira/browse/AMBARI-25485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25485: Labels: pull-request-available (was: ) > Change authentication method from get to post > - > > Key: AMBARI-25485 > URL: https://issues.apache.org/jira/browse/AMBARI-25485 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: Dmytro Vitiuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > > Currently we are using GET method while login: > GET > api/v1/users/$ > {username} > We need to change it to post. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25481) Customize Widget Threshold validation issue
[ https://issues.apache.org/jira/browse/AMBARI-25481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25481: Labels: pull-request-available (was: ) > Customize Widget Threshold validation issue > --- > > Key: AMBARI-25481 > URL: https://issues.apache.org/jira/browse/AMBARI-25481 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.6 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25478) Badly formatted request may cause Ambari to crash
[ https://issues.apache.org/jira/browse/AMBARI-25478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25478: Labels: pull-request-available (was: ) > Badly formatted request may cause Ambari to crash > - > > Key: AMBARI-25478 > URL: https://issues.apache.org/jira/browse/AMBARI-25478 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: Dmytro Vitiuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.6 > > > Metrics request with only start timestamp can lead to throwing of out of > memory exception: > curl -g -u admin:admin > 'http://:8080/api/v1/clusters//?fields=metrics/load/1-min._avg[15]' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25473) Upgrade Infra Solr Clients fails if it is installed on only one host
[ https://issues.apache.org/jira/browse/AMBARI-25473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25473: Labels: pull-request-available (was: ) > Upgrade Infra Solr Clients fails if it is installed on only one host > > > Key: AMBARI-25473 > URL: https://issues.apache.org/jira/browse/AMBARI-25473 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.5 >Reporter: Szilard Antal >Assignee: Szilard Antal >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.6 > > > Executed command: > {code:java} > [root@santal-atlas-dc-upgr ~]# > /usr/lib/ambari-infra-solr-client/ambariSolrMigration.sh --ini-file > $CONFIG_INI_LOCATION --mode backup | tee backup_output.txt Execute command: > /usr/bin/python /usr/lib/ambari-infra-solr-client/migrationHelper.py > --ini-file ambari_solr_migration.ini --action check-shards Dumping > collections data to > /usr/lib/ambari-infra-solr-client/migrate/data/check_collections.json ... > DONE Checking available shards for 'fulltext_index' collection... > -- Number of shards: 1 OK: Found active leader > replica for shard1 Index size per shard for fulltext_index: - shard1: 71 > bytes Index size per host for fulltext_index (consider this for backup): - > 172.22.111.200: 71 bytes -- Checking available > shards for 'edge_index' collection... -- Number > of shards: 1 OK: Found active leader replica for shard1 Index size per shard > for edge_index: - shard1: 71 bytes Index size per host for edge_index > (consider this for backup): - 172.22.111.200: 71 bytes > -- Checking available shards for 'vertex_index' > collection... -- Number of shards: 1 OK: Found > active leader replica for shard1 Index size per shard for vertex_index: - > shard1: 16.8 KB Index size per host for vertex_index (consider this for > backup): - 172.22.111.200: 16.8 KB -- Full index > size per hosts: (consider this for backup) - 172.22.111.200: 16.94 KB All > warnings: 0 Check shards - PASSED -- Command > elapsed time: 00:00:03 -- Migration helper > command FINISHED Execute command: /usr/bin/python > /usr/lib/ambari-infra-solr-client/migrationHelper.py --ini-file > ambari_solr_migration.ini --action upgrade-solr-clients Sending upgrade > request: [Upgrade Solr Clients] Traceback (most recent call last): File > "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 2002, in > upgrade_solr_clients(options, accessor, parser, config) File > "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 517, in > upgrade_solr_clients response = post_json(accessor, > CLUSTERS_URL.format(cluster) + REQUESTS_API_URL, cmd_request) File > "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 250, in > post_json response = accessor(url, 'POST', json.dumps(request_body)) File > "/usr/lib/ambari-infra-solr-client/migrationHelper.py", line 117, in > do_request raise Exception('Problem with accessing api. Reason: > {0}'.format(exc)) Exception: Problem with accessing api. Reason: HTTP Error > 500: Internal Server Error Total Runtime: 00:00:03 Upgrade Solr Clients > command FAILED. Stop migration commands ... > {code} > ambari-server.log: > > {code:java} > Caused by: org.apache.ambari.server.ServiceComponentHostNotFoundException: > ServiceComponentHost not found, clusterName=atlas_upgr_cl, > serviceName=AMBARI_INFRA_SOLR, serviceComponentName=INFRA_SOLR_CLIENT, > hostName= > at > org.apache.ambari.server.state.ServiceComponentImpl.getServiceComponentHost(ServiceComponentImpl.java:346) > at > org.apache.ambari.server.controller.MaintenanceStateHelper.isOperationAllowed(MaintenanceStateHelper.java:111) > at > org.apache.ambari.server.controller.MaintenanceStateHelper.isOperationAllowed(MaintenanceStateHelper.java:87) > at > org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper$1.shouldHostBeRemoved(AmbariCustomCommandExecutionHelper.java:287) > at > org.apache.ambari.server.controller.MaintenanceStateHelper.filterHostsInMaintenanceState(MaintenanceStateHelper.java:423) > at > org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addCustomCommandAction(AmbariCustomCommandExecutionHelper.java:278) > at > org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:1187) > at >
[jira] [Updated] (AMBARI-25472) Disable autocomplete on login screen
[ https://issues.apache.org/jira/browse/AMBARI-25472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25472: Labels: pull-request-available (was: ) > Disable autocomplete on login screen > > > Key: AMBARI-25472 > URL: https://issues.apache.org/jira/browse/AMBARI-25472 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25471) After node reboot autostart of components takes too much time.
[ https://issues.apache.org/jira/browse/AMBARI-25471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25471: Labels: pull-request-available (was: ) > After node reboot autostart of components takes too much time. > -- > > Key: AMBARI-25471 > URL: https://issues.apache.org/jira/browse/AMBARI-25471 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Attachments: AMBARI-25471.patch > > > The reason for this is because ambari-agent does not know start order. And so > if INFRA_SOLR with timeout of 10 hours starts before ZOOKEEPER, which it > requires, it’s a big problem. As well as it blocks agent queue for any other > commands. The solution is to run the commands in parallel. Also for fast > autostart users might want to disable retry_gap: {noformat}/var/lib/ambari- > server/resources/scripts/configs.py -a set -l localhost -n cluster_name -u > admin -p admin -c cluster-env -k retry_gap_in_sec -v 0{noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25469) Bad UTF encoding on Alert listener receiver
[ https://issues.apache.org/jira/browse/AMBARI-25469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25469: Labels: pull-request-available (was: ) > Bad UTF encoding on Alert listener receiver > --- > > Key: AMBARI-25469 > URL: https://issues.apache.org/jira/browse/AMBARI-25469 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.7.5 >Reporter: Dmytro Vitiuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.6 > > > The problem observed on gce cluster during testing of Ambari Kerberos slowness > {code:java} > 2020-01-29 09:42:37,550 ERROR [alert-event-bus-2] > AmbariJpaLocalTxnInterceptor:188 - [DETAILED ERROR] Internal exception (1) : > org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding > "UTF8": 0x00 > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433) > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2178) > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306) > at > org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) > at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) > at > org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:155) > at > org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:132) > at > org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:892) > at > org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964) > at > org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633) > at > org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149) > at > org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134) > at > org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845) > at > org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614) > at > org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:285) > at > org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169) > at > org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134) > at > org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:77) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:55) > at > org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$c6d5f173.saveEntities() > at > org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener.onAlertEvent(AlertReceivedListener.java:388) > at > org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$c6d5f173.CGLIB$onAlertEvent$0() > at > org.apache.ambari.server.events.listeners.alerts.AlertReceivedListener$$EnhancerByGuice$$c6d5f173$$FastClassByGuice$$3f418344.invoke() > at > com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:76) > at > org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:44) > at > com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:77) > at > com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:55) > at >
[jira] [Updated] (AMBARI-25465) Postgresql service naming convention changed on SUSE 12 SP2
[ https://issues.apache.org/jira/browse/AMBARI-25465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25465: Labels: pull-request-available (was: ) > Postgresql service naming convention changed on SUSE 12 SP2 > --- > > Key: AMBARI-25465 > URL: https://issues.apache.org/jira/browse/AMBARI-25465 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.4, 2.7.5 >Reporter: Szilard Antal >Assignee: Szilard Antal >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > > Ambari server setup is failing to succeed when being initiated on Suse 12 SP2 > operating system. > The new installation of pgsql 9.6 creates > "/usr/lib/systemd/system/postgresql-9.6.service" instead of > "/usr/lib/systemd/system/postgresql.service". > This was handled for Redhat previously but due to this > [wiki|https://wiki.postgresql.org/wiki/Zypper_Installation] site the same fix > is needed on SLES 12 as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25464) Components autostart does not work sometimes after ambari-agent restart
[ https://issues.apache.org/jira/browse/AMBARI-25464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25464: Labels: pull-request-available (was: ) > Components autostart does not work sometimes after ambari-agent restart > --- > > Key: AMBARI-25464 > URL: https://issues.apache.org/jira/browse/AMBARI-25464 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Attachments: AMBARI-25464.patch > > > Spawned from https://jira.cloudera.com/browse/ENGESC-469 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25454) API exception on trying to assign permission to user group with custom Ambari Views
[ https://issues.apache.org/jira/browse/AMBARI-25454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25454: Labels: pull-request-available (was: ) > API exception on trying to assign permission to user group with custom Ambari > Views > --- > > Key: AMBARI-25454 > URL: https://issues.apache.org/jira/browse/AMBARI-25454 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-views >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > > Issue appears when logic trying to fetch allowed statuses for the request > scope. The problem is that views are pushed to the request scope and have no > allowance to have Ambari admin permissions. > Here are several ways to solve the problem: > - do not include views for such kind of the request to the scope > - instead of failing, give a warning to the log, and if there are no objects > left in the scope, show to the user last warning in return > The less intrusive way is to done it in a second way as first way may change > the logic of how it currently work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25461: Labels: pull-request-available (was: ) > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25459) Ambari doesn't show versions page after invalid repo was added
[ https://issues.apache.org/jira/browse/AMBARI-25459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25459: Labels: pull-request-available (was: ) > Ambari doesn't show versions page after invalid repo was added > -- > > Key: AMBARI-25459 > URL: https://issues.apache.org/jira/browse/AMBARI-25459 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.5 >Reporter: Papirkovskyy Myroslav >Assignee: Papirkovskyy Myroslav >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.6 > > > Steps to reproduce: > # Deploy cluster. > # Add repository version with ":" as credentials (set skip > validation before saving). > # Try to open versions page. > ambari-server log: > {code:java} > 2020-01-18 00:45:14,915 ERROR [ambari-client-thread-388] ReadHandler:99 - Bad > request: > java.util.regex.PatternSyntaxException: Dangling meta character '*' near > index 0 > *:* > ^ > at java.util.regex.Pattern.error(Pattern.java:1955) > at java.util.regex.Pattern.sequence(Pattern.java:2123) > at java.util.regex.Pattern.expr(Pattern.java:1996) > at java.util.regex.Pattern.compile(Pattern.java:1696) > at java.util.regex.Pattern.(Pattern.java:1351) > at java.util.regex.Pattern.compile(Pattern.java:1028) > at java.lang.String.replaceFirst(String.java:2178) > at > org.apache.ambari.server.utils.URLCredentialsHider.hideCredentials(URLCredentialsHider.java:48) > at > org.apache.ambari.server.controller.internal.RepositoryResourceProvider.getResources(RepositoryResourceProvider.java:182) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java: > 965) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:139) > at > org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529) > at > org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:482) > at > org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503) > at > org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503) > at > org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:454) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:164) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:128) > at > org.apache.ambari.server.api.services.ClusterStackVersionService.getClusterStackVersions(ClusterStackVersionService.java:68) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25457) Hive 3 Grafana dashboards showing outdated metrics
[ https://issues.apache.org/jira/browse/AMBARI-25457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25457: Labels: grafana hive metrics pull-request-available (was: grafana hive metrics) > Hive 3 Grafana dashboards showing outdated metrics > --- > > Key: AMBARI-25457 > URL: https://issues.apache.org/jira/browse/AMBARI-25457 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3, 2.7.4, 2.7.5 >Reporter: Tamas Payer >Assignee: Tamas Payer >Priority: Major > Labels: grafana, hive, metrics, pull-request-available > > Some of the metrics' name has been changed in Hive 3. Due to this change many > graphs shows no data on Hive Home, HiveServer2 and HiveMetastore dashboards. > Suggested changes: > +HiveSever2+ > The _default.General.api_get_all_databases_ and > _default.General.api_get_partitions_by_names_ metrics are not provided by > HiveServer2 anymore - only by HiveMetastore - so the "API Times" row with the > two charts has been removed. > +Hive Metastore+ > |*Original Name*| *New Name*| > |default.General.api_get_all_databases_75thpercentile|default.General.api_get_databases_75thpercentile| > |default.General.api_get_all_databases_999thpercentile|default.General.api_get_databases_999thpercentile| > |default.General.memory.heap.max|default.General.heap.max| > |default.General.memory.heap.used|default.General.heap.used| > |default.General.memory.heap.committed|default.General.heap.committed| > |default.General.memory.non-heap.max|default.General.non-heap.max| > |default.General.memory.non-heap.used|default.General.non-heap.used| > |default.General.memory.non-heap.committed|default.General.non-heap.committed| > > +Hive Home+ > > | *Original Name*| *New Name*| > |default.General.init_total_count_db|default.General.total_count_dbs| > |default.General.init_total_count_tables|default.General.total_count_tables| > |default.General.init_total_count_partitions|default.General.total_count_partitions| > |default.General.api_create_table_count|api_create_table_req_count| > |default.General.memory.heap.max|default.General.heap.max| > |default.General.memory.heap.used|default.General.heap.used| > |default.General.memory.heap.committed|default.General.heap.committed| > |default.General.memory.non-heap.max|default.General.non-heap.max| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25455) Ambari-agent does not restart the agent when memory leak happens
[ https://issues.apache.org/jira/browse/AMBARI-25455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25455: Labels: pull-request-available (was: ) > Ambari-agent does not restart the agent when memory leak happens > > > Key: AMBARI-25455 > URL: https://issues.apache.org/jira/browse/AMBARI-25455 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Attachments: AMBARI-25455.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
[ https://issues.apache.org/jira/browse/AMBARI-25453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25453: Labels: pull-request-available (was: ) > If hive.server2.webui.use.ssl was setted to true it will always use https, > does not matter if now it is false > - > > Key: AMBARI-25453 > URL: https://issues.apache.org/jira/browse/AMBARI-25453 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-22043) deleting and uploading files Using the HDFS View
[ https://issues.apache.org/jira/browse/AMBARI-22043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22043: Labels: pull-request-available (was: ) > deleting and uploading files Using the HDFS View > > > Key: AMBARI-22043 > URL: https://issues.apache.org/jira/browse/AMBARI-22043 > Project: Ambari > Issue Type: Bug > Components: ambari-views > Environment: AMBARI:- 2.5.0.3 > HDP 2.6 > ENTOS 7 >Reporter: Vijay Kumar >Assignee: Akhil Naik >Priority: Minor > Labels: pull-request-available > > When using HDFS File View when I do a file delete, followed by another upload > and delete of the same file, I'm getting the error shown below. (Failed to > move the file to .Trash). > One workaround is when you get the Delete pop-up, you can check the "delete > permanently" box. > This only occurs if the file is already present in .Trash > Works fine when using the command line. > admin@vnagarajan-gvklab1 ~$ hadoop fs -touchz /user/admin/testdelete > admin@vnagarajan-gvklab1 ~$ hadoop fs -rm /user/admin/testdelete > 17/09/20 22:46:38 INFO fs.TrashPolicyDefault: Moved: > 'hdfs://gvklab1.openstacklocal:8020/user/admin/testdelete' to trash at: > hdfs://gvklab1.openstacklocal:8020/user/admin/.Trash/Current/user/admin/testdelete > admin@vnagarajan-gvklab1 ~$ hadoop fs -touchz /user/admin/testdelete > admin@vnagarajan-gvklab1 ~$ hadoop fs -rm /user/admin/testdelete > 17/09/20 22:46:49 INFO fs.TrashPolicyDefault: Moved: > 'hdfs://gvklab1.openstacklocal:8020/user/admin/testdelete' to trash at: > hdfs://gvklab1.openstacklocal:8020/user/admin/.Trash/Current/user/admin/testdelete1505947609951 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25450) [ubuntu16] HDP install failed for upgrade from HDP-3.0.1.0-187 to HDP-3.1.5.0-139
[ https://issues.apache.org/jira/browse/AMBARI-25450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25450: Labels: pull-request-available (was: ) > [ubuntu16] HDP install failed for upgrade from HDP-3.0.1.0-187 to > HDP-3.1.5.0-139 > -- > > Key: AMBARI-25450 > URL: https://issues.apache.org/jira/browse/AMBARI-25450 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Attachments: AMBARI-25450.patch > > > Package Manager failed to install packages: No package found for > sqoop-$\\{stack_version}(expected name: sqoop-3-1-5-0-139) Traceback (most > recent call last): File "/var/lib/ambari- > agent/cache/custom_actions/scripts/install_packages.py", line 493, in > InstallPackages().execute() File "/usr/lib/ambari- > agent/lib/resource_management/libraries/script/script.py", line 352, in > execute method(env) File "/var/lib/ambari- > agent/cache/custom_actions/scripts/install_packages.py", line 156, in > actionexecute raise Fail("Failed to distribute repositories/install packages") > resource_management.core.exceptions.Fail: Failed to distribute > repositories/install packages Live Cluster : > [+http://172.27.120.193:8080/+|http://172.27.120.193:8080/] ambari-server > version : 2.7.5.0-67 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25448) Mask credentials during install step
[ https://issues.apache.org/jira/browse/AMBARI-25448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25448: Labels: pull-request-available (was: ) > Mask credentials during install step > > > Key: AMBARI-25448 > URL: https://issues.apache.org/jira/browse/AMBARI-25448 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > > This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25447) Multiple filter conditions not working in Ambari workflow manager view
[ https://issues.apache.org/jira/browse/AMBARI-25447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25447: Labels: pull-request-available (was: ) > Multiple filter conditions not working in Ambari workflow manager view > -- > > Key: AMBARI-25447 > URL: https://issues.apache.org/jira/browse/AMBARI-25447 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25446) Credentials should not be shown on cleartext on Ambari UI
[ https://issues.apache.org/jira/browse/AMBARI-25446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25446: Labels: pull-request-available (was: ) > Credentials should not be shown on cleartext on Ambari UI > - > > Key: AMBARI-25446 > URL: https://issues.apache.org/jira/browse/AMBARI-25446 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Attachments: AMBARI-25446.patch > > > Please see screenshot attached. Ambari UI - Stack and Versions page shows > username and password in cleartext . We should atleast hide the password Also > in Review page for UI install cc [~accountid:557058:af856db7-a0ad- > 4e2b-b848-f11f481bf96f] / [~accountid:5dc59258b6e6b50c58af136b] / > [~accountid:557058:e797d548-8a74-4f63-a68d-616111201b1c] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25445) VDF registration fails with SunCertPathBuilderException: unable to find valid certification path to requested target' on HTTPS cluster
[ https://issues.apache.org/jira/browse/AMBARI-25445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25445: Labels: pull-request-available (was: ) > VDF registration fails with SunCertPathBuilderException: unable to find valid > certification path to requested target' on HTTPS cluster > --- > > Key: AMBARI-25445 > URL: https://issues.apache.org/jira/browse/AMBARI-25445 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-25445.patch > > > Retrying deploy with latest build after BUG-122455 was fixed Here Stack > registration is failing with {code} An internal system exception occurred: > Could not load url from https://1055c7c3-1b7b- > 43f6-80a7-3e72cb0f8912:cloudera_techprevi...@archive-test.cloudera.com/p/HDP- > GPL/centos7/3.x/BUILDS/3.1.5.0-139/repodata/repomd.xml. > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target {code} 172.27.74.1 is a live node > where issue has occurred. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25444) Deploy fails with 401:Unauthorized on HDP-GPL; whereas url is actually accessible with credentials supplied by Releng team
[ https://issues.apache.org/jira/browse/AMBARI-25444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25444: Labels: pull-request-available (was: ) > Deploy fails with 401:Unauthorized on HDP-GPL; whereas url is actually > accessible with credentials supplied by Releng team > -- > > Key: AMBARI-25444 > URL: https://issues.apache.org/jira/browse/AMBARI-25444 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Attachments: AMBARI-25444.patch > > > We are trying to deploy with paywalled repos of HDP and Ambari (ones supplied > in RELENG-7654) but deploy is failing at client install with {code} > RuntimeError: Failed to execute command '/usr/bin/yum -y install hdp-select', > exited with code '1', message: 'https://:@archive-test.cloudera.com/p > /HDP-GPL/centos7/3.x/BUILDS/3.1.5.0-139/repodata/repomd.xml: [Errno 14] HTTPS > Error 401 - Unauthorized {code} This url is accessible with credentials RE has > supplied ie; https://1055c7c3-1b7b- > 43f6-80a7-3e72cb0f8912:cloudera_techprevi...@archive-test.cloudera.com/p/HDP- > GPL/centos7/3.x/BUILDS/3.1.5.0-139/repodata/repomd.xml So not sure which > credential is Ambari picking as from the error it looks like the credentials > Ambari is using on this repo is incorrect. Could you please take a look Live > cluster : http://172.27.136.132:8080/ Repo urls used here for deploy: Ambari : > https://1055c7c3-1b7b-43f6-80a7-3e72cb0f8912:Cloudera_TechPreview2@archive- > test.cloudera.com/p/ambari/2.7.5.0-64/centos7/ambaribn.repo HDP: > https://1055c7c3-1b7b-43f6-80a7-3e72cb0f8912:Cloudera_TechPreview2@archive- > test.cloudera.com/p/HDP/centos7/3.x/BUILDS/3.1.5.0-139 cc > [~accountid:557058:af856db7-a0ad- > 4e2b-b848-f11f481bf96f]/[~accountid:5dc59258b6e6b50c58af136b] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25443) Create principal/keytab operation with multi threaded
[ https://issues.apache.org/jira/browse/AMBARI-25443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25443: Labels: pull-request-available (was: ) > Create principal/keytab operation with multi threaded > - > > Key: AMBARI-25443 > URL: https://issues.apache.org/jira/browse/AMBARI-25443 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > > Ambari Principal and keytabs create operation runs in sequential manner, > which taking a lot of time on a large cluster. > To cut the time, each step should be palatalized between cluster nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25426) Error while Validating Coordinator xml in Workflow Manager View
[ https://issues.apache.org/jira/browse/AMBARI-25426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25426: Labels: pull-request-available (was: ) > Error while Validating Coordinator xml in Workflow Manager View > --- > > Key: AMBARI-25426 > URL: https://issues.apache.org/jira/browse/AMBARI-25426 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.4 >Reporter: Akhil Naik >Assignee: Akhil Naik >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2019-11-27 at 3.10.16 PM.png > > > Description : > there is an Javascript code when following operation is performed due to > which there is an Error message which is unnecessary > *steps to reproduce* > * Open WFM view > * Create Coordinator > * Select xml file & save > * Try Validate > * As soon as we open validate window it is giving error if we click on > validate its validating though > The error Screen shot attached : !Screenshot 2019-11-27 at 3.10.16 PM.png! > *The error in javascript console : * > {code:java} > vendor-03ed9177dfebfe0523a6e14f3a1c.js:13 Error: TypeError: Cannot read > property '_name' of undefined > at r. > (oozie-designer-431d8215c58dd06e3b4e78162c4b0483.js:formatted:1422) > at y (vendor-03ed9177dfebfe0523a6e14f3a1c.js:19) > at b (vendor-03ed9177dfebfe0523a6e14f3a1c.js:19) > at g (vendor-03ed9177dfebfe0523a6e14f3a1c.js:19) > at h (vendor-03ed9177dfebfe0523a6e14f3a1c.js:19) > at vendor-03ed9177dfebfe0523a6e14f3a1c.js:13 > at invoke (vendor-03ed9177dfebfe0523a6e14f3a1c.js:5) > at r.flush (vendor-03ed9177dfebfe0523a6e14f3a1c.js:5) > at n.flush (vendor-03ed9177dfebfe0523a6e14f3a1c.js:5) > at a.end (vendor-03ed9177dfebfe0523a6e14f3a1c.js:6) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25424) Failed to edit workflow from Ambari workflow Manager while accessing Ambari UI over Knox
[ https://issues.apache.org/jira/browse/AMBARI-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25424: Labels: pull-request-available (was: ) > Failed to edit workflow from Ambari workflow Manager while accessing Ambari > UI over Knox > > > Key: AMBARI-25424 > URL: https://issues.apache.org/jira/browse/AMBARI-25424 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.3 >Reporter: amarnath reddy pappu >Priority: Major > Labels: pull-request-available > > Ambari workflow manager view is accessed over knox, editing the workflow from > the view will fail as knox fails to identify/parse the xml format. > Exception in knox logs > {code:java|bgColor=#f5f5f5} > ==> gateway.log <== > 2018-03-28 10:16:25,542 ERROR hadoop.gateway > (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter: > com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' > (code 60)): expected a valid value (number, String, array, object, 'true', > 'false' or 'null') > at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2] > 2018-03-28 10:16:25,542 ERROR hadoop.gateway > (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter: > com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' > (code 60)): expected a valid value (number, String, array, object, 'true', > 'false' or 'null') > at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2] > 2018-03-28 10:16:25,542 ERROR hadoop.gateway > (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter: > com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' > (code 60)): expected a valid value (number, String, array, object, 'true', > 'false' or 'null') > at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2] > 2018-03-28 10:16:25,543 ERROR hadoop.gateway > (GatewayFilter.java:doFilter(141)) - Gateway processing failed: > com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' > (code 60)): expected a valid value (number, String, array, object, 'true', > 'false' or 'null') > at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2] > com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' > (code 60)): expected a valid value (number, String, array, object, 'true', > 'false' or 'null') > at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2] > at > com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1369) > at > com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:599) > at > com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:520) > at > com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleUnexpectedValue(ReaderBasedJsonParser.java:1379) > at > com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:669) > at > org.apache.hadoop.gateway.filter.rewrite.impl.json.JsonFilterReader.read(JsonFilterReader.java:89) > at > org.apache.hadoop.gateway.filter.rewrite.impl.json.JsonUrlRewriteFilterReader.read(JsonUrlRewriteFilterReader.java:32) > at > org.apache.commons.io.input.ReaderInputStream.fillBuffer(ReaderInputStream.java:198) > at > org.apache.commons.io.input.ReaderInputStream.read(ReaderInputStream.java:242) > {code} > {code:java|bgColor=#f5f5f5} > ==> gateway-audit.log <== > 18/03/28 10:16:25 > ||6e7f841c-3aa9-4d8f-a71f-bfbc6138dedf|audit|10.200.4.250|AMBARI|anonymous|||access|uri|/gateway/ui/ambari/api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/wfm/resources/proxy/readWorkflow?workflowPath=/user/admin/workflow.xml=WORKFLOW|failure| > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25413) Ambari is changing the truststore permission from 444/644 to 640.
[ https://issues.apache.org/jira/browse/AMBARI-25413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25413: Labels: pull-request-available (was: ) > Ambari is changing the truststore permission from 444/644 to 640. > - > > Key: AMBARI-25413 > URL: https://issues.apache.org/jira/browse/AMBARI-25413 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.4 >Reporter: Aashish Bathla >Assignee: Szilard Antal >Priority: Major > Labels: pull-request-available > > When running ambari-server setup-security and choosing '[1] Enable HTTPS for > Ambari server.' we give the following information: > Do you want to disable HTTPS [y/n] (n)? n > SSL port [8080] ? 8080 > Enter path to Certificate: > Enter path to Private Key: > Please enter password for Private Key: > Generating random password for HTTPS keystore...done. > Importing and saving Certificate...done. > Thereafter Unix permission of the systemwide Java truststore > /var/lib/ca-certificates/java-cacerts are changed from mode 444 to 640. > In consequence Applications do not start anymore because the truststore is > not world readable. It's creating impact on applications which is run by > other users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25441) HDP-GPL field is not available in version registration page but present in edit page
[ https://issues.apache.org/jira/browse/AMBARI-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25441: Labels: pull-request-available (was: ) > HDP-GPL field is not available in version registration page but present in > edit page > > > Key: AMBARI-25441 > URL: https://issues.apache.org/jira/browse/AMBARI-25441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.5 > > > New version registration page does not have HDP-GPL field. But this field is > present when we are editing the version urls after registering. -- This message was sent by Atlassian Jira (v8.3.4#803005)