Message-ID: <344238565.9151.1711723863009.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9150_1930289742.1711723863009" ------=_Part_9150_1930289742.1711723863009 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html How to use clustering for workers

How to use clustering for workers

Let=E2=80=99s say you wish to partition your render farm into 2 = departments, post and promo.  Qube! supports the idea of partitioning = your render farm into "clusters".  You can divide up your fa= rm between any number of departments, while still allowing the departments = to share the machines.
 
As an example, you could allocate s= ome of your render nodes to the /post cluster, and some to the /promo clust= er (Qube! workers - your render nodes - belong to 1 and only 1 cluster). &n= bsp;Users would submit their jobs to either the /post cluster or the /promo= cluster - this can be configured so that it's transparent to the user.&nbs= p;

A worker in the /post cluster will run the lowest-priority job in the /p= ost cluster before it will run the highest-priority job in the /promo clust= er.

A worker in the /promo cluster will run the lowest-priority job in the /= promo cluster before it will run the highest-priority job in the /post clus= ter.

You could also add machines to the / cluster (the "root" clust= er).  Workers in the / cluster will give equal priority to jobs from a= ll departments.

The simplest way to set a worker's cl= uster is in WranglerView running on the supervisor, see: Centralized Worker Configurat= ion

The relavant configuration parameter = is worker_cluster.=

= worker_cluster =3D /post

Clusterin= g and restrictions 

Optionally, some or all workers in either the /post or /promo cluster ca= n be configured to ~only~ run jobs in their respective clusters via the&nbs= p;worker_restrictions value. Yo= u can have some of the /post workers be available to promo department if th= ere are no post jobs, while other /post workers will remain dedicated to th= e post department.

The most common case is that the worker is restricted to only accepting = jobs that are submitted into the worker's cluster:

worker_cluster =3D /promo

worker_restrictions =3D /promo 

but more complex scenarios are outlin= e in the documentation for worker_restrictions <= /span>

See Also

------=_Part_9150_1930289742.1711723863009--