Azure / Azure/Azure-Spring-Apps
partitionOwnershipExpirationInterval setting not applied
- 主要语言
- 没有语言数据
- 星标
- 9
- 派生
- 11
- PR 合并指标
- 30 天内没有已合并 PR
描述
**Describe the bug**
We are using **spring-cloud-azure-starter-eventhubs** version 7.4.0. We have configured rebalancing and partition ownership expiration internal as per documentation:
```
spring:
cloud:
azure:
eventhubs:
processor:
load-balancing:
partition-ownership-expiration-interval: 30s
update-interval: 10s
```
We can clearly see in logs that load balancing is performed every 10s, as configured, but partition ownership is only re-assigned after the default 2 minutes. The configuration property is ignored.
**To Reproduce**
Create an eventhubs consumer with above configuration. It is sufficient to make it listen to a topic with only one partition configured. Then stop the pod/instance, at which point a new instance will automatically be started up. In the logs, it can be seen that the new instance performs load balancing every 10s, but only after 2 minutes it obtains ownership of the partition that was released by the earlier terminated listener.
**Expected behavior**
The new consumer should be granted ownership of the partition after 30s, as per configuration.
**Screenshots**
n/a
**Additional context**
n/a
**Can we contact you for additional details?**
Y
If yes, please send us your contact information to AzureSpringCloud-Talk@service.microsoft.com and include the issue number in the email title.
贡献指南
这个仓库没有索引到贡献指南
调研方向
首先跟踪 Spring Cloud Azure Event Hubs 处理器针对 partition-ownership-expiration-interval 的配置及其负载均衡设置。使用单分区 topic、30 秒的过期间隔和一个已终止的实例进行复现;完成的标准是替代 consumer 在约 30 秒后而不是默认的两分钟后获得 ownership。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- azure, spring, spring-boot
- 领域
- cloud, distributed-systems
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 55/100