Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
After upgrading to HDP 2.2.4.2 we removed the HDP 2.2.0 directories to make
sure we didn't have any hidden dependencies. When restarting services,
supervisors failed to start with this error:
Fail: Execution of 'ambari-sudo.sh ln s /usr/lib/storm/lib/ambari-metrics
storm-sink*.jar /usr/hdp/current/storm-client/lib/ambari-metrics-storm-
sink.jar' returned 1. ln: creating symbolic link `/usr/hdp/current/storm-
client/lib/ambari-metrics-storm-sink.jar': No such file or directory
2015-05-22 13:33:27,950 - Command: /usr/bin/hdp-select status storm-supervisor
> /tmp/tmpXh9erp
We removed the supervisors and redeployed them, thinking it might be solved by
a fresh deployment. When starting the newly deployed supervisors, we got this
error:
Fail: Execution of 'ambari-sudo.sh ln s /usr/lib/storm/lib/ambari-metrics
storm-sink*.jar /usr/hdp/current/storm-client/lib/ambari-metrics-storm-
sink.jar' returned 1. ln: creating symbolic link `/usr/hdp/current/storm-
client/lib/ambari-metrics-storm-sink.jar': No such file or directory
2015-05-22 13:36:59,979 - Command: /usr/bin/hdp-select status storm-supervisor
> /tmp/tmp4iP41d
When a supervisor is deployed (in the absence of the nimbus, DRPC server or
UI) it does create a /usr/hdp/current/storm-supervisor link that correctly
links to /usr/hdp/<latestVersion>/storm, but it does not create a link for
storm-client. Ambari Metrics tries to create the link for its jar using the
storm-client link.
Ambari Metrics needs to change the path for its link to use the appropriate
component (in this case storm-supervisor).
Attachments
Issue Links
- links to
