I recently ran into an issue where someone registered a new Selenium node with our hub, but the new node was not configured the same as the other nodes. It occurred to me that just anyone could add a misconfigured node and completely ruin the integrity of our test results without realizing it. For instance, maybe their node reports that Chrome is available, but the path to chromedriver.exe is incorrect.
Is it possible to remotely shut down a Selenium grid node? For example, can I invoke a command on the hub which triggers a shutdown signal to be sent to all the nodes, or--better yet--can I just send a command directly to the unwanted node?
Note that I do not have access to the machine that is running the node, so I cannot simply kill the process from the command-line.