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.

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

Questions about the acquire of boundAsyncPool #3055

Open
soafftt opened this issue Nov 19, 2024 · 1 comment
Open

Questions about the acquire of boundAsyncPool #3055

soafftt opened this issue Nov 19, 2024 · 1 comment
Labels
for: team-attention An issue we need to discuss as a team to make progress status: waiting-for-triage

Comments

@soafftt
Copy link

soafftt commented Nov 19, 2024

Project is using boundAsyncPool for Redis Pipeline functionality.

There are two AWS Elasticache Redis Slaves, and we are using DirDnsResolver to disable DnsCache as much as possible.

It seems like a traffic that doesn't require the use of a pool, but I'm using a pipeline because there are many concurrent commands.

There is a phenomenon in which the acqure of boundAsyncPool provides connection in the FIFO, so it is crowded to one of the two Slaves.

Can you give me some advice to solve these issues?

@soafftt soafftt changed the title Questions about the acquisition of boundAsyncPool Questions about the acquire of boundAsyncPool Nov 19, 2024
@tishun tishun added for: team-attention An issue we need to discuss as a team to make progress status: waiting-for-triage labels Nov 22, 2024
@tishun
Copy link
Collaborator

tishun commented Nov 22, 2024

@soafftt , please allow the team some time to get to this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: team-attention An issue we need to discuss as a team to make progress status: waiting-for-triage
Projects
None yet
Development

No branches or pull requests

2 participants