We run a Magento 1 CE cluster where we have split the frontend and admin away to separate clusters. This gives us the ability to deploy schema changes to the admin host first, which is great, but it also introduces a problem.
When we deploy modules to the admin host, we typically leave all caches on except layout cache. With our last deploy our admin broke, because it threw an error on a missing helper class.
The reason for this is probably, that the fronts (admin and fonts share the same cache prefix id) did not have that module, and the admin picked up on that cache?
How could we prevent this in future? Would it help to disable all caches when we deploy?