Hi,
A quick workaround is to override the TenantJobSchedulerFactoryBean and set a property to enable/disable the fineract instance for running the Quartz scheduler.
Another solution is to change from RAMStore to JDBCStore, you need to add some wrappers to avoid the issue of Quartz about the JobDetail when using Method Invoker, because of the non-serializable objetcs.
And of course a more complex solution is to use something like XXL-Job or Elastic-Job.
Regards.
Victor
El 3 de noviembre de 2019 a las 11:49 AM Ashutosh Prasad Panigrahi <[email protected]> escribió:
Hello Friends,
I am new to Fineract and doing a small POC using Fineract (Monolith) and not Fineract CN.
I want to run multiple Fineract servers pointing to the same Database server to scale the API
However my fear is that with this approach the scheduler & Batch jobs will get started in all the API servers.
Is there any way to stop schedulers coming up automatically with the server.
I would ideally like to isolate the batch jobs to a separate hardware .
Any suggestions ?
RegardsAshutosh
