azure-functions-host: Cosmos DB Trigger: Consumption plan not creating instances
- Function App version: 1.0
- Function App name: consumer-egress-func
- Function name(s) (as appropriate): ChangeFeedFunc
- Region: West Europe
Cosmos DB change feed doesn’t get triggered the first time, until I manually visit the Function App -> Change Feed Function -> function.json -> Logs. This change feed is being observed on a partitioned collection with 25k RUs. Function is hosted on consumption plan with a single lease (leases collection: 400 RUs). Once it gets triggered it works fine afterwards but the first time I always have to navigate to the Logs as mentioned above.
The behavior is not tied to a specific Collection or Cosmos DB account but always reproducible by deploying this ARM template and running these load tests. The trigger is configured in code here.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 24 (14 by maintainers)
@ealsur I can confirm that using an HTTP Trigger correctly forces a wakeup and consequently triggers a changefeed.
@ealsur The existence of leases collection doesn’t matter. Tried both reusing it and re-creating a new one every time, but the end result is still that I have to navigate to the portal in order for Change Feed to “kick in”.
Nevermind, I found the logs with the specific error. We’re investigating…