Standard agent queue records are going to Broken-Process when we restart the Pega hosts
Hi,
When we deploy new changes to our Prod system, we usually restart the hosts. Here we are observing the Standard agent queue records are going to Broken-Process.
does n't it handle by Pega? By killing all the processes before initiating the restart.
what happens to Standard Agent and Advanced agent processing at the time of restart?
Sometimes, we are stopping all the agents and then do the restart and then start the agents. This is very time consuming which is impacting our deployments.
can anyone help me on this?
***Edited by Moderator Marissa to update categories***
DirecTV
US
@Shivan- Why do you need system restart after every deployment ? I'm not sure about your Pega version and application changes. Code change deployment doesn't need server restart.
Amazon.com Inc
US
Hi Akshay,
We don't restart the Pega server on each deployment unless it has few data pages to refresh, Data base table instances , deploying lot of changes in system.
Also sometimes or the other, we will restart the server right. I wanted to understand how Pega behaves and precaustions we can take to avoid Broken-processes for standard agents.
Currently we face issues with Data-Admin-DB-Table instances and the changes in one host are not reflecting in other hosts. So when we have these instances in product, we are restarting the server. I just found out that we have Hot fix(Link below) for this issue and we will add the hot fix and see the behavior. But still there are occasions where we wanted to restart right.
https://community.pega.com/support/support-articles/db-change-issue-multi-node-system
BTW, we are using Pega7.18 version.