[SERVER-22827] Weird behaviour of currentOp()/killOp() in sharded configurations Created: 24/Feb/16  Updated: 07/Apr/23  Resolved: 25/Feb/16

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

Type: Bug Priority: Minor - P4
Reporter: Eriks Sarguns Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4984 make it possible to interrupt operati... Closed
Operating System: ALL
Participants:

 Description   

We have sharded cluster with one replica set rs1

When we call db.currentOp() trough mongos
it returns string in field "opid":"rs1:34234232342", when normally we expect to get number

db.killOp() doesn't support strings, so we cannot call db.killOp("rs1:34234232342")

What we understood, we can connect directly to replicaSet and run db.killOp(34234232342) // remove "rs1"

Then it works.

But why this cannot be done by mongo router itself? If it knows on which replica set operation is running, then it could route this killOp to appropriate RS. Its understandable that then function killOp() should accept also string, or add new param for replica identification



 Comments   
Comment by Ramon Fernandez Marina [ 25/Feb/16 ]

Thanks for your report eriks.sarguns@opuscapita.com; if I understand the description correctly then I believe this ticket to be a duplicate of SERVER-4984, so I'm going to mark it as such. Feel free to watch SERVER-4984 for any updates and/or vote for it.

Cheers,
Ramón.

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