Need an API to provide instance id routing to a subset of control-queues

Open
#1,079 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
api, backend, distributed-systems

Research direction

Start by reviewing the control-queue orchestration queuing and instance-id routing entry points. Clarify how to queue one orchestration per control-queue and how callers should select a subset when queues are hogged. Done means the API requirements, routing behavior, and validation expectations are specified and covered by tests.

Written by the indexing model from the issue text.

Description

This is more like requirement than an issue. Here are 2 requirements:

  1. Need to queue orchestrations one for each control-queue. Basically, to monitor the behavior and not to keep any control-queue empty.
  2. Given that some control-queue are hogged, need to load balance explicitly to specific subset of control-queues.
Dominant language
C#
Stars
1.7k
Forks
335
Avg merge
4d 2h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/durabletask

All issues in Azure/durabletask

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.