13.2. Rolling Upgrades Using Hot Rod (Remote Client-Server Mode)

Begin a new cluster (Target Cluster)

Configure the Target Cluster with a RemoteCacheStore

Figure 13.1. Configure the Target Cluster with a RemoteCacheStore

<subsystem xmlns="urn:jboss:datagrid:infinispan:6.1" 
           default-cache-container="local">
    <cache-container name="local"                         
	             default-cache="default">
        <local-cache name="default"                         
		     start="EAGER">
            <locking isolation="NONE"                         
                     acquire-timeout="30000"                         
                     concurrency-level="1000"                         
                     striping="false"/>
            <transaction mode="NONE"/>
            <remote-store cache="default"                         
                          socket-timeout="60000"                         
                          tcp-no-delay="true"                         
                          hotrod-wrapping="true">
                <remote-server outbound-socket-binding="remote-store-hotrod-server"/>
	    </remote-store>
        </local-cache>
    </cache-container>
    <cache-container name="security"/>
</subsystem>

Configure clients to point to the Target Cluster

Figure 13.2. Clients point to the Target Cluster with the Source Cluster as RemoteCacheStore for the Target Cluster.

Dump the Source Cluster keyset

• JMX

  Invoke the recordKnownGlobalKeyset operation on the RollingUpgradeManager MBean on the Source Cluster for every cache that needs to be migrated.

• CLI

  Invoke the upgrade --dumpkeys command on the Source Cluster for every cache that needs to be migrated, or use the --all switch to dump all caches in the cluster.

Fetch remaining data from the Source Cluster

• JMX

  Invoke the synchronizeData operation and specify the hotrod parameter on the RollingUpgradeManager MBean on the Target Cluster for every cache that needs to be migrated.

• CLI

  Invoke the upgrade --synchronize=hotrod command on the Target Cluster for every cache that needs to be migrated, or use the --all switch to synchronize all caches in the cluster.

Disabling the RemoteCacheStore

• JMX

  Invoke the disconnectSource operation specifying the hotrod parameter on the RollingUpgradeManager MBean on the Target Cluster.

• CLI

  Invoke the upgrade --disconnectsource=hotrod command on the Target Cluster.