Riak — Anatomy of a Request

5. Anatomy of a Request get(“conferences/surge”) client Riak hash(“conferences/oredev”) Get Handler (FSM) == 10, 11, 12 Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 The Ring

6. Anatomy of a Request get(“conferences/surge”) client Riak Get Handler (FSM) get(“conferences/oredev”) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 The Ring

7. Anatomy of a Request get(“conferences/surge”) client Riak R=2 Get Handler (FSM) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 The Ring

8. Anatomy of a Request get(“conferences/surge”) client Riak R=2 v1 Get Handler (FSM) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 The Ring

9. Anatomy of a Request get(“conferences/surge”) client Riak R=2 v1 v2 Get Handler (FSM)

10. Anatomy of a Request get(“conferences/surge”) client v2 Riak R=2 v2 Get Handler (FSM)

11. Anatomy of a Request get(“conferences/surge”) v2

12. Read Repair get(“conferences/surge”) client v2 Riak R=2 v1 v2 Get Handler (FSM) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 v1 v2

13. Read Repair get(“conferences/surge”) client v2 Riak R=2 v2 Get Handler (FSM) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 v1 v2

14. Read Repair get(“conferences/surge”) client v2 Riak R=2 v2 Get Handler (FSM) Coordinating node Cluster 6 7 8 9 10 11 12 13 14 15 16 v1 v1 v2

15. Read Repair get(“conferences/surge”) client v2 Riak R=2 v2 Get Handler (FSM) Coordinating node Cluster v2 v2 6 7 8 9 10 11 12 13 14 15 16 v2 v2 v2

Editor's Notes

1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
1) Client requests a key\n2) Get handler starts up to service the request\n3) Hashes key to its owner partitions (N=3)\n4) Sends similar &#x201C;get&#x201D; request to those partitions\n5) Waits for R replies that concur (R=2)\n6) Resolves the object, replies to client\n7) Third reply may come back at any time, but FSM replies as soon as quorum is satisfied/violated\n
\n
\n
\n
\n
\n
\n
\n
\n
\n

Riak — Anatomy of a Request

Recommended

Recommended

More Related Content

Recently uploaded

Recently uploaded (20)

Featured

Featured (20)

Riak — Anatomy of a Request

Editor's Notes