jahstreet commented on pull request #167:
URL: https://github.com/apache/incubator-livy/pull/167#issuecomment-644922185
@JagadeeshNagella , could you please share with me the diff so that I could
patch this PR branch and try it out? Also you might be interested in [this
answer](https://sta
jahstreet commented on pull request #249:
URL: https://github.com/apache/incubator-livy/pull/249#issuecomment-644914983
@lukatera , you can check that PR:
https://github.com/apache/incubator-livy/pull/167 . Basically this PR is the
clean backport from the former one.
lukatera commented on pull request #249:
URL: https://github.com/apache/incubator-livy/pull/249#issuecomment-644650074
> Hi @lukatera , upgrading ZooKeeper client is out of scope of this PR and
is a good candidate for a separate one. Feel free to open it. Later we can
rebase this one to ma
jahstreet commented on pull request #249:
URL: https://github.com/apache/incubator-livy/pull/249#issuecomment-644612554
Hi @lukatera , upgrading ZooKeeper client is out of scope of this PR and is
a good candidate for a separate one. Feel free to open it. Later we can rebase
this one to mas
lukatera commented on pull request #249:
URL: https://github.com/apache/incubator-livy/pull/249#issuecomment-644585957
I had some issues with using ZooKeeper as a recovery method. When one of the
zookeepers is not up in Kubernetes, its address is not published (i.e. there is
none), and thu
