microsoft / microsoft/durabletask-mssql
Inquiry: Limits on Orchestration Instance's History
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Does the MS SQL Provider for DTFx impose a limit on the number of history records (dt.History table) for an orchestration instance? Is it possible to configure one?
Specifically I'm wondering what mechanisms are in place to avoid a never-ending orchestration from browning-out our service's database.
Thank you!
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the MS SQL provider's handling of the dt.History table and orchestration-instance history. Determine whether history limits or configuration are mentioned, and whether any mechanism addresses never-ending orchestrations. Done means documenting the supported behavior or identifying the provider area that would need a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100