anchor.diff:  # If port 0 is specified Redis will not listen on a TCP socket.
   #SET PER PROCESS
   port <%= p('redis.broker.dedicated_port') %>
  +
  +# TCP listen() backlog.
  +#
  +# In high requests-per-second environments you need an high backlog in order
  +# to avoid slow clients connections issues. Note that the Linux kernel
  +# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  +# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  +# in order to get the desired effect.
  +tcp-backlog 511
   
   # If you want you can bind a single interface, if the bind option is not
   # specified all the interfaces will listen for incoming connections.
  
positive.code: auto-aof-rewrite-percentage 100
  auto-aof-rewrite-min-size 64mb
  
  ################################ LUA SCRIPTING  ###############################
  
  # Max execution time of a Lua script in milliseconds.
  
negative.code: # administrative / dangerous commands.
  slave-read-only <%= p('redis.replication.slave_read_only') %>
  
  # Replication SYNC strategy: disk or socket.
  #
  # -------------------------------------------------------
  # WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY
  # -------------------------------------------------------
  #
  # New slaves and reconnecting slaves that are not able to continue the replication
  # process just receiving differences, need to do what is called a "full
  # synchronization". An RDB file is transmitted from the master to the slaves.
  # The transmission can happen in two different ways:
  #
  # 1) Disk-backed: The Redis master creates a new process that writes the RDB
  #                 file on disk. Later the file is transferred by the parent
  #                 process to the slaves incrementally.
  # 2) Diskless: The Redis master creates a new process that directly writes the
  #              RDB file to slave sockets, without touching the disk at all.
  #
  # With disk-backed replication, while the RDB file is generated, more slaves
  # can be queued and served with the RDB file as soon as the current child producing
  # the RDB file finishes its work. With diskless replication instead once
  # the transfer starts, new slaves arriving will be queued and a new transfer
  # will start when the current one terminates.
  #
  # When diskless replication is used, the master waits a configurable amount of
  # time (in seconds) before starting the transfer in the hope that multiple slaves
  # will arrive and the transfer can be parallelized.
  #
  # With slow disks and fast (large bandwidth) networks, diskless replication
  # works better.
  repl-diskless-sync no
  
  # When diskless replication is enabled, it is possible to configure the delay
  # the server waits in order to spawn the child that transfers the RDB via socket
  # to the slaves.
  #
  # This is important since once the transfer starts, it is not possible to serve
  # new slaves arriving, that will be queued for the next RDB transfer, so the server
  # waits a delay in order to let more slaves arrive.
  #
  # The delay is specified in seconds, and by default is 5 seconds. To disable
  # it entirely just set it to 0 seconds and the transfer will start ASAP.
  repl-diskless-sync-delay 5
  
  # Slaves send PINGs to server in a predefined interval. It's possible to change
  # this interval with the repl_ping_slave_period option. The default value is 10
  # seconds.
  