To get a faster redis failover -


i working 2 redis instances monitored 1 sentinel. when master goes down , there "+sdown", run notification-script promote slave master using following command on redis-client:

slaveof no one .

it works fine.

my question is, takes around 10 secs slave become master , application continue working again.

how can reduce time stamp?

below sentinel config::::

sentinel monitor mymaster 127.0.0.1 6379 1  sentinel down-after-milliseconds mymaster 5000  sentinel failover-timeout mymaster 900000  sentinel can-failover mymaster yes  sentinel parallel-syncs mymaster 1  sentinel notification-script mymaster /etc/init.d/config/script.sh 

this not direct answer question, description of different setup avoids need having quick response (in scenario's).

when model use case in uml, never put redis sentinel in default flow. sentinel our guard situations unknown errors occor: exceptional flow.

if know beforehand if client needs connect different redis instance, instruct client so, using redis pub/sub (combined low resolution polling, since pub/sub traffic not guaranteed-delivery).

kind regards, tw


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

android - Keyboard hides my half of edit-text and button below it even in scroll view -

css - Make div keyboard-scrollable in jQuery Mobile? -