Alerts for queue processor (QP) items which took more than 15 minutes to run could result in the system marking the node as 'unhealthy'. In environments with Pega Health Check enabled, this would shut down the node gracefully. It was not possible to change this default as it was hardcoded. In order to support systems that may have custom processes that run beyond 15 minutes, a a new setting has been exposed that allows configuration of the interval after which a node with long-running queue processor is marked as unhealthy and is restarted. By default this remains 900000 milliseconds / 900 seconds / 15 minutes, but it may be adjusted up to 24 hours to avoid premature node shutdown. The stale thread detection mechanism will take that setting into account and use the provided value or default to 15 minutes if the value was not provided. In addition, the threshold's units in the UI have been changed from ms to seconds.
Resolved in Product Version: 8.3.6
***Edited by Moderator: Pooja Gadige to add capability tag***
@Tarun Bolla I've checked the description listed against this Issue-649451 (fixed in Pega 8.5.4 under ISSUE-640749)
The configuration mentioned appears to be a possibility to set node's health check timeout to extend a default 15 minutes.
You should be able to find this configuration on the Queue Processor rule form to allow for setting a timeout value that will be used to mark node as unhealthy. . This value defaults to 15 minutes and can be extended up to 24 hours.
Posted: 7 months ago
Posted: 4 May 2022 10:16 EDT
Tarun Kumar Reddy Bolla (Tarun Bolla)