4.2. Redeploy Specific Clusters

When making changes that impact a single cluster, such as changing an alias or restoring from an earilier cluster topology descriptor file, you only redeploy the effected cluster.

To redeploy a specific cluster:

Verify the timestamp on the currently deployed Cluster Topology WAR files.

ls -lh /var/lib/knox/data/deployments
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 ad.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 dynamicgroup.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 myCluster.war.14505eeb448
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 myOtherCluster.war.14505ea9980
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 preauth127sla.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 preauth254sla.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 sandbox.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 staticgroup.war.14505e7e618

Redeploy a specific cluster. -
```
$gateway_home/bin/knoxcli.sh redeploy --cluster $cluster_name
```
where $cluster_name is the name of the cluster topology descriptor (without the XML extension). For example, myCluster.

Verify that the cluster was deployed.

ls -lh /var/lib/knox/data/deployments
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 ad.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 dynamicgroup.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 myCluster.war.14505eeb448
drwxrwxr-x 3 knox knox 4.0K Mar 28 00:50 myCluster.war.145062ab3a8
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 preauth127sla.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 preauth254sla.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 sandbox.war.14505e7e618
drwxrwxr-x 3 knox knox 4.0K Mar 27 23:54 staticgroup.war.14505e7e618

A new file with the current timestamp is created.

Legal notices