Skip to content

Commit 1b77c6a

Browse files
committed
Learn Editor: Update storage-task-known-issues.md
1 parent 159f4f3 commit 1b77c6a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/storage-actions/storage-tasks/storage-task-known-issues.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,6 @@ ms.author: normesta
1414

1515
This article describes limitations and known issues of storage tasks. The issues that appear in this article reflect the current state of the service. This list will change over time as support continues to expand.
1616

17-
## Storage account regions
18-
19-
During the public, you can target only storage accounts that are in the same region as the storage tasks.
20-
2117
## Scale limits
2218

2319
| Scale factor | Supported limit |
@@ -30,6 +26,10 @@ During the public, you can target only storage accounts that are in the same reg
3026

3127
Azure Storage Actions autoscales its processing tasks based on the volume of data in a storage account, subject to internal limits. The duration of execution depends on the number of blobs in the storage account, as well as their hierarchy in Azure Data Lake Storage Gen2. The first execution of a task over a path prefix might take longer than subsequent executions. Azure Storage Actions are also designed to be self-regulating and to allow application workloads on the storage account to take precedence. As a result, the scale and the duration of execution also depend on the available transaction capacity given the storage account's maximum request limit. The following are typical processing scales, which might be higher if you have more transaction capacity available, or might be lower for lesser spare transaction capacity on the storage account.
3228

29+
## Storage account regions
30+
31+
Task assignments can only be applied on storage accounts that are in the same region as the storage tasks.
32+
3333
## Billing doesn't show task assignment name
3434

3535
Billing meters show up on the bill with only the storage account name. Subscription bill doesn't show the task assignment name for which the meter was emitted. To correlate the meter with the task assignment, you must look at the resource metrics for Storage Actions filtered by the storage account for that day.

0 commit comments

Comments
 (0)