Target servers still takes old values after updating

[ramnath_ananth]

Hi,

We had 4.19.01 multi- region setup and had updated our 2 target servers for one of our deployments.

We saw that the request was still routing to one of the old target servers but the environment configuration had only new values. Could someone explain what could be the reason for taking the old values ?

Appreciate the help

Thanks

Ram

[nagashree_b]

Is this occurring always or occurring as soon as the target server change is made?

If its the latter -

1. In a setup with multiple message processors, there could be a possibility that the changes are not propagated to all the message processors. You may be able to validate it by making multiple calls and observe that some calls are routed to the new target while some are routed to the old target

2. Apigee caches the kvms, target server configs etc internally. These caches are not accessible and cannot be explicitly invalidated. Usually within 180 seconds the values would expire. If the request is sent within this 180 seconds and the changes are not propagated, you might see the requests routing to the old target.

If you are seeing the requests routed to the old target even after 3-4 minutes after the change, it would be good to look at the message processor logs for indications of any errors or warnings.

A message processor restart will often fix the problem, but the restart might not help you determine the cause.