Skip to content

Commit 86b5586

Browse files
authored
(AzureCXP) fixes MicrosoftDocs/azure-docs#438802
Updated document by removing line no: 20
1 parent 25c1280 commit 86b5586

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/event-hubs/apache-kafka-troubleshooting-guide.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ If the traffic is excessive, the service has the following behavior:
1717
- If produce request's delay exceeds request time-out(*request.timeout.ms*), Event Hubs returns **Policy Violation** error code.
1818
- If fetch request's delay exceeds request time out, Event Hubs logs the request as throttled and responds with empty set of records and no error code.
1919

20-
[Dedicated clusters](event-hubs-dedicated-overview.md) don't have throttling mechanisms. You're free to consume all of your cluster resources.
21-
2220
## No records received
2321
You might see consumers not getting any records and constantly rebalancing. In this scenario, consumers don't get any records and constantly rebalance. There's no exception or error when it happens, but the Kafka logs will show that the consumers are stuck trying to rejoin the group and assign partitions. There are a few possible causes:
2422

0 commit comments

Comments
 (0)