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
Ivan Tyagov
neoppod
Commits
dd556379
Commit
dd556379
authored
Aug 20, 2012
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Comment about backup limitations
parent
8832bd42
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
10 additions
and
0 deletions
+10
-0
TODO
TODO
+5
-0
neo/master/backup_app.py
neo/master/backup_app.py
+3
-0
neo/storage/replicator.py
neo/storage/replicator.py
+2
-0
No files found.
TODO
View file @
dd556379
...
@@ -85,6 +85,11 @@ RC - Review output of pylint (CODE)
...
@@ -85,6 +85,11 @@ RC - Review output of pylint (CODE)
Currently, storage presence is broadcasted to client nodes too early, as
Currently, storage presence is broadcasted to client nodes too early, as
the storage node would refuse them until it has only up-to-date data (not
the storage node would refuse them until it has only up-to-date data (not
only up-to-date cells, but also a partition table and node states).
only up-to-date cells, but also a partition table and node states).
- In backup mode, 2 simultaneous replication should be possible so that:
- outdated cells does not block backup for too long time
- constantly modified partitions does not prevent outdated cells to
replicate
Current behaviour is undefined and the above 2 scenarios may happen.
- Create a specialized PartitionTable that know the database and replicator
- Create a specialized PartitionTable that know the database and replicator
to remove duplicates and remove logic from handlers (CODE)
to remove duplicates and remove logic from handlers (CODE)
- Consider insert multiple objects at time in the database, with taking care
- Consider insert multiple objects at time in the database, with taking care
...
...
neo/master/backup_app.py
View file @
dd556379
...
@@ -141,6 +141,9 @@ class BackupApplication(object):
...
@@ -141,6 +141,9 @@ class BackupApplication(object):
tid
=
app
.
backup_tid
tid
=
app
.
backup_tid
# Wait for non-primary partitions to catch up,
# Wait for non-primary partitions to catch up,
# so that all UP_TO_DATE cells are really UP_TO_DATE.
# so that all UP_TO_DATE cells are really UP_TO_DATE.
# XXX: Another possibility could be to outdate such cells, and
# they would be quickly updated at the beginning of the
# RUNNING phase. This may simplify code.
# Any unfinished replication from upstream will be truncated.
# Any unfinished replication from upstream will be truncated.
while
pt
.
getCheckTid
(
xrange
(
pt
.
getPartitions
()))
<
tid
:
while
pt
.
getCheckTid
(
xrange
(
pt
.
getPartitions
()))
<
tid
:
poll
(
1
)
poll
(
1
)
...
...
neo/storage/replicator.py
View file @
dd556379
...
@@ -227,6 +227,8 @@ class Replicator(object):
...
@@ -227,6 +227,8 @@ class Replicator(object):
return
return
app
=
self
.
app
app
=
self
.
app
# Choose a partition with no unfinished transaction if possible.
# Choose a partition with no unfinished transaction if possible.
# XXX: When leaving backup mode, we should only consider UP_TO_DATE
# cells when leaving backup mode.
for
offset
in
self
.
replicate_dict
:
for
offset
in
self
.
replicate_dict
:
if
not
self
.
partition_dict
[
offset
].
max_ttid
:
if
not
self
.
partition_dict
[
offset
].
max_ttid
:
break
break
...
...
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