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

CoordinatorWorker received CommitRequests with different epochs when collecting metadata from SinkWriters #19337

Open
ly9chee opened this issue Nov 11, 2024 · 0 comments
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@ly9chee
Copy link
Contributor

ly9chee commented Nov 11, 2024

Describe the bug

Recently, I observed that the meta continuously prints the WARN logs:
WARN risingwave_meta::manager::sink_coordination::coordinator_worker: current epoch is 7476731719516160 but get request from 7476732374876160

There are dozens of StarRocks sinks in my cluster, some of them with a parallelism of 3. when I changed all of the sinks' parallelism to 1, the WARN log disappeared.

Error message/log

No response

To Reproduce

Creating starrocks sink with parallelism greater than 1 and sink_decouple enabled.

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

2.0.2

Additional context

No response

@ly9chee ly9chee added the type/bug Something isn't working label Nov 11, 2024
@github-actions github-actions bot added this to the release-2.2 milestone Nov 11, 2024
@wenym1 wenym1 self-assigned this Nov 12, 2024
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

2 participants