[SERVER-20518] Ability to view / kill connections Created: 21/Sep/15  Updated: 08/Jan/24  Resolved: 17/Dec/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 2.6.0, 3.0.0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Anil Kumar Assignee: Benjamin Caimano (Inactive)
Resolution: Won't Fix Votes: 4
Labels: product
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-44164 Create the killOperations command Closed
is related to SERVER-20522 Ability to change the number of non-s... Closed
Participants:
Case:

 Description   

The server should provide the ability for the administrators to list and kill specific connections from the users. This is specifically useful in following scenarios:

  • In large enterprises where the roles of system administration are segregated from database administration and DBA may not have the ability to kill the connections using OS utilities.
  • To monitor the active connection at any given point of time. Although the same can be done by analyzing the log file or by enabling audit, none of them are realtime options without building additional facilities around it.

The user may be interested in listing / killing connections for various reasons like forcing the nearest read (to kill the stale connection pool) when a nearest member is brought up online.



 Comments   
Comment by Benjamin Caimano (Inactive) [ 17/Dec/19 ]

We do not think we are able to spend the development effort required to support this feature. As always, please feel free to reopen this ticket or submit a new ticket.

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