search

hazelcast / hazelcast-csharp-client

Hazelcast .NET Client
https://hazelcast.com/clients/dotnet/
Apache License 2.0
102 stars 49 forks source link

[TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs [API-2031] #461

Open hz-devops-test opened 3 years ago

hz-devops-test commented 3 years ago

The tracking issue for the Java side PR.

See https://github.com/hazelcast/hazelcast/pull/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 log this as it is, we output something like below.

... cluster connect timeout: 9223372036854775807 ms, ...

To make this more clear, we will replace this with the output below.

... cluster connect timeout: INFINITE, ...

If the user has provided some other timeout value (such as 999 ms), the output will still be as it is now.

... cluster connect timeout: 999 ms, ...
github-actions[bot] commented 1 year ago

Internal Jira issue: API-2031