Shahab Tajik
Shahab Tajik
This is already fixed in server code https://github.com/temporalio/temporal/pull/5661. It will be included in the next patch or minor release whenever comes first (1.23.2 or 1.24.0).
Starting to work on this. As the first step, I'm thinking to add a boolean dynamic config (per namespace+task queue) to allow disabling sync match when there is a backlog....
@paulnpdev no, this config will not be exposed to the client (at least not now). Only the server operator can turn this flag on. Because this has implications on the...
@paulnpdev taskQ level. More specifically, the combination of namespace + taskQ name + taskQ type (workflow vs activity)
After deeper analysis based on synthetic and customer workloads, it turned out that: - **Sync match rarely happens in presence of a backlog.** This is because sync match request (for...
I think we need to follow up this quickly by adding caching for the stats otherwise I'm concerned about the fanout load that each describetaskqueue request will make.
cc @rodrigozhou
@jbrody-nexxa I'd like to understand more about your use case. > My team has Workflows and Activities developed on different release cycles. In this case, first thing I'd think is...
@jbrody-nexxa we discussed this internally. We want to support it, but it is right now in backlog behind some other more important items.