AlinsRan commented on issue #2708: URL: https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-3848565194
> How can I reduce the interval? Endpoint updates will also immediately trigger synchronization. https://github.com/apache/apisix-helm-chart/blob/7e5b8dff478dcc86373d6bd9071ab5444c97602b/charts/apisix-ingress-controller/values.yaml#L96 > INFO provider.client client/client.go:177 syncing all resources It indicates that the synchronization is in progress, not that it has been completed successfully. If the synchronization succeeds, APISIX should not retain IPs of Pods that have already been deleted. > use of Upstream health-checks Using health check ups can alleviate this issue. > socket hang up I think you can solve this problem first and then continue to observe. > It recovers after restarting the apisix deployment. What I find confusing is why restarting APISIX resolves the issue, whereas restarting apisix-ingress-controller does not. This seems to suggest that the problem may not be solely on the controller side. To better understand the situation, could you please share more details about your deployment? * How many APISIX Pods are running? * Are there any CPU or memory limits configured for APISIX or apisix-ingress-controller? * Have you observed the CPU and memory usage of both APISIX and apisix-ingress-controller around the time when the issue occurs? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
