X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/14304c7af0b0dd7bc9345b6c5aeb61a3bdc1d3b0..9c983060b6f0fc6dc42310587b9858b7f8b968de:/doc/install/install-keep-balance.html.textile.liquid diff --git a/doc/install/install-keep-balance.html.textile.liquid b/doc/install/install-keep-balance.html.textile.liquid index f8d7656499..4c735a1eec 100644 --- a/doc/install/install-keep-balance.html.textile.liquid +++ b/doc/install/install-keep-balance.html.textile.liquid @@ -3,18 +3,25 @@ layout: default navsection: installguide title: Install Keep-balance ... +{% comment %} +Copyright (C) The Arvados Authors. All rights reserved. + +SPDX-License-Identifier: CC-BY-SA-3.0 +{% endcomment %} Keep-balance deletes unreferenced and overreplicated blocks from Keep servers, makes additional copies of underreplicated blocks, and moves blocks into optimal locations as needed (e.g., after adding new servers). {% include 'notebox_begin' %} -If you are installing keep-balance on an existing system with valuable data, you can run keep-balance in "dry run" mode first and review its logs as a precaution. To do this, use the @keepstore -never-delete=true@ flag or remove the @-commit-trash@ flag from your keep-balance startup script. +If you are installing keep-balance on an existing system with valuable data, you can run keep-balance in "dry run" mode first and review its logs as a precaution. To do this, edit your keep-balance startup script to use the flags @-commit-pulls=false -commit-trash=false@. {% include 'notebox_end' %} h2. Install keep-balance -Keep-balance can be installed anywhere with access to Keep services. Typically it runs on the same host as keepproxy. +Keep-balance can be installed anywhere with network access to Keep services. Typically it runs on the same host as keepproxy. + +*A cluster should have only one keep-balance process running at a time.* On Debian-based systems: @@ -48,7 +55,7 @@ Options: h3. Create a keep-balance token -Create a privileged Arvados API token for use by keep-balance. *On the API server*, run: +Create an Arvados superuser token for use by keep-balance. *On the API server*, run:
apiserver:~$ cd /var/www/arvados-api/current
@@ -57,9 +64,20 @@ zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
 
-h3. Create a configuration file +h3. Update keepstore configuration files -Create @/etc/arvados/keep-balance/keep-balance.yml@ using the token you generated in the previous step. Follow this YAML format: +On each node that runs keepstore, save the token you generated in the previous step in a text file like @/etc/arvados/keepstore/system-auth-token.txt@ and then create or update @/etc/arvados/keepstore/keepstore.yml@ with the following key: + + +
SystemAuthTokenFile: /etc/arvados/keepstore/system-auth-token.txt
+
+
+ +Restart all keepstore services to apply the updated configuration. + +h3. Create a keep-balance configuration file + +On the host running keep-balance, create @/etc/arvados/keep-balance/keep-balance.yml@ using the token you generated above. Follow this YAML format:
Client:
@@ -139,22 +157,26 @@ run: /etc/service/keep-balance: (pid 12520) 2s; run: log: (pid 12519) 2s
 
 h2. Enable delete operations on keepstore volumes
 
-Ensure your keepstore services have the "delete" operation enabled. Otherwise, even when unneeded data is identified by keep-balance, it will never be deleted from the underlying storage devices.
+Ensure your keepstore services have the "delete" operation enabled. If it is disabled (which is the default), unneeded blocks will be identified by keep-balance, but will never be deleted from the underlying storage devices.
 
-Either use the @EnableDelete@ flag in your YAML configuration file @/etc/arvados/keepstore/keepstore.yml@:
+Add the @-never-delete=false@ command line flag to your keepstore run script:
 
 
-
...
-BlobSigningKeyFile: /etc/keepstore/blob-signing.key
-EnableDelete: true
-Listen: :25107
-...
+
keepstore -never-delete=false -volume=...
 
-Or use the @-never-delete=false@ command line flag in your run script: +{% comment %} +// To replace the above section when the keepstore page recommends YAML... + +Use the @EnableDelete@ flag in your YAML configuration file @/etc/arvados/keepstore/keepstore.yml@: -
keepstore -never-delete=false -volume=...
+
...
+BlobSigningKeyFile: /etc/keepstore/blob-signing.key
+EnableDelete: true
+Listen: :25107
+...
 
+{% endcomment %}