Revolyssup commented on issue #10093: URL: https://github.com/apache/apisix/issues/10093#issuecomment-2205464786
> [#10093 (comment)](https://github.com/apache/apisix/issues/10093#issue-1869257753) > > ``` > The requests will be all fail, while the dns resolution not ok failed to parse domain: test.com, error: failed to query the DNS server: dns client error: 101 empty record received; > > But when the dns server is stable, the dns resolution of apisix did not resume immediately, the requests got error [lua] init.lua:486: handle_upstream(): failed to set upstream: no valid upstream node for hours, until we do apisix reload, the dns turns ok. > ``` > > It’s always showing a 503 error even if the DNS is okay. I think there may be some cache that makes APISIX unaware of the DNS resume. @wklken I meant to ask the behavior in your patch. After your patch, you do not get the 503 after dns server resumes. Right? -- 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]
