You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
The $magento-cloud db:size command can return very confusing information, like 1021% being used. (I tried attaching the image, do not understand if it worked out).
Talked to two support agents, and they do not recommend customers using this command.
Description:
The $magento-cloud db:size command can return very confusing information, like 1021% being used. (I tried attaching the image, do not understand if it worked out).
Talked to two support agents, and they do not recommend customers using this command.
Possible solutions:
I suggest this command usage recommendations should be double-checked. Thank you.
Additional information:
See Manage disk space topic. Possibly add more information and guidance about interpreting the output of db:size command.
The text was updated successfully, but these errors were encountered:
shrielenee
changed the title
Feedback on page: /cloud/project/manage-disk-space.html
Need more info about interpreting output of db:size command
Jan 9, 2020
So thinking that the article update which provides separate instructions for checking db-size on Integration and checking it on dedicated clusters (Pro Staging and Production_ might clarify the use of these commands. @almarchenko Can you check the updated article: https://devdocs.magento.com/cloud/project/manage-disk-space.html?
Uh oh!
There was an error while loading. Please reload this page.
General issue
The $magento-cloud db:size command can return very confusing information, like 1021% being used. (I tried attaching the image, do not understand if it worked out).
Talked to two support agents, and they do not recommend customers using this command.
Description:
The $magento-cloud db:size command can return very confusing information, like 1021% being used. (I tried attaching the image, do not understand if it worked out).
Talked to two support agents, and they do not recommend customers using this command.
Possible solutions:
I suggest this command usage recommendations should be double-checked. Thank you.
Additional information:
See Manage disk space topic. Possibly add more information and guidance about interpreting the output of
db:size
command.The text was updated successfully, but these errors were encountered: