[AMBARI-22716] zeppelin.livy.url is not getting updated after moving livy to a new host#161
Merged
Merged
Conversation
…ivy to a new host (prabhjyotsingh)
Contributor
Author
|
@venkatasairamlanka Please help review/merge this to trunk and branch-2.6. |
|
Refer to this link for build results (access rights to CI server needed): |
|
LGTM. |
prabhjyotsingh
changed the title
prabhjyotsingh
changed the title
|
LGTM |
nitirajrathore
added a commit
that referenced
this pull request
Jan 22, 2018
[AMBARI-22716] zeppelin.livy.url is not getting updated after moving livy to a new host #161
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
zeppelin.livy.url is not getting updated after moving livy to a new host
How was this patch tested?
Manually
zeppelin.livy.url is not getting updated after moving livy to a new host
Steps to reproduce :
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.