Azure / Azure/Azure-Functions

Azure Function Cosmos Trigger, Unable to handle partitions in parallel when there is retry

Open
#2,184 3 comments 1 reaction 1 assignee Claimed by @v-bbalaiagar View on GitHub
bug
Dominant language
PowerShell
Stars
1.1k
Forks
215
Avg merge
4h 2m
Merged PRs (30d)
1

Description

#### Here is what I have ####
* Cosmos Serverless account
* Cosmos container **partitioned by "id"**
* Azure function app hosted on slot of a Premium app
* The function app is triggered by cosmos db change feed
* The function app has Exponential Retry policy
```csharp
[ExponentialBackoffRetry(15, "00:15:00", "24:00:00")]
```
* The function is .Net 6 app

#### Expected Behaviour ####
* When the app fails for a given partition, it should stop handling that partition for 15 minutes first time (as per retry policy) but other partitions should get executed on time in parallel and should not wait the retry duration

#### Actual Behaviour ####
* All partitions will wait the retry duration. The app doesn't handle cosmos db change feed in parallel nor it scales. When the function retries it retries the failed item and all other partitions changes keep in the queue, when that item fails, the function go into sleeping again ignoring all other partitions.

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.