[
https://issues.apache.org/jira/browse/LIVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904955#comment-16904955
]
Oleksandr Shevchenko commented on LIVY-616:
-------------------------------------------
[~jerryshao]
Or you mean Livy HTTP endpoint for getting Livy Server address? Without
creating LivyDiscoveryManager, with just simple 'curl'?
But to use this HTTP endpoint we already need to have Livy Server address.
So, now I see only two scenarios. Using LivyDiscoveryManager directly or use
Java/Scala client.
One more thing. Will be good if we can simplify creating of client
{code}
val address = LivyDiscoveryManager(livyConf).getServerUri()
val client = LivyClientBuilder.setURI(s"http://$address";).build
{code}
I mean don't specify uri in LivyClientBuilder in client code.
{code}
val client = LivyClientBuilder.build
{code}
We can set URI by LivyDiscoveryManager from Livy project side but it requires
adding "livy-server" dependency to "livy-client-common".
> Livy Server discovery
> ---------------------
>
> Key: LIVY-616
> URL: https://issues.apache.org/jira/browse/LIVY-616
> Project: Livy
> Issue Type: Improvement
> Components: Server
> Reporter: Oleksandr Shevchenko
> Priority: Major
> Attachments: Livy Server discovery spec.pdf
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, there isn't a way to get Livy Server URI by the client without
> setting Livy address explicitly to livy.conf. A client should set
> "livy.server.host" variable and then get it via LivyConf. The same behavior
> if you want to use Livy with Zeppelin, we need to set "zeppelin.livy.url". It
> very inconvenient when we install Livy packages on couple nodes and don't
> know where exactly Livy Server will be started e.g. by Ambari or Cloudera
> Manager. Also, in this case, we need to have Livy configuration files on a
> node where we want to get Livy address.
> It will be very helpful if we will add Livy Server address to Zookeeper and
> expose API for clients to get Livy URL to use it in client code for REST
> calls.
> Livy already supports state saving in Zookeeper but I don't see that we store
> Livy server address somewhere. Before starting investigating and
> implementation I want to ask here about this.
> Please, correct me if I missed something.
> Any comments will be highly appreciated!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
