Blender ver 2.81a on windows host and linux slaves
host machine is windows 10
aall cr versions are the same, newest
Network is 1Gbps and probably is going to be 10Gbps
Why render results from servers sometimes arent going back to host machine
When it happens, the render result is empty, even a piece isnt comming back.
What can be the cause of this problem? Can network be a bottleneck that causes render piece not returning to host as a result?
Ok, can we have an example project to try and reproduce this problem in our lab? We have linux servers, mac and windows machines, so we'd like to be able to emulate your environment and try to get this issue happening in our lab. If we can do that, we can very likely solve this problem :)
I will check the logs soon.
The problem is not noticeable with small projects (both linked and not, using f.e. 7 servers we have up and running now) but i'd say 75%-90% of large projects (i mean like 4+ or more GB files etc) fails with sync or render. If somehow we have synced 4 servers we have noticed 3 ways to "finish" the render.
1st - after servers jobs are done, rendered image returns to host and is getting "glued" into one piece
2nd - renders are not returning (all of them, not piece or two) but they are rendered in dir /cr/server/UUID/file.exr
3rd - everything crashes including headless instances servers
We have found a way to render linked projects, network usage of host ethernet card is peaking at 900Mb/s+, on slaves too due to linked files. As i saw, communication between host and slaves goes through TCP and is using jumbo frames, am i right? I have never found any info about that. Can jumbo frame and/or MTU config be the problem in our case?
I’m looking forward to your opinion.
Hi there :)
At 1Gbps your network is more than capable, I would say that isn't the reason. Would you be able to tell us how many frames are having this problem? Is it all of them, half, just a few?
Have you checked for any errors? The latest version of Crowdrender shows errors and warnings coming from nodes, there's a little info icon next to the node which you can click and it will show you all the output from the node's render process, you can search for text in this output by typing 'error' or 'warning' and seeing if there are problems.
Finally if you cannot find anything obvious, perhaps you'd like to submit a support ticket and we can look at your logs? You can attach logs, screenshots and a detailed description of what you did, and how to reproduce the problem. We can then take a look and see what's up :)
Wishing you all the best