[SERVER-12622] Traceability of connections in a sharded environment Created: 05/Feb/14  Updated: 08/Feb/23  Resolved: 23/Sep/19

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

Type: Improvement Priority: Major - P3
Reporter: Simone Sciarrati Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding
Participants:

 Description   

In a sharded environment there is no way to detect the originator of the query from either mongos or mongos. db.correntOp() reports all connections as originating from the mongos but there is no way to track it back to the originating client. Adding comments to the queries as suggested here http://docs.mongodb.org/manual/reference/operator/meta/comment/ is a workaround that does not help if queries are run manually (either authorised or non authorised users). Generally speaking having this info in Mongo itself seems to me like the right place.


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