[SERVER-8351] Metrics are displayed for replication even if there is no replication Created: 26/Jan/13  Updated: 06/Dec/22  Resolved: 09/Aug/18

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

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: metrics, serverstatus, serverstatussection
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

We should find a way of disabling replication counters: maybe optionally hiding branches or moving metrics into (named) ServerStatusSections?



 Comments   
Comment by Scott Hernandez (Inactive) [ 08/Mar/16 ]

Yes, still an issue (see the sections below under opcountersRepl, and metrics.repl):

db.serverStatus()
{
	"host" : "FOO",
	"advisoryHostFQDNs" : [ "BAR" ],
	"version" : "3.3.2-93-g487da54",
	"process" : "mongod",
	"pid" : NumberLong("22484234098234892349823423123123123039234987897234987234987234897234987"),
	"uptime" : 67714,
	"uptimeMillis" : NumberLong("6771408998798787"),
	"uptimeEstimate" : 15697,
	"localTime" : ISODate("2016-03-08T15:56:08.835Z"),
	"asserts" : {
		"regular" : 0,
		"warning" : 0,
		"msg" : 0,
		"user" : 18,
		"rollovers" : 0
	},
	"connections" : { ... },
	"opcounters" : {
		"insert" : 0,
		"query" : 1,
		"update" : 21,
		"delete" : 0,
		"getmore" : 0,
		"command" : 17
	},
	"opcountersRepl" : {
		"insert" : 0,
		"query" : 0,
		"update" : 0,
		"delete" : 0,
		"getmore" : 0,
		"command" : 0
	},
	"storageEngine" : {
		"name" : "wiredTiger",
		"supportsCommittedReads" : true,
		"readOnly" : false,
		"persistent" : true
	},
	...
	"metrics" : {
		...
		"record" : {
			"moves" : NumberLong(0)
		},
		"repl" : {
			"executor" : {
				"counters" : {
					"eventCreated" : 0,
					"eventWait" : 0,
					"cancels" : 0,
					"waits" : 0,
					"scheduledNetCmd" : 0,
					"scheduledDBWork" : 0,
					"scheduledXclWork" : 0,
					"scheduledWorkAt" : 0,
					"scheduledWork" : 0,
					"schedulingFailures" : 0
				},
				"queues" : {
					"networkInProgress" : 0,
					"dbWorkInProgress" : 0,
					"exclusiveInProgress" : 0,
					"sleepers" : 0,
					"ready" : 0,
					"free" : 0
				},
				"unsignaledEvents" : 0,
				"eventWaiters" : 0,
				"shuttingDown" : false,
				"networkInterface" : "\n      NetworkInterfaceASIO:\n\t Operations _inGetConnection: 0\n\t Operations _inProgress: 0\n\n"
			},
			"apply" : {
				"batches" : {
					"num" : 0,
					"totalMillis" : 0
				},
				"ops" : NumberLong(0)
			},
			"buffer" : {
				"count" : NumberLong(0),
				"maxSizeBytes" : 268435456,
				"sizeBytes" : NumberLong(0)
			},
			"network" : {
				"bytes" : NumberLong(0),
				"getmores" : {
					"num" : 0,
					"totalMillis" : 0
				},
				"ops" : NumberLong(0),
				"readersCreated" : NumberLong(0)
			},
			"preload" : {
				"docs" : {
					"num" : 0,
					"totalMillis" : 0
				},
				"indexes" : {
					"num" : 0,
					"totalMillis" : 0
				}
			}
		},
		"storage" : {
			"freelist" : {
				"search" : {
					"bucketExhausted" : NumberLong(0),
					"requests" : NumberLong(0),
					"scanned" : NumberLong(0)
				}
			}
		},
		"ttl" : {
			"deletedDocuments" : NumberLong(0),
			"passes" : NumberLong(308)
		}
	},
	"ok" : 1
}

Comment by Eric Milkie [ 08/Mar/16 ]

Is this still an issue? Where are the metrics today?

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