[AMBARI-22716] zeppelin.livy.url is not getting updated after moving livy to a new host

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.1
• Fix Version/s: 2.6.2
• Component/s: ambari-sever

Environment

ambari-server --version 2.6.1.0-137
HDP-2.6.4.0-86

• Assignee: Prabhjyot Singh
• Reporter: Supreeth Sharma
• Created: 02/Jan/18 17:52
• Updated: 26/Apr/18 22:31
• Resolved: 26/Apr/18 22:31

Description

zeppelin.livy.url is not getting updated after moving livy to a new host

Steps to reproduce :
1) Create a cluster with both Spark and Spark2 component
2) Delete livy component from current host.
3) Add the livy component on a new host
4) Restart zeppelin server.
5) Now check the zeppelin interpreter settings. zeppelin.livy.url is still referring to older livy host.
Its not reflecting the new livy server address.

Note 1 : If I restart zeppelin server after step1 (ie after deleting the livy host) before performing rest of the steps, then changes are getting reflected properly. System test was mistakenly doing this step so didn't fail during nightly run

Note 2 : Issue is happening only when both Spark and Spark2 are installed. If cluster contains only Spark2, this feature works as expected.
Issue is coming if I add Spark(version 1) to it.

Issue Links

• links to: Review Link