Code Monkey home page Code Monkey logo

haredis's Introduction

Examples

The up script starts example services. The services are r1-r6 (Redis instances), s1-s6 (Sentinel instances), and haproxy, an haproxy instance in front of the 6 redis instances.

$ ./up all
Starting r1
Starting s1
Starting r2
Starting s2
Starting r3
Starting s3
Starting r4
Starting s4
Starting r5
Starting s5
Starting r6
Starting s6
Starting haproxy
$ ./status
Redis 6661: slave  127.0.0.1 6664
Redis 6662: slave  127.0.0.1 6664
Redis 6663: slave  127.0.0.1 6664
Redis 6664: master
Redis 6665: slave  127.0.0.1 6664
Redis 6666: slave  127.0.0.1 6664
sentinel 7661
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7662
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7663
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7664
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7665
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7666
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664

The down script stops the services that up starts. These can be one at a time, or all at once.

$ ./down r4
$ ./status
Redis 6661: slave  127.0.0.1 6664
Redis 6662: master
Redis 6663: slave  127.0.0.1 6664
Redis 6664: offline
Redis 6665: slave  127.0.0.1 6664
Redis 6666: slave  127.0.0.1 6664
sentinel 7661
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7662
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7663
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7664
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7665
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664
sentinel 7666
  master: 127.0.0.1 6664
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6664
    127.0.0.1:6662 -> 127.0.0.1:6664
    127.0.0.1:6663 -> 127.0.0.1:6664
    127.0.0.1:6665 -> 127.0.0.1:6664
    127.0.0.1:6666 -> 127.0.0.1:6664

Then wait for the sentinels to catch up, and run status again.

$./status
Redis 6661: slave  127.0.0.1 6662
Redis 6662: master
Redis 6663: slave  127.0.0.1 6662
Redis 6664: offline
Redis 6665: slave  127.0.0.1 6662
Redis 6666: slave  127.0.0.1 6662
sentinel 7661
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662
sentinel 7662
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662
sentinel 7663
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662
sentinel 7664
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662
sentinel 7665
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662
sentinel 7666
  master: 127.0.0.1 6662
  slaves: 
    127.0.0.1:6661 -> 127.0.0.1:6662
    127.0.0.1:6663 -> 127.0.0.1:6662
    127.0.0.1:6664 -> ?:0
    127.0.0.1:6665 -> 127.0.0.1:6662
    127.0.0.1:6666 -> 127.0.0.1:6662

After this, the original docs follow.

Redis HA - sentinel + haproxy

  • sentinel: autoswitch master/slave
  • haproxy: active check for only master node
  • haproxy api: disable failed nodes to prevent multimaster

"diagram"

without haproxy maintenance mode

  A is master, B is slave
  A crashes, sentinel convert B to master
  A is recovered (still master)
  haproxy balancing between A and B, until sentinel convert A to slave
  data written to A are lost

witch haproxy maintenance mode via notification script

  A is master, B is slave
  A crashes, sentinel convert B to master
  haproxy disable A
  A is recovered (still master) but disabled in haproxy
  haproxy points only to B

Run redis cluster

redis-server --port 6666
redis-server --port 6667
redis-server --port 6668

Set slaves

redis-cli -p 6667 SLAVEOF 127.0.0.1 6666
redis-cli -p 6668 SLAVEOF 127.0.0.1 6666

Run sentinel

redis-server sentinel.conf  --sentinel

Run haproxy

haproxy -f haproxy.cfg -db

Open http://localhost:8080/ and try kill some redis

Notice

tested on

  • redis 2.8.6
  • haproxy 1.5-dev21

[!] in production on single host you must specify different data dir before SLAVEOF command otherwise you loose data on master

haredis's People

Contributors

bertrama avatar falsecz avatar grosscol avatar tahajahangir avatar wision avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.