[SERVER-25990] Remove extra_info.heap_usage_bytes from serverStatus Created: 07/Sep/16  Updated: 03/Apr/19  Resolved: 22/Sep/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.9, 3.3.12
Fix Version/s: 3.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Samantha Ritter (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-8782 Document that extra_info.heap_usage_b... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2016-10-10
Participants:

 Description   

The calculation of heap_usage_bytes is based on 32-bit values obtained from mallinfo which overflow above 4 GB, so it produces completely incorrect information in most cases.

The correct heap size is available in tcmalloc.generic.heap_size, which is a 64-bit value.



 Comments   
Comment by Samantha Ritter (Inactive) [ 22/Sep/16 ]

Our serverStatus command documentation needs to be updated with this change. Drivers that use the heap_usage_bytes field of the serverStatus command will need to stop using this field.

Comment by Githook User [ 22/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}

Message: SERVER-25990 Remove heap_usage_bytes from serverStatus output
Branch: master
https://github.com/mongodb/mongo/commit/bba9c97803dd5bcab8f8634565154aae5e3eda35

Comment by Githook User [ 22/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}

Message: SERVER-25990 Remove heap_usage_bytes from serverStatus output
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/2edc7f42221c06a2f47d857dbaa1249382d02bcc

Comment by Bruce Lucas (Inactive) [ 07/Sep/16 ]

I created DOCS-8782 to at least document the issue if we can't remove the field.

Generated at Thu Feb 08 04:10:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.