-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
sql: incomplete vectorized traces #59555
Comments
To clarify - the query runs in parallel on the three nodes, but the traces for the actual flow and scans are missing from node 2 and 3. It looks like a problem with tracing when using the vectorized engine. I tried to repro locally in a simpler case and could not - I saw traces for scans from all nodes. |
Yeah, it is a known issue (#55821) that we intend to address for 21.1 release. |
An update here is that #61380 will fix it and will be in 21.1: |
Describe the problem
I ran across an interesting observation while trying to explain how queries are run in parallel within CRDB. I was using the internal KV workload and have a fair number of ranges distributed across three nodes:
I was expecting that the above query would run in parallel, but when looking at the Jaeger trace collected, it appears to not be serial.
[stmt-bundle-625911811735650305.zip](https://github.com/cockroachdb/cockroach/files/5889843/stmt-bundle-625911811735650305.zip) [stmt-bundle-628463749489590273.zip](https://github.com/cockroachdb/cockroach/files/5889847/stmt-bundle-628463749489590273.zip)
At the advise of engineering, I ran this by disabling vectorization
SET vectorize = off
and it appeared to run as expected albeit longer.The text was updated successfully, but these errors were encountered: