 |
 |
Pablo Rey Mayo wrote: > Frederic Schaer wrote: > >> Hem... who said it is mandatory to have the cron job running on the >> MON after the one on the CE ?? >> >> The job running on the MON host is joining/publishing data into RGMA >> : it merges different MySQL tables and then sends the data. >> If it's running before the CE job ran, then you'll publish data for >> the day before... I don't see the problem... > > > Yes, of course, it is not mandatory to have the cron job running on > the MON after the one on the CE but it is very recommendable or no?. I would say it's not really important, but... (see below) > At least, we want to publish our accounting data each day and not one > day later. Then schedule the job on the MON Box to run every 12 hours (or more frequently) : if there's no data to publish, there will be nearly no overload on any host, and you'll be sure data is sent at most 12 (or less) hours after it's been processed on the CE. Since it's not the CE that publishes the data (and that's good : don't charge the CE more than needed), you can not achieve real time anyway ;) Cheers, Fred > Cheers. > >> Cheers, >> Fred >> >> Pablo Rey Mayo wrote: >> >>> Steve Fisher wrote: >>> >>>> Hi, >>>> >>>> To avoid having all sites publishing a day's records simultaneously, >>>> Oliver has changed the YAIM for the forthcoming LCG 2.7.0 to have cron >>>> running the job at a random time. >>>> >>>> Meanwhile please change the crontab entry manually to some "random" >>>> time >>>> >>>> See: http://goc.grid-support.ac.uk/gridsite/accounting/faq.html#cron >>>> >>>> Steve >>>> >>> Are you taking into account that the Apel should run in the MON >>> after it run in the CE?. Taking into account that you have to run the >>> YAIM in two differents machines (CE and MON), I like to know how you >>> has >>> solved this issue if it is possible. >>> >> >> > >