When to chose "All associated nodes" in Job Scheduler
I can't think of any situation that any custom batch process has to be run on "All associated nodes" in Job Scheduler. Can anyone give some examples please ?
ING Bank
NL
Hi @GhassenM, What if you have to regularly delete or send (to an external datalake) some files that were extracted/stored on a given node? Pega has a few OOTB ones like NodeCleaner that run on all associated nodes.
Royal Bank of Canada
CA
@GhassenM Yes I agree in most scenarios we can't use that option as it is very difficult to distribute the load to all nodes to avoid duplicate processing for eg processing of objects, sending emails etc. I have seen in my previous project, the custom implementation of some extraction jobs running Advanced agent on all nodes (instead of using Bix because of some gap) in Pega 7.x version. Before opening the case they look into the lock table to avoid duplicate processing between nodes. I think we can use Job schedulers on all nodes in such rare implementations.