Re: [I] bug: upstream in route domain ip changes not been detected and use the old ip [apisix]

["nic-6443 (via GitHub)" <gi...@apache.org>]

nic-6443 commented on issue #12436:
URL: https://github.com/apache/apisix/issues/12436#issuecomment-4998363014

   Wrapping this up after re-verifying both mechanisms. The original 3.2.x behavior (resolved IPs written back into the cached upstream nodes, so the route never re-resolves until reload) was structurally removed in 3.14.0 by #12607 — DNS results now live in a separate `dns_nodes` snapshot. What was later reported here on 3.14.1 matches the one residual case, #12973: a transient DNS failure freezes `original_nodes`, after which real node changes are treated as no-change. That one is fixed by #13137, already on master and shipping with the next release, expected later this month.
   
   So: upgrading to ≥3.14.0 fixes the behavior reported here, and the transient-failure edge case lands in the next release. Closing.
   


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