Do not treat a JedisDataException as a FatalConnectionException
Opened this issue · 0 comments
smukil commented
java.lang.RuntimeException: java.lang.RuntimeException: com.netflix.dyno.connectionpool.exception.FatalConnectionException: FatalConnectionException: [host=Host [hostname=ec2-35-171-6-221.compute-1.amazonaws.com, ipAddress=100.77.84.38, port=8102, rack: us-east-1e, datacenter: us-east-1, status: Up, hashtag=null], latency=0(0), attempts=1]redis.clients.jedis.exceptions.JedisDataException: ERR Dynomite: Failed to achieve Quorum
A "failed to achieve quorum" error ultimately ends up being treated as though something is wrong with the connection and Dyno shuts down the connection because of this. This is incorrect, and we should handle this failure differently.