From a30cdccc1cfed59882243c8686ed02fd54039ff2 Mon Sep 17 00:00:00 2001 From: Daniel Bernstein Date: Fri, 6 Apr 2018 10:57:00 -0700 Subject: [PATCH] Adds howto for temporarily stopping the manifest-cleaner. --- mill-setup.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/mill-setup.md b/mill-setup.md index 634e43f..856d020 100644 --- a/mill-setup.md +++ b/mill-setup.md @@ -43,3 +43,15 @@ a bootstrap duracloud account using credentials associated with the account tha Once your [DuraCloud Application](duracloud-webapp-setup.md) is deployed you should be able to follow the steps to [create a new account](creating-new-accounts.md), employing the account that you have already been using to host your DuraCloud core infrastructure. + +## How-Tos + +### How to pause the Manifest Cleaner + +Occassionally you may want to pause the activity of the manifest cleaner in order to lighten the load on the database. The manifest cleaner (manifest-cleaner-.jar) is responsible for purging manifest records that have been flagged for deletion. When the contents of large spaces are deleted (as is the case when a bridge snapshot completes), a large number of deletes will hit the database at the same time. When those deleted manifest entries are purged from the manifest table, it can result in slower performance of the manifest table indices which can in turn slow the throughput of writes to the manifest table. In turn this can exacerbate a back up of unprocessed audit messages. To ameliorate this situation, you can temporarily suspend the manifest-cleaner until the audit queue has been consumed to a reasonable size. + +1. Log into the sentinel. +2. ``cd /home/duracloud`` +3. ``sudo mv manifest-cleaner-.jar manifest-cleaner.jar.offline`` +4. ``sudo service manifest-cleaner stop`` +5. Verify that the manifest-cleaner java process is no longer running. \ No newline at end of file