You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a Jedis Client to talk to Redis via twemproxy
Can you please go ahead and test these scenarios :
Testcase 1) Both the redis instances are up and running (twemp works fine)
Testcase 2) Stop Redis instance running on one of the box and then check if the request goes to the other slave where REDIS is up and running. If the failure_limit is set to 2 in the twemproxy conf then the node fails to be ejected. Though the Node gets ejected when the failure_limit is set to 1 and the request is then routed to the other slave.
Testcase 3) Restart the redis instance stopped in Testcase 2. The node should get restored and the requests should again be distributed randomly amongst the two slaves.
Testcase 1 and Testcase 3 work fine but Testcase 2 fails to work on failure_limit set to 2. Can you please retest this at your side ?
The text was updated successfully, but these errors were encountered:
charsyam
added a commit
to charsyam/twemproxy
that referenced
this issue
Jun 25, 2013
@hrishimantri reported this:
Can you please go ahead and test these scenarios :
Testcase 1) Both the redis instances are up and running (twemp works fine)
Testcase 2) Stop Redis instance running on one of the box and then check if the request goes to the other slave where REDIS is up and running. If the failure_limit is set to 2 in the twemproxy conf then the node fails to be ejected. Though the Node gets ejected when the failure_limit is set to 1 and the request is then routed to the other slave.
Testcase 3) Restart the redis instance stopped in Testcase 2. The node should get restored and the requests should again be distributed randomly amongst the two slaves.
Testcase 1 and Testcase 3 work fine but Testcase 2 fails to work on failure_limit set to 2. Can you please retest this at your side ?
The text was updated successfully, but these errors were encountered: