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.

Sign up for GitHub

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

Jump to bottom

bug: dispatcher_id should be downstream's fragment_id instead of actor_id #13592

Closed
Tracked by #13591
fuyufjh opened this issue Nov 22, 2023 · 0 comments
Closed
Tracked by #13591

bug: dispatcher_id should be downstream's fragment_id instead of actor_id #13592

fuyufjh opened this issue Nov 22, 2023 · 0 comments
Assignees
@BugenZhao
Labels
type/bug Something isn't working
Milestone
release-1.5

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Nov 22, 2023 •
edited
Loading

Observed from metrics:

image

It seems that the "fragment_id" is not actually a fragment_id but a actor_id?

Might be caused by this:

risingwave/src/compute/src/rpc/service/exchange_service.rs

Line 111 in 32717b4

up_down_actor_ids,

Seems wrong?

image

Pointed by @shanicky ❤️
@fuyufjh fuyufjh mentioned this issue Nov 22, 2023
Closed
3 tasks
@github-actions github-actions bot added this to the release-1.5 milestone Nov 22, 2023
@fuyufjh fuyufjh changed the title bug: should be downstream's instead of bug: dispatcher_id should be downstream's fragment_id instead of actor_id Nov 22, 2023
@fuyufjh fuyufjh added the type/bug Something isn't working label Nov 22, 2023
@BugenZhao BugenZhao mentioned this issue Nov 24, 2023
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BugenZhao BugenZhao

Labels
type/bug Something isn't working
Projects
None yet
Milestone
release-1.5
Development

No branches or pull requests
2 participants
@fuyufjh @BugenZhao