vortegatorres commented on issue #2708:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-3852697800

   > Using health check ups can alleviate this issue.
   
   I will try this then.
   
   > I think you can solve this problem first and then continue to observe.
   
   I applied the fix defined in that issue, and the number of errors dropped 
drastically, but still it see few of these errors:
   ```
   2026-02-05 11:29:27.240 error 2026-02-05T10:29:27.240Z       ERROR   
provider        apisix/provider.go:282  failed to sync  {"error": "failed to 
sync 1 configs: GatewayProxy/<REDACTED>/apisix-config"}
   
   2026-02-05 11:29:27.238 error 2026-02-05T10:29:27.238Z       ERROR   
provider.client client/client.go:210    failed to sync resources        
{"name": "GatewayProxy/<REDACTED>/apisix-config", "error": "ADC execution 
errors: [ADC execution error for GatewayProxy/<REDACTED>/apisix-config: 
[ServerAddr: 
http://<SERVER_1>:9180,http://<SERVER_2>:9180,http://<SERVER_3>:9180,http://<SERVER_4>:9180,http://<SERVER_5>:9180,
 Err: connect ECONNREFUSED <SERVER_5>:9180]]"}
   
   2026-02-05 11:29:27.238 error 2026-02-05T10:29:27.238Z       ERROR   
provider.client client/client.go:269    failed to execute adc command   
{"config": 
{"name":"GatewayProxy/<REDACTED>/apisix-config","serverAddrs":["http://<SERVER_1>:9180","http://<SERVER_2>:9180","http://<SERVER_3>:9180","http://<SERVER_4>:9180","http://<SERVER_5>:9180"],"tlsVerify":false},
 "error": "ADC execution error for GatewayProxy/<REDACTED>/apisix-config: 
[ServerAddr: 
http://<SERVER_1>:9180,http://<SERVER_2>:9180,http://<SERVER_3>:9180,http://<SERVER_4>:9180,http://<SERVER_5>:9180,
 Err: connect ECONNREFUSED <SERVER_5>:9180]"}
   
   2026-02-05 11:29:27.238 error 2026-02-05T10:29:27.238Z       ERROR   
provider.executor       client/executor.go:142  failed to run http sync for 
server      {"server": 
"http://<SERVER_1>:9180,http://<SERVER_2>:9180,http://<SERVER_3>:9180,http://<SERVER_4>:9180,http://<SERVER_5>:9180",
 "error": "ServerAddr: 
http://<SERVER_1>:9180,http://<SERVER_2>:9180,http://<SERVER_3>:9180,http://<SERVER_4>:9180,http://<SERVER_5>:9180,
 Err: connect ECONNREFUSED <SERVER_5>:9180"}
   
   2026-02-05 11:29:27.238 error 2026-02-05T10:29:27.237Z       ERROR   
provider.executor       client/executor.go:328  ADC Server sync failed  
{"result": 
{"status":"partial_failure","total_resources":5,"success_count":4,"failed_count":1,"success":[{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"0001-01-01T00:00:00Z","synced_at":"2026-02-05T10:29:23Z","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"0001-01-01T00:00:00Z","synced_at":"2026-02-05T10:29:23Z","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"0001-01-01T00:00:00Z","synced_at":"2026-02-05T10:29:23Z","response":{"status":0,"headers":null}},{"event":{"resourceType":"","type":"","resourceId":"","resourceName":""},"failed_at":"0001-01-01T00:00:00Z","synced_at":"2026-02-05T10:29:23Z","response":{"status":0,"headers":null}}],"failed":[{"event":{"resourceTyp
 
e":"","type":"","resourceId":"","resourceName":""},"failed_at":"2026-02-05T10:29:27.237Z","synced_at":"0001-01-01T00:00:00Z","reason":"connect
 ECONNREFUSED <SERVER_5>:9180","response":{"status":0,"headers":null}}]}, 
"error": "ADC Server sync failed: connect ECONNREFUSED <SERVER_5>:9180"}
   ```
   
   > How many APISIX Pods are running?
   
   Between 4 and 15.
   
   > 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?
   
   Yes, we have limits, but during the incidents, the CPU and memory usages 
were very low.
   
   


-- 
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]

Reply via email to