-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cockroachdb: consent query slow #1789
Comments
lopezator
added a commit
to lopezator/hydra
that referenced
this issue
Apr 8, 2020
Add an index over subject and client_id in order to avoid the (sometimes) underperformant zigzag join query. Closes ory#1789 Related to ory#1755 cockroachdb/cockroach#47179
lopezator
added a commit
to lopezator/hydra
that referenced
this issue
Apr 8, 2020
Add an index over subject and client_id in order to avoid the (sometimes) underperformant zigzag join query. Closes ory#1789 Related to ory#1755 cockroachdb/cockroach#47179
lopezator
added a commit
to lopezator/hydra
that referenced
this issue
May 7, 2020
Add an index over subject and client_id in order to avoid the (sometimes) underperformant zigzag join query. Closes ory#1789 Related to ory#1755 cockroachdb/cockroach#47179
lopezator
added a commit
to lopezator/hydra
that referenced
this issue
May 21, 2020
Add an index over subject and client_id in order to avoid the (sometimes) underperformant zigzag join query. Closes ory#1789 Related to ory#1755 cockroachdb/cockroach#47179
aeneasr
pushed a commit
that referenced
this issue
May 22, 2020
Add an index over subject and client_id in order to avoid the (sometimes) underperformant zigzag join query. Closes #1789 Related to #1755 cockroachdb/cockroach#47179
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Related issues:
#1755
cockroachdb/cockroach#47179
Apparently there is an intermittent (sometimes not reproducible) issue when zigzag join queries hit multiple regions.
More info about zigzag joins here:
cockroachdb/cockroach#23520 (comment)
As CockroachDB moves the leaseholder location and learns from usage, this is not reproducible always, but can be performing slow for a while, sometimes days.
Additional context
Underperformant query (sometimes we saw times as high as 50s):
Its query plan (EXPLAIN ):
You can see the culprit zigzag join here.
The text was updated successfully, but these errors were encountered: