Kiling a remote shared page cache risks bringing the Stone down
If a remote shared page cache is killed using SIGTERM (which normally performs a clean shutdown), there are code paths in which it does not correctly wait for all threads to detach from the Stone's cache. This results in the Stone exit.
Workaround
The risk of hitting this bug is proportional to the number of active gems running on the cache at the time of the kill. To minimize the risk, terminate all the gems first, before killing the cache.
Last updated: 12/3/18