You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/hpc-cache/prime-cache.md
+41-14Lines changed: 41 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Use the cache priming feature to populate or preload cache contents
4
4
author: ekpgh
5
5
ms.service: hpc-cache
6
6
ms.topic: how-to
7
-
ms.date: 05/29/2022
7
+
ms.date: 05/31/2022
8
8
ms.author: v-erinkelly
9
9
---
10
10
@@ -180,8 +180,7 @@ The cache accesses the manifest file once when the priming job starts. The SAS U
180
180
181
181
Use the Azure portal to create a priming job. View your Azure HPC Cache in the portal and select the **Prime cache** page under the **Settings** heading.
182
182
183
-

184
-
<!-- to do: screenshot with more diverse jobs and statuses -->
183
+

185
184
186
185
Click the **Add priming job** text at the top of the table to define a new job.
187
186
@@ -199,19 +198,17 @@ If you can’t find the manifest file, your cache might not be able to access th
199
198
200
199
Priming jobs are listed in the **Prime cache** page in the Azure portal.
201
200
202
-

201
+
This page shows each job's name, its state, its current status, and summary statistics about the priming progress. The summary in the **Details** column updates periodically as the job progresses. The **Job status** field is populated when a priming job starts; this field also gives basic error information like **Invalid manifest** if a problem occurs.
203
202
204
-
This page shows each job's name, its state, its current status, and summary statistics about the priming progress. The summary in the **Details** column updates periodically as the job progresses. The **Status** field is populated when a priming job starts; this field also gives basic error information like **Invalid manifest** if a problem occurs.
203
+
While a job is running, the **Percentage complete** column shows an estimate of the progress.
205
204
206
-
Before a priming job starts, it has the state **Queued**. Its **Status** and **Details** fields are empty.
205
+
Before a priming job starts, it has the state **Queued**. Its **Job status**, **Percentage complete**, and **Details** fields are empty.
207
206
208
-
While a job is running, the column **Percentage complete** shows an estimate of the
207
+

209
208
210
-

209
+
Click the **...** section at the right of the table to pause or resume a priming job. (It might take a few minutes for the status to update.)
211
210
212
-
Click the **...** section at the right of the table to pause or resume a priming job.
213
-
214
-
To delete a priming job, select it in the list and use the delete control at the top of the table.
211
+
To delete a priming job, select it in the list and use the **Stop** control at the top of the table. You can use the **Stop** control to delete a job in any state.
215
212
216
213
## Azure REST APIs
217
214
@@ -241,7 +238,7 @@ For the `primingManifestUrl` value, pass the file’s SAS URL or other HTTPS URL
241
238
242
239
### Stop a priming job
243
240
244
-
The `stopPrimingJob` interface cancels a job (if it is running) and removes it from the job list.
241
+
The `stopPrimingJob` interface cancels a job (if it is running) and removes it from the job list. Use this interface to delete a priming job in any state.
245
242
246
243
```rest
247
244
@@ -270,7 +267,37 @@ BODY:
270
267
271
268
```
272
269
273
-
<!-- ***[ ?? should we add pause/resume APIs here too? ??]*** -->
270
+
### Pause a priming job
271
+
272
+
The `pausePrimingJob` interface suspends a running job.
* How long does a failed or completed priming job stay in the list?
284
311
285
-
Priming jobs persist in the list until you delete them. On the portal **Prime cache** page, check the checkbox next to the job and select the **Delete** control at the top of the list.
312
+
Priming jobs persist in the list until you delete them. On the portal **Prime cache** page, check the checkbox next to the job and select the **Stop** control at the top of the list to delete the job.
286
313
287
314
* What happens if the content I’m pre-loading is larger than my cache storage?
0 commit comments