Exposed columns does not reflect across all nodes
Hi,
Greetings. Hope you are doing well! I am on Pega 8.7.0 and deployed a code which has a column exposed on a table to target environment. This exposed column is not reflected across all nodes in a cluster, example, this works on the node from which the deployment has been done but when users try to create cases which are logged onto other node, they get a commit error complaining on this exposed column. A restart of the cluster had resolved the issue but i want to know if there are other options that we should consider without a down-time to the end users?
Regards,
Bharat
Capgemini
IN
Hi Komarina,
Basically these types of issues come while nodes are not in synch.so definitely restart will needed to overcome the issue.
IQZ Systems
US
@KOMARINA DB connection needs to reset for Pega to know newly exposed column. Pega restart does the job.
Another option is to reset the connection without server restart (this may need to be performed on each every node) is
- Open database table instance in which you exposed new column
- Save the instance
- Test connectivity
For eg; exposing new column in assign work list tables will need a save instance & test connectivity
Accenture
GB
@Byshu_Ayyappaswamy Sure, that is the problem, I am on a load balancer and it is hard to logon to specific nodes. I thought there might be another alternatives.
Regards,
Bharat
Accenture
GB
JPMorgan Chase
IN
@KOMARINA This issue of in-correct cache also happens when your hazel cast is not functioning right.
Check the health of your hazel cast and apply rolling restart of your nodes.