Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZODB
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
nexedi
ZODB
Commits
6d3df193
Commit
6d3df193
authored
Oct 12, 2014
by
Chris McDonough
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #6 from mgrbyte/master
Update multi-zodb-gc.rst
parents
5ed3779f
5e879bbc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
documentation/articles/multi-zodb-gc.rst
documentation/articles/multi-zodb-gc.rst
+3
-3
No files found.
documentation/articles/multi-zodb-gc.rst
View file @
6d3df193
...
@@ -84,7 +84,7 @@ Garbage collection
...
@@ -84,7 +84,7 @@ Garbage collection
------------------
------------------
We configured the ZEO server to skip garbage collection as part of the normal
We configured the ZEO server to skip garbage collection as part of the normal
pack in the abo
c
e config (`pack-gc = false`). Instead we use explicit garbage
pack in the abo
v
e config (`pack-gc = false`). Instead we use explicit garbage
collection via a different job::
collection via a different job::
bin/multi-zodb-gc etc/zeo.conf
bin/multi-zodb-gc etc/zeo.conf
...
@@ -112,13 +112,13 @@ Reference analysis and POSKeyErrors
...
@@ -112,13 +112,13 @@ Reference analysis and POSKeyErrors
If our database has any POSKeyErrors, we can find and repair those.
If our database has any POSKeyErrors, we can find and repair those.
Either we already have the oid
's of lost objects
or we can check the entire
Either we already have the oid
s of lost objects,
or we can check the entire
database for any errors. To check everything we run the following command::
database for any errors. To check everything we run the following command::
$ bin/multi-zodb-check-refs etc/zeo.conf
$ bin/multi-zodb-check-refs etc/zeo.conf
This can take about 15 to 30 minutes on moderately sized databases of up to
This can take about 15 to 30 minutes on moderately sized databases of up to
10gb
but depends
on disk speed. We'll write down the reported errors, as we'll
10gb
, dependent
on disk speed. We'll write down the reported errors, as we'll
need them later on to analyze them.
need them later on to analyze them.
If there are any lost objects, we can create a reference database to make it
If there are any lost objects, we can create a reference database to make it
...
...
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