anchor.diff:  # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
   # You can also append an optional chroot string to the urls to specify the
   # root directory for all kafka znodes.
  -zookeeper.connect=localhost:2181
  +zookeeper.connect=<%= localip %>:2181
   
   # Timeout in ms for connecting to zookeeper
   zookeeper.connection.timeout.ms=2000
  
positive.code: 
  ############################# Socket Server Settings #############################
  
  # The port the socket server listens on
  port=9092
  
  # Hostname the broker will bind to. If not set, the server will bind to all interfaces
  #host.name=localhost
  
  # Hostname the broker will advertise to producers and consumers. If not set, it uses the
  # value for "host.name" if configured.  Otherwise, it will use the value returned from
  # java.net.InetAddress.getCanonicalHostName().
  #advertised.host.name=<hostname routable by clients>
  
  # The port to publish to ZooKeeper for clients to use. If this is not set,
  # it will publish the same port that the broker binds to.
  
negative.code: ############################# Log Flush Policy #############################
  
  # Messages are immediately written to the filesystem but by default we only fsync() to sync
  # the OS cache lazily. The following configurations control the flush of data to disk.
  # There are a few important trade-offs here:
  #    1. Durability: Unflushed data may be lost if you are not using replication.
  #    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
  #    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks.
  # The settings below allow one to configure the flush policy to flush data after a period of time or
  # every N messages (or both). This can be done globally and overridden on a per-topic basis.
  
  