I'm testing distributed processing using Compressor over my company network. In the transcode I've got running right now, 3 of the 4 cores on the services-only Mac have suddenly gone down.
Batch Monitor reports "3x crash HOST [iMac name] service down". I checked Activity Monitor on that machine, and the four instances of Compressor are visible, but three of them are showing 0% CPU load. The segments that were being processed by those cores have gone to "Failed" or "Cancelled", but the segments on the cores that are still live are still transcoding.
Does the fact that Compressor hasn't just cancelled the entire job mean that it can automatically recover from this and reschedule the failed/cancelled segments to working cores as they become available? Or do I have to intervene to make it do this? Or is the whole session a write-off and I just have to start again from the beginning and hope it doesn't happen again?