search

AcademySoftwareFoundation / OpenCue

A render management system you can deploy for visual effects and animation productions.
https://www.opencue.io
Apache License 2.0
832 stars 202 forks source link

Unmonitoring jobs on the "Monitor Jobs" pane doesn't work properly #475

Open gregdenton opened 5 years ago

gregdenton commented 5 years ago

Unmonitorting failing jobs removes them from the pane as expected, but they come back after a 10 seconds.

gregdenton commented 5 years ago

This only happens to failing jobs. Completed jobs behave properly.

kalisp commented 4 years ago

Just FYI I tried this on up-to-date (12/3/2019) master branch on test job from https://www.opencue.io/docs/quick-starts/quick-start-linux/ and couldn't replicate it.

Attaching screenshot if it would help. opencue_unmonitor_475

sharifsalah commented 4 years ago

Thanks @kalisp. From your screenshot, it looks like you're running a variation on the simple echo command from the quick start. I suspect the reason you're able to un-monitor the jobs successfully in your case, is that the job is failing very quickly, such that all of the frames have failed. If you try a longer running job, you might see the behavior described by @gregdenton.

I've recently noticed that I first have to "kill" a job and then un-monitor it for it to remain un-monitored.

By the way, I'm planning to add a follow-up guide / tutorial to the quick start that explains how to run a more real-world rendering job in the sandbox. You can follow along in https://github.com/AcademySoftwareFoundation/opencue.io/issues/122.

kalisp commented 4 years ago

I tested it on longer running frames (used Blender and sleep in command line job), couldn't reproduce it there either. But maybe I am doing something wrong here.

Looking forward for a guide with Blender and Docker. I followed 'Quick Start for Linux', great job there. I would just highlight there system requirements (memory) as that is only mentioned in 'Quick Start for Mac' and later in regular installation (imho).

I tried that on a small machine and RQD kept dying on me, that error message about not enough memory is pretty hidden during pip installing requirements. Then I found same issue somewhere here and figured it out (I needed 4 GB of memory for pip finishing unpacking something big).

bcipriano commented 4 years ago

I tried that on a small machine and RQD kept dying on me, that error message about not enough memory is pretty hidden during pip installing requirements.

Hopefully this won't happen anymore -- now that #560 is merged RQD doesn't install PySide anymore, which was the cause for running out of RAM in (I think) every case I've seen so far.

But agreed on need to update the docs. Thanks!