Skip to content
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

Merged
merged 7 commits into from
Aug 21, 2024

Conversation

azharone
Copy link
Contributor

Summary

Doc Page Title - <Enter a one sentence summation of the pertinent changes (including not-yet-completed work) provided by this PR.>

@azharone azharone requested a review from a team as a code owner August 19, 2024 19:36
Copy link

👋 @azharone
Thanks for opening your first pull request! @pantheon-systems/docs-admins is excited to review this!

If you like this project, please ⭐star⭐ our repo.

@azharone
Copy link
Contributor Author

@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.

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)?

Copy link
Contributor Author

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.

Copy link

⚡ 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
🛠️ Manage in Pantheon: https://dashboard.pantheon.io/site/2b30153f-e8b1-4427-b076-6109e704ba5d/overview

Copy link
Contributor Author

@azharone azharone left a 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.

@IngridKwok
Copy link
Contributor

@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?

@azharone
Copy link
Contributor Author

@IngridKwok
I can remove the screenshot from this Release Notes as its not related to the change we are deploying. The change Wordpress to WordPress will have to be a docs change. I will raise a request with the docs team to do that. Will that work?

@IngridKwok
Copy link
Contributor

@azharone It works. Thanks.

Copy link

⚡ 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
🛠️ Manage in Pantheon: https://dashboard.pantheon.io/site/2b30153f-e8b1-4427-b076-6109e704ba5d/overview

Copy link

⚡ 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
🛠️ Manage in Pantheon: https://dashboard.pantheon.io/site/2b30153f-e8b1-4427-b076-6109e704ba5d/overview

@rachelwhitton rachelwhitton merged commit 4a1b5e5 into main Aug 21, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants