AWS Thinkbox Discussion Forums

On Complete not working ?

The “On Complete” option when I submit a job from the Maya submit script is not doing anything.
Whatever I set it to “Delete” or “Archive”, the job, once successfully completed, just stays in the Monitor list.
Also I don’t see anything in the jobsArchived folder and I can still see the option I previously set when I look at the Job Properties.
Using version v6.0.0.51362 R

Am I missing something ? or is this a bug ?
thank you

Jobs with “On Complete” settings are processed during housecleaning, which is done on regular intervals if you are running Pulse, or at random intervals if you are not. The Monitor also has an option in the Tools menu (while in super user mode) to manually perform a housecleaning. Can you try running the manual housecleaning from the monitor to see if the jobs get properly cleaned up?

On testing this here, it appears that the housecleaning is working properly. However, I did find a bug where running a manual housecleaning after the previous manual housecleaning deleted or archived a job resulted in this error:

Error occurred during periodic house cleaning: Object reference not set to an instance of an object. (System.NullReferenceException)

So if you see this error, restart the Monitor and try again. We’re pretty sure this error ONLY affects the Monitor, and it’s already been fixed internally.

Cheers,

  • Ryan

Oh ok I understand now. I guess because we don’t have Pulse running so sometime I thought it wasn’t working. Yes the manual housecleaning goes as you describe it.
Just two questions then:

  • in what interval of time is the random value chosen from ?
  • is it possible to force the archive right after the job is completed in some other way ?

thank you

Between each task, a slave will count the number of running slaves and set this to X. Then, it will have a 1 in X chance of performing housecleaning.

To have it run on a regular interval, you can just run Pulse on one of your slave machines, or you could have it run on your repository machine or database machine if that’s an option. Deadline no longer uses Pulse as a proxy in version 6, and since most of the advanced Pulse features are disabled by default (power management, slave throttling, web service, etc), it should just sit there quietly and clean things up for you.

A benefit to running Pulse though is that it will log repository and slave statistics for you.

Cheers,

  • Ryan
Privacy | Site terms | Cookie preferences