Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[馃殌 Feature]: Grid endpoint to kill all sessions of all nodes connected to a hub #12031

Closed
ksingha161 opened this issue May 12, 2023 · 3 comments

Comments

@ksingha161
Copy link

ksingha161 commented May 12, 2023

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

@github-actions
Copy link

@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
Copy link
Member

diemol commented May 12, 2023

Duplicate of #11519

Feel free to add more information over there.

Copy link

github-actions bot commented Dec 9, 2023

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants