[PR] fix: health checker can't be released due to health parent being rele… [apisix]

["Revolyssup (via GitHub)" <gi...@apache.org>]

Revolyssup opened a new pull request, #11760:
URL: https://github.com/apache/apisix/pull/11760

   When a client requests, if the currently hit route or the corresponding upstream changes again, APISIX will try to re-create the health check checker for the upstream of the currently hit route and release the original health check checker.
   
   During the process of re-creating the health check checker, when each upstream node is added as the target of the health check, the locking operation may take a long time to execute.
   
   If the process of creating a health check checker is relatively long, and the route or the corresponding upstream changes at the same time, the parent of the upstream has been released, and in the previous step, the re-created healthcheck checker will be added to an empty object (the original intention is to Added to the new upstream parent), the checker can't be released, resulting in an "orphan" checker, which always performs health checks on the old nodes.


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

Re: [PR] fix: the health checker can't be released due to the health parent being released early [apisix]

["Revolyssup (via GitHub)" <gi...@apache.org>]

Revolyssup merged PR #11760:
URL: https://github.com/apache/apisix/pull/11760


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