hrishimantri
hrishimantri
Manju, I have tested this out and it seems to work fine. When would this patch be added to the master branch ?
@charsyam @manjuraj this doesnt seem to work when the server_failure_limit is set to 2. It keeps on showing connection refused error in the log. Setting it to 1 works fine....
@charsyam this is the config I used for testing : redis_read: listen: 0:22122 hash: murmur distribution: random auto_eject_hosts: true redis: true server_retry_timeout: 60000 server_connections : 2 server_failure_limit: 2 backlog: 512...
@charsyam any updates on this ?
@charsyam these are the logs i see : [Mon Jun 17 16:55:40 2013] nc.c:177 nutcracker-0.2.4 started on pid 11560 [Mon Jun 17 16:55:40 2013] nc.c:181 run, rabbit run / dig...
@charsyam to explain you more on how I'm testing this : 1) There are 2 redis instances running on two different boxes 2) Twemproxy is installed on a client box...
@charsyam - any updates to my previous comment ? Did you get a chance to look into testcase 2 ?
@manjuraj can you please apply this patch to the twemproxy_heartbeat branch ?