-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Allow calls to opcache_reset to be disabled in config #19948
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
Allow calls to opcache_reset to be disabled in config #19948
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one @samjf - just a couple of points but otherwise this looks pretty straightforward
- Normally we go for enable_ rather than disable_ for new configs, see https://developer.matomo.org/guides/piwiks-ini-configuration#naming
- This might be good to create a brief new FAQ for and/or at least mention in the developer changelog
Thanks @justinvelluppillai I'll make a fix for those and I'll keep those on file when making PRs in future. |
fyi @samjf we may also need to add an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you add the 4.12.4 section to the changelog and move your change there we can include this in the release today 👍🏽
Other changes look good
CHANGELOG.md
Outdated
@@ -27,6 +27,9 @@ The Product Changelog at **[matomo.org/changelog](https://matomo.org/changelog)* | |||
|
|||
* The methods `setExcludedReferrers` and `getExcludedReferrers` have been added to the JavaScript tracker. They allow setting and receiving the referrers the JavaScript tracker should ignore. If a referrer matches an entry on that list, it will not be passed with the tracking requests and the attribution cookie will stay unchanged. This can for example be used if you need to forward your users to an external service like SSO or payment and don't want any visits or conversions being attributed to those services. | |||
|
|||
### New config.ini.php settings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer in 4.12.0 but 4.12.4 (if we merge it now).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't realise it was by patch version, but it makes sense hehe. I'll change this now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one I've removed "general" from the changelog as it's not a GeneralConfig
so that might be confusing, otherwise looks good to merge.
Description:
ref: CLOUD-798
From time to time, we experience corrupt opcaches that cause outages which can cause various random errors to occur. After investigating we found that certain processes we use call Matomo console commands which result in the reset of the opcache. We believe it is likely that multiple concurrent opcache resets might result in the corrupt opcache.
This PR simply provides a configuration switch which can be used to disable opcache resets. This is off by default. When enabled this configuration will allow better control over the opcache and will likely allow us to avoid opcache corruption.
This configuration change was added in the cache section of the configuration as such:
Cache['disable_opcache_reset']
Review