Azure / Azure/Azure-Spring-Apps
partitionOwnershipExpirationInterval setting not applied
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 9
- Fork
- 11
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**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.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start by tracing the Spring Cloud Azure Event Hubs processor configuration for partition-ownership-expiration-interval and its load-balancing setup. Reproduce with a single-partition topic, a 30-second expiration interval, and a terminated instance; done means the replacement consumer obtains ownership after about 30 seconds rather than the default two minutes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure, spring, spring-boot
- Ambito
- cloud, distributed-systems
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 55/100