Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[BUG] Configuration subscription stops permanently after the daprd sidecar restarts

未关闭
  • 哪里不对？
#1,232 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
grpc, python
领域
api, backend

调研方向

Start in dapr/clients/grpc/_response.py with ConfigurationWatcher, then trace subscribe_configuration() in both dapr.clients.DaprClient and dapr.aio.clients.DaprClient. Reproduce the stream failure by restarting daprd, and verify that both subscription paths recover and deliver later updates without restarting the application.

由索引模型根据 Issue 内容生成。

描述

kind/bug

Expected Behavior

DaprClient.subscribe_configuration() keeps delivering configuration updates for the lifetime of the client.
If the daprd sidecar process exits and comes back (for example an OOM kill of the sidecar container while the application container keeps running), the SDK should re-establish SubscribeConfigurationAlpha1 against the new sidecar and continue calling the handler. Updates that happened while the sidecar was down should be visible on the new subscription, or the application should at least be able to observe that the previous stream ended.
Unary calls such as get_configuration() already work again once the new sidecar is listening. The long-lived configuration subscription should recover the same way.

Actual Behavior

The subscription works after a fresh application start. After daprd restarts, the handler is never called again. The application process stays healthy, so a Kubernetes pod is not recreated, and dynamic config updates are silently lost until the application process itself restarts.
ConfigurationWatcher in dapr/clients/grpc/_response.py reads SubscribeConfigurationAlpha1 on a daemon thread. When the stream raises, the thread prints to stdout and returns:

except Exception:
    print(f'{self.store_name} configuration watcher for keys {self.keys} stopped.')
    pass

There is no retry. subscribe_configuration() does not retain the ConfigurationWatcher, so nothing is left to start a new stream. The failure is not reported through the Python logger, and the returned subscription id belongs to the dead sidecar.
Seen with dapr Python SDK 1.18.3. Both dapr.clients.DaprClient.subscribe_configuration and dapr.aio.clients.DaprClient.subscribe_configuration use this watcher.

Steps to Reproduce the Problem

  1. Run an app with a configuration.redis component and the Python SDK 1.18.3.
  2. Subscribe once at startup:
from dapr.clients import DaprClient
def handler(subscription_id, response):
    print("update", subscription_id, {k: v.value for k, v in response.items.items()})
with DaprClient() as client:
    subscription_id = client.subscribe_configuration(
        store_name="configstore",
        keys=["my-key"],
        handler=handler,
    )
    print("subscribed", subscription_id)
    # keep the process alive
  1. Confirm a config change invokes handler.
  2. Restart only daprd. In Kubernetes this is a sidecar OOM (OOMKilled) while the app container keeps the same process. Locally, stop and start the daprd process without restarting the app.
  3. Change my-key again after daprd is healthy.
    handler is not called. Stdout may contain {store} configuration watcher for keys [...] stopped. Recreating the app process makes updates work again until the next sidecar restart.

Release Note

RELEASE NOTE: FIX Reconnect configuration subscriptions after the Dapr sidecar stream drops.

主要语言
Python
星标
272
派生
152
平均合并
2 天 22 小时
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

dapr/python-sdk 的其他 Issue

查看 dapr/python-sdk 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。