SeleniumHQ/selenium

[๐Ÿš€ Feature]: Grid endpoint to kill all sessions of all nodes connected to a hub

ksingha161 opened this issue ยท 3 comments

Feature and motivation

Motivation -
I have a grid setup where 4 nodes are connected to 1 hub. I killed all all browsers in task manager (windows) but the sessions in my grid public url still shows as active. Is there already a feature or can we implement one where we are able to close all sessions connected to a hub? I checked some grid endpoints but they needed node uri. The below screenshot shows grid public url which says sessions as still active even after killing all browsers
image

Usage example

Steps to reproduce -

  1. Start grid with multiple nodes connected to a hub
  2. kill all browsers in all the nodes
  3. check grid public url, sessions would still be active

Currently if I need to kill all sessions I need to login to all machines separately and restart grid, which is not very optimal approach.

or If there could be a way to get all sessions related to a node uri then we could just hit this api in a loop to delete all sessions
http://<node:uri>/se/grid/node/session/sessionId

@ksingha161, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

diemol commented

Duplicate of #11519

Feel free to add more information over there.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.