You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Supreeth Sharma (JIRA)" <ji...@apache.org> on 2018/01/02 17:53:00 UTC
[jira] [Created] (AMBARI-22716) zeppelin.livy.url is not getting
updated after moving livy to a new host
Supreeth Sharma created AMBARI-22716:
----------------------------------------
Summary: zeppelin.livy.url is not getting updated after moving livy to a new host
Key: AMBARI-22716
URL: https://issues.apache.org/jira/browse/AMBARI-22716
Project: Ambari
Issue Type: Bug
Components: ambari-sever
Affects Versions: 2.6.1
Environment: ambari-server --version 2.6.1.0-137
HDP-2.6.4.0-86
Reporter: Supreeth Sharma
Priority: Critical
Fix For: 2.6.1
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)