-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cached data from current release causes new release to fail with redis caching #151
Comments
We have also experienced this. But we have seen that
We still have some issues in our production environment during production releases - where classes are not generated. Maybe |
That's not possible, but I should make sure that running commands between release_path and current_path the cache should be flushed. |
Small update: you also need to fix the autoloader because that is cached too. So run this too: |
Trying to get a fail-safe method for this but it feels like there isn't one. As soon as you flush the redis cache there is the possibility that a visitor is on the site and trigger the redis cache for the current release, while you were trying to fill it with the release_path. |
Also an issue when running php 7.2 / 7.3 in your current release and the latest release need php 7.4 |
Decided to go with using a different cache prefix for each deployment. This way generated files and other caches don't interfere with each other during a deploy for a site that has allot of visitors. Because this runs before composer, if also fixes the issue with the classmap cache.
Works when env.php does not have a cache prefix yet. Also Magento fixes the |
Similar issue to: #138
When running magento:maintenance:enable the redis cache is not correct. You fixed it by flushing before app:config:import, but it should have done a cache flush after the magento:maintenance:enable in the release_path
issue with cache:
To fix it I added the following to override it:
The issue is that a cache:flush needs to be done after the maintenance:enable, because then it does a maintenance:enable in the current_path (
capistrano-magento2/lib/capistrano/tasks/deploy.rake
Line 74 in 3d32c7d
The text was updated successfully, but these errors were encountered: