-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: the status endpoint of a restarted node is called multiple times #13646
Comments
@joerg1985, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
I don't fully understand, what do you mean by multiple times? |
@diemol Depending on the number of restarts the number of calls to the /status endpoint grows. Let's say the node A is restarted 9 times, while the node B is not restated. |
These are the corresponding logs of the hub, the restarted node is registered for each restart and all instances ( The PR will ensure only
|
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
What happened?
Restarting a node will register a new node to the hub, with the same status URL.
The restarted node will now get multiple calls to the status endpoint.
The
GridModel
does detect this state and updated the internal model correctly, but i am not sure about theMap<NodeId, Node> nodes
inside theLocalDistributor
. TheHealthCheck
inside theRemoteNode
is not stopped and keeps calling the status endpoint.How can we reproduce the issue?
Relevant log output
Operating System
Win 10 x64
Selenium version
4.17.0
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
4.17.0
The text was updated successfully, but these errors were encountered: