[SERVER-57124] Running collStats command on mongos fails for time-series collection Created: 21/May/21  Updated: 21/May/21  Resolved: 21/May/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Julia Ruddy (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-56883 db.collection.stats() errors on time-... Closed
Operating System: ALL
Steps To Reproduce:
  1. Create a sharded cluster
  2. Create a time-series collection
  3. Connect to the mongos
  4. On the time-series collection, run the following command: db.runCommand({ collStats: "timeseries"})
Participants:

 Description   

Running db.runCommand({ collStats: "timeseries"}) on a mongos for a time-series collection results in the following error: 

{
	"ok" : 0,
	"errmsg" : "expected  to have a numeric type, but it is a missing",
	"code" : 13118,
	"codeName" : "Location13118",
	"$clusterTime" : {
		"clusterTime" : Timestamp(1621607006, 1),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	},
	"operationTime" : Timestamp(1621607002, 1)
} 

The InTel team depends on this command for Data Explorer to work properly so it is important that this behavior is uniform across deployment types. 



 Comments   
Comment by Julia Ruddy (Inactive) [ 21/May/21 ]

louis.williams, thanks so much! I will follow along there.

Comment by Louis Williams [ 21/May/21 ]

Hi julia.ruddy, thanks for reporting this bug! This looks like a duplicate of SERVER-56883, so I'm going to close this out. I'll raise the priority of that ticket and pull it forward.

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