docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed syntax and incorporated editorial feedback

This commit is contained in:
Maria Bermudez 2018-12-12 12:30:28 -08:00
parent cd710189db
commit e0a665eb48
4 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
datacenter/dtr/2.5/guides/admin/configure/deploy-caches/configuration-reference.md
View File

@ -43,8 +43,7 @@ Below you can find the description for each parameter, specific to DTR caches.
no
</td>
<td>
The TTL for blobs in the cache. This field takes a positive integer and an optional suffix indicating the unit of time. If
this field is configured, "storage.delete.enabled" must be configured to true. Possible units are:
A positive integer and an optional unit of time suffix to determine the TTL (Time to Live) value for blobs in the cache. If <code>blobttl</code> is configured, <code>storage.delete.enabled</code> must be set to <code>true</code>. Acceptable units of time are:
<ul>
<li><code>ns</code> (nanoseconds)</li>
<li><code>us</code> (microseconds)</li>

8
datacenter/dtr/2.5/guides/admin/upgrade.md
View File

@ -80,15 +80,15 @@ one replica at a time. It will also perform certain data migrations. If anything
fails or the upgrade is interrupted for any reason, you can re-run the upgrade
command and it will resume from where it left off.
#### Upgrade DTR Caches
If you have previously [deployed a DTR cache](/datacenter/dtr/2.5/guides/admin/configure/deploy-caches/simple), make sure to run the upgrade command on the DTR cache nodes to keep them in sync with your upstream DTR replicas. This prevents authentication errors and other weird behaviors.
## Patch upgrade
A patch upgrade changes only the DTR containers and it's always safer than a minor
upgrade. The command is the same as for a minor upgrade.
## DTR cache upgrade
If you have previously [deployed a cache](/datacenter/dtr/2.5/guides/admin/configure/deploy-caches/), make sure to [upgrade the node dedicated for your cache](/v18.03/ee/upgrade/) to keep it in sync with your upstream DTR replicas. This prevents authentication errors and other weird behaviors.
## Download the vulnerability database
After upgrading DTR, you need to re-download the vulnerability database.

3
ee/dtr/admin/configure/deploy-caches/configuration-reference.md
View File

@ -43,8 +43,7 @@ Below you can find the description for each parameter, specific to DTR caches.
no
</td>
<td>
The TTL for blobs in the cache. This field takes a positive integer and an optional suffix indicating the unit of time. If
this field is configured, "storage.delete.enabled" must be configured to true. Possible units are:
A positive integer and an optional unit of time suffix to determine the TTL (Time to Live) value for blobs in the cache. If <code>blobttl</code> is configured, <code>storage.delete.enabled</code> must be set to <code>true</code>. Acceptable units of time are:
<ul>
<li><code>ns</code> (nanoseconds)</li>
<li><code>us</code> (microseconds)</li>

7
ee/dtr/admin/upgrade.md
View File

@ -86,9 +86,6 @@ one replica at a time. It will also perform certain data migrations. If anything
fails or the upgrade is interrupted for any reason, you can rerun the upgrade
command and it will resume from where it left off.
#### Upgrade DTR Caches
If you have previously [deployed a DTR cache](/ee/dtr/admin/configure/deploy-caches/simple/), make sure to run the upgrade command on the DTR cache nodes to keep them in sync with your upstream DTR replicas. This prevents authentication errors and other weird behaviors.
#### Metadata Store Migration
@ -114,6 +111,10 @@ Alternatively, select **API** from the bottom left navigation pane of the DTR we
A patch upgrade changes only the DTR containers and is always safer than a minor version
upgrade. The command is the same as for a minor upgrade.
## DTR cache upgrade
If you have previously [deployed a cache](/ee/dtr/admin/configure/deploy-caches/), make sure to [upgrade the node dedicated for your cache](/ee/upgrade) to keep it in sync with your upstream DTR replicas. This prevents authentication errors and other weird behaviors.
## Download the vulnerability database
After upgrading DTR, you need to redownload the vulnerability database.