text: <?xml version="1.0" encoding="UTF-8"?>
  <hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.5.xsd"
             xmlns="http://www.hazelcast.com/schema/config"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <network>
          <port auto-increment="true" port-count="100">5701</port>
          <outbound-ports>
              <!--
              Allowed port range when connecting to other nodes.
              0 or * means use system provided port.
              -->
              <ports>0</ports>
          </outbound-ports>
          <join>
              <multicast enabled="false"/>
              <tcp-ip enabled="false"/>
              <aws enabled="false"/>
          </join>
      </network>
      <map name="cache">
          <!--
             Data type that will be used for storing recordMap.
             Possible values:
             BINARY (default): keys and values will be stored as binary data
             OBJECT : values will be stored in their object forms
             NATIVE : values will be stored in non-heap region of JVM
          -->
          <in-memory-format>BINARY</in-memory-format>
  
          <!--
              Number of backups. If 1 is set as the backup-count for example,
              then all entries of the map will be copied to another JVM for
              fail-safety. 0 means no backup.
          -->
          <backup-count>1</backup-count>
          <!--
              Number of async backups. 0 means no backup.
          -->
          <async-backup-count>0</async-backup-count>
          <!--
            Maximum number of seconds for each entry to stay in the map. Entries that are
            older than <time-to-live-seconds> and not updated for <time-to-live-seconds>
            will get automatically evicted from the map.
            Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
          -->
          <time-to-live-seconds>10</time-to-live-seconds>
          <!--
            Maximum number of seconds for each entry to stay idle in the map. Entries that are
            idle(not touched) for more than <max-idle-seconds> will get
            automatically evicted from the map. Entry is touched if get, put or containsKey is called.
            Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
          -->
          <max-idle-seconds>0</max-idle-seconds>
          <!--
              Valid values are:
              NONE (no eviction),
              LRU (Least Recently Used),
              LFU (Least Frequently Used).
              NONE is the default.
          -->
          <eviction-policy>NONE</eviction-policy>
          <!--
              Maximum size of the map. When max size is reached,
              map is evicted based on the policy defined.
              Any integer between 0 and Integer.MAX_VALUE. 0 means
              Integer.MAX_VALUE. Default is 0.
          -->
          <max-size policy="PER_NODE">0</max-size>
          <!--
              When max. size is reached, specified percentage of
              the map will be evicted. Any integer between 0 and 100.
              If 25 is set for example, 25% of the entries will
              get evicted.
          -->
          <eviction-percentage>25</eviction-percentage>
          <!--
              Minimum time in milliseconds which should pass before checking
              if a partition of this map is evictable or not.
              Default value is 100 millis.
          -->
          <min-eviction-check-millis>100</min-eviction-check-millis>
          <!--
              While recovering from split-brain (network partitioning),
              map entries in the small cluster will merge into the bigger cluster
              based on the policy set here. When an entry merge into the
              cluster, there might an existing entry with the same key already.
              Values of these entries might be different for that same key.
              Which value should be set for the key? Conflict is resolved by
              the policy set here. Default policy is PutIfAbsentMapMergePolicy
  
              There are built-in merge policies such as
              com.hazelcast.map.merge.PassThroughMergePolicy; entry will be overwritten if merging entry exists for the key.
              com.hazelcast.map.merge.PutIfAbsentMapMergePolicy ; entry will be added if the merging entry doesn't exist in the cluster.
              com.hazelcast.map.merge.HigherHitsMapMergePolicy ; entry with the higher hits wins.
              com.hazelcast.map.merge.LatestUpdateMapMergePolicy ; entry with the latest update wins.
          -->
          <merge-policy>com.hazelcast.map.merge.PutIfAbsentMapMergePolicy</merge-policy>
  
      </map>
      <reliable-topic name="firehose">
          <read-batch-size>10</read-batch-size>
          <topic-overload-policy>BLOCK</topic-overload-policy>
          <statistics-enabled>true</statistics-enabled>
      </reliable-topic>
  
      <properties>
        <property name="hazelcast.version.check.enabled">false</property>
      </properties>
  </hazelcast>
  