Skip to content

DOCS-5171 & DOCS-5172: mongostat stat corrections #2264

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

Merged
merged 2 commits into from
Apr 7, 2015

Conversation

schmalliso
Copy link
Contributor

Note: The steps thing fixed a build error I was getting. Do with it what you will.


The amount of virtual memory in megabytes used by the process at
the time of the last :program:`mongostat` call.

.. describe:: non-mapped

The total amount of virtual memory excluding all mapped memory at
.. versionchanged:: 3.0.0
Only for :ref:`storage-mmapv1`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this compile correctly without the blank line in between versionchanged and the next line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes ma'am.

non-mapped

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so weird. I can't even pull this pull request. if I do a fake
.. versionchanged:: 3.0.0
This is a test

Mine nags at me, but we seem to have build errors due to michael's debian step and one of the toc's is looking for the core/tag-sharding in toc-sharded-cluster-data.yaml which doesn't allow for any actual builds. eh.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed the Debian step here, since it wasn't building at all for me either.

As for tag-aware-sharding, I moved it, but it should be fine (6d9e8f2)? I just copy-pasted it across. Maybe I'll cherry-pick this commit into a new master.

@schmalliso schmalliso force-pushed the tools-mongostat-corrections branch from 5388200 to db4ba31 Compare April 7, 2015 16:31
@schmalliso
Copy link
Contributor Author

Perhaps now it will be more content?

@schmalliso schmalliso merged commit db4ba31 into mongodb:master Apr 7, 2015
@schmalliso schmalliso deleted the tools-mongostat-corrections branch January 15, 2016 16:40
mongo-cr-bot pushed a commit that referenced this pull request Dec 13, 2022
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.

2 participants