Troubleshooting issue with HttpNettyClient in DataHub regarding connection pooling and DNS resolution cache

Original Slack Thread

I see datahub using HttpNettyClient to make requests to gms but it always make requests to the first inetaddress return by dns resolver and cache the inetaddress forever without using the second inetaddress if gms replicas is 2. I think this might be caused by connection pool. Is there a way to turn off keep alive or set connection ttl?

I know people can do it on httpcomponents.httpclient but not sure about HttpNettyClient .

Hey there! :wave: Make sure your message includes the following information if relevant, so we can help more effectively!

  1. Which DataHub version are you using? (e.g. 0.12.0)
  2. Please post any relevant error logs on the thread!