[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gyrex-dev] Gyrex Jobs
|
It's fine with me if I don't have to care who executes a job, as long as
the job runs only once.
Another question in this context: How can I realize a job that should be
executed on every node of a certain type? For example one node saves an
object and every node that holds an index should run a job, that takes
the Object out of the DB and updates the local index.
Am 16.12.2015 um 19:14 schrieb Gunnar Wagenknecht:
Hi Jürgen.
Jobs are executed only once. You can influence the instance which will be executing a job by using queues. For example, you could have a priority queue which is backed by a set of dedicated machines. Or you can have a special queue which is only processed by a single machine. But that's somewhat contradictory to the nature of distributed jobs. :)
-Gunnar
--
Jürgen Albert
Geschäftsführer
Data In Motion UG (haftungsbeschränkt)
Kahlaische Str. 4
07745 Jena
Mobil: 0157-72521634
E-Mail: j.albert@xxxxxxxxxxxxxxx
Web: www.datainmotion.de
XING: https://www.xing.com/profile/Juergen_Albert5
Rechtliches
Jena HBR 507027
USt-IdNr: DE274553639
St.Nr.: 162/107/04586
