db.killOp not working in Cluster Sharding

André Antônio Lemos de Moraes shared this problem 6 months ago
Solved

When I am using the Cluster mongo with Sharding, the db.killOp operation gives an error and does not perform the operation as when I am using only Replica Set.

Comments (2)

photo
1

What's your MongoDB Server Version? There are some restrictions on this operation, see https://docs.mongodb.com/manual/reference/method/db.killOp/#kill-read-operations

photo
1

I think I expressed myself badly, the problem is in the "Monitoring -> In Progress Operation for This Instance" functionality on this screen has a "Kill Operation" functionality that when the mongo is in Cluster Sharding the problem mentioned above happens.


Mongo Server Version 3.6.17


7e6dfa297aafc42e44a997e33f38436d

2fe92fbbbeb4a5a2fd2b9c948eea9cd8

photo
1

Although according to MongoDB's official documentation, opid should be a number, the actual return result may be a string. https://docs.mongodb.com/manual/reference/method/db.currentOp/#output-fields

Anyway, We have worked out a new beta build to fix this issue, please download and give it a try. According to the picture, I assume you are using the windows system.

Windows: https://s3.mongobooster.com/download/releasesv5/nosqlbooster4mongo-5.2.10-beta.2.exe

photo
1

Resolved in 5.2.10

photo