-
Notifications
You must be signed in to change notification settings - Fork 760
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: query hangs when 2 nodes in cluster #17351
Comments
Seems to be another bug, can you share the dataset(parquet files) to reproduce this hang? And please provide the full logs with |
These are the dump of pipeline. I will have to ask about providing data as it is customer data
|
Can you trigger the hang with |
It looks like setting that does indeed fix the issue. I set to 0, could not reproduce. Set it back and it hang on the first execution |
Do you still need the data, or do you have an idea where to look? |
Yes, better to provide the data that could reproduce the issue. You can use
|
OK, I have the data and a script that should demonstrate the issue.
|
I reproduced it with simple case with 2 nodes.
https://pastila.nl/?000c2302/608024eb42a672312ff98d192fe62ca5#tLmRducW0uZHtzduF9Nuzw== |
using cte to replace the view v1
|
Another reproduce case without loading data
|
Search before asking
Version
v1.2.680-p3
What's Wrong?
When running with 2 query nodes, one particular query seems to hang indefinitely. When expanded to 3 nodes, it runs quickly. I attach logs for the query nodes. The hanging query id is
6c44bc25-bf60-4919-9119-d41de5f983e8
, but interestingly whilst getting the logs the same query ran quickly the first time I ran it, which would be query id59a95344-2476-4b2b-b9b1-30475371d4c4
, but that seems to have ran on query node 1 firstly.databend-query-0.txt
databend-query-1.txt
How to Reproduce?
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: