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

[Question] Several "Unable to poll" errors multiple times per day

未关闭
#291 2 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
grpc, ruby

调研方向

从 issue 中描述的 workflow 和 activity 任务队列轮询路径开始,使用 temporal-ruby 修订版 3e0dae708ec0e3eab8c44b57b64f5cd1881848 和 grpc 1.59.2。未指定文件或测试;完成意味着确定反复出现的 „Socket closed“ 错误是否属于预期,并记录其原因或缓解措施。

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

描述

Hey folks,

We've been using this ruby for quite a while, 1 year I would say and since then, we've been seeing a lot of "Unable to poll" errors. For example, last week, there were 700 of those for one of our service. This affects all our different using this sdk.

Unable to poll Workflow task queue

#<GRPC::Unavailable: 14:Socket closed. debug_error_string:{UNKNOWN:Error received from peer  {grpc_message:"Socket closed", grpc_status:14, created_time:"2024-03-19T14:52:38.963074635+00:00"}}>

And this

Unable to poll activity task queue

#<GRPC::Unavailable: 14:Socket closed. debug_error_string:{UNKNOWN:Error received from peer  {created_time:"2024-03-19T14:52:38.963058558+00:00", grpc_status:14, grpc_message:"Socket closed"}}>

Would someone have an idea of what might be causing those errors? Are they "normal" or expected from time to time within Temporal? We don't have a fancy configuration or anything we mostly use the default config and we use 20 as the thread pool size for both activity and workflow. I can share more relevant details if needed.

Note, this error doesn't cause any of our activities or workflows to fail, it just happens once every now and then and recovers.

temporal-ruby + grpc version

GIT
  remote: https://github.com/coinbase/temporal-ruby
  revision: 3e0dae708ec0e3eab8c44b57b64f5cd1881848e6
  
grpc (1.59.2)
主要语言
Ruby
星标
287
派生
113
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

coinbase/temporal-ruby 的其他 Issue

查看 coinbase/temporal-ruby 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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