I am trying to figure out where this is configured in Pega. I only see the pyGetHealthStatus activity which was used in Pega 7.
Can you help to figure out where this JSON is configured? Also, is there a way to administratively manipulate this information? I want to mark a node as unavailable so a load balancer does not send any additional traffic to that node prior to performing a quiesce via an API call.
***Edited by Moderator Marissa to update platform capability tags; add SR Details****
Thanks. We're using an AWS Classic ELB. However, we don't have full control of our AWS Infrastructure. There is another group in our organization that handles this. I was looking for a way that we could manage it and work with the current Load Balancer rules. We can have them configure the Load Balancer to Deregister an Instance and/or Configure Slow Draining, but since it is managed by another group, we need to put in a ticket to have this completed. We can go down this route if it is the best suggestion.
Do you have any other suggestions on handling this either from an API call, or some other authenticated method in Pega?
Posted: 3 years ago
Posted: 22 Apr 2019 17:20 EDT
Kevin Zheng (KevinZheng_GCS)
Director, Technical Support
When quiescing a node, do you need to de-register the node from the ELB first? When the cookie is invalidated at the LB, is the health of the pingService for that node changed accordingly or could the load balancer send the user back to the same node?