You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/09/14 09:23:02 UTC

[GitHub] [apisix-ingress-controller] chzhuo opened a new issue #682: bug: Informer recursively trigger update event

chzhuo opened a new issue #682:
URL: https://github.com/apache/apisix-ingress-controller/issues/682


   ### Issue description
   Informer recursively trigger `update`,  because  `recordStatus`
   
   ### Environment
   
   apisix-ingress-controller: master branch commit 1e1be7401ba3707ba660a7d61df5118fc5725eff
   k8s server:  v1.19.3
   ### Minimal test code / Steps to reproduce the issue
   
   apisix-ingress-controller config:
   ```yaml
   log_level: "debug"
   kubernetes:
     kubeconfig: /home/chenzhuo/.kube/config
   apisix:
     default_cluster_base_url: "http://10.0.5.14:9080/apisix/admin"
     default_cluster_admin_key: "edd1c9f034335f136f87ad84b625c8f1"
   ```
   open the debug log,  you will see continuously log `ApisixRoute update event arrived`.  I founed that  https://github.com/apache/apisix-ingress-controller/blob/1e1be7401ba3707ba660a7d61df5118fc5725eff/pkg/ingress/status.go#L38  will recursively cause update event
   
   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] chzhuo commented on issue #682: bug: Informer recursively trigger update event

Posted by GitBox <gi...@apache.org>.
chzhuo commented on issue #682:
URL: https://github.com/apache/apisix-ingress-controller/issues/682#issuecomment-919880812


   I think should monitor the length of workqueue and the delay of that event from being received to applying to APISIX admin-API


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #682: bug: Informer recursively trigger update event

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #682:
URL: https://github.com/apache/apisix-ingress-controller/issues/682#issuecomment-919581617


   Thanks! I will try to reproduce locally.
   
   cc @gxthrj @tokers 


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] gxthrj commented on issue #682: bug: Informer recursively trigger update event

Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #682:
URL: https://github.com/apache/apisix-ingress-controller/issues/682#issuecomment-919714740


   I checked the code of `recordStatus`, it will not return an error, and if the `recordStatus` fails, it will not cause a retry.
   
   Please show the status of ApisixRoute by using `kubectl describe xxx`, there will be a message for the error.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] tokers commented on issue #682: bug: Informer recursively trigger update event

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #682:
URL: https://github.com/apache/apisix-ingress-controller/issues/682#issuecomment-919624202


   Good catch, we may ignore status-only changes when the events arriving.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org