Skip to content

Commit e2a5fd6

Browse files
Merge pull request #276508 from anboisve/patch-26
Update stream-analytics-autoscale.md
2 parents b01447c + 2d5340c commit e2a5fd6

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/stream-analytics/stream-analytics-autoscale.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ahartoon
55
ms.author: anboisve
66
ms.service: stream-analytics
77
ms.topic: how-to
8-
ms.date: 05/10/2022
8+
ms.date: 05/28/2024
99
---
1010

1111
# Autoscale streaming units
@@ -95,6 +95,9 @@ The following procedure shows you how to add a condition to automatically increa
9595
9. Select **Save**.
9696
:::image type="content" source="./media/stream-analytics-autoscale/save-scale-rule-streaming-units-limits.png" alt-text="Screenshot showing the Save option for a rule." lightbox="./media/stream-analytics-autoscale/save-scale-rule-streaming-units-limits.png" :::
9797

98+
> [!NOTE]
99+
> Flapping refers to a loop condition that causes a series of opposing scale events. Flapping happens when a scale event triggers the opposite scale event. Refer to [this](https://learn.microsoft.com/azure/azure-monitor/autoscale/autoscale-flapping)) article which describes flapping in autoscale and how to avoid it.
100+
98101
### Scale to specific number of streaming units
99102

100103
Follow these steps to configure the rule to scale the job to use specific number of streaming units. Again, the default condition is applied when none of the other scale conditions match.

0 commit comments

Comments
 (0)