Skip to content

Remove the FencedLock image link #843

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

Merged
yuce merged 2 commits into from
Oct 27, 2026
Merged

Remove the FencedLock image link #843

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92c0b59
Remove the FencedLock image link
yuce Oct 27, 2026
aa0f8af
Remove the StackOverflow link
yuce Oct 27, 2026
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
1 change: 0 additions & 1 deletion docs/securing_client_connection.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,6 @@ configuration and then go over the configuration options one by one:

``open /Applications/Python\ 3.9/Install\ Certificates.command``

See this `StackOverflow answer <https://stackoverflow.com/a/62374703>`__ for more information.

Enabling TLS/SSL
^^^^^^^^^^^^^^^^
Expand Down
5 changes: 0 additions & 5 deletions docs/using_python_client_with_hazelcast.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -808,11 +808,6 @@ After that, once Client-1 comes back alive, its write request will be
rejected by the external service, and only Client-2 will be able to
safely talk to it.

.. figure:: https://docs.hazelcast.com/hazelcast/latest/_images/FencedLock.png
:alt: CP Fenced Lock diagram

CP Fenced Lock diagram

You can read more about the fencing token idea in Martin Kleppmann’s
“How to do distributed locking” blog post and Google’s Chubby paper.

Expand Down
Loading