Re:Livy：Task submission scheduling problem in yarn mode

[adley]

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-05 16:01:26, "ipconfig"  wrote:

Hi:
There are two tasks in my program. Task one caches data locally to the 
device node where the current session is located (not hdfs). Task two will read 
the data cached by task one when submitted, so I need to submit both task one 
and task two To the same device node.
now using livy, I submit both task one and task two to the same session. 
Can I ensure that these two tasks are scheduled to the same running node and 
get the cached data?

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

[Saisai Shao]

Though we haven't tried such use case before, from my understanding I think
Livy cannot support it, and such usage scenario seems not a typical usage
pattern.

adley  于2020年3月8日周日 下午9:40写道：

> 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 successful, no error is
> reported, but it has no effect. The execution result shows that the class
> implementation in oldjar is still called.
> Can Livy support the repeated submission of jar packages under one
> client?
>

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

[adley]

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 successful, no error is 
reported, but it has no effect. The execution result shows that the class 
implementation in oldjar is still called. 
Can Livy support the repeated submission of jar packages under one client?