-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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 Server Fails to Start with DistSQL Error #106537
Labels
A-multitenancy
Related to multi-tenancy
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
db-cy-23
T-sql-queries
SQL Queries Team
Comments
jeffswenson
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-multitenancy
Related to multi-tenancy
T-sql-queries
SQL Queries Team
T-multitenant
Issues owned by the multi-tenant virtual team
labels
Jul 10, 2023
jeffswenson
added a commit
to jeffswenson/cockroach
that referenced
this issue
Jul 10, 2023
This PR contains a test that reproduces cockroachdb#106537. Part of: cockroachdb#106537 Release note: None
jeffswenson
added a commit
to jeffswenson/cockroach
that referenced
this issue
Jul 11, 2023
This contains fixes to two sources of flakes in TestDirectoryConnect: - sqlproxy http draining is now tied into the stopper. This avoids a source of goroutine leaks. - The sql server is gracefully drained to work around cockroachdb#106537. When combined with cockroachdb#106599, I was able to run the test for 25K interations under stress with no flakes. Fixes: cockroachdb#105402
jeffswenson
added a commit
to jeffswenson/cockroach
that referenced
this issue
Jul 11, 2023
This contains fixes to two sources of flakes in TestDirectoryConnect: - sqlproxy http draining is now tied into the stopper. This avoids a source of goroutine leaks. - The sql server is gracefully drained to work around cockroachdb#106537. When combined with cockroachdb#106599, I was able to run the test for 25K interations under stress with no flakes. Fixes: cockroachdb#105402
craig bot
pushed a commit
that referenced
this issue
Jul 11, 2023
106549: sqlproxyccl: deflake TestDirectoryConnect r=JeffSwenson a=JeffSwenson This contains fixes to two sources of flakes in TestDirectoryConnect: - sqlproxy http draining is now tied into the stopper. This avoids a source of goroutine leaks. - The sql server is gracefully drained to work around #106537. When combined with #106599, I was able to run the test for 25K interations under stress with no flakes. Fixes: #105402 Co-authored-by: Jeff <[email protected]>
exalate-issue-sync
bot
removed
the
T-multitenant
Issues owned by the multi-tenant virtual team
label
Aug 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-multitenancy
Related to multi-tenancy
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
db-cy-23
T-sql-queries
SQL Queries Team
Describe the problem
SQL servers identify themselves in the system.sql_instances table. The table
contains the sql address and rpc address of the sql server. Here are example
contents of the sql_instances table:
If the sql_instance table contains a stale row with an ipaddress+port that is
reused by something else, then sql servers will fail to start with a distsql
error. It looks like a query run during sql server start up attempts to
schedule a dist sql flow on the stale instance and the distsql query failing
causes the process to crash.
This was discovered while attempting to deflake
#105402. The bug could happen in
production if an ip address was reused by another tenant or if a sql server
container crashed in a pod and was restarted.
To Reproduce
PR 106538 contains a regression test. Running the test will fail with the following stack trace:
Jira issue: CRDB-29607
The text was updated successfully, but these errors were encountered: