[SERVER-16608] collStats scale argument does not apply to maxSize Created: 19/Dec/14  Updated: 24/Dec/14  Resolved: 23/Dec/14

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 2.8.0-rc3
Fix Version/s: 2.8.0-rc4

Type: Bug Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Operating System: ALL
Steps To Reproduce:

Create a capped collection (or use the oplog as in the above example).

Run collStats with and without a scale argument.

See that maxSize is the same in both.

Participants:

 Description   

 db.runCommand({"collStats": "oplog.rs"})
{
	"ns" : "local.oplog.rs",
	"count" : 1,
	"size" : 88,
	"avgObjSize" : 88,
	"numExtents" : 1,
	"storageSize" : 67108864,
	"nindexes" : 0,
	"lastExtentSize" : 67108864,
	"paddingFactor" : 1,
	"paddingFactorNote" : "paddingFactor is unused and unmaintained in 2.8. It remains hard coded to 1.0 for compatibility only.",
	"userFlags" : 0,
	"capped" : true,
	"max" : NumberLong("9223372036854775807"),
	"maxSize" : 67108864,
	"totalIndexSize" : 0,
	"indexSizes" : {
		
	},
	"ok" : 1
}

db.runCommand({"collStats": "oplog.rs", scale: 1024})
{
	"ns" : "local.oplog.rs",
	"count" : 1,
	"size" : 0,
	"avgObjSize" : 88,
	"numExtents" : 1,
	"storageSize" : 65536,
	"nindexes" : 0,
	"lastExtentSize" : 65536,
	"paddingFactor" : 1,
	"paddingFactorNote" : "paddingFactor is unused and unmaintained in 2.8. It remains hard coded to 1.0 for compatibility only.",
	"userFlags" : 0,
	"capped" : true,
	"max" : NumberLong("9223372036854775807"),
	"maxSize" : 67108864,
	"totalIndexSize" : 0,
	"indexSizes" : {
		
	},
	"ok" : 1
}


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