Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neoppod
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Levin Zimmermann
neoppod
Commits
6c35f692
Commit
6c35f692
authored
Jan 23, 2018
by
Kirill Smelkov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
.
parent
d228eacd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
46 additions
and
0 deletions
+46
-0
go/NOTES
go/NOTES
+46
-0
No files found.
go/NOTES
View file @
6c35f692
...
@@ -350,6 +350,52 @@ PACKET x #0x0003 GetObject > S1 (127.0.0.1:4452
...
@@ -350,6 +350,52 @@ PACKET x #0x0003 GetObject > S1 (127.0.0.1:4452
...
...
Replication communication
-------------------------
replication types:
- asynchronous (e.g. to backup cluster or to replicate already committed data to newly added storage node)
- synchronous (on transaction commit - C stores data to all S assigned for
oid in PT and waits for all stores to complete)
XXX synchronous replication interracts with commit.
XXX "OUT_OF_DATE -> UP_TO_DATE is done in several steps" -> XXX which?
XXX
""" A replicating node can not depend on other nodes to fetch the data
recently/being committed because that can not be done atomically: it could miss
writes between the processing of its request by a source node and the reception
of the answer. """
XXX -> should not be the case with proper dump-stream based replication protocol.
XXX -> jm: document example
Therefore, outdated cells are writable: a storage node asks the master for
transactions being committed and then it is expected to fully receive from the
client any transaction that is started after this answer.
XXX -> recheck this is good idea.
R = requester
S = seeder
item = Transaction(meta) | Object(meta+data)
R -> S []items (which R already has) XXX exact message
R <- S missing-item
R <- S missing-item
...
R <- S missing-item
R <- S []items-to-delete
Py: out-of-order answers
Py: out-of-order answers
------------------------
------------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment