Re:Livy：Task submission scheduling problem in yarn mode

With the gradual understanding of livy, my opinion is that livy only keeps the context on the driver side, but specifically on which running node the worker / exectutor side is executing, it is controlled by yarn, and livy cannot control these. I wonder if this is correct? At 2020-03-

Can a livy client upload and run different jar packages multiple times?

Hi： I followed the official example-PiApp.java, and tried to submit and run successfully. Then I modified the code and called client.uploadJar (newjar) again after client.submit, and finally called the class implementation in newjar, client.submit ( newjar-newclass), the upload is succe

In yarn mode, can the use of livy resident context avoid the time loss of multiple resource allocation?

Hi： By using livy and spark, can it achieve similar effects to llama (impala) and save time consumption of yarn container resource allocation? Reference link: https://cloudera.github.io/llama/