-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Ensure getmypid is only used when available otherwise disable SharedSiteIds #21216
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
Conversation
I'm tempted to say we should also apply this change here: I know it's not needed, as the climulti might not be used in this case anymore, but in terms of abstraction I think it could at some point be useful if we use |
This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers |
@sgiehl I've added the extra |
d5fd88b
to
d847d4e
Compare
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.
Did some local testing with and without getmypid function disabled. Archiving now works in both cases, so guess this should fix the related issues.
Description:
Fixes #20537
Based on @sgiehl's changes in #20540 and also incorporating the feedback from @tsteur:
Disabling
SharedSiteIds
seems like the safer option if using random process ids. Since the current state is that archiving doesn't run at all and fails with an error on hosts withoutgetmypid()
I'd suggest a fix that may degrade performance on some edge cases (only ifgetmyid()
is disabled) is preferable to no fix at all. We could perhaps document somewhere that hosting providers who disablegetmypid()
are not recommended for installations with many sites or high traffic.I've tested this by disabling
getmypid()
locally, recreating the original issue and then successfully running archiving with the fix applied.Review