You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by am...@apache.org on 2016/12/15 03:40:57 UTC
svn commit: r1774363 -
/jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md
Author: amitj
Date: Thu Dec 15 03:40:57 2016
New Revision: 1774363
URL: http://svn.apache.org/viewvc?rev=1774363&view=rev
Log:
OAK-301: Minor formatting change for blobstore
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md?rev=1774363&r1=1774362&r2=1774363&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/plugins/blobstore.md Thu Dec 15 03:40:57 2016
@@ -164,9 +164,10 @@ The details of the process are as follow
* All the references are collected in the DataStore in a file with the format `references-[repository-id]`
(e.g. references-988373a0-3efb-451e-ab4c-f7e794189273).
* One completion of the above process on all repositories, the sweep phase needs to be triggered.
- * This can be executed by running `MarkSweepGarbageCollector#collectGarbage(false)` on one of the repositories,
+ * This can be executed by running `MarkSweepGarbageCollector#collectGarbage(false)` on one of the repositories,
where false indicates to run sweep also.
- * The sweep process checks for availability of the references file from all registered repositories and aborts otherwise.
+ * The sweep process checks for availability of the references file from all registered repositories and aborts
+ otherwise.
* All the references available are collected.
* All the blobs available in the DataStore are collected and deletion candidates identified by calculating all the
blobs available not appearing in the blobs referenced. Only blobs older than a specified time interval from the
@@ -182,7 +183,8 @@ The shared DataStore garbage collection
The status of the GC operations on all the repositories connected to the DataStore can be checked by calling:
-* `MarkSweepGarbageCollector#getStats()` which returns a list of `GarbageCollectionRepoStats` objects having the following fields:
+* `MarkSweepGarbageCollector#getStats()` which returns a list of `GarbageCollectionRepoStats` objects having the
+following fields:
* repositoryId - The repositoryId of the repository
* local - Indicates whether the repositoryId is of local instance where the operation ran
* startTime - Start time of the mark operation on the repository
@@ -191,10 +193,12 @@ The status of the GC operations on all t
* numLines - Number of references available
* If the MBeans are registered in the MBeanServer then the following can also be used to retrieve the status:
* `BlobGC#getBlobGCStatus()` which returns a CompositeData with the above fields.
-
-This operation can also be used to ascertain when the 'Mark' phase has executed successfully on all the repositories, as part of the steps to automate the GC in the Shared DataStore configuration.
+
+This operation can also be used to ascertain when the 'Mark' phase has executed successfully on all the repositories,
+ as part of the steps to automate GC in the Shared DataStore configuration.
It should be a sufficient condition to check that the references file is available on all repositories.
-If the server running Oak has remote JMX connection enabled the following code example can be used to connect remotely and check if the mark phase has concluded on all repository instances.
+If the server running Oak has remote JMX connection enabled the following code example can be used to connect
+remotely and check if the mark phase has concluded on all repository instances.
```java
@@ -263,20 +267,21 @@ public class GetGCStats {
```
#### Consistency Check
-The data store consistency check will report any data store binaries that are missing but are still referenced. The consistency check can be triggered by:
+The data store consistency check will report any data store binaries that are missing but are still referenced. The
+consistency check can be triggered by:
* `MarkSweepGarbageCollector#checkConsistency`
* If the MBeans are registered in the MBeanServer then the following can also be used:
* `BlobGCMbean#checkConsistency`
-After the consistency check is complete, a message will show the number of binaries reported as missing. If the number is greater than 0, check the logs configured for `org.apache.jackrabbit.oak.plugins.blob.MarkSweepGarbageCollector` for more details on the missing binaries.
+After the consistency check is complete, a message will show the number of binaries reported as missing. If the
+number is greater than 0, check the logs configured for `org.apache.jackrabbit.oak.plugins.blob
+.MarkSweepGarbageCollector` for more details on the missing binaries.
Below is an example of how the missing binaries are reported in the logs:
>
> 11:32:39.673 INFO [main] MarkSweepGarbageCollector.java:600 Consistency check found [1] missing blobs
-> 11:32:39.673 WARN [main] MarkSweepGarbageCollector.java:602 Consistency check failure in the the blob store : DataStore backed BlobStore [org.apache.jackrabbit.oak.plugins.blob.datastore.OakFileDataStore], check missing candidates in file /tmp/gcworkdir-1467352959243/gccand-1467352959243
-
-
+> 11:32:39.673 WARN [main] MarkSweepGarbageCollector.java:602 Consistency check failure in the the blob store : DataStore backed BlobStore [org.apache.jackrabbit.oak.plugins.blob.datastore.OakFileDataStore], check missing candidates in file /tmp/gcworkdir-1467352959243/gccand-1467352959243
[1]: http://serverfault.com/questions/52861/how-does-dropbox-version-upload-large-files
[2]: http://wiki.apache.org/jackrabbit/DataStore