How to safely shut down DR server?

[pokoy]

I have some renders that will take a bit longer to render and some of the DR servers will be needed for working during the days.

What's the safe way to shut down a DR server? Close the server window or rather the CMD window? Which one to close first? I guess what I'd like to know is how to make sure all rendered tiles will be transmitted to the DR master and nothing's going to be lost?

[Frood]

If you know what you are doing you can close it when you like imho (drserver window). You may check the working directory for a possibly needed manual cleanup afterwards. The master will just report the slave as failed after a while. However you will not be able to let the slave rejoin until a new job arrives/a frame change occurs. Render result is sent in "Synchronization interval" (+/- a few seconds) regulary, this is the maximum render contribution which is waisted.

But I would not do it like this anyway. Have you considered to just let the dr job(s) run and work with another session with adjusted affinity/priority (also remember that you can use string options to adjust thread usage for DR slaves)? If ram is not a problem that should be ok.

Personally when having no dedicated render node available I would let the jobs crunch by backburner (as service) with idle priority/adjusted affinity in the background on one box each to get the full advantage of adaptivity (corona 1.5.2).


Good Luck

[Christa Noel]

... just let the dr job(s) run and work with another session with adjusted affinity/priority (also remember that you can use string options to adjust thread usage for DR slaves)? If ram is not a problem that should be ok.

yes, that is a safe method when we need to do extra works, and I did that almost in my every works :)
but eventhough the priority is changed to low, you will still feel a little bit heavier in bigger scene

[pokoy]

I hoped a certain procedure would make sure all tiles are transferred.

Thanks for the ideas, guys, but I really need to shut down any DR activity, then logout the user and login another one to work without any background processing.

[Frood]

then logout the user and login another one to work

Running DrServer.exe as service avoids user dependency completely and you can log on/off whomever you want even during rendering, and start/stop DrServer whenever you want without affecting the currently logged in user (if any).

But I´m sure you already know ;)

Good Luck