We have Flowable implemented application deployed in Active-Passive model. So whenever there was an entry to Timer Job table and it tries for 3 attempts and in case of failed to process it moves to dead letter table. This is expected in Active datacenter, where as in passive data center it does the same in parallel. Please note both data centers has its own DB and its 2 way replica.
We end up with DB replica broke up since both the datacenters are processing timer table record by its own. Let us know is there any way to stop passive data center not to process the timer job or set retries are zero ? Appreciate your quick help on this.
We have solution as property basis on/off async as follows and this requires a restart of instance. Do we have any Flowable API based turn on/off for the below property ? Appreciate your help.
Subscribe to get latest updates