Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: "Failed to fetch filter key extractor tables" causing compaction task to fail until restarting meta node #14459

Closed
hzxa21 opened this issue Jan 9, 2024 · 4 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@hzxa21
Copy link
Collaborator

hzxa21 commented Jan 9, 2024

Describe the bug

We see these message flooding the compactor log and compaction tasks keeps failing until meta node restart
"Failed to fetch filter key extractor tables [{35157}. [[35157]] may be removed by meta-service. "
image

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

1.5.1

Additional context

No response

@hzxa21 hzxa21 added the type/bug Something isn't working label Jan 9, 2024
@github-actions github-actions bot added this to the release-1.7 milestone Jan 9, 2024
@zwang28
Copy link
Contributor

zwang28 commented Jan 9, 2024

It happened once before. I suspect there is a code path in meta node that a failed/cancelled stream job doesn't notify hummock manager to remove stale table ids.

@hzxa21
Copy link
Collaborator Author

hzxa21 commented Mar 6, 2024

May be related: #15355. Do we know whether this issue can occur without #15355? cc @zwang28

@zwang28
Copy link
Contributor

zwang28 commented Mar 7, 2024

duplicate of #15144

@zwang28 zwang28 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2024
@zwang28
Copy link
Contributor

zwang28 commented Mar 7, 2024

May be related: #15355. Do we know whether this issue can occur without #15355? cc @zwang28

There have been quite some changes of meta's stream job management between v1.5.1 when this issue occurred, and latest v1.7.
I'll look into it in v1.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants