Scheduler configured to run on "Any one associated node" is running on all nodes
Hi,
Greetings. I have a job scheduler configured to run on "Any one associated node" however it is running on all backgroundprocessing nodes and is causing locks. Is this the expected behaviour?
I am on Pega 8.4.2
Regards,
Bharat
Maantic Inc
US
@MarissaRogers, Could you please route this question to corresponding POC.
We are also facing similar issue V8.5.2
ING Nederland
NL
@KOMARINA Is this happening in all environments or only certain?
Is there any difference between the environments it is operating?
Can someone confirm, please?
Maantic Inc
US
@KC_Janga For us it is happening only in prod. no difference in environment configuration.
Initially we are not had this in prod, it started recently.
Citibank
IN
Hi John Paul Raja, even I am facing this issue. In 8.4 this is not running on all nodes but in 8.6 the job scheduler is running on all available nodes even if the configuration is "Run on any one associated node". Do you have an update on this issue so that we can also solve the issue?
Updated: 13 Jan 2022 11:44 EST
Maantic Inc
US
@AvinashV9782 - this issue occurs because of Split-Brain Syndrome.
Request your admin or corresponding team to restart all the nodes and each node see one another.
split brain syndrome reference doc - https://docs-previous.pega.com/pega-services-troubleshooting/split-brain-syndrome-and-cluster-fracturing-faqs
Additional info : if you are using PDC for monitoring, enable notification for PEGA0108.PDC trigger notification when split brain issue occurs.
Citibank
IN
@JohnPaulRaja,C Thank you so much John Paul Raja. I will check the document you have tagged.
Corporation Service Company
US
@AvinashV9782 @JohnPaulRaja,C We are also facing the same issue in UAT and PROD environments. Do we have any solution for this? We are on Pega 8.6.2
Maantic Inc
US
@AroraPiyush Request your admin or corresponding team to restart all the nodes and each node see one another.