On Sun, Aug 21, 2022 at 10:32 AM Staniel Yao <yaolixin...@gmail.com> wrote:
> I think it's because the MAX_CONNECTION_AGE is only affecting the > connection between Nginx and backend and doesn't affect the client > connection to Nginx itself. Am I right on this? > Correct. The necessary configuration would be in nginx. I also try to tune some Nginx config map value such as keep-alive > <https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#keep-alive> > but it's also not helping. > I'd expect keep-alive or keep-alive-requests to help. Maybe you are using an older version of nginx before they got rid of the http2-specific configuration? So in summary, I would like to get some suggestion to understand: > 1: Why my client switch DNS every other *83* mins? It seems a weird magic > number as I can not find anything related. > I have to imagine that is related to nginx cycling the connection after 10k requests. Multiply 83 minutes by an estimated queries per minute and maybe it will make more sense. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oMs-6R2_%2BZNwxe7PfxnLu8W5kLjLyi6YJTk6N3p8bJf1w%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature
