Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: 2.2.2
Component/s: Replication
Labels:
- MongosOperationManagement
Environment:
Debian 6.0 kernel: Linux 2.6.38-2-amd64
cluster: a sharded cluster with 4 replica sets. Each rs contains a primary & a secondary & an arbiter

Assigned Teams:

Replication
Operating System:
Linux
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

I wanted to use db.killOp() to kill some long time queries which were performed on secondaries by using read preference "Secondary".
But the jobs are not shown when I use db.currentOp() so I can not kill them.
(Queries performed on primaries can be shown by using db.currentOp())

duplicates

SERVER-19318 currentOp command should return cursor

Closed

related to

SERVER-8878 db.currentOp() and db.killOp() on a mongos should display the host the op is running on.

Closed

SERVER-34633 Allow $currentOp to retrieve operations from all members of each shard in a cluster

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: stronglee
Participants:: [DO NOT USE] Backlog - Replication Team, Bernard Gorman, Eliot Horowitz, Ofer Cohen, stronglee
Votes:: 4 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jan 10 2013 02:25:38 PM UTC
Updated:: Dec 06 2022 05:26:04 AM UTC
Resolved:: Apr 17 2018 07:24:48 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates