You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2017/11/28 03:35:00 UTC

[jira] [Comment Edited] (LIVY-421) support multi statements run at the same time

    [ https://issues.apache.org/jira/browse/LIVY-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268034#comment-16268034 ] 

Jeff Zhang edited comment on LIVY-421 at 11/28/17 3:34 AM:
-----------------------------------------------------------

> 1. Your multi-interpreter design hopes a user's request always submit to a specified interpreter? That is, a user and an interpreter one by one corresponding
> 2. Does this require the user to know which interpreter to submit the snippet to?

It doesn't to be one-to-one relationship. User could specify which interpreter he want to submit in theory. Livy could expose such api, it is client's responsibility to decide which interpreter to submit code.



was (Author: zjffdu):
> 1. Your multi-interpreter design hopes a user's request always submit to a specified interpreter? That is, a user and an interpreter one by one corresponding
> 2. Does this require the user to know which interpreter to submit the snippet to?

It doesn't not to be one-to-one relationship. User could specify which interpreter he want to submit in theory. Livy could expose such api, it is client's responsibility to decide which interpreter to submit code.


> support multi statements run at the same time
> ---------------------------------------------
>
>                 Key: LIVY-421
>                 URL: https://issues.apache.org/jira/browse/LIVY-421
>             Project: Livy
>          Issue Type: Improvement
>          Components: REPL
>    Affects Versions: 0.4
>            Reporter: zhuweibin
>              Labels: performance
>
> In the v0.4.0-incubating's’ implementation, the number of threads used to execute the statement code is hardcoded to one. When idle resources are sufficient to execute multiple statements, a lot of resources are wasted and blocking statements run. We are considering improvements in one of two ways:
> # 1. Add a configuration in livy.conf to globally control the number of threads in interpreterExecutor for all repl/sessions to execute statements
> # 2 in the session to create a rest api parameter to set the maximum number of statements can be run at the same time the number of statements
> hope to discuss this issue, thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)