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

[PLAT-305, API-468] Pretty print cluster connect timeout in logs #18642

Merged
merged 1 commit into from May 6, 2021

Conversation

mdumandag
Copy link
Contributor

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

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, ...
```
@srknzl
Copy link
Member

srknzl commented May 6, 2021

run-lab-run

@mdumandag
Copy link
Contributor Author

unrelated test failure reported on #18644

@mdumandag
Copy link
Contributor Author

run-lab-run

@hz-devops-test
Copy link

The job Hazelcast-pr-builder of your PR failed. (Hazelcast internal details: build log, artifacts).
Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log file
--------------------------
-------TEST FAILURE-------
--------------------------
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   MetricsTest.availableViaJmx:422 name: total not published
[INFO] 
[ERROR] Tests run: 38321, Failures: 1, Errors: 0, Skipped: 995
[INFO] 

[ERROR] There are test failures.

@mdumandag
Copy link
Contributor Author

One more unrelated test failure that is already reported #18626

@mdumandag
Copy link
Contributor Author

run-lab-run

@mdumandag mdumandag merged commit ae1e4a7 into hazelcast:master May 6, 2021
@mdumandag mdumandag deleted the timeout-logging branch May 6, 2021 10:13
@degerhz degerhz changed the title [PLAT-305] Pretty print cluster connect timeout in logs [PLAT-305, API-468] Pretty print cluster connect timeout in logs May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
All Languages Should Check Used by clients team to track fixes on the java client that should potentially backported to others Source: Internal PR or issue was opened by an employee Team: Client Type: Enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants