Skip to content
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.

Sign up for GitHub

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

Jump to bottom

There is a deadlock problem in acquiring the connection #21202

Open
natehuangting opened this issue Sep 26, 2022 · 1 comment
Open

There is a deadlock problem in acquiring the connection #21202

natehuangting opened this issue Sep 26, 2022 · 1 comment
Labels
in: kernel status: volunteer wanted type: enhancement

Comments

@natehuangting
Copy link
Contributor

Bug Report

Assume that the logical table t_order corresponds to ds_${0..1}.t_order. The maximum number of connections for both ds_0 and ds_1 is 1. Request 1 has obtained the connection of ds_0, and is ready to request the connection of ds_1. Request 2 has obtained the connection of ds_1, and prepare to acquire the connection of ds_0. This is deadlock

Which version of ShardingSphere did you use?

master

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy
@TeslaCN
Copy link
Member

TeslaCN commented Sep 30, 2022

@tuichenchuxin I don't think this is a bug. It could be an enhancement.

@github-actions github-actions bot added the stale label Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: kernel status: volunteer wanted type: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@taojintianxia @TeslaCN @natehuangting @tuichenchuxin