[
https://issues.apache.org/jira/browse/LIVY-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-168:
----------------------------
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.
> Differentiate BatchSession & InteractiveSession
> -----------------------------------------------
>
> Key: LIVY-168
> URL: https://issues.apache.org/jira/browse/LIVY-168
> Project: Livy
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 0.2
> Reporter: Jeff Zhang
> Priority: Major
> Fix For: 0.10.0
>
>
> For now, BatchSession & InteractiveSession both extend Session and use
> SessionManager. This cause several issues:
> 1. Garbage Collection is not necessary for BatchSession.
> 2. BatchSession & InteractiveSession use their own SessionManager which
> means there would be a same session id for both BatchSession &
> InteractiveSession. e.g. In the following log there's 2 session with id 0
> which is very confused.
> {code}
> 16/06/14 15:10:39 INFO SessionManager: Registering new session 0
> 16/06/14 15:29:30 INFO InteractiveSession: Creating LivyClient for sessionId: > 0
> 16/06/14 15:29:30 WARN RSCConf: Your hostname, jzhangMBPr.local, resolves to
> a loopback address, but we couldn't find any external IP address!
> 16/06/14 15:29:30 WARN RSCConf: Set livy.rsc.rpc.server.address if you need
> to bind to another address.
> 16/06/14 15:29:30 INFO SessionManager: Registering new session 0
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
