[
https://issues.apache.org/jira/browse/LIVY-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-545:
----------------------------
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.
> Eldest Statement will be discarded even if user never get its result
> --------------------------------------------------------------------
>
> Key: LIVY-545
> URL: https://issues.apache.org/jira/browse/LIVY-545
> Project: Livy
> Issue Type: Bug
> Components: REPL
> Affects Versions: 0.5.0
> Reporter: weiwenda
> Priority: Major
> Labels: performance
> Fix For: 0.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. when repl.session's statement num has reach threshold which is configured
> by livy.rsc.retained-statements, default as 100. The submit of 101th
> statement will lead to the discard of the eldest statement (should be No.1).
> 2. The discard means this statement is not attainable anymore. And if user
> forget to get the result of this discarded statement before or didn't
> request the result in time, he must resubmit same statement again hoping
> server won't discard again.
> 3. In above workflow, cluster do some unnecessary effort. If the discarded
> statement need hours of time to execute, this serve mode will waste a lot of
> money.
> 4. maybe resolve this problem by allow persist statement or discard statement
> that have be read in priority.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
