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

[Bug] auvacuum worker worked in loop and it is caused to High CPU usage

未关闭
#1,850 10 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

首先,在包含几个 PXF foreign tables 的干净数据库上复现该循环,然后检查 auvacuum worker logs 以及报告中显示的 vacuum 失败。完成的标准是 vacuum 不再处理这些 foreign tables,worker 停止循环,并消除高 CPU 使用率。

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

描述

type: Bug
Apache Cloudberry version

We are trying to test Apache Cloudberry 2.1.0 on Astra Linux 1.8.1 (Debian 12 based)

What happened

Hello,
We found the next problem with auvacuum worker using not correct logic and trying to vacuum PXF foreghn tables located on Hadoop.
It is caused to high CPU usage by autovacuum workers on database with high coung of PXF tables

Image

In Cloudberry master log we can see many messages by the next screenshoot we can see

Image

When we can run vacuum on problem database, vacuum crashed by the next error

Image

And we can identify this object as PXF foreighn table

Image
What you think should happen instead

And i think correct about vacuum logic can not work with foreighn tables and in Greenplum logic means not use PXF tables too in this mechanizm.

How to reproduce

I think need to create couple of PXF tables on clean DB.

Operating System

Astra Linux 1.8.1 (Debian 12 based)

Anything else

Every time.

Are you willing to submit PR?
  • Yes, I am willing to submit a PR!
Code of Conduct
主要语言
C
星标
1.4k
派生
248
平均合并
4 天 10 小时
30 天内合并 PR
40

环境准备

从这里开始

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

apache/cloudberry 的其他 Issue

查看 apache/cloudberry 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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