mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

wording

Browse source
This commit is contained in:
Joey Hess 2024-06-30 11:28:17 -04:00
parent f833a28844
commit cecd151e23
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/tips/clusters.mdwn
View file

@ -76,7 +76,7 @@ For example:
By default, when a file is uploaded to a cluster, it is stored on every node of By default, when a file is uploaded to a cluster, it is stored on every node of
the cluster. To control which nodes to store to, the [[preferred_content]] of the cluster. To control which nodes to store to, the [[preferred_content]] of
each node can be configured. each individual node can be configured.
It's also a good idea to configure the preferred content of the cluster's It's also a good idea to configure the preferred content of the cluster's
gateway. To avoid files redundantly being stored on the gateway gateway. To avoid files redundantly being stored on the gateway
@ -119,8 +119,8 @@ in the git-annex branch. That tells other repositories about the cluster.
Started proxying for node3 Started proxying for node3
Operations that affect multiple nodes of a cluster can often be sped up by Operations that affect multiple nodes of a cluster can often be sped up by
configuring annex.jobs in the repository that will serve the cluster to configuring annex.jobs in the gateway repository.
clients. In the example above, the nodes are all disk bound, so operating In the example above, the nodes are all disk bound, so operating
on more than one at a time will likely be faster. on more than one at a time will likely be faster.
$ git config annex.jobs cpus $ git config annex.jobs cpus