[
https://issues.apache.org/jira/browse/AMBARI-14257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-14257:
---------------------------------------
Description:
Problem
Storm metrics do not work after upgrading from versions < 2.1.1 to 2.1.2.
ClassNotFound exception seen in the logs when storm metrics reporter class is
accessed.
Bug
Storm lib directory is usually found in /usr/hdp/current/storm-nimbus/lib. In
the code we try to delete the link from /usr/lib/storm/lib which is not
present. Hence, we never update the symlink in the actual location thus causing
a stale symlink.
Fix
Change the symlink deletion logic to look at the correct location. Also fix a
bug in resource_management.system module where the action='delete' for Links
must call the os.path.lexists rather than os.path.exists to return true for
broken symlinks
was:
Problem
Storm metrics do not work after upgrading from versions < 2.1.1 to 2.1.2.
ClassNotFound exception seen in the logs when storm metrics reporter class is
accessed.
Bug
Storm lib directory is usually found in /usr/hdp/current/storm-nimbus/lib. In
the code we try to delete the link from /usr/lib/storm/lib which is not
present. Hence, we never update the symlink in the actual location thus causing
a stale symlink.
Fix
Change the symlink deletion logic to look at the correct location.
> Storm metrics do not work after upgrading Ambari to 2.1.2.
> ----------------------------------------------------------
>
> Key: AMBARI-14257
> URL: https://issues.apache.org/jira/browse/AMBARI-14257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.1.2
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.2.0
>
>
> Problem
> Storm metrics do not work after upgrading from versions < 2.1.1 to 2.1.2.
> ClassNotFound exception seen in the logs when storm metrics reporter class is
> accessed.
> Bug
> Storm lib directory is usually found in /usr/hdp/current/storm-nimbus/lib. In
> the code we try to delete the link from /usr/lib/storm/lib which is not
> present. Hence, we never update the symlink in the actual location thus
> causing a stale symlink.
> Fix
> Change the symlink deletion logic to look at the correct location. Also fix a
> bug in resource_management.system module where the action='delete' for Links
> must call the os.path.lexists rather than os.path.exists to return true for
> broken symlinks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)