5 releases (3 breaking)

0.4.0 Nov 1, 2024
0.3.0 Jul 12, 2024
0.2.0 May 10, 2024
0.1.1 Apr 18, 2024
0.1.0 Feb 28, 2024

#1998 in Algorithms

Download history 652/week @ 2024-08-05 750/week @ 2024-08-12 931/week @ 2024-08-19 660/week @ 2024-08-26 705/week @ 2024-09-02 575/week @ 2024-09-09 2121/week @ 2024-09-16 4919/week @ 2024-09-23 6573/week @ 2024-09-30 4099/week @ 2024-10-07 7266/week @ 2024-10-14 5981/week @ 2024-10-21 8307/week @ 2024-10-28 11235/week @ 2024-11-04 6406/week @ 2024-11-11 11599/week @ 2024-11-18

38,481 downloads per month
Used in 12 crates (via pingora-load-balancing)

Apache-2.0

44KB
303 lines

pingora-ketama

A Rust port of the nginx consistent hashing algorithm.

This crate provides a consistent hashing algorithm which is identical in behavior to nginx consistent hashing.

Using a consistent hash strategy like this is useful when one wants to minimize the amount of requests that need to be rehashed to different nodes when a node is added or removed.

Here's a simple example of how one might use it:

use pingora_ketama::{Bucket, Continuum};

fn main() {
    // Set up a continuum with a few nodes of various weight.
    let mut buckets = vec![];
    buckets.push(Bucket::new("127.0.0.1:12345".parse().unwrap(), 1));
    buckets.push(Bucket::new("127.0.0.2:12345".parse().unwrap(), 2));
    buckets.push(Bucket::new("127.0.0.3:12345".parse().unwrap(), 3));
    let ring = Continuum::new(&buckets);

    // Let's see what the result is for a few keys:
    for key in &["some_key", "another_key", "last_key"] {
        let node = ring.node(key.as_bytes()).unwrap();
        println!("{}: {}:{}", key, node.ip(), node.port());
    }
}
# Output:
some_key: 127.0.0.3:12345
another_key: 127.0.0.3:12345
last_key: 127.0.0.2:12345

We've provided a health-aware example in pingora-ketama/examples/health_aware_selector.rs.

For a carefully crafted real-world example, see the pingora-load-balancing crate.

Dependencies

~78KB