[SERVER-21681] In-memory storage engine not reporting index size Created: 26/Nov/15  Updated: 21/Nov/16  Resolved: 11/Mar/16

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.2.0-rc2
Fix Version/s: 3.2.5, 3.3.3

Type: Bug Priority: Major - P3
Reporter: Ruben Terceno Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Steps To Reproduce:

Start an in-Memory instance (I have verified the problem with both standalone and RS).
Load some data in any collection.
db.stats() and db.c.stats() shows index size to be 4096 independently of the collection size. If several index are created, each one is 4096 bytes size.

Sprint: Integration F (02/01/16), Integration 10 (02/22/16), Integration 11 (03/14/16)
Participants:
Linked BF Score: 0

 Description   

Playing with 3.2.0-rc4 I have found that the db.stats() command is always informing the size of indexes as 4096 bytes.

MongoDB Enterprise inMem:PRIMARY> db.stats()
{
	"db" : "POCDB",
	"collections" : 1,
	"objects" : 1876714,
	"avgObjSize" : 285.37579247557164,
	"dataSize" : 535568745,
	"storageSize" : 535568745,
	"numExtents" : 0,
	"indexes" : 1,
	"indexSize" : 4096,
	"ok" : 1
}

This is also affecting compass index size report.



 Comments   
Comment by Githook User [ 29/Mar/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-21681 Replace 'or' with operator || to fix Windows build

(cherry picked from commit 73409b9364b8d83442a23a57ad910fc0438511ec)
Branch: v3.2
https://github.com/mongodb/mongo/commit/d62c6451399b1655eb31fc9554ac14928f7bb7cd

Comment by Githook User [ 29/Mar/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-21681: Use cursor statistics to derive index sizes for inMemory

(cherry picked from commit 7ed2327abb1168d7f89e3cd05c8740eee20dcdde)
Branch: v3.2
https://github.com/mongodb/mongo/commit/333fad00034cd35dd0b1ffabefd3b6ee9ed5f849

Comment by Githook User [ 11/Mar/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-21681 Replace 'or' with operator || to fix Windows build
Branch: master
https://github.com/mongodb/mongo/commit/73409b9364b8d83442a23a57ad910fc0438511ec

Comment by Githook User [ 11/Mar/16 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-21681: Use cursor statistics to derive index sizes for inMemory
Branch: master
https://github.com/mongodb/mongo/commit/7ed2327abb1168d7f89e3cd05c8740eee20dcdde

Comment by Kelsey Schubert [ 03/Dec/15 ]

I have verified this behavior on 3.2.0-rc5 enterprise on linux and OS X. I'm sending it to triage.

Generated at Thu Feb 08 03:58:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.