[
https://issues.apache.org/jira/browse/LIVY-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-451:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Failed to use Livy in Docker container launched on same node as YARN
> --------------------------------------------------------------------
>
> Key: LIVY-451
> URL: https://issues.apache.org/jira/browse/LIVY-451
> Project: Livy
> Issue Type: Bug
> Components: RSC
> Affects Versions: 0.3, 0.5.0
> Reporter: Ivan Dzikovsky
> Priority: Major
> Fix For: 0.10.0
>
>
> I've tried to run Livy inside of Docker container on same node as I have YARN.
> As I've found, to make it works I need to expose some ports (LIVY-337), so
> I've added {{-p 10000-10010:10000-10010}} option to Docker run command.
> It works when Livy container launched on other machine, but when it launched
> on same node as YARN, Spark Driver fails to start.
> After some investigation, I've found that Spark Driver (which is inside of
> YARN) tries to use same ports that configured for Spark Launcher
> (livy.rsc.launcher.port.range option), and it was not able to start as all
> ports from that range was already bound by Docker daemon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
