[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [gyrex-dev] Scaling of Gyrex Jobs
|
Hi,
I will give it a try, but how can I create a volatile Job? As far as I
can the see, the IStatus will always find its way in the job history. My
solution would be to provide an own IJobHistoryStorage that ends in the
void or stores the results anywhere else.
Jürgen.
Am 07.12.2015 um 08:25 schrieb Gunnar Wagenknecht:
Hi Jürgen.
Given the current implementation this will depend heavily on your ZooKeeper cluster. The current implementation would put a lot write activity on your ZooKeeper cluster because the job history is stored in ZooKeeper. In the past we've discussed implementing an alternate ZooKeeper history storage location. However, that hasn't been implemented yet.
Depending on what your requirements are, you may also benefit from a volatile job, i.e. one that doesn't store history at all.
-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
