Eventhub configuration for multi silo setup wont implicity create consumer groups
- Dominant language
- C#
- Stars
- 10.9k
- Forks
- 2.1k
- Avg merge
- 14h 42m
- Merged PRs (30d)
- 354
Description
We've been running in a single silo setup for some time but now we've looked to harden the setup by increasing the number of hosts/clustering but the eventhub configuration was set to use the $default consumer group.
This resulted in unhealthy silos and the logs pointing to this shared consumer group which we've tried to resolve unsuccessfully.
Is it correct to assume each silo needs its own consumer group? If so can they be created on the fly?
Or configuration looks like
` b.ConfigureEventHub(ob => ob.Configure( options =>
{
options.ConfigureEventHubConnection(new EventHubConnection(configuration.AzureSettings.EventHubConnectionString, eventhubName), consumerGroupName);
}));
`
Contributor guide
Assessment
This issue has not been assessed yet.