anchor.diff:  #
   # By default the priority is 100.
   slave-priority 100
  +
  +# It is possible for a master to stop accepting writes if there are less than
  +# N slaves connected, having a lag less or equal than M seconds.
  +#
  +# The N slaves need to be in "online" state.
  +#
  +# The lag in seconds, that must be <= the specified value, is calculated from
  +# the last ping received from the slave, that is usually sent every second.
  +#
  +# This option does not GUARANTEES that N replicas will accept the write, but
  +# will limit the window of exposure for lost writes in case not enough slaves
  +# are available, to the specified number of seconds.
  +#
  +# For example to require at least 3 slaves with a lag <= 10 seconds use:
  +#
  +# min-slaves-to-write 3
  +# min-slaves-max-lag 10
  +#
  +# Setting one or the other to 0 disables the feature.
  +#
  +# By default min-slaves-to-write is set to 0 (feature disabled) and
  +# min-slaves-max-lag is set to 10.
   
   ################################## SECURITY ###################################
   
  
positive.code: # be a good idea.
  repl-disable-tcp-nodelay no
  
  # The slave priority is an integer number published by Redis in the INFO output.
  # It is used by Redis Sentinel in order to select a slave to promote into a
  # master if the master is no longer working correctly.
  #
  # A slave with a low priority number is considered better for promotion, so
  # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
  # pick the one wtih priority 10, that is the lowest.
  #
  # However a special priority of 0 marks the slave as not able to perform the
  # role of master, so a slave with priority of 0 will never be selected by
  
negative.code: # You can reclaim memory used by the slow log with SLOWLOG RESET.
  slowlog-max-len 128
  
  ############################# Event notification ##############################
  
  # Redis can notify Pub/Sub clients about events happening in the key space.
  # This feature is documented at http://redis.io/topics/keyspace-events
  # 
  # For instance if keyspace events notification is enabled, and a client
  # performs a DEL operation on key "foo" stored in the Database 0, two
  # messages will be published via Pub/Sub:
  #
  # PUBLISH __keyspace@0__:foo del
  # PUBLISH __keyevent@0__:del foo
  #
  # It is possible to select the events that Redis will notify among a set
  # of classes. Every class is identified by a single character:
  #
  #  K     Keyspace events, published with __keyspace@<db>__ prefix.
  #  E     Keyevent events, published with __keyevent@<db>__ prefix.
  #  g     Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
  #  $     String commands
  #  l     List commands
  #  s     Set commands
  #  h     Hash commands
  #  z     Sorted set commands
  #  x     Expired events (events generated every time a key expires)
  #  e     Evicted events (events generated when a key is evicted for maxmemory)
  #  A     Alias for g$lshzxe, so that the "AKE" string means all the events.
  #
  #  The "notify-keyspace-events" takes as argument a string that is composed
  #  by zero or multiple characters. The empty string means that notifications
  #  are disabled at all.
  #
  #  Example: to enable list and generic events, from the point of view of the
  #           event name, use:
  #
  #  notify-keyspace-events Elg
  #
  #  Example 2: to get the stream of the expired keys subscribing to channel
  #             name __keyevent@0__:expired use:
  #
  #  notify-keyspace-events Ex
  #
  #  By default all notifications are disabled because most users don't need
  #  this feature and the feature has some overhead. Note that if you don't
  #  specify at least one of K or E, no events will be delivered.
  notify-keyspace-events ""
  
  ############################### ADVANCED CONFIG ###############################
  
  # Hashes are encoded using a memory efficient data structure when they have a
  