Skip to content

Commit 14eabad

Browse files
authored
Merge pull request #113386 from mamccrea/patch-53
Stream Analytics: Update stream-analytics-troubleshoot-input.md
2 parents 0ca82a0 + c4a88a5 commit 14eabad

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

articles/stream-analytics/stream-analytics-troubleshoot-input.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sidram
66
ms.reviewer: mamccrea
77
ms.service: stream-analytics
88
ms.topic: conceptual
9-
ms.date: 03/31/2020
9+
ms.date: 05/01/2020
1010
ms.custom: seodec18
1111
---
1212

@@ -46,9 +46,18 @@ In cases where the message payload is greater than 32 KB or is in binary format,
4646

4747
A best practice for using Event Hubs is to use multiple consumer groups for job scalability. The number of readers in the Stream Analytics job for a specific input affects the number of readers in a single consumer group. The precise number of receivers is based on internal implementation details for the scale-out topology logic and is not exposed externally. The number of readers can change when a job is started or during job upgrades.
4848

49-
The error shown when the number of receivers exceeds the maximum is:
49+
The following error messages are shown when the number of receivers exceeds the maximum. The error message includes a list of existing connections made to Event Hub under a consumer group. The tag `AzureStreamAnalytics` indicates that the connections are from Azure Streaming Service.
5050

51-
`The streaming job failed: Stream Analytics job has validation errors: Job will exceed the maximum amount of Event Hub Receivers.`
51+
```
52+
The streaming job failed: Stream Analytics job has validation errors: Job will exceed the maximum amount of Event Hub Receivers.
53+
54+
The following information may be helpful in identifying the connected receivers: Exceeded the maximum number of allowed receivers per partition in a consumer group which is 5. List of connected receivers –
55+
AzureStreamAnalytics_c4b65e4a-f572-4cfc-b4e2-cf237f43c6f0_1,
56+
AzureStreamAnalytics_c4b65e4a-f572-4cfc-b4e2-cf237f43c6f0_1,
57+
AzureStreamAnalytics_c4b65e4a-f572-4cfc-b4e2-cf237f43c6f0_1,
58+
AzureStreamAnalytics_c4b65e4a-f572-4cfc-b4e2-cf237f43c6f0_1,
59+
AzureStreamAnalytics_c4b65e4a-f572-4cfc-b4e2-cf237f43c6f0_1.
60+
```
5261

5362
> [!NOTE]
5463
> When the number of readers changes during a job upgrade, transient warnings are written to audit logs. Stream Analytics jobs automatically recover from these transient issues.

0 commit comments

Comments
 (0)