Doug Daulton
Forum Replies Created
-
Have tried the AFP mount method and am having trouble. Here are the methods I have tried. In each case, I have all machines mapped to the same folder mounted locally over AFP.
1) Primary machine as “as Services and cluster controller” with other machines “as Services only”.
2) Primary machine as “QuickCluster with services” with other machines “as Services only”.
3) All machines as “QuickCluster with services”.
In each case, I submit a job using “This Computer Plus” and the job goes into the queue and just hangs. There is no movement or status updating. I even let it run overnight thinking it might need to copy some files. In the AM, it was still hung.
Here is a video walking through the setup and render.
https://screencast.com/t/Nv5kLnP0GTPx
What am I missing?
Thanks,
Doug
-
Wow. Just reread that. Lots of typos I missed. Sorry for my fat fingers.
In any case, the only one that may require clarification is “through out”. I meant “throughput”. I think auto-correct got me. 😀
-
Bob,
RE: SAN is not a render farm. Understood. I was thinking of the SAN as attached storage for the render farm, as it seems that Compressor 4 requires a central data store to allow distributed rendering.
I plan to use Ethernet, probably link aggregated Gigabit as I am working with ProRes and not Uncompressed. So, if my research is accurate, it should give me the through out I need.
Having said that, I now suspect a SAN is overkill for my needs. Rather, I think I could do a DIY NAS an mount it to all the render nodes using AFP. In this case, I still plan to explore using NICs and a managed switch with link aggregation to get the maximum throughput across the “farm”. Any gotchas with that idea?
Thanks,
Doug
PS: Did I send you an email? I don’t think I have you email address. 🙂 If I did, I don’t seem to have it. In any case, thanks for taking the time to answer. We are exploring adding C4D to the mix, so your use case is very timely and valuable.
-
Thanks Ian. Will give it a go with that configuration.