Closed anar-khalilov closed 1 year ago
There a regular poll to each service that checks if the schema has changed, the default period is 10s.
If it is taking longer than that to update I would check the logs to see if it is having trouble talking to the downstream services, as it might be getting stuck there, the schema will stay at the previous seen version until it can complete a poll of the list of services.
We have encountered cases where we make schema modifications in our service and see the changes right away when we query schema in the SERVICE alone, but not in gateway. It behaves like the schema is being cached but it takes a lot of time for a cache to reload (hours sometimes). Is there a cache mechanism and how can we disable it?