Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21681

In-memory storage engine not reporting index size

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-rc2
    • Fix Version/s: 3.2.5, 3.3.3
    • Component/s: Storage
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      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.

      Show
      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)

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: