Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1503
That's correct for LivySparkInterpreter, LivyPySparkInterpreter and
LivySparkRInterpreter. Because they use FIFOScheduler. If you check the
implenentaion of FIFOScheduler, there's only one thread in it, and each job
will run in FIFO order. But this is different for LivySparkSQLInterpreter as it
can use ParallelScheduler if set zeppelin.livy.concurrentSQL as true. This is
why I mention before there're many issues in LivyInterpreter, it doesn't make
sense to use FIFOScheduler for LivySparkInterpreter, LivyPySparkInterpreter and
LivySparkRInterpreter. Because each user's sessions are isolated in livy, we
should use ParallelScheduler.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
