The current implementation of a full cluster restart will save the CH and state for all caches.

If caches does not have a persistence or the persistence is a shared one this might not be necesarry as the cache can start correctly with one node (empty or consistent persistence).
In that case it should be allowed to start the cache and make it available.

There are two approaches

• use extra parameter for shutdown to allow it
  This will leave the default behavior the same and the admin need to decide
• change the current behavior and add a parameter to flag a FULL cluster restart

The benefit of the full cluster restart is that the caches will be available for clients only if the cluster is completely restarted, so no further state-transfer is needed for optimal performance