[TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs [API-2031] #461
Labels
Jira
Creates a corresp. Jira issue in the APIs project.
Source: Tracking
Originated from the Tracking bot.
Comments
github-actions
bot
changed the title
|
Internal Jira issue: API-2031 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tracking issue for the Java side PR.
See hazelcast/hazelcast#18642 for details.
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.
The text was updated successfully, but these errors were encountered: