Laksh Singla b82ad59dfe Better logging in ServiceClientImpl (#15269) ... ServiceClientImpl logs the cause of every retry, even though we are retrying the connection attempt. This leads to slight pollution in the logs because a lot of the time, the reason for retrying is the same. This is seen primarily in MSQ, when the worker task hasn't launched yet however controller attempts to connect to the worker task, which can lead to scary-looking messages (with INFO log level), even though they are normal. This PR changes the logging logic to log every 10 (arbitrary number) retries instead of every retry, to reduce the pollution of the logs. Note: If there are no retries left, the client returns an exception, which would get thrown up by the caller, and therefore this change doesn't hide any important information.		2023-11-02 11:32:49 +05:30
..
src	Better logging in ServiceClientImpl (#15269)	2023-11-02 11:32:49 +05:30
pom.xml	Use min of scheduler threads and server threads for subquery guardrails. (#15295)	2023-11-01 22:34:53 -07:00