Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit4c776e1

Browse files
committed
Split raftable into modules to make sources more managable.
1 parentd1698fc commit4c776e1

File tree

7 files changed

+950
-862
lines changed

7 files changed

+950
-862
lines changed

‎contrib/raftable/Makefile‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
MODULES = raftable
1+
MODULES = raftable worker blockmem state
22
EXTENSION = raftable
33
DATA = raftable--1.0.sql
44

‎contrib/raftable/README‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,8 @@ When 'frontend' issues a read command, the 'backend' returns the data from the
99
local replica of the 'state' which is in the shared memory of current instance.
1010

1111
When 'frontend' issues a write command, the 'backend' connects to the current
12-
'raftable' leader directly through TCP. Raftable leader returns the state
13-
version number V after the update gets applied (acked by the majority of
14-
'raftable' workers). Then the backend waits until the local state version
15-
number becomes at least V and returns 'ok' to the frontend.
12+
'raftable' leader directly through TCP and sends an update. Raftable leader
13+
returns 'ok' to the backend when the update gets applied on current instance.
1614

1715
The backend can also issue commands to itself through C API.
1816

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp