running IStateful jobs per machine in a cluster with Quartz.net -



running IStateful jobs per machine in a cluster with Quartz.net -

i running cluster of quartz.net services reading of standard adojobstore. behaviour i'm looking explained in title, i'm wanting run stateful jobs per machine in cluster. believe stateful job run one-at-a-time whole cluster. uncertainty quartz.net supports stateful job per machine in cluster function ality i've looked long , hard there other way replicate behaviour in quartz.net?

another way set threadcount per job type opposed current situation threadcount specified per machine, give me behaviour i'm looking , able run specific job type one-at-a-time per machine.

any suggestions?

if job start times of jobs not crucial, can seek these

you can utilize proper grouping name triggers & jobs based on machine name in cluster (for identification) , see if grouping name of triggers correspond machine name firing on (attach trigger listener , create corresponding checks in vetojobexecution , homecoming false if job should not run in machine, else homecoming true).

if stopped trigger beingness picked same machine 1 time again , 1 time again can seek standby , startdelayed on scheduler avoid that.

this suggestion , haven't verified it.

quartz.net

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -