-
Notifications
You must be signed in to change notification settings - Fork 684
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
Release note for protecting the directory size overload #9186
Conversation
👋 @azharone If you like this project, please ⭐star⭐ our repo. |
@rachelwhitton @stevector @IngridKwok @[email protected] Please review the PR. |
|
||
**Before:** Users could continue writing files to a directory indefinitely, although exceeding 100k files in a single directory would reduce performance and put the site at risk of complete & irreparable volume corruption. | ||
|
||
**After:** Sites are permitted to store up to 100k files per directory. When a directory reaches 50k files due to export or backup activities, a warning will be displayed on the dashboard and an email notification will be sent to the site owner (limited to one per seven days). The warning system functionality remains unchanged. If the file count in a directory exceeds 100k substantially, additional writes will be blocked to avoid system instability. |
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.
Should customers take any action to prevent this condition in the future? If so, can we link to the documentation of what they should do (e.g. a configuration option or module/plugin)?
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.
There is no action item required from the customer regarding this change. The documentation linked in the RS directs the customers on how to avoid getting into such situations.
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9186-documentation.appa.pantheon.site |
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.
Responded to the review comment.
@azharone I've edited the release note. Please note that "WordPress" should always have an uppercase "P" (Wordpress → WordPress). Could you also update the screenshots to reflect these and other changes accordingly? |
@IngridKwok |
@azharone It works. Thanks. |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9186-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9186-documentation.appa.pantheon.site |
Summary
Doc Page Title - <Enter a one sentence summation of the pertinent changes (including not-yet-completed work) provided by this PR.>