You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: Failed to run the query
Caused by these errors (recent errors listed first):
1: gRPC request to meta service failed: Internal error
2: gRPC request to stream service failed: Internal error
3: actor 105 not found in info table
Reported in one of our customer and discovered by @shanicky , this is a corner for creating streaming jobs. It only appears under the following three situations:
the streaming job is create sink into table.
the sink is performing temporary joins on multiple tables.
The set of CNs that all joined tables distributed on is a subset of the set of CNs that the target table distributed on. In other words, some actors in the target table are distributed on CNs that are not present in the join tables.
Currently we only broadcast the info of new actors and all upstream actors to compute nodes that only have some building actors during creation of streaming job.
It works for streaming jobs except for sink into table, because we broadcast actor infos of the sink and new target table jobs separately. Under the situation mentioned above, Some actors of the sink on some CNs do not know the information of the upstream sink actors when building.
yezizp2012
changed the title
bug: The actor information has not been broadcasted to the affected CN
bug: the actor information has not been broadcasted to the affected CNs
Jan 31, 2024
Describe the bug
Reported in one of our customer and discovered by @shanicky , this is a corner for creating streaming jobs. It only appears under the following three situations:
create sink into table
.Currently we only broadcast the info of new actors and all upstream actors to compute nodes that only have some building actors during creation of streaming job.
risingwave/src/meta/src/stream/stream_manager.rs
Lines 400 to 409 in e05015a
It works for streaming jobs except for sink into table, because we broadcast actor infos of the sink and new target table jobs separately. Under the situation mentioned above, Some actors of the sink on some CNs do not know the information of the upstream sink actors when building.
risingwave/src/meta/src/stream/stream_manager.rs
Lines 493 to 505 in e05015a
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: