Skip to content

[TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs #404

@hz-devops-test

Description

@hz-devops-test

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 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, ...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions