[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #822: bug: CRD and Endpoint watch performance

[GitBox <gi...@apache.org>]

tao12345666333 commented on issue #822:
URL: https://github.com/apache/apisix-ingress-controller/issues/822#issuecomment-1005373609


   After discussing with @crazyMonkey1995 , he is currently encountering the following problems:
   
   * He encountered some 502 errors during rolling updates of a large number of instances. (No health check is configured)  The main focus here is that the endpoint update is not fast enough. 
   
       * I think there are two pieces of information that need attention.
   
           1. The health check is very helpful for Apache APISIX to remove nodes in time;
           2. In #760, we have fixed the usage of workqueue and no longer limit the flow, so that the endpoint can be updated more quickly
   
       * action item:
           
           1. Perform stress testing to cover this scenario. @tao12345666333 
   
   * The problem of APISIX Ingress controller  resource limiting.
       * #760 It can solve this problem and has been released in v1.4.
   
   * In the single-instance APISIX scenario, APISIX Ingress controller cannot re-establish a connection with the dead apisix
       * https://github.com/apache/apisix-ingress-controller/pull/774  It can solve this problem and has been released in v1.4.


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