Inicio Explorar Ayuda
Iniciar sesión
ditsing
/
ruaft
1
0
Fork 0
Archivos Incidencias 0 Pull Requests 0 Wiki
Árbol: c6d3ce06f3
Ramas Etiquetas
ruaft
/
durio
Jing Yang bca6f94695 Upgrade durio to the new storage system. hace 2 años
..
src bca6f94695 Upgrade durio to the new storage system. hace 2 años
Cargo.lock d437abc009 Update Cargo.lock in durio. hace 2 años
Cargo.toml c8fa496d8a Move durio to its own workspace. hace 3 años
README.md 27abdaee17 Add a README for durio. hace 4 años
build.sh 847feb248e Fix durio build after the project structure change. hace 2 años
curl.sh f3059b79ff Create a two-pi-plus-dev setup for durio. hace 4 años
pi-setup-notes.md b551bac311 Add Pi setup instructions. hace 4 años
run_smoke_test.sh 8bc2df1990 Remove test logger from durio. hace 3 años
setup-build-debian.sh 4d0f07bc7e Add a script to prepare a debian machine to cross build durio. hace 2 años

README.md

durio

durio is a distributed KV store that comes with a simple HTTP interface. I run it on Raspberry Pis. In this repo you can find scripts (build.sh, curl.sh) and notes (pi-setup-notes) to help build, run and test durio on Raspberry Pis.

By default durio has 3 replicas. Each replica has a web server, a KV server and a raft instance behind it. The 3 web servers talk to all KV servers, while each KV server only talks to the raft instance in the same process.

durio relies on warp to provide the web server, and tarpc to run the RPC services.

Clients

Clients connected to one web server get a consistent (linearizable) view of the data stored in the KV store. The web servers can accept multiple incoming requests. At any given time, at most one request will be sent to the leading KV server. That limits the amount of data one web server can process.