Skip to content

Conversation

mdumandag
Copy link
Contributor

Before this change, we were logging the cluster connect timeout
as it is. Its default value is equal to sys.maxsize, so the
logs were like

... cluster connect timeout: 92233720368547758067s ...

We now output INFINITE for the default value.

... cluster connect timeout: INFINITE

If the user provides a different value, it will be printed
as it is now.

Closes #404

Before this change, we were logging the cluster connect timeout
as it is. Its default value is equal to `sys.maxsize`, so the
logs were like

```
... cluster connect timeout: 92233720368547758067s ...
```

We now output `INFINITE` for the default value.

```
... cluster connect timeout: INFINITE
```

If the user provides a different value, it will be printed
as it is now.
@mdumandag mdumandag added this to the 4.2 milestone May 6, 2021
@mdumandag mdumandag self-assigned this May 6, 2021
@mdumandag mdumandag requested a review from yuce May 10, 2021 07:32
Copy link
Contributor

@yuce yuce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

Copy link
Contributor

@yuce yuce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM

@mdumandag mdumandag merged commit 464b2d3 into hazelcast:master May 10, 2021
@mdumandag mdumandag deleted the timeout-logging branch May 10, 2021 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs
3 participants