[jira] [Assigned] (AMBARI-24872) NIFI-Hosts dashboard does not show any metrics in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-24872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-24872: -- Assignee: Aravindan Vijayan > NIFI-Hosts dashboard does not show any metrics in Grafana > - > > Key: AMBARI-24872 > URL: https://issues.apache.org/jira/browse/AMBARI-24872 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: amarnath reddy pappu >Assignee: Aravindan Vijayan >Priority: Critical > > Description > In Grafana, NIFI-Hosts dashboard does not show any metrics though data > present in the AMS. > Steps to reproduce it > 1. Install the cluster the and add NIFI service. > 2. Goto NIFI and add Ambari reporting task so that it sends the metrics to > AMS. > 3. You can see NIFI-Home shows the Graphs but NIFI-Hosts does not. > Below API call returns the data points > http://xxx:6188/ws/v1/timeline/metrics?metricNames=jvm.uptime._avg=nifi==1541611634=1541698034 > where as with hostname clause it does not return any > http://xxx:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=jvm.uptime._avg=%=nifi==1541611634=1541698034=20=avg=false > NIFI is sending instanceid and but AMS is not handling correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25089) NIFI-Hosts dashboard does not show any metrics in Grafana
[ https://issues.apache.org/jira/browse/AMBARI-25089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-25089. Resolution: Duplicate > NIFI-Hosts dashboard does not show any metrics in Grafana > - > > Key: AMBARI-25089 > URL: https://issues.apache.org/jira/browse/AMBARI-25089 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25089) NIFI-Hosts dashboard does not show any metrics in Grafana
Aravindan Vijayan created AMBARI-25089: -- Summary: NIFI-Hosts dashboard does not show any metrics in Grafana Key: AMBARI-25089 URL: https://issues.apache.org/jira/browse/AMBARI-25089 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.3 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25078) Add metering metrics to AMS Metric Monitor
[ https://issues.apache.org/jira/browse/AMBARI-25078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-25078. Resolution: Fixed > Add metering metrics to AMS Metric Monitor > -- > > Key: AMBARI-25078 > URL: https://issues.apache.org/jira/browse/AMBARI-25078 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25078) Add metering metrics to AMS Metric Monitor
Aravindan Vijayan created AMBARI-25078: -- Summary: Add metering metrics to AMS Metric Monitor Key: AMBARI-25078 URL: https://issues.apache.org/jira/browse/AMBARI-25078 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25077) Grafana on a workload cluster should show visualization of only it's own cluster (collector is shared for multiple clusters)
[ https://issues.apache.org/jira/browse/AMBARI-25077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-25077. Resolution: Fixed > Grafana on a workload cluster should show visualization of only it's own > cluster (collector is shared for multiple clusters) > > > Key: AMBARI-25077 > URL: https://issues.apache.org/jira/browse/AMBARI-25077 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25077) Grafana on a workload cluster should show visualization of only it's own cluster (collector is shared for multiple clusters)
Aravindan Vijayan created AMBARI-25077: -- Summary: Grafana on a workload cluster should show visualization of only it's own cluster (collector is shared for multiple clusters) Key: AMBARI-25077 URL: https://issues.apache.org/jira/browse/AMBARI-25077 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23466) Upgrade AMS Grafana version to 5.2.4
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-23466. Resolution: Fixed > Upgrade AMS Grafana version to 5.2.4 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24738) Update grafana datasource to get values from new object
[ https://issues.apache.org/jira/browse/AMBARI-24738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24738: --- Fix Version/s: (was: trunk) 2.8.0 > Update grafana datasource to get values from new object > --- > > Key: AMBARI-24738 > URL: https://issues.apache.org/jira/browse/AMBARI-24738 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > In the new grafana version templateSrv doesn't have some fields. We need to > get these values from a different fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-23478.
Resolution: Fixed
PR merged to trunk.
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-23478:
---
Fix Version/s: (was: 3.0.0)
2.8.0
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Aravindan Vijayan
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24563:
---
Fix Version/s: (was: 2.7.1)
2.7.3
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-24563) global name 'VERIFY_DEPENDENCY_CMD' is not defined'
[
https://issues.apache.org/jira/browse/AMBARI-24563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reopened AMBARI-24563:
This patch has not been committed into branch-2.7. Please commit this to
branch-2.7.
> global name 'VERIFY_DEPENDENCY_CMD' is not defined'
> ---
>
> Key: AMBARI-24563
> URL: https://issues.apache.org/jira/browse/AMBARI-24563
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.1
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> STR:-
> 1. deploy the cluster with HDP-3.0.1.0-164 + ambari_version : 2.7.1.0-147
> 2. added a patch targetVDF-29-08-2018-00-53-55.xml
> 3. install version
> {code}
> 2018-08-29 16:47:27,225 - Package Manager failed to install packages: Failed
> to execute command '/usr/bin/apt-get -o Dpkg::Options::=--force-confdef
> --allow-unauthenticated --assume-yes install -o
> Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts= hdp-select', exited
> with code '100', message: 'E: dpkg was interrupted, you must manually run
> 'dpkg --configure -a' to correct the problem.
> '
> 2018-08-29 16:47:27,250 - Could not install packages. Error: global name
> 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 136, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 447, in install_packages
> if not self.repo_mgr.verify_dependencies():
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py", line
> 218, in verify_dependencies
> err_msg = Logger.filter_text("Failed to verify package dependencies.
> Execution of '%s' returned %s. %s" % (VERIFY_DEPENDENCY_CMD, code, out))
> NameError: global name 'VERIFY_DEPENDENCY_CMD' is not defined
> The above exception was the cause of the following exception:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 486, in
> InstallPackages().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 149, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
[ https://issues.apache.org/jira/browse/AMBARI-24550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened AMBARI-24550: > Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 > to 2.7.1.0 > -- > > Key: AMBARI-24550 > URL: https://issues.apache.org/jira/browse/AMBARI-24550 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > STR: > 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0 > 2) Upgrade Ambari to 2.7.1.0 > Yarn Timeline Service V2 Reader goes down after some time. > Reason: the placeholders in yarn.timeline-service.reader.webapp.address and > yarn.timeline-service.reader.webapp.https.address are no longer replaced by > the stack code so these values become empty. In this case the timeline reader > will use the default ports which may conflict with other ports used by > other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
[ https://issues.apache.org/jira/browse/AMBARI-24550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24550: --- Fix Version/s: (was: 2.7.1) 2.7.3 > Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 > to 2.7.1.0 > -- > > Key: AMBARI-24550 > URL: https://issues.apache.org/jira/browse/AMBARI-24550 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > STR: > 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0 > 2) Upgrade Ambari to 2.7.1.0 > Yarn Timeline Service V2 Reader goes down after some time. > Reason: the placeholders in yarn.timeline-service.reader.webapp.address and > yarn.timeline-service.reader.webapp.https.address are no longer replaced by > the stack code so these values become empty. In this case the timeline reader > will use the default ports which may conflict with other ports used by > other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24550) Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 to 2.7.1.0
[ https://issues.apache.org/jira/browse/AMBARI-24550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659224#comment-16659224 ] Aravindan Vijayan commented on AMBARI-24550: [~amagyar] This is missing from branch-2.7. Please commit this to branch-2.7 as well. > Yarn Timeline Service V2 Reader goes down after Ambari Upgrade from 2.7.0.0 > to 2.7.1.0 > -- > > Key: AMBARI-24550 > URL: https://issues.apache.org/jira/browse/AMBARI-24550 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > STR: > 1) Install cluster with Ambari2.7.0.0 + HDP-3.0.0.0 > 2) Upgrade Ambari to 2.7.1.0 > Yarn Timeline Service V2 Reader goes down after some time. > Reason: the placeholders in yarn.timeline-service.reader.webapp.address and > yarn.timeline-service.reader.webapp.https.address are no longer replaced by > the stack code so these values become empty. In this case the timeline reader > will use the default ports which may conflict with other ports used by > other components. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24491) Workflow Manager should add ${nameNone}/ string to the beginning of app path
[
https://issues.apache.org/jira/browse/AMBARI-24491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659212#comment-16659212
]
Aravindan Vijayan commented on AMBARI-24491:
Please commit this to branch-2.7 and trunk.
> Workflow Manager should add ${nameNone}/ string to the beginning of app path
>
>
> Key: AMBARI-24491
> URL: https://issues.apache.org/jira/browse/AMBARI-24491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: venkat
>Assignee: venkat
>Priority: Blocker
> Fix For: 2.7.3
>
>
> When I use Workflow Manager to create a workflow for Oozie and add a spark
> action and provide *Application* path using the *Browse* button, Ambari WFM
> only inserts the app path in this form: */path/to/app*
> In this case the result is a FileNotFoundException in Oozie.
> *Workaround*:
> When I modify the app path to *${nameNode}/path/to/app* then the job will run
> successfully.
> Please see tag of the attached generated good and bad workflow xmls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24491) Workflow Manager should add ${nameNone}/ string to the beginning of app path
[
https://issues.apache.org/jira/browse/AMBARI-24491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24491:
---
Fix Version/s: 2.7.3
> Workflow Manager should add ${nameNone}/ string to the beginning of app path
>
>
> Key: AMBARI-24491
> URL: https://issues.apache.org/jira/browse/AMBARI-24491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: venkat
>Assignee: venkat
>Priority: Major
> Fix For: 2.7.3
>
>
> When I use Workflow Manager to create a workflow for Oozie and add a spark
> action and provide *Application* path using the *Browse* button, Ambari WFM
> only inserts the app path in this form: */path/to/app*
> In this case the result is a FileNotFoundException in Oozie.
> *Workaround*:
> When I modify the app path to *${nameNode}/path/to/app* then the job will run
> successfully.
> Please see tag of the attached generated good and bad workflow xmls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24491) Workflow Manager should add ${nameNone}/ string to the beginning of app path
[
https://issues.apache.org/jira/browse/AMBARI-24491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24491:
---
Priority: Blocker (was: Major)
> Workflow Manager should add ${nameNone}/ string to the beginning of app path
>
>
> Key: AMBARI-24491
> URL: https://issues.apache.org/jira/browse/AMBARI-24491
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: venkat
>Assignee: venkat
>Priority: Blocker
> Fix For: 2.7.3
>
>
> When I use Workflow Manager to create a workflow for Oozie and add a spark
> action and provide *Application* path using the *Browse* button, Ambari WFM
> only inserts the app path in this form: */path/to/app*
> In this case the result is a FileNotFoundException in Oozie.
> *Workaround*:
> When I modify the app path to *${nameNode}/path/to/app* then the job will run
> successfully.
> Please see tag of the attached generated good and bad workflow xmls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
[ https://issues.apache.org/jira/browse/AMBARI-24797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24797. Resolution: Fixed > Support regex based metric inclusion in KafkaTimelineMetricsReporter > > > Key: AMBARI-24797 > URL: https://issues.apache.org/jira/browse/AMBARI-24797 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > The request is to to add an additional config property > *external.kafka.metrics.include.regex* to include metrics based on regex > patterns. This property can take multiple comma separated regex expressions. > Implementation Logic > * By default, a metric will be included. > * If the metric starts with any of the prefixes in the exclude.prefix > property, it is a candidate for discarding. > * However, for an "excluded" metric, if the metric starts with any of the > prefixes in include.prefix or matches any pattern in include.regex, it will > NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24797) Support regex based metric inclusion in KafkaTimelineMetricsReporter
Aravindan Vijayan created AMBARI-24797: -- Summary: Support regex based metric inclusion in KafkaTimelineMetricsReporter Key: AMBARI-24797 URL: https://issues.apache.org/jira/browse/AMBARI-24797 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 The request is to to add an additional config property *external.kafka.metrics.include.regex* to include metrics based on regex patterns. This property can take multiple comma separated regex expressions. Implementation Logic * By default, a metric will be included. * If the metric starts with any of the prefixes in the exclude.prefix property, it is a candidate for discarding. * However, for an "excluded" metric, if the metric starts with any of the prefixes in include.prefix or matches any pattern in include.regex, it will NOT be discarded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24771) Fix CVE issues for Ambari Metrics (2.7.3)
[ https://issues.apache.org/jira/browse/AMBARI-24771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24771. Resolution: Fixed > Fix CVE issues for Ambari Metrics (2.7.3) > - > > Key: AMBARI-24771 > URL: https://issues.apache.org/jira/browse/AMBARI-24771 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24771) Fix CVE issues for Ambari Metrics (2.7.3)
Aravindan Vijayan created AMBARI-24771: -- Summary: Fix CVE issues for Ambari Metrics (2.7.3) Key: AMBARI-24771 URL: https://issues.apache.org/jira/browse/AMBARI-24771 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.7.3 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24637) Ambari metrics service check failed during UI deploy
[ https://issues.apache.org/jira/browse/AMBARI-24637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24637: --- Fix Version/s: (was: 2.8.0) 2.7.3 > Ambari metrics service check failed during UI deploy > > > Key: AMBARI-24637 > URL: https://issues.apache.org/jira/browse/AMBARI-24637 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 2h > Remaining Estimate: 0h > > Race conditions in UUID computation helper caused issues in writes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24750) HTTP 500 internal server error caused by NPE when trying to set loglevel in logsearch
[
https://issues.apache.org/jira/browse/AMBARI-24750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24750:
---
Fix Version/s: 2.7.3
> HTTP 500 internal server error caused by NPE when trying to set loglevel in
> logsearch
> -
>
> Key: AMBARI-24750
> URL: https://issues.apache.org/jira/browse/AMBARI-24750
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
>Affects Versions: 2.7.1
>Reporter: Péter Gergő Barna
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This request sometimes returns HTTP 500 internal server error:
>
> {noformat}
> curl -vv -X PUT --header 'Content-Type: application/json' --header 'Accept:
> application/json' --header 'Authorization: Basic YWRtaW46YWRtaW4=' -d
> '{"filter":{"storm_worker_event":{"hosts":[],"defaultLevels":["FATAL","ERROR","WARN","INFO","DEBUG","TRACE","UNKNOWN"],"expiryTime":null,"label":"storm_worker_event","overrideLevels":[]}}}'
>
> 'http://my.host:61888/api/v1/shipper/filters/streamline-181008-150631-i7y-1/level'{noformat}
>
> a corresponding entry appears in this log
> ambari-logsearch-portal/logsearch.json:
>
>
> {noformat}
> {"level":"WARN","file":"ShipperConfigManager.java","thread_name":"qtp1188445627-1735","line_number":142,"logger_name":"org.apache.ambari.logsearch.manager.ShipperConfigManager","logtime":"1539020343816","log_message":"Could
> not update log level filters java.lang.NullPointerException at
> org.apache.ambari.logsearch.config.zookeeper.LogLevelFilterManagerZK.setLogLevelFilters(LogLevelFilterManagerZK.java:86)
> at
> org.apache.ambari.logsearch.manager.ShipperConfigManager.setLogLevelFilters(ShipperConfigManager.java:138)
> at
> org.apache.ambari.logsearch.rest.ShipperConfigResource.setLogLevelFilter(ShipperConfigResource.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
> at
> org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
> at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at
> org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:315) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:297) at
> org.glassfish.jersey.internal.Errors.process(Errors.java:267) at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
> at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
> at
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
> at
>
[jira] [Updated] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24723: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
[ https://issues.apache.org/jira/browse/AMBARI-24723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24723: --- Status: Patch Available (was: Open) > Support wild cards in AppId and InstanceId fields in AMS GET API. > - > > Key: AMBARI-24723 > URL: https://issues.apache.org/jira/browse/AMBARI-24723 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24723) Support wild cards in AppId and InstanceId fields in AMS GET API.
Aravindan Vijayan created AMBARI-24723: -- Summary: Support wild cards in AppId and InstanceId fields in AMS GET API. Key: AMBARI-24723 URL: https://issues.apache.org/jira/browse/AMBARI-24723 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24688) Backend changes for the newer version of AMS Grafana.
[ https://issues.apache.org/jira/browse/AMBARI-24688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24688. Resolution: Fixed > Backend changes for the newer version of AMS Grafana. > - > > Key: AMBARI-24688 > URL: https://issues.apache.org/jira/browse/AMBARI-24688 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 5.2.4
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Fix Version/s: 2.8.0 > Upgrade AMS Grafana version to 5.2.4 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24705) Fix build issues in ambari-metrics repo.
[ https://issues.apache.org/jira/browse/AMBARI-24705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24705. Resolution: Fixed PR merged. Verified that the post merge master build succeeded. > Fix build issues in ambari-metrics repo. > - > > Key: AMBARI-24705 > URL: https://issues.apache.org/jira/browse/AMBARI-24705 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24706) Fix issues in ambari common python package publishing utility.
[ https://issues.apache.org/jira/browse/AMBARI-24706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24706. Resolution: Fixed PR merged. > Fix issues in ambari common python package publishing utility. > -- > > Key: AMBARI-24706 > URL: https://issues.apache.org/jira/browse/AMBARI-24706 > Project: Ambari > Issue Type: Task >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24706) Fix issues in ambari common python package publishing utility.
Aravindan Vijayan created AMBARI-24706: -- Summary: Fix issues in ambari common python package publishing utility. Key: AMBARI-24706 URL: https://issues.apache.org/jira/browse/AMBARI-24706 Project: Ambari Issue Type: Task Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24705) Fix build issues in ambari-metrics repo.
Aravindan Vijayan created AMBARI-24705: -- Summary: Fix build issues in ambari-metrics repo. Key: AMBARI-24705 URL: https://issues.apache.org/jira/browse/AMBARI-24705 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24695) Remove ambari-metrics from ambari repository.
[ https://issues.apache.org/jira/browse/AMBARI-24695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24695. Resolution: Fixed > Remove ambari-metrics from ambari repository. > - > > Key: AMBARI-24695 > URL: https://issues.apache.org/jira/browse/AMBARI-24695 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24695) Remove ambari-metrics from ambari repository.
Aravindan Vijayan created AMBARI-24695: -- Summary: Remove ambari-metrics from ambari repository. Key: AMBARI-24695 URL: https://issues.apache.org/jira/browse/AMBARI-24695 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24688) Backend changes for the newer version of AMS Grafana.
Aravindan Vijayan created AMBARI-24688: -- Summary: Backend changes for the newer version of AMS Grafana. Key: AMBARI-24688 URL: https://issues.apache.org/jira/browse/AMBARI-24688 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.8.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24679) Fix race condition in agent during registration and topology updates.
[
https://issues.apache.org/jira/browse/AMBARI-24679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24679.
Resolution: Fixed
> Fix race condition in agent during registration and topology updates.
> -
>
> Key: AMBARI-24679
> URL: https://issues.apache.org/jira/browse/AMBARI-24679
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.8.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code}
> ambari_agent - CustomServiceOrchestrator.py - [4840] - root - ERROR - Caught
> an exception while executing custom service command: 'exceptions.KeyError'>: 7; 7#012Traceback (most recent call last):#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 324, in runCommand#012 command = self.generate_command(command_header)#012
> File "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py",
> line 504, in generate_command#012 command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp)#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in
> get_configuration#012 'clusterHostInfo':
> self.topology_cache.get_cluster_host_info(cluster_id),#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ClusterTopologyCache.py", line 108,
> in get_cluster_host_info#012 hostnames =
> [self.hosts_to_id[cluster_id][host_id].hostName for host_id in
> component_dict.hostIds]#012KeyError: 7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24653) YARN Timeline server v2 related system tests fail.
[ https://issues.apache.org/jira/browse/AMBARI-24653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24653. Resolution: Fixed > YARN Timeline server v2 related system tests fail. > -- > > Key: AMBARI-24653 > URL: https://issues.apache.org/jira/browse/AMBARI-24653 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24679) Fix race condition in agent during registration and topology updates.
Aravindan Vijayan created AMBARI-24679:
--
Summary: Fix race condition in agent during registration and
topology updates.
Key: AMBARI-24679
URL: https://issues.apache.org/jira/browse/AMBARI-24679
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.8.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.8.0
{code}
ambari_agent - CustomServiceOrchestrator.py - [4840] - root - ERROR - Caught an
exception while executing custom service command: :
7; 7#012Traceback (most recent call last):#012 File
"/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
324, in runCommand#012 command = self.generate_command(command_header)#012 File
"/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
504, in generate_command#012 command_dict =
self.configuration_builder.get_configuration(cluster_id, service_name,
component_name, required_config_timestamp)#012 File
"/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in
get_configuration#012 'clusterHostInfo':
self.topology_cache.get_cluster_host_info(cluster_id),#012 File
"/usr/lib/ambari-agent/lib/ambari_agent/ClusterTopologyCache.py", line 108, in
get_cluster_host_info#012 hostnames =
[self.hosts_to_id[cluster_id][host_id].hostName for host_id in
component_dict.hostIds]#012KeyError: 7
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 5.2.4
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Summary: Upgrade AMS Grafana version to 5.2.4 (was: Upgrade AMS Grafana version to 4.x) > Upgrade AMS Grafana version to 5.2.4 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24556) Aggregation across clusters are not being done in AMS for even when multiple cluster support is enabled.
[ https://issues.apache.org/jira/browse/AMBARI-24556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24556. Resolution: Fixed > Aggregation across clusters are not being done in AMS for even when multiple > cluster support is enabled. > > > Key: AMBARI-24556 > URL: https://issues.apache.org/jira/browse/AMBARI-24556 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24637) Ambari metrics service check failed during UI deploy
[ https://issues.apache.org/jira/browse/AMBARI-24637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24637. Resolution: Fixed PR merged. > Ambari metrics service check failed during UI deploy > > > Key: AMBARI-24637 > URL: https://issues.apache.org/jira/browse/AMBARI-24637 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Race conditions in UUID computation helper caused issues in writes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24637) Ambari metrics service check failed during UI deploy
[ https://issues.apache.org/jira/browse/AMBARI-24637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24637: --- Fix Version/s: (was: 2.7.2) 2.8.0 > Ambari metrics service check failed during UI deploy > > > Key: AMBARI-24637 > URL: https://issues.apache.org/jira/browse/AMBARI-24637 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Race conditions in UUID computation helper caused issues in writes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Affects Version/s: (was: 3.0.0) 2.7.1 > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-23466: -- Assignee: Aravindan Vijayan > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Affects Version/s: (was: 2.7.1) > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 4.x
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23466: --- Fix Version/s: (was: 3.0.0) > Upgrade AMS Grafana version to 4.x > -- > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24653) YARN Timeline server v2 related system tests fail.
Aravindan Vijayan created AMBARI-24653: -- Summary: YARN Timeline server v2 related system tests fail. Key: AMBARI-24653 URL: https://issues.apache.org/jira/browse/AMBARI-24653 Project: Ambari Issue Type: Bug Affects Versions: 2.7.2 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24637) Ambari metrics service check failed during UI deploy
Aravindan Vijayan created AMBARI-24637: -- Summary: Ambari metrics service check failed during UI deploy Key: AMBARI-24637 URL: https://issues.apache.org/jira/browse/AMBARI-24637 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.1 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.2 Race conditions in UUID computation helper caused issues in writes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24568) Runtime issue : Post trunk merge, POST HOST API call fails while calling checkAndAddExternalCollectorHosts() fn.
[
https://issues.apache.org/jira/browse/AMBARI-24568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned AMBARI-24568:
--
Assignee: Aravindan Vijayan
> Runtime issue : Post trunk merge, POST HOST API call fails while calling
> checkAndAddExternalCollectorHosts() fn.
>
>
> Key: AMBARI-24568
> URL: https://issues.apache.org/jira/browse/AMBARI-24568
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Swapan Shridhar
>Assignee: Aravindan Vijayan
>Priority: Major
> Fix For: 3.0.0
>
>
> *Ambari branch :* branch-feature-AMBARI-14714
> HOST POST API CALL that fails while deploying cluster:
> {code:title=POST http://IP:8080/api/v1/clusters/c1/hosts}
> Body :
> {"RequestInfo":\{"query":"Hosts/host_name.in(host-1.openstacklocal)"},"Body":\{"host_components":[{"HostRoles":{"component_name":"ZOOKEEPER_SERVER","service_name":"ZOOKEEPER","service_group_name":"HDPCORE"}}]}}:
> {code}
>
> Exception Trace:
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.ConfigurationResourceProvider.getResourcesAuthorized(ConfigurationResourceProvider.java:258)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.getResources(AbstractAuthorizedResourceProvider.java:277)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getConfigProperties(AbstractProviderModule.java:974)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getDesiredConfigMap(AbstractProviderModule.java:999)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getDesiredConfigMap(AbstractProviderModule.java:990)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.checkAndAddExternalCollectorHosts(AbstractProviderModule.java:386)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.initProviderMaps(AbstractProviderModule.java:919)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.checkInit(AbstractProviderModule.java:857)
> at
> org.apache.ambari.server.controller.internal.AbstractProviderModule.getMetricsServiceType(AbstractProviderModule.java:348)
> at
> org.apache.ambari.server.controller.metrics.MetricsPropertyProviderProxy.checkPropertyIds(MetricsPropertyProviderProxy.java:97)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.providesRequestProperties(ClusterControllerImpl.java:554)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.populateResources(ClusterControllerImpl.java:152)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:424)
> 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.handlers.QueryCreateHandler.handleRequest(QueryCreateHandler.java:58)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:162)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.HostService.createHosts(HostService.java:172)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
>
[jira] [Resolved] (AMBARI-24557) Remove legacy storm sink module from ambari-metrics.
[ https://issues.apache.org/jira/browse/AMBARI-24557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24557. Resolution: Fixed PR merged to trunk. > Remove legacy storm sink module from ambari-metrics. > > > Key: AMBARI-24557 > URL: https://issues.apache.org/jira/browse/AMBARI-24557 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24557) Remove legacy storm sink module from ambari-metrics.
Aravindan Vijayan created AMBARI-24557: -- Summary: Remove legacy storm sink module from ambari-metrics. Key: AMBARI-24557 URL: https://issues.apache.org/jira/browse/AMBARI-24557 Project: Ambari Issue Type: Task Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24556) Aggregation across clusters are not being done in AMS for even when multiple cluster support is enabled.
Aravindan Vijayan created AMBARI-24556: -- Summary: Aggregation across clusters are not being done in AMS for even when multiple cluster support is enabled. Key: AMBARI-24556 URL: https://issues.apache.org/jira/browse/AMBARI-24556 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.1 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24503) LLAP application on Yarn fails with CNF exception on sysprepped cluster.
[
https://issues.apache.org/jira/browse/AMBARI-24503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24503.
Resolution: Fixed
PR merged to trunk and branch-2.7
> LLAP application on Yarn fails with CNF exception on sysprepped cluster.
>
>
> Key: AMBARI-24503
> URL: https://issues.apache.org/jira/browse/AMBARI-24503
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> LLAP Yarn application failed to start due to missing azure class.
> {code}
> 18/08/15 20:08:28 INFO service.ServiceMaster: Kind: YARN_AM_RM_TOKEN,
> Service: , Ident: (appAttemptId { application_id { id: 4 cluster_timestamp:
> 1534200616336 } attemptId: 3 } keyId: 1688030095)
> 18/08/15 20:08:28 INFO service.AbstractService: Service Service Master failed
> in state INITED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> 18/08/15 20:08:28 INFO service.ServiceMaster: Stopping app master
> 18/08/15 20:08:28 ERROR service.ServiceMaster: Error starting service master
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24494) Ambari API does not return AssignmentManager HBase point in time metrics through API.
[ https://issues.apache.org/jira/browse/AMBARI-24494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24494. Resolution: Fixed PR merged to trunk and branch-2.7 > Ambari API does not return AssignmentManager HBase point in time metrics > through API. > -- > > Key: AMBARI-24494 > URL: https://issues.apache.org/jira/browse/AMBARI-24494 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-24503) LLAP application on Yarn fails with CNF exception on sysprepped cluster.
[
https://issues.apache.org/jira/browse/AMBARI-24503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reopened AMBARI-24503:
> LLAP application on Yarn fails with CNF exception on sysprepped cluster.
>
>
> Key: AMBARI-24503
> URL: https://issues.apache.org/jira/browse/AMBARI-24503
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> LLAP Yarn application failed to start due to missing azure class.
> {code}
> 18/08/15 20:08:28 INFO service.ServiceMaster: Kind: YARN_AM_RM_TOKEN,
> Service: , Ident: (appAttemptId { application_id { id: 4 cluster_timestamp:
> 1534200616336 } attemptId: 3 } keyId: 1688030095)
> 18/08/15 20:08:28 INFO service.AbstractService: Service Service Master failed
> in state INITED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> 18/08/15 20:08:28 INFO service.ServiceMaster: Stopping app master
> 18/08/15 20:08:28 ERROR service.ServiceMaster: Error starting service master
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24485) HDP-3.0 Hive Interactive server fails to start on a sys-prepped cluster
[ https://issues.apache.org/jira/browse/AMBARI-24485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24485. Resolution: Fixed PR merged to trunk and branch-2.7 > HDP-3.0 Hive Interactive server fails to start on a sys-prepped cluster > --- > > Key: AMBARI-24485 > URL: https://issues.apache.org/jira/browse/AMBARI-24485 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > > On sysprepped clusters, Ambari needs to create the > /user/hive/.yarn/package/LLAP in the sysprep step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24503) LLAP application on Yarn fails with CNF exception on sysprepped cluster.
[
https://issues.apache.org/jira/browse/AMBARI-24503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24503:
---
Summary: LLAP application on Yarn fails with CNF exception on sysprepped
cluster. (was: LLAP application on Yarn fails with CNF exception.)
> LLAP application on Yarn fails with CNF exception on sysprepped cluster.
>
>
> Key: AMBARI-24503
> URL: https://issues.apache.org/jira/browse/AMBARI-24503
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Major
> Fix For: 2.7.1
>
>
> LLAP Yarn application failed to start due to missing azure class.
> {code}
> 18/08/15 20:08:28 INFO service.ServiceMaster: Kind: YARN_AM_RM_TOKEN,
> Service: , Ident: (appAttemptId { application_id { id: 4 cluster_timestamp:
> 1534200616336 } attemptId: 3 } keyId: 1688030095)
> 18/08/15 20:08:28 INFO service.AbstractService: Service Service Master failed
> in state INITED
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> 18/08/15 20:08:28 INFO service.ServiceMaster: Stopping app master
> 18/08/15 20:08:28 ERROR service.ServiceMaster: Error starting service master
> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
> at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
> at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
> at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
> at
> org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
> at
> org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
> at
> org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
> at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
> Caused by: java.lang.ClassNotFoundException: Class
> org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24503) LLAP application on Yarn fails with CNF exception.
Aravindan Vijayan created AMBARI-24503:
--
Summary: LLAP application on Yarn fails with CNF exception.
Key: AMBARI-24503
URL: https://issues.apache.org/jira/browse/AMBARI-24503
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.1
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.1
LLAP Yarn application failed to start due to missing azure class.
{code}
18/08/15 20:08:28 INFO service.ServiceMaster: Kind: YARN_AM_RM_TOKEN, Service:
, Ident: (appAttemptId { application_id { id: 4 cluster_timestamp:
1534200616336 } attemptId: 3 } keyId: 1688030095)
18/08/15 20:08:28 INFO service.AbstractService: Service Service Master failed
in state INITED
java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
at
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
at
org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
at
org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
at
org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
at
org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
at
org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
Caused by: java.lang.ClassNotFoundException: Class
org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
at
org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
at
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
... 12 more
18/08/15 20:08:28 INFO service.ServiceMaster: Stopping app master
18/08/15 20:08:28 ERROR service.ServiceMaster: Error starting service master
java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2596)
at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3320)
at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3352)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124)
at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:226)
at
org.apache.hadoop.yarn.service.utils.CoreFileSystem.(CoreFileSystem.java:73)
at
org.apache.hadoop.yarn.service.utils.SliderFileSystem.(SliderFileSystem.java:41)
at
org.apache.hadoop.yarn.service.ServiceMaster.serviceInit(ServiceMaster.java:100)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
at org.apache.hadoop.yarn.service.ServiceMaster.main(ServiceMaster.java:338)
Caused by: java.lang.ClassNotFoundException: Class
org.apache.hadoop.fs.azure.NativeAzureFileSystem not found
at org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2500)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2594)
... 12 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24400) Tests in ambari-metrics fail with java.lang.NoSuchFieldError: mapper
[
https://issues.apache.org/jira/browse/AMBARI-24400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583349#comment-16583349
]
Aravindan Vijayan commented on AMBARI-24400:
[~alishap] I am not able to reproduce this locally or in github test runs. Can
you tell me if there is something specific to your environment?
> Tests in ambari-metrics fail with java.lang.NoSuchFieldError: mapper
>
>
> Key: AMBARI-24400
> URL: https://issues.apache.org/jira/browse/AMBARI-24400
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Alisha Prabhu
>Priority: Major
> Labels: ppc64le, x86_64
> Attachments: AMBARI-24400.patch
>
>
> Commands used at ./ambari/ambari-metrics/ :
> mvn -Dtest=AggregatedMetricsPublisherTest -DfailIfNoTests=false test
> mvn -Dtest=RawMetricsPublisherTest -DfailIfNoTests=false test
> Error :
> {code:java}
> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.641 sec <<<
> FAILURE! - in
> org.apache.hadoop.metrics2.sink.timeline.AggregatedMetricsPublisherTest
> testProcessMetrics(org.apache.hadoop.metrics2.sink.timeline.AggregatedMetricsPublisherTest)
> Time elapsed: 0.043 sec <<< ERROR!
> java.lang.NoSuchFieldError: mapper
> at
> org.apache.hadoop.metrics2.sink.timeline.AggregatedMetricsPublisherTest.testProcessMetrics(AggregatedMetricsPublisherTest.java:65)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24494) Ambari API does not return AssignmentManager HBase point in time metrics through API.
Aravindan Vijayan created AMBARI-24494: -- Summary: Ambari API does not return AssignmentManager HBase point in time metrics through API. Key: AMBARI-24494 URL: https://issues.apache.org/jira/browse/AMBARI-24494 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24485) HDP-3.0 Hive Interactive server fails to start on a sys-prepped cluster
[ https://issues.apache.org/jira/browse/AMBARI-24485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24485: --- Summary: HDP-3.0 Hive Interactive server fails to start on a sys-prepped cluster (was: HDP-3.0 Hive Interactive server fails to start) > HDP-3.0 Hive Interactive server fails to start on a sys-prepped cluster > --- > > Key: AMBARI-24485 > URL: https://issues.apache.org/jira/browse/AMBARI-24485 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 10m > Remaining Estimate: 0h > > On sysprepped clusters, Ambari needs to create the > /user/hive/.yarn/package/LLAP in the sysprep step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24485) HDP-3.0 Hive Interactive server fails to start
Aravindan Vijayan created AMBARI-24485: -- Summary: HDP-3.0 Hive Interactive server fails to start Key: AMBARI-24485 URL: https://issues.apache.org/jira/browse/AMBARI-24485 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.1 On sysprepped clusters, Ambari needs to create the /user/hive/.yarn/package/LLAP in the sysprep step. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24471) URL rewrite rules in gateway cannot be applied when the response content from ambari server is compressed
[
https://issues.apache.org/jira/browse/AMBARI-24471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24471.
Resolution: Fixed
PR merged to trunk and branch-2.7
> URL rewrite rules in gateway cannot be applied when the response content from
> ambari server is compressed
> -
>
> Key: AMBARI-24471
> URL: https://issues.apache.org/jira/browse/AMBARI-24471
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We we try to access the cluster through gateway using the cluster public
> endpoint, we receive 500 internal server error with following error message.
> Outbound rewrite rules cannot be applied when the content of the HTTP
> response is encoded ("gzip").
> We need a way to disable the response content compression on server side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24470) HDP 3.0 Livy2-Server fails to start
[
https://issues.apache.org/jira/browse/AMBARI-24470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24470.
Resolution: Fixed
PR merged to branch-2.7
> HDP 3.0 Livy2-Server fails to start
> ---
>
> Key: AMBARI-24470
> URL: https://issues.apache.org/jira/browse/AMBARI-24470
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 148, in
> LivyServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 62, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 52, in configure
> setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
> line 52, in setup_livy
> params.HdfsResource(None, action="execute")
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 663, in action_execute
> self.get_hdfs_resource_executor().action_execute(self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 159, in action_execute
> logoutput=logoutput,
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
> --config /usr/hdp/3.0.1.0-65/hadoop/conf jar
> /var/lib/ambari-agent/lib/fast-hdfs-resource.jar
> /var/lib/ambari-agent/tmp/hdfs_resources_1533930112.17.json' returned 1.
> Initializing filesystem uri: hdfs://mycluster
> Creating: Resource [source=null,
> target=zk0-host:2181,zk1-host:2181,zk2-host:2181, type=directory,
> action=create, owner=livy, group=null, mode=700, recursiveChown=false,
> recursiveChmod=false, changePermissionforParents=false, manageIfExists=true]
> in hdfs://mycluster
> Exception occurred, Reason: java.net.URISyntaxException: Relative path in
> absolute URI: zk0-host:2181,zk1-host:2181,zk2-host:2181
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: zk0-host:2181,zk1-host:2181,zk2-host:2181
> at org.apache.hadoop.fs.Path.initialize(Path.java:259)
> at org.apache.hadoop.fs.Path.(Path.java:217)
> at
> org.apache.ambari.fast_hdfs_resource.Resource.checkResourceParameters(Resource.java:193)
> at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
[jira] [Created] (AMBARI-24471) URL rewrite rules in gateway cannot be applied when the response content from ambari server is compressed
Aravindan Vijayan created AMBARI-24471:
--
Summary: URL rewrite rules in gateway cannot be applied when the
response content from ambari server is compressed
Key: AMBARI-24471
URL: https://issues.apache.org/jira/browse/AMBARI-24471
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.1
We we try to access the cluster through gateway using the cluster public
endpoint, we receive 500 internal server error with following error message.
Outbound rewrite rules cannot be applied when the content of the HTTP response
is encoded ("gzip").
We need a way to disable the response content compression on server side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24470) HDP 3.0 Livy2-Server fails to start
Aravindan Vijayan created AMBARI-24470:
--
Summary: HDP 3.0 Livy2-Server fails to start
Key: AMBARI-24470
URL: https://issues.apache.org/jira/browse/AMBARI-24470
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.1
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 148, in
LivyServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 62, in start
self.configure(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
line 52, in configure
setup_livy(env, 'server', upgrade_type=upgrade_type, action = 'config')
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
line 52, in setup_livy
params.HdfsResource(None, action="execute")
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 663, in action_execute
self.get_hdfs_resource_executor().action_execute(self)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
line 159, in action_execute
logoutput=logoutput,
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 314,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
--config /usr/hdp/3.0.1.0-65/hadoop/conf jar
/var/lib/ambari-agent/lib/fast-hdfs-resource.jar
/var/lib/ambari-agent/tmp/hdfs_resources_1533930112.17.json' returned 1.
Initializing filesystem uri: hdfs://mycluster
Creating: Resource [source=null,
target=zk0-host:2181,zk1-host:2181,zk2-host:2181, type=directory,
action=create, owner=livy, group=null, mode=700, recursiveChown=false,
recursiveChmod=false, changePermissionforParents=false, manageIfExists=true] in
hdfs://mycluster
Exception occurred, Reason: java.net.URISyntaxException: Relative path in
absolute URI: zk0-host:2181,zk1-host:2181,zk2-host:2181
java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path
in absolute URI: zk0-host:2181,zk1-host:2181,zk2-host:2181
at org.apache.hadoop.fs.Path.initialize(Path.java:259)
at org.apache.hadoop.fs.Path.(Path.java:217)
at
org.apache.ambari.fast_hdfs_resource.Resource.checkResourceParameters(Resource.java:193)
at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:318)
at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: java.net.URISyntaxException: Relative path in absolute URI:
zk0-host:2181,zk1-host:2181,zk2-host:2181
at java.net.URI.checkPath(URI.java:1823)
at java.net.URI.(URI.java:745)
at org.apache.hadoop.fs.Path.initialize(Path.java:256)
... 9 more
Traceback (most recent call last):
{noformat}
--
This
[jira] [Resolved] (AMBARI-24385) Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No such file or directory)
[
https://issues.apache.org/jira/browse/AMBARI-24385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24385.
Resolution: Fixed
> Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No
> such file or directory)
> ---
>
> Key: AMBARI-24385
> URL: https://issues.apache.org/jira/browse/AMBARI-24385
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: unit-test
> Fix For: 2.7.1
>
>
> Many branch-2.7 test runs from Github are failing with
> {noformat}
> 2018-07-30 21:33:23,838 ERROR [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:readMetricWhitelistFromFile(132)) - Unable to
> parse metric file
> java.io.FileNotFoundException:
> /home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder%402/ambari-metrics/ambari-metrics-timelineservice/target/test-classes/test_data/metric_blacklist.dat
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.readMetricWhitelistFromFile(TimelineMetricsFilter.java:117)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.initializeMetricFilter(TimelineMetricsFilter.java:85)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilterTest.testMetricBlacklisting(TimelineMetricsFilterTest.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:344)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:269)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:184)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> 2018-07-30 21:33:23,842 INFO [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:initializeMetricFilter(86)) - Blacklisting 0
> metrics
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24385) Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No such file or directory)
[
https://issues.apache.org/jira/browse/AMBARI-24385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576652#comment-16576652
]
Aravindan Vijayan commented on AMBARI-24385:
This is a duplicate of AMBARI-23811.cc [~adoroszlai]
> Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No
> such file or directory)
> ---
>
> Key: AMBARI-24385
> URL: https://issues.apache.org/jira/browse/AMBARI-24385
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: unit-test
> Fix For: trunk
>
>
> Many branch-2.7 test runs from Github are failing with
> {noformat}
> 2018-07-30 21:33:23,838 ERROR [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:readMetricWhitelistFromFile(132)) - Unable to
> parse metric file
> java.io.FileNotFoundException:
> /home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder%402/ambari-metrics/ambari-metrics-timelineservice/target/test-classes/test_data/metric_blacklist.dat
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.readMetricWhitelistFromFile(TimelineMetricsFilter.java:117)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.initializeMetricFilter(TimelineMetricsFilter.java:85)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilterTest.testMetricBlacklisting(TimelineMetricsFilterTest.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:344)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:269)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:184)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> 2018-07-30 21:33:23,842 INFO [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:initializeMetricFilter(86)) - Blacklisting 0
> metrics
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24385) Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No such file or directory)
[
https://issues.apache.org/jira/browse/AMBARI-24385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24385:
---
Fix Version/s: (was: 2.7.1)
trunk
> Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No
> such file or directory)
> ---
>
> Key: AMBARI-24385
> URL: https://issues.apache.org/jira/browse/AMBARI-24385
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: unit-test
> Fix For: trunk
>
>
> Many branch-2.7 test runs from Github are failing with
> {noformat}
> 2018-07-30 21:33:23,838 ERROR [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:readMetricWhitelistFromFile(132)) - Unable to
> parse metric file
> java.io.FileNotFoundException:
> /home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder%402/ambari-metrics/ambari-metrics-timelineservice/target/test-classes/test_data/metric_blacklist.dat
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.readMetricWhitelistFromFile(TimelineMetricsFilter.java:117)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.initializeMetricFilter(TimelineMetricsFilter.java:85)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilterTest.testMetricBlacklisting(TimelineMetricsFilterTest.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:344)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:269)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:184)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> 2018-07-30 21:33:23,842 INFO [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:initializeMetricFilter(86)) - Blacklisting 0
> metrics
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24385) Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No such file or directory)
[
https://issues.apache.org/jira/browse/AMBARI-24385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned AMBARI-24385:
--
Assignee: Doroszlai, Attila (was: Aravindan Vijayan)
> Unit test error in ambari-metrics-timelineservice: metric_blacklist.dat (No
> such file or directory)
> ---
>
> Key: AMBARI-24385
> URL: https://issues.apache.org/jira/browse/AMBARI-24385
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: unit-test
> Fix For: 2.7.1
>
>
> Many branch-2.7 test runs from Github are failing with
> {noformat}
> 2018-07-30 21:33:23,838 ERROR [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:readMetricWhitelistFromFile(132)) - Unable to
> parse metric file
> java.io.FileNotFoundException:
> /home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder%402/ambari-metrics/ambari-metrics-timelineservice/target/test-classes/test_data/metric_blacklist.dat
> (No such file or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.readMetricWhitelistFromFile(TimelineMetricsFilter.java:117)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilter.initializeMetricFilter(TimelineMetricsFilter.java:85)
> at
> org.apache.ambari.metrics.core.timeline.TimelineMetricsFilterTest.testMetricBlacklisting(TimelineMetricsFilterTest.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:344)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:269)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:240)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:184)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:286)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:240)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> 2018-07-30 21:33:23,842 INFO [main] timeline.TimelineMetricsFilter
> (TimelineMetricsFilter.java:initializeMetricFilter(86)) - Blacklisting 0
> metrics
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
[ https://issues.apache.org/jira/browse/AMBARI-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24367. Resolution: Fixed > Fix integration test regressions in AMS collector due to scale changes. > --- > > Key: AMBARI-24367 > URL: https://issues.apache.org/jira/browse/AMBARI-24367 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > * Extend HBaseTestingUtility to spin up standalone HBase cluster for > integraton testing instead of distributed mode instance with HDFS. > * Fix integration test regressions from 2.7.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23112) Some libraries are not relocated in ambari-metrics-common jar
[ https://issues.apache.org/jira/browse/AMBARI-23112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-23112. Resolution: Fixed Pushed to trunk,. > Some libraries are not relocated in ambari-metrics-common jar > - > > Key: AMBARI-23112 > URL: https://issues.apache.org/jira/browse/AMBARI-23112 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: AMBARI-23112.patch > > Time Spent: 4h 10m > Remaining Estimate: 0h > > Some libraries are not relocated in ambari-metrics-common jar, that means > some classes are exists in the jar, and those can be on the classpath as well > (with different versions), which can cause issues. > Libaries which are not shaded: (not sure that conventional, but i think we > should not include those dependencies in the uberjar if those are not shaded): > * commons-lang > * commons-math3 > * commons-codec > * jackson-xc > * jackson-core-asl / jackson-mapper-asl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24403:
---
Fix Version/s: 2.7.1
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24403:
---
Fix Version/s: trunk
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24398) HDP 3.0 Hive meta store fails to start on a sysprepped Azure cluster.
[ https://issues.apache.org/jira/browse/AMBARI-24398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24398. Resolution: Fixed > HDP 3.0 Hive meta store fails to start on a sysprepped Azure cluster. > -- > > Key: AMBARI-24398 > URL: https://issues.apache.org/jira/browse/AMBARI-24398 > Project: Ambari > Issue Type: Bug >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24398) HDP 3.0 Hive meta store fails to start on a sysprepped Azure cluster.
Aravindan Vijayan created AMBARI-24398: -- Summary: HDP 3.0 Hive meta store fails to start on a sysprepped Azure cluster. Key: AMBARI-24398 URL: https://issues.apache.org/jira/browse/AMBARI-24398 Project: Ambari Issue Type: Bug Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
[ https://issues.apache.org/jira/browse/AMBARI-24395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24395. Resolution: Fixed Pushed to both the branches. > Upgrade AMS hadoop dependency build number to the latest. > - > > Key: AMBARI-24395 > URL: https://issues.apache.org/jira/browse/AMBARI-24395 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24395) Upgrade AMS hadoop dependency build number to the latest.
Aravindan Vijayan created AMBARI-24395: -- Summary: Upgrade AMS hadoop dependency build number to the latest. Key: AMBARI-24395 URL: https://issues.apache.org/jira/browse/AMBARI-24395 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.1 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: trunk, 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
[ https://issues.apache.org/jira/browse/AMBARI-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24367: --- Description: * Extend HBaseTestingUtility to spin up standalone HBase cluster for integraton testing instead of distributed mode instance with HDFS. * Fix integration test regressions from 2.7.0. was: * Extend HBaseTestingUtility to spin up standalone HBase cluster for integraton testing instead of distributed mode instance with HDFS. * Fix integration test regressions from 2.7.0. * Enable integration tests by default. > Fix integration test regressions in AMS collector due to scale changes. > --- > > Key: AMBARI-24367 > URL: https://issues.apache.org/jira/browse/AMBARI-24367 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.7.1 > > > * Extend HBaseTestingUtility to spin up standalone HBase cluster for > integraton testing instead of distributed mode instance with HDFS. > * Fix integration test regressions from 2.7.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24367) Fix integration test regressions in AMS collector due to scale changes.
Aravindan Vijayan created AMBARI-24367: -- Summary: Fix integration test regressions in AMS collector due to scale changes. Key: AMBARI-24367 URL: https://issues.apache.org/jira/browse/AMBARI-24367 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.1 * Extend HBaseTestingUtility to spin up standalone HBase cluster for integraton testing instead of distributed mode instance with HDFS. * Fix integration test regressions from 2.7.0. * Enable integration tests by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24290) Fix issues in AMS multiple cluster support.
[ https://issues.apache.org/jira/browse/AMBARI-24290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24290. Resolution: Fixed > Fix issues in AMS multiple cluster support. > --- > > Key: AMBARI-24290 > URL: https://issues.apache.org/jira/browse/AMBARI-24290 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24340) AMS Migration tools should auto-detect whitelist file
[
https://issues.apache.org/jira/browse/AMBARI-24340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24340.
Resolution: Fixed
> AMS Migration tools should auto-detect whitelist file
> -
>
> Key: AMBARI-24340
> URL: https://issues.apache.org/jira/browse/AMBARI-24340
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
> upgrade, running the following command with no arguments fails:
> {noformat}
> # /usr/sbin/ambari-metrics-collector upgrade_start
> {noformat}
> This is the error in the logs:
> {noformat}
> 2018-07-12 13:47:05,373 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 9504, metadata objects from store.
> 2018-07-12 13:47:05,517 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 5 host objects from store.
> 2018-07-12 13:47:05,528 INFO
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Looking for whitelisted metric names...
> 2018-07-12 13:47:05,529 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> No whitelisted metrics specified. Exiting...
> 2018-07-12 13:47:05,530 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Exception during system setup, exiting...
> java.lang.Exception: List of whitelisted metrics must be provided
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24340) AMS Migration tools should auto-detect whitelist file
[
https://issues.apache.org/jira/browse/AMBARI-24340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24340:
---
Summary: AMS Migration tools should auto-detect whitelist file (was: AMS
Migration tools should auto-detect whitelisting)
> AMS Migration tools should auto-detect whitelist file
> -
>
> Key: AMBARI-24340
> URL: https://issues.apache.org/jira/browse/AMBARI-24340
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.7.1
>
>
> In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
> upgrade, running the following command with no arguments fails:
> {noformat}
> # /usr/sbin/ambari-metrics-collector upgrade_start
> {noformat}
> This is the error in the logs:
> {noformat}
> 2018-07-12 13:47:05,373 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 9504, metadata objects from store.
> 2018-07-12 13:47:05,517 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 5 host objects from store.
> 2018-07-12 13:47:05,528 INFO
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Looking for whitelisted metric names...
> 2018-07-12 13:47:05,529 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> No whitelisted metrics specified. Exiting...
> 2018-07-12 13:47:05,530 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Exception during system setup, exiting...
> java.lang.Exception: List of whitelisted metrics must be provided
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24340) AMS Migration tools should auto-detect whitelisting
Aravindan Vijayan created AMBARI-24340:
--
Summary: AMS Migration tools should auto-detect whitelisting
Key: AMBARI-24340
URL: https://issues.apache.org/jira/browse/AMBARI-24340
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.1
In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
upgrade, running the following command with no arguments fails:
{noformat}
# /usr/sbin/ambari-metrics-collector upgrade_start
{noformat}
This is the error in the logs:
{noformat}
2018-07-12 13:47:05,373 INFO
org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
Retrieved 9504, metadata objects from store.
2018-07-12 13:47:05,517 INFO
org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
Retrieved 5 host objects from store.
2018-07-12 13:47:05,528 INFO
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
Looking for whitelisted metric names...
2018-07-12 13:47:05,529 ERROR
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
No whitelisted metrics specified. Exiting...
2018-07-12 13:47:05,530 ERROR
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
Exception during system setup, exiting...
java.lang.Exception: List of whitelisted metrics must be provided
at
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
at
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24290) Fix issues in AMS multiple cluster support.
[ https://issues.apache.org/jira/browse/AMBARI-24290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24290: --- Affects Version/s: 2.7.0 > Fix issues in AMS multiple cluster support. > --- > > Key: AMBARI-24290 > URL: https://issues.apache.org/jira/browse/AMBARI-24290 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24290) Fix issues in AMS multiple cluster support.
Aravindan Vijayan created AMBARI-24290: -- Summary: Fix issues in AMS multiple cluster support. Key: AMBARI-24290 URL: https://issues.apache.org/jira/browse/AMBARI-24290 Project: Ambari Issue Type: Bug Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24180) Ambari metrics Service Check fails.
[ https://issues.apache.org/jira/browse/AMBARI-24180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24180. Resolution: Fixed > Ambari metrics Service Check fails. > --- > > Key: AMBARI-24180 > URL: https://issues.apache.org/jira/browse/AMBARI-24180 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24180) Ambari metrics Service Check fails.
[ https://issues.apache.org/jira/browse/AMBARI-24180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-24180: --- Summary: Ambari metrics Service Check fails. (was: Ambari metrics Service Check fails post EU . Error - 401 Authentication required in response) > Ambari metrics Service Check fails. > --- > > Key: AMBARI-24180 > URL: https://issues.apache.org/jira/browse/AMBARI-24180 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24179) Ambari Metrics Service check fails after deleting a host
[
https://issues.apache.org/jira/browse/AMBARI-24179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned AMBARI-24179:
--
Assignee: Aravindan Vijayan (was: Dmytro Sen)
> Ambari Metrics Service check fails after deleting a host
>
>
> Key: AMBARI-24179
> URL: https://issues.apache.org/jira/browse/AMBARI-24179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.7.0
>
>
> ambari metrics service check failed immediately after deleting a host:
> {code:java}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
> line 304, in
> AMSServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
> line 184, in service_check
> raise Fail("All metrics collectors are unavailable.")
> resource_management.core.exceptions.Fail: All metrics collectors are
> unavailable.
> stdout:
> 2018-06-25 04:42:25,088 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-1541/hadoop/conf
> 2018-06-25 04:42:25,095 - checked_call['hostid'] {}
> 2018-06-25 04:42:25,100 - checked_call returned (0, '1bac1213')
> 2018-06-25 04:42:25,102 - Ambari Metrics service check was started.
> 2018-06-25 04:42:25,121 - Generated metrics for host
> ctr-e138-1518143905142-378410-01-09.hwx.site :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "ctr-e138-1518143905142-378410-01-12.hwx.site",
> "starttime": 1529901745000,
> "metrics": {
> "1529901745000": 0.602995821312,
> "1529901746000": 1529901745000
> }
> }
> ]
> }
> 2018-06-25 04:42:25,122 - Connecting (POST) to
> ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics/
> 2018-06-25 04:42:25,132 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site: 200 OK
> 2018-06-25 04:42:25,133 - Http data:
> 2018-06-25 04:42:25,133 - Metrics were saved.
> 2018-06-25 04:42:25,133 - Connecting (GET) to
> ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric=ctr-e138-1518143905142-378410-01-12.hwx.site=seconds=false=1529901685000=amssmoketestfake=1529901806000
> 2018-06-25 04:42:25,138 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:25,138 - Http data: {"metrics":[]}
> 2018-06-25 04:42:25,138 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:25,139 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:35,154 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:35,154 - Http data: {"metrics":[]}
> 2018-06-25 04:42:35,154 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:35,155 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:45,170 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:45,170 - Http data: {"metrics":[]}
> 2018-06-25 04:42:45,171 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:45,171 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:55,186 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:55,186 - Http data: {"metrics":[]}
> 2018-06-25 04:42:55,187 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:55,187 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:43:05,204 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:43:05,204 - Http data: {"metrics":[]}
> 2018-06-25 04:43:05,205 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:43:05,205 - Ambari Metrics service check failed on collector
> host ctr-e138-1518143905142-378410-01-09.hwx.site. Reason : Values
> 0.602995821312 and 1529901745000 were not found in the response.
> 2018-06-25 04:43:05,207 - Exception while running function '>' for
[jira] [Resolved] (AMBARI-24179) Ambari Metrics Service check fails after deleting a host
[
https://issues.apache.org/jira/browse/AMBARI-24179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan resolved AMBARI-24179.
Resolution: Duplicate
> Ambari Metrics Service check fails after deleting a host
>
>
> Key: AMBARI-24179
> URL: https://issues.apache.org/jira/browse/AMBARI-24179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.7.0
>
>
> ambari metrics service check failed immediately after deleting a host:
> {code:java}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
> line 304, in
> AMSServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
> line 184, in service_check
> raise Fail("All metrics collectors are unavailable.")
> resource_management.core.exceptions.Fail: All metrics collectors are
> unavailable.
> stdout:
> 2018-06-25 04:42:25,088 - Using hadoop conf dir:
> /usr/hdp/3.0.0.0-1541/hadoop/conf
> 2018-06-25 04:42:25,095 - checked_call['hostid'] {}
> 2018-06-25 04:42:25,100 - checked_call returned (0, '1bac1213')
> 2018-06-25 04:42:25,102 - Ambari Metrics service check was started.
> 2018-06-25 04:42:25,121 - Generated metrics for host
> ctr-e138-1518143905142-378410-01-09.hwx.site :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "ctr-e138-1518143905142-378410-01-12.hwx.site",
> "starttime": 1529901745000,
> "metrics": {
> "1529901745000": 0.602995821312,
> "1529901746000": 1529901745000
> }
> }
> ]
> }
> 2018-06-25 04:42:25,122 - Connecting (POST) to
> ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics/
> 2018-06-25 04:42:25,132 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site: 200 OK
> 2018-06-25 04:42:25,133 - Http data:
> 2018-06-25 04:42:25,133 - Metrics were saved.
> 2018-06-25 04:42:25,133 - Connecting (GET) to
> ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric=ctr-e138-1518143905142-378410-01-12.hwx.site=seconds=false=1529901685000=amssmoketestfake=1529901806000
> 2018-06-25 04:42:25,138 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:25,138 - Http data: {"metrics":[]}
> 2018-06-25 04:42:25,138 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:25,139 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:35,154 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:35,154 - Http data: {"metrics":[]}
> 2018-06-25 04:42:35,154 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:35,155 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:45,170 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:45,170 - Http data: {"metrics":[]}
> 2018-06-25 04:42:45,171 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:45,171 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:42:55,186 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:42:55,186 - Http data: {"metrics":[]}
> 2018-06-25 04:42:55,187 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:42:55,187 - Values weren't stored yet. Retrying in 10 seconds.
> 2018-06-25 04:43:05,204 - Http response for host
> ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
> 2018-06-25 04:43:05,204 - Http data: {"metrics":[]}
> 2018-06-25 04:43:05,205 - Metrics were retrieved from host
> ctr-e138-1518143905142-378410-01-09.hwx.site
> 2018-06-25 04:43:05,205 - Ambari Metrics service check failed on collector
> host ctr-e138-1518143905142-378410-01-09.hwx.site. Reason : Values
> 0.602995821312 and 1529901745000 were not found in the response.
> 2018-06-25 04:43:05,207 - Exception while running function '>' for
>
[jira] [Created] (AMBARI-24180) Ambari metrics Service Check fails post EU . Error - 401 Authentication required in response
Aravindan Vijayan created AMBARI-24180: -- Summary: Ambari metrics Service Check fails post EU . Error - 401 Authentication required in response Key: AMBARI-24180 URL: https://issues.apache.org/jira/browse/AMBARI-24180 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24171) Fix issues in AMS aggregation and writes.
[ https://issues.apache.org/jira/browse/AMBARI-24171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24171. Resolution: Fixed PR merged to trunk. > Fix issues in AMS aggregation and writes. > - > > Key: AMBARI-24171 > URL: https://issues.apache.org/jira/browse/AMBARI-24171 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > * AMS aggregation does not work when metrics have instanceId defined > * Fix bug in distributed 5-min host aggregator. > * Fix issues where AMS discards whole set of metrics even when 1 of them has > NaN values. > * Fix issues in precision calculation whereby the table TTL is also taken > into account. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24171) Fix issues in AMS aggregation and writes.
Aravindan Vijayan created AMBARI-24171: -- Summary: Fix issues in AMS aggregation and writes. Key: AMBARI-24171 URL: https://issues.apache.org/jira/browse/AMBARI-24171 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 * AMS aggregation does not work when metrics have instanceId defined * Fix bug in distributed 5-min host aggregator. * Fix issues where AMS discards whole set of metrics even when 1 of them has NaN values. * Fix issues in precision calculation whereby the table TTL is also taken into account. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
[ https://issues.apache.org/jira/browse/AMBARI-24105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24105. Resolution: Fixed PR merged to trunk. > Jackson library version mismatch casue MR jobs to fail > -- > > Key: AMBARI-24105 > URL: https://issues.apache.org/jira/browse/AMBARI-24105 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
Aravindan Vijayan created AMBARI-24105: -- Summary: Jackson library version mismatch casue MR jobs to fail Key: AMBARI-24105 URL: https://issues.apache.org/jira/browse/AMBARI-24105 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24066) Metrics Collector issues modify HTable descriptor calls every time it restarts.
[ https://issues.apache.org/jira/browse/AMBARI-24066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24066. Resolution: Fixed PR merged to trunk. > Metrics Collector issues modify HTable descriptor calls every time it > restarts. > --- > > Key: AMBARI-24066 > URL: https://issues.apache.org/jira/browse/AMBARI-24066 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > * Fix issues in AMS HBase tables policies initialization. > * Cleanup downsampling code and config. > * Add ability to blacklist metrics through a file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24066) Metrics Collector issues modify HTable descriptor calls every time it restarts.
Aravindan Vijayan created AMBARI-24066: -- Summary: Metrics Collector issues modify HTable descriptor calls every time it restarts. Key: AMBARI-24066 URL: https://issues.apache.org/jira/browse/AMBARI-24066 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 * Fix issues in AMS HBase tables policies initialization. * Cleanup downsampling code and config. * Add ability to blacklist metrics through a file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24041) AMS truncates metric response quietly
[ https://issues.apache.org/jira/browse/AMBARI-24041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24041. Resolution: Fixed > AMS truncates metric response quietly > - > > Key: AMBARI-24041 > URL: https://issues.apache.org/jira/browse/AMBARI-24041 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > In a cluster with around 120 topics available, trying to fetch all the topic > metrics from AMS using the wild card query returns truncated response. > Query with Wildcard > Time interval around 7 days since the beginning of the cluster > http://<>:6188/ws/v1/timeline/metrics?appId=kafka_broker=kafka.server.BrokerTopicMetrics.MessagesInPerSec.topic.%.count._sum=MINUTES=152758760=152819240 > (returns truncated response) > Latest metrics > http://<>:6188/ws/v1/timeline/metrics?appId=kafka_broker=kafka.server.BrokerTopicMetrics.MessagesInPerSec.topic.%.count._sum > (returns valid response) > Metadata Query returns all 120 topic metrics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
