Azure / Azure/Azure-Spring-Apps

partitionOwnershipExpirationInterval setting not applied

Open
#60 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

**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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.