When resetting the checkpoints for a consumer, which occasionally could happen, the scale monitor assumes that the event count is last enqueued sequence number + 1.
This could lead to the scale metrics reporting very high event count until the consumer has created new checkpoints for all the partitions. When encountering this situation, the scale monitor should respect the initial offset position, or just return a number that ensures that the vote is None until the consumer has checkpointed.
When resetting the checkpoints for a consumer, which occasionally could happen, the scale monitor assumes that the event count is last enqueued sequence number + 1.
https://github.com/Azure/azure-functions-eventhubs-extension/blob/5eb8543e47b448eb3b485a571a2ceb1ab404650f/src/Microsoft.Azure.WebJobs.Extensions.EventHubs/Listeners/EventHubsScaleMonitor.cs#L255
This could lead to the scale metrics reporting very high event count until the consumer has created new checkpoints for all the partitions. When encountering this situation, the scale monitor should respect the initial offset position, or just return a number that ensures that the vote is
Noneuntil the consumer has checkpointed.