When I submit a render to the cloud (google) I have an rsync job that precedes the render, and the render job has a dependency on the rsync job. the render job also has an asset dependency on the list of assets given to the rsync. The net result being the rsync job pushes all references, caches, textures, etc and the render file itself to the cloud, then the render job starts.
The issue I’m having is the rsync job has finished, and the assets are uploaded (verified by command line render on the vm). Nonetheless, the render job is still paused.
Would this be due to the balancer, the crawler or something else? What do I check and how do I debug? Thank you.
-ctj
Hi Christopher,
The Balancer / Asset Crawler asset checking functionality is strictly read-only for the purpose of weighting Groups to determine VM instance count targets, so we can rule those out.
Does the rsync job show that it has completed without errors? What happens if you remove the rsync job dependency and just retain the assets dependency (and the also vice versa)? This might reveal where the hangup is occurring. What does the Test Dependencies feature show in the Job Dependencies View?
the rsync job finished without errors. I’ll have a look at Test Dependencies does. The job eventually when through last night, but I’ll have many oportunities today to test the dependencies. 