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.

Sign up for GitHub

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

Jump to bottom

Use latest documentation version link #162

Merged
merged 1 commit into from
Jul 9, 2024
Merged

Use latest documentation version link #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion upgrade-guides/v4.0-v5.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ version of hazelcast-wm.

In Hazelcast Platform 5.x, Hazelcast clients now default to indefinite cluster connect timeout where previously
this timeout was 20 seconds. This is important for hazelcast-wm usage - for more info, see
[this page](https://docs.hazelcast.com/hazelcast/5.4/clients/java#configuring-client-connection-retry)
[this page](https://docs.hazelcast.com/hazelcast/latest/clients/java#configuring-client-connection-retry)
or follow the guidance below to restore this setting.

To preserve a 20 second cluster timeout in Hazelcast 5.x clients, add the following entry to your
Expand Down
Loading