[SERVER-18095] currentOp on a mongoS shows shard operations that are not labelled as being on a shard Created: 17/Apr/15  Updated: 06/Dec/22  Resolved: 13/Apr/18

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

Type: Bug Priority: Major - P3
Reporter: Joanna Cheng Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: curop, currentop
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

Some examples

		{
			"desc" : "TTLMonitor",
			"threadId" : "0x7ff5c3614cc0",
			"active" : false
		},
		{
			"desc" : "DataFileSync",
			"threadId" : "0x7ff5c35058d0",
			"active" : false
		},
		{
			"desc" : "journal writer",
			"threadId" : "0x7fc5c3e031f0",
			"active" : false
		},
		{
			"desc" : "durability",
			"threadId" : "0x7fc5c3c23430",
			"active" : false
		},

None of these make sense on a mongoS - there are no data files, no TTL indexes, and no journal.

By contrast, this is how a "normal" operation on a shard is marked, where there is an "opid" that is clearly marked as being from a shard:

		{
			"desc" : "durability",
			"threadId" : "0x7ff5c3707260",
			"opid" : "shard01:3",
			"active" : false,
			"op" : "none",
			"ns" : "",
			"query" : {
 
			},
			"numYields" : 0,
			"locks" : {
				"MMAPV1Journal" : "R"
			},
			"waitingForLock" : true,
			"lockStats" : {
				"MMAPV1Journal" : {
					"acquireCount" : {
						"R" : NumberLong(1)
					},
					"acquireWaitCount" : {
						"R" : NumberLong(1)
					},
					"timeAcquiringMicros" : {
						"R" : NumberLong(39415924)
					}
				}
			}
		},



 Comments   
Comment by Andy Schwerin [ 13/Apr/18 ]

In the 3.7 unstable branch, which will become 4.0, currentOp in sharding has been substantially improved.

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