Chapter 15. Performing rolling upgrades for Data Grid Server clusters

Procedure

1. Create a remote cache store configuration, in JSON format, that allows the target cluster to connect to the source cluster.

   Remote cache stores on the target cluster use the Hot Rod protocol to retrieve data from the source cluster.

   {
     "remote-store": {
       "cache": "myCache",
       "shared": true,
       "raw-values": true,
       "security": {
         "authentication": {
           "digest": {
             "username": "username",
             "password": "changeme",
             "realm": "default"
           }
         }
       },
       "remote-server": [
         {
           "host": "127.0.0.1",
           "port": 12222
         }
       ]
     }
   }

2. Use the Data Grid Command Line Interface (CLI) or REST API to add the remote cache store configuration to the target cluster so it can connect to the source cluster.

   • CLI: Use the migrate cluster connect command on the target cluster.

     [//containers/default]> migrate cluster connect -c myCache --file=remote-store.json

   • REST API: Invoke a POST request that includes the remote store configuration in the payload with the rolling-upgrade/source-connection method.

     POST /v2/caches/myCache/rolling-upgrade/source-connection

3. Repeat the preceding step for each cache that you want to migrate.

4. Switch clients over to the target cluster, so it starts handling all requests.

   1. Update client configuration with the location of the target cluster.
   2. Restart clients.

Procedure

1. Start synchronizing each cache that you want to migrate to the target cluster with the Data Grid Command Line Interface (CLI) or REST API.

   • CLI: Use the migrate cluster synchronize command.

     migrate cluster synchronize -c myCache

   • REST API: Use the ?action=sync-data parameter with a POST request.

     POST /v2/caches/myCache?action=sync-data

     When the operation completes, Data Grid responds with the total number of entries copied to the target cluster.

2. Disconnect each node in the target cluster from the source cluster.

   • CLI: Use the migrate cluster disconnect command.

     migrate cluster disconnect -c myCache

   • REST API: Invoke a DELETE request.

     DELETE /v2/caches/myCache/rolling-upgrade/source-connection