temporalio / temporalio/temporal

Dynamic config change listener

Open
#2,915 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.
Existing dynamic config is built as poll model, meaning when a value is needed, a function call needs to be made to get the latest value.

This poll model works well for values that are accessed frequently, but not for values that are rarely accessed or even accessed only once. For example, configs that are used only at service start time, like task worker pool size.

In those cases, either the config updates are completely ignored when the service is running or each component needs to have its own poller to periodically check if the config value is updated or not (e.g. https://github.com/temporalio/temporal/pull/2911). For values that are rarely updated, it is not efficient and also causes a lot of duplicated code for polling value updates.

Describe the solution you'd like
Add support for push model in dynamic config so that a listener can be registered for a certain key.

Describe alternatives you've considered

Additional context

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the dynamic config implementation and its current polling access path. Define how a listener is registered for a key and how updates are delivered, then add coverage for listener registration and change notification. Done means rarely accessed configuration values can receive updates without each component implementing its own poller.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.