When using chirpstack v3, I often encounter the problem Redis: connection pool timeout (code: 2). Related to (Redis: connection pool timeout (code: 2))
After checking, I found it due to application-server too busy that AS did not release the redis connection in time, actually, I checked redis itself and it was working properly.
For these reason and To keep migration(v3 → v4) easy, I upgraded to chirpstack v4, and try to deployed multiple chirpstack components to avoid this problem.
So the various instances of chirpstack can work together to process more data, but the subsequent bottleneck will be mqtt, redis and postgres. Is it right?
Thank you very much for your patient and prompt response, it helped me a lot.