-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.2
-
Component/s: Diagnostics, Sharding
-
Sharding
-
ALL
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) } } } },