TiFlash v8.5.8: SIGSEGV in RegionCollector::run during a BTreeMap range lookup

未关闭
#11,236 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
linux, rust
领域
backend, databases

调研方向

Start with components/raftstore/src/coprocessor/region_info_accessor.rs at RegionCollector::run around line 780, then trace the BTreeMap::range call into the Proxy revision identified by the engine Git hash. Check existing crash reports and tests for this signature; the report does not identify a triggering event or provide a reproducer. Done means determining whether this revision has a known matching crash and documenting which RegionCollector events or state would help diagnose a recurrence.

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

描述

contribution

A TiFlash process exited with SIGSEGV on a production cluster. The application signal log recorded a read from unmapped address 0x16a. The service manager then restarted the process.

Environment: TiFlash v8.5.8, engine Git hash 3abdec8bff315647a056e6bf910abd4b59af2011, Linux x86-64.

Crash stack (faulting frame first, Rust symbols shortened for readability):

btree::search::NodeRef::find_lower_bound_index
    libtiflash_proxy.so+89803221
BTreeMap::range
    libtiflash_proxy.so+89777476
RegionCollector::run
    libtiflash_proxy.so+89934952
    components/raftstore/src/coprocessor/region_info_accessor.rs:780
yatp worker

The faulting instruction address recorded in the core matched the address in the application signal stack. The application log provided the symbolized Proxy frames. The core was truncated.

Reproduction: Observed in production. We have not identified the triggering Region event or produced a standalone reproducer.

Is this crash signature known for the Proxy revision shipped with TiFlash v8.5.8? Which RegionCollector events or state should we capture if it recurs?

主要语言
C++
星标
1k
派生
428
平均合并
2 天 7 小时
30 天内合并 PR
100

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

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

从这里开始

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

pingcap/tiflash 的其他 Issue

查看 pingcap/tiflash 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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