| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(dns): resolv.conf options timeout: 0 is ignored (#12640) ### Summary The `options timeout: 0` has a specific meaning in `resolv.conf`. It means that the request will be sent to all nameservers without waiting and whoever answers first, will be accepted. In Kong the `options timeout: 0` cause actually all the DNS queries themselves to timeout. This is bad as some platforms tend to follow `options timeout: 0` as a good practice when having more than one resolver. Kong should in future support parallel thread based resolving from multiple resolvers, but first we need to get this fix to stop it causing issues. Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com> | 2 年前 | |
fix(dns): eliminate asynchronous timer in `syncQuery()` to prevent deadlock risk (#11900) * Revert "fix(conf): set default value of `dns_no_sync` to `on` (#11869)" This reverts commit 3be2513a60b9f5f0a89631ff17c202e6113981c0. * fix(dns): introduce the synchronous query in syncQuery() to prevent hang risk Originally the first request to `syncQuery()` will trigger an asynchronous timer event, which added the risk of thread pool hanging. With this patch, cold synchronously DNS query will always happen in the current thread if current phase supports yielding. Fix FTI-5348 --------- Co-authored-by: Datong Sun <datong.sun@konghq.com> | 2 年前 | |
style(tests): reindex Test::Nginx tests (#13187) ### Summary Just reindex Test::Nginx tests with `reindex` found at: https://github.com/openresty/openresty-devel-utils/blob/master/reindex Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com> | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 |