From 42b1f44d84d765154f7e5cfacb90c00980aba793 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Wed, 24 Nov 2021 13:41:25 +0100 Subject: [PATCH] docs: add note about Unleash using MurmurHash for stickiness. --- website/docs/advanced/stickiness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/stickiness.md b/website/docs/advanced/stickiness.md index 55dddd60c0..65ca93c8e3 100644 --- a/website/docs/advanced/stickiness.md +++ b/website/docs/advanced/stickiness.md @@ -7,7 +7,7 @@ _Stickiness_ is how Unleash guarantees that the same user gets the same features ## Calculation -By default, Unleash calculates stickiness based on the user id and the group id. If the user id is unavailable, it falls back to using the session id instead. It hashes these values to a number between 0 and 100. This number is what determines whether a user will see a specific feature or variant. Because the process is deterministic, the same user will always get the same number. +By default, Unleash calculates stickiness based on the user id and the group id. If the user id is unavailable, it falls back to using the session id instead. It hashes these values to a number between 0 and 100 using the [MurmurHash hash function](https://en.wikipedia.org/wiki/MurmurHash). This number is what determines whether a user will see a specific feature or variant. Because the process is deterministic, the same user will always get the same number. If both the user id and the session id is unavailable, the calculation returns a random value and stickiness is not guaranteed.