In this release we will push an update to the hypernode-servicectl command-line tool that will make it so that the app user is now also privileged to restart the Redis service. It will be possible to restart the default Redis instance that is commonly used for the full page cache, but it will also be possible to restart the optional persistent Redis instance that is more suited for storing user sessions because of the configured eviction policy. Restarting Redis (instead of just flushing it) can sometimes have some utility in rare low memory situations where the cache gets confused and can not be gracefully manipulated anymore.