Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
neo
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
Stefane Fermigier
neo
Commits
d14e3e7f
Commit
d14e3e7f
authored
Apr 04, 2018
by
Kirill Smelkov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
.
parent
4000df14
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
TODO
TODO
+3
-3
No files found.
TODO
View file @
d14e3e7f
...
@@ -46,7 +46,7 @@
...
@@ -46,7 +46,7 @@
Storage
Storage
- Use libmysqld instead of a stand-alone MySQL server.
- Use libmysqld instead of a stand-alone MySQL server.
- In backup mode, 2 simultaneous replication should be possible so that:
NOTE
- In backup mode, 2 simultaneous replication should be possible so that:
- outdated cells does not block backup for too long time
- outdated cells does not block backup for too long time
- constantly modified partitions does not prevent outdated cells to
- constantly modified partitions does not prevent outdated cells to
replicate
replicate
...
@@ -60,7 +60,7 @@
...
@@ -60,7 +60,7 @@
not degrade performance for client nodes. But when there's only 1 storage
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
left for a partition, it may be wanted to guarantee a minimum speed to
avoid complete data loss if another failure happens too early.
avoid complete data loss if another failure happens too early.
- Find a way not to always start replication from the beginning. Currently,
NOTE
- Find a way not to always start replication from the beginning. Currently,
a temporarily down nodes can't replicate from where it was interrupted,
a temporarily down nodes can't replicate from where it was interrupted,
which is an issue on big databases. (SPEED)
which is an issue on big databases. (SPEED)
- Pack segmentation & throttling (HIGH AVAILABILITY)
- Pack segmentation & throttling (HIGH AVAILABILITY)
...
@@ -80,7 +80,7 @@
...
@@ -80,7 +80,7 @@
- Check replicas: (HIGH AVAILABILITY)
- Check replicas: (HIGH AVAILABILITY)
- Automatically tell corrupted cells to fix their data when a good source
- Automatically tell corrupted cells to fix their data when a good source
is known.
is known.
- Add an option to also check all rows of trans/obj/data, instead of only
NOTE
- Add an option to also check all rows of trans/obj/data, instead of only
keys (trans.tid & obj.{tid,oid}).
keys (trans.tid & obj.{tid,oid}).
Master
Master
...
...
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