Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
hz-devops-test opened this issue May 6, 2021 · 1 comment
Labels
Priority: Low to-jira Use to create a placeholder Jira issue in Jira APIs Project

Comments

@hz-devops-test
Copy link

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, ...
@yuce yuce added the to-jira Use to create a placeholder Jira issue in Jira APIs Project label Aug 12, 2022
@github-actions github-actions bot changed the title [TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs [TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs [API-1506] Aug 12, 2022
@github-actions
Copy link

Internal Jira issue: API-1506

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low to-jira Use to create a placeholder Jira issue in Jira APIs Project
Projects
None yet
Development

No branches or pull requests

2 participants