Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cosmos DB Trigger: Consumption plan not creating instances
See original GitHub issue- 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.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:24 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@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”.