Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Need more info about interpreting output of db:size command #6245

Closed
almarchenko opened this issue Dec 18, 2019 · 3 comments
Closed

Need more info about interpreting output of db:size command #6245

almarchenko opened this issue Dec 18, 2019 · 3 comments
Assignees

Comments

@almarchenko
Copy link
Contributor

almarchenko commented Dec 18, 2019

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.

@shrielenee shrielenee added groomed Help Wanted Help wanted for issue/PR labels Jan 9, 2020
@shrielenee 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
@hguthrie
Copy link
Contributor

hguthrie commented May 7, 2020

Ah, yes. I think we might address this problem in the PR #7171
We shall see...

@meker12
Copy link
Contributor

meker12 commented May 18, 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?

@meker12
Copy link
Contributor

meker12 commented Jun 4, 2020

@almarchenko Closing this issue based on recent update. If needed, open a new issue for any further updates required.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants