[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gyrex-dev] Gyrex Jobs
|
Hi,
currently we use the remote event admin approach and It works pretty
well. We just gave the jobs approach a few thoughts. The Point is, in
the End we handle the indexing via Eclipse jobs. Therefor the question
arose, if we could use a centralized job creation.
Thx for the information,
Jürgen.
Am 17.12.2015 um 15:24 schrieb Gunnar Wagenknecht:
Hi Jürgen,
Am 17.12.2015 um 11:16 schrieb Jürgen Albert <j.albert@xxxxxxxxxxxxxxxxxx>:
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.
It sounds like this isn't a good use case for Gyrex distributed jobs. This sounds more like a use case for an distributed event bus. Every time an event is received, a local thread could perform the indexing.
As for distributed jobs, I would expect the implementation to be different - one job builds the index and then distributes it to all the nodes requiring the new index. The distribution could happen via a shared drive or using scp or some other protocol.
-Gunnar
_______________________________________________
gyrex-dev mailing list
gyrex-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/gyrex-dev
--
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
