Open soafftt opened 1 week ago
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 , please allow the team some time to get to this question.
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?