Functions host fails to create "leases" collection
See original GitHub issueI have multiple CosmosDBTriggers
set up with LeaseCollectionName = "leases", CreateLeaseCollectionIfNotExists = true
attributes. A console app deletes and recreates all collections (it also deletes the leases
collection) on a regular basis. When a function is run, the associated trigger is supposed to create the leases
collection if it doesn’t exist. Unfortunately, sometimes this collection is not created.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Troubleshoot issues with the Azure Functions trigger for ...
Your Azure function fails to start, with error message "The lease collection, if partitioned, must have partition key equal to id" This error ......
Read more >Error in Azure function - Host lock lease acquired by ...
1 Answer 1 · The message Host lock lease acquired by instance ID '0000000000000000000000006000A33F' is not an error message, it's an expected ...
Read more >How to fix "The listener for function was unable to start. Out of ...
Here is another pretty quick one – trying to debug Azure Functions fails with a confusing error message about failing to create a...
Read more >Azure Cosmos DB Change Feed
Create Function to Add Documents to Cosmos DB ... Lease collections are a critical part of the Cosmos DB Change Feed. ... Host;...
Read more >Error in Azure function - Host lock lease ... - appsloveworld.com
The message Host lock lease acquired by instance ID '0000000000000000000000006000A33F' is not an error message, it's an expected message, which means your ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kashimiz I will provide the requested information next time the issue happens. I added a lease collection prefix to every trigger since they were sharing the same collection and did not observe the issue since then. However, I deleted & created the collections only once after this change. If I observe the issue again, I will provide the information.
Hi @adrianknight89, We are proceeding to close the ticket since there were no visible errors. Please feel free to open a new issue in case of any further errors occur