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
Carlos Ramos Carreño
neoppod
Commits
53df0e1a
Commit
53df0e1a
authored
Jul 24, 2014
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
typos
parent
55a60277
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
5 additions
and
6 deletions
+5
-6
README
README
+0
-1
TODO
TODO
+2
-2
neo/storage/handlers/storage.py
neo/storage/handlers/storage.py
+1
-1
neo/storage/replicator.py
neo/storage/replicator.py
+2
-2
No files found.
README
View file @
53df0e1a
...
...
@@ -108,7 +108,6 @@ a. Edit your zope.conf, add a neo import and edit the `zodb_db` section by
%import neo.client
<zodb_db main>
# Main FileStorage database
<NEOStorage>
master_nodes 127.0.0.1:10000
name <cluster name>
...
...
TODO
View file @
53df0e1a
...
...
@@ -94,8 +94,8 @@ RC - Review output of pylint (CODE)
- Make listening address and port optionnal, and if they are not provided
listen on all interfaces on any available port.
- Make replication speed configurable (HIGH AVAILABILITY)
In its current implementation, replication runs at lowest priority,
not
to
degrades
performance for client nodes. But when there's only 1 storage
In its current implementation, replication runs at lowest priority, to
not degrade
performance for client nodes. But when there's only 1 storage
left for a partition, it may be wanted to guarantee a minimum speed to
avoid complete data loss if another failure happens too early.
- Pack segmentation & throttling (HIGH AVAILABILITY)
...
...
neo/storage/handlers/storage.py
View file @
53df0e1a
...
...
@@ -77,7 +77,7 @@ class StorageOperationHandler(EventHandler):
deleteTransaction
(
tid
)
assert
not
pack_tid
,
"TODO"
if
next_tid
:
# More than one chunk ? This could a full replication so avoid
# More than one chunk ? This could
be
a full replication so avoid
# restarting from the beginning by committing now.
self
.
app
.
dm
.
commit
()
self
.
app
.
replicator
.
fetchTransactions
(
next_tid
)
...
...
neo/storage/replicator.py
View file @
53df0e1a
...
...
@@ -47,7 +47,7 @@ Replication is partial, starting from the greatest stored tid in the partition:
There is no check that item values on both nodes matches.
TODO: Packing and replication currently fail when the
n
happen at the same time.
TODO: Packing and replication currently fail when the
y
happen at the same time.
"""
import
random
...
...
@@ -228,7 +228,7 @@ class Replicator(object):
app
=
self
.
app
# 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
.
# cells.
for
offset
in
self
.
replicate_dict
:
if
not
self
.
partition_dict
[
offset
].
max_ttid
:
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