This discussion is archived
3657 Views 4 Replies Latest reply: Aug 8, 2010 1:29 AM by vjnews
Currently Being ModeratedAug 5, 2010 3:24 PM (in response to vjnews)For Final Cut Server (FCSvr) all transcoding can be clustered using an Apple Qmaster cluster.
So add a couple of Xserves cluster them using Qmaster, configure FCSvr to use this cluster and all transcoding will be handle distributively over this cluster.
Hope this helps.
XPlatform Consulting8 Core Mac Pro, Mac OS X (10.6.4)
Currently Being ModeratedAug 6, 2010 7:26 AM (in response to vjnews)I have tried this several ways, in several iterations, and have never gotten it to work successfully. I always have to go back and set Final Cut Server to use its own sever for generating proxies. I have an XSan with several servers as XSan clients (so no AFP share), I even moved the Proxy bundle onto the XSan so everyone had access to it, but still get hiccups and artifacts in my proxies. If you get it to work, please post back here. I'd like to know.
Currently Being ModeratedAug 6, 2010 9:47 AM (in response to Daniel Harrell1)Actually it's quite easy to use a Compressor cluster for Proxy generation and other encodings in FCSvr. One thing you might want to consider, is that you need to tell the cluster controller to use an Xsan volume for the temporary storage.
This way the other cluster nodes can access files via Xsan without the cluster controller needing to share the cluster storage through NFS, which is dramatically faster.
Yet, if you use Xsan as the cluster storage, after a reboot of the cluster controller it can happen, that qmaster starts before Xsan and therefore doesn't find the Xsan volume. If this happens, qmaster creates a local directory with the same path like the cluster storage, which a) leads to the fact that qmaster stores temporary data on the boot disk which is slower than Xsan, needs NFS resharing and can fill up the boot disk easily, and b) prevents your Xsan volume from being mounted, as Xsan detects, that there is already a folder in your local filesystem at the place where Xsan should usually be mounted.
To circumvent these issues, you need to rewrite the qmaster launchd job at /Library/LaunchDaemons/com.apple.qmaster.qmasterd.plist to look something like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
where /Volumes/XsanVolume/Qmaster needs to be the Xsan path to your temporary qmaster directory.
Now qmaster waits for your Xsan volume to be mounted before it starts itself.
Hope this helps.
AndréMacBook Pro, Mac OS X (10.6.4)