We have frequently running job schedulers set to “Any one associated node”. Every time a node runs the job, all the other nodes write to the log:
WARN - Detected duplicate job scheduler execution. Skipping execution.
The message logs despite this Pega category being set to ERROR. It’s very noisy. Anyone have a clue why it’s doing this?
@mjosborn85 I’m also seeing this even though I have turned off this log category it’s still producing WARN log entries every 30s or so. This needs a fix ASAP as this is filling up the logs very quickly.
UPDATE
Have raised SR INC-A26412 for this problem as it’s filling up our Splunk quota.
@CraigA52 We experience the same flood of log messages since we’re running Pega 8.8. Please keep us posted on any news on the ticket you raised. Thanks.
@CraigA52 and @SaschaW1 , good news. It took some persistence and intervention from @ChrisKoyl and @adama2 (big shout out and thank you), but bug ticket BUG-842447 was filed for this. They were using “warnForced”. (Didn’t even know there was such a thing). Likely the developer didn’t foresee what would happen with quickly cycling schedules in a cluster.
I don’t have insight to the number or ETA, but it ought to be a simple one-word change in the code.
@mjosborn85 @ChrisKoyl Thanks for Identifying the issue. Do we have any ETA. We are in Pega 8.8.2 and see same logs.
Thanks,
Prem K
@mjosborn85 Any update on this? I’m seeing this on Pega 8.8.2 as well as Pega 23.1.2
@CraigA52 , not sure about versions, but on 8.8.4 I just double-checked and I’m seeing none of these messages. If anyone at Pega is watching, may we know what platform release contained the fix for BUG-842447?