anchor.diff:          <!-- Thrift is used to maintain and sync slot (message groups) ranges between MB nodes. -->
           <thriftServerHost><%= @mb_thrift_server %></thriftServerHost>
           <thriftServerPort><%= @mb_thrift_port %></thriftServerPort>
  +        <thriftSOTimeout>0</thriftSOTimeout>
           <!--Thrift server reconnect timeout. Value specified in SECONDS-->
           <thriftServerReconnectTimeout>5</thriftServerReconnectTimeout>
           <!-- Hazelcast reliable topics are used to share all notifications across the MB cluster (e.g. subscription
           changes), And this property defines the time-to-live for a notification since its creation. (in Seconds) -->
           <clusterNotificationTimeout>10</clusterNotificationTimeout>
  +
  +        <!-- Configurations related RDBMS based coordination algorithm -->
  +        <rdbmsBasedCoordination enabled="false">
  +            <!-- Heartbeat interval used in the RDBMS base coordination algorithm in milliseconds -->
  +            <heartbeatInterval>5000</heartbeatInterval>
  +
  +            <!-- Time to wait before informing others about coordinator change in milliseconds. This value should be
  +            larger than a database read time including network latency and should be less than heartbeatInterval -->
  +            <coordinatorEntryCreationWaitTime>3000</coordinatorEntryCreationWaitTime>
  +
  +            <!-- Time interval used to poll database for membership related events in milliseconds. -->
  +            <eventPollingInterval>4000</eventPollingInterval>
  +        </rdbmsBasedCoordination>
  +
  +        <!-- Enabling this will make the cluster notifications such as Queue changes(additions and deletions),
  +        Subscription changes, etc. sent within the cluster be synchronized using RDBMS. If set to false, Hazelcast
  +        will be used for this purpose.-->
  +        <RDBMSBasedClusterEventSynchronization enabled="false">
  +
  +            <!--Specifies the interval at which, the cluster events will be read from the database. Needs to be
  +            declared in milliseconds. Setting this to a very low value could downgrade the performance where as
  +            setting this to a large value could increase the time taken for a cluster event to be synchronized in
  +            all the nodes in a cluster.-->
  +            <eventSyncInterval>1000</eventSyncInterval>
  +
  +        </RDBMSBasedClusterEventSynchronization>
       </coordination>
   
  -    <!-- You can enable/disable specific messaging transports in this section. By default all 
  -    transports are enabled. This section also allows you to customize the messaging flows used 
  +    <!-- You can enable/disable specific messaging transports in this section. By default all
  +    transports are enabled. This section also allows you to customize the messaging flows used
       within WSO2 MB. NOT performance related, but logic related. -->
       <transports>
           <amqp enabled="true">
  
positive.code:             <transactionMessageWriters>1</transactionMessageWriters>
          </inboundEvents>
  
          <failover>
  
          </failover>
  
      </performanceTuning>
  
  
negative.code:   ~  under the License.
    -->
  
  <!-- This is the root configuration file of WSO2 Message Broker (MB). Links to configurations of
  associated libraries are also specified here.
  
  [Note for developers] - If you intend to rename or modify a property name, remember to update
  relevant, org.wso2.andes.configuration.enums.AndesConfiguration, enum value using the Xpath
  expression of the property.
  
  This file is ciphertool compliant. Refer PRODUCT_HOME/repository/conf/security/cipher-text.properties for examples.-->
  <broker>
  
      <coordination>
          <!-- You can override the cluster node identifier of this MB node using the nodeID.
          If it is left as "default", the default node ID will be generated for it. (Using IP + UUID).
          The node ID of each member should ALWAYS be unique.-->
          <nodeID>default</nodeID>
  