-
Notifications
You must be signed in to change notification settings - Fork 459
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
Loss of interactivity with a join #7577
Comments
We need to look into the plan to understand whether this is actually expected (e.g. X cross-joins) or not. |
The query did not initially have cross joins, so if any are present they are due to transformations. Either way, even a query with a cross join in it should not cause a liveness problem. Here is the plan, it seems it has 1 cross join in it:
|
@philip-stoev Do you think we can close this issue? It's not quite clear anymore what it should be tracking, since the loss of interactivity problem doesn't exist anymore with the platform's decoupling of adapter and compute. If we take "loss of interactivity" as meaning "queries to a cluster don't return" then I think this issue might still be valid. But with the case reported in this issue, it's actually not too bad either. On my local machine:
The problematic cross join here is a delta join, and for those the fueling works reasonably well. This is not the case for differential cross joins (which are essentially unfueled), so maybe we should open a ticket for those instead. |
Im closing this in favor of #19093. Feel free to reopen if you disagree, @philip-stoev. |
What version of Materialize are you using?
What was the issue?
Loss of interactivity is observed when the following large join is processed:
This is against a very small TPC-C schema and the predicates in this query should all be reasonable. There are realistic join conditions throughout.
Is the issue reproducible? If so, please provide reproduction instructions.
Please attach any applicable log files.
The
mz_scheduling_histogram
report:Perf report:
The text was updated successfully, but these errors were encountered: