microsoft / microsoft/durabletask-netherite
409 The specified container already exists after switching to Netherite (JavaScript)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 37
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Hi guys! Hope you are doing fine!
Latest versions of assets at the moment of creating the issue:
Runtime: JavaScript (compiled from TypeScript)
Core Tools Version: 4.0.5148 Commit hash: N/A (64-bit)
Function Runtime Version: 4.17.3.20392
"durable-functions": "^2.1.2",
"@azure/functions": "^3.5.1",
"@azure/storage-blob": "^12.14.0",
Latest Azurite: 3.23.0
Switched to Netherite locally with connections to Azure Event Hubs, AzureWebJobsStorage: "UseDevelopmentStorage=true"
and started observing a lot of:
409 The specified container already exists
Does anyone have some idea of what the root cause could be?
Let me know if I can provide more info.
Thanks in advance!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named in the report. Begin by reproducing the local Netherite setup with Azure Event Hubs, AzureWebJobsStorage set to UseDevelopmentStorage=true, and Azurite, then trace the source of the 409 container-already-exists errors. Done means identifying the root cause and documenting a confirmed resolution or additional reproduction details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript, typescript
- Domain
- backend, cloud, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100