Pretty print cluster connect timeout in logs #18648
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clean backport of #18642
The default value for the cluster connect timeout is infinite,
so it is represented with
Long.MAX_VALUE
. When we try to logthis as it is, we output something like below.
To make this more clear, we will replace this with the
output below.
If the user has provided some other timeout value (such as 999 ms),
the output will still be as it is now.