-
Notifications
You must be signed in to change notification settings - Fork 596
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(recovery): DynamicFilterExecutor exit unexpected when randomly kill meta #5726
Comments
@jon-chuang would you please help to take a look? |
@yezizp2012 Is the behaviour required that there is completely no error? Now with my PR for fix it seems that we are flooded with error messages like: 2022-01-02T02:22:48.841810Z ERROR node{id=7 name="compute-2"}:task{id=201064}: risingwave_stream::executor::actor: actor exit without stop barrier actor_id=25057 |
Cool!!! Those are expected error messages in deterministic recovery test. Then I guess this bug will be fixed with you PR. |
But it seems we have another deterministic test bug now. I will investigate. |
Seems like the DynamicFilterExecutor still exit unexpected. We can reproduce it using the following command: RUST_BACKTRACE=1 ./risedev sslt -- --kill-meta "e2e_test/streaming/dynamic_filter.slt" The test failed in L44:
Cc @jon-chuang , could you please help to take a look again? 😂 |
Indeed, I only fixed cluster recovery error on LHS, not RHS 😢 Looks like I will have to fix RHS now ~ |
Command
Bug
actors exit unexpected when executing include ../tpch/insert_orders.slt.part:
Seems like this bug caused in range cache of dynamic_filter state.
The text was updated successfully, but these errors were encountered: