Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Snowball effect with reconnecting to poor performing node #1252
We have a problem with JedisPool that aggravates perf issues of redis nodes when this issues only start to appear.
What we have:
If redis is starting to stuck for 4ms, instead of each read, we do
and only after that we have new Jedis instance for new read, but... actually nothing changed, we could just continue to use old instance.
So, when our Redis Cluster start to experience some perf issues - we finish it off by invalidating Jedis.
I could implement and provide PR for any solution solving or providing possibility to improve current standard flow.
What do you think?
This was referenced
Apr 6, 2016
referenced this issue
Apr 13, 2016
Final version which is working in our prod and does it fine: https://github.com/Spikhalskiy/jedis/releases/tag/PP-2
It's master with merged related pull requests.