Doofus100500

I also noticed that this is somehow related to the number of Linux nodes. Currently, when I left only 2 Windows nodes and one Linux node in the cluster, the...

@JorTurFer I've got more log's & i think the trouble is not in selenium. That's how cluster of selenium look's like: GraphQL before test: ``` curl -X POST -H "Content-Type:...

@Wolfe1 Hello, is there a tentative forecast for when you will be able to address this issue?

> Still plan to get to this eventually 🐌 @Wolfe1 hi, is there any chance that you can address this issue in the near future?

> Still plan to get to this eventually 🐌 @Wolfe1 hi, is there any chance that you can address this issue in the near future?

@Wolfe1 Hi, could you please review my PR that should fix this? https://github.com/kedacore/keda/pull/5917

But after restarting the distributor, it once again starts "seeing" the nodes created after its restart. >Can you double check that? How can i check this?

While studying the issue, I discovered an interesting feature: if at least one node is connected to the grid, the distributor continues to connect newly created nodes correctly(However, this has...

> https://www.selenium.dev/documentation/grid/getting_started/#node-and-hub-on-different-machines `Distributor interacts with New Session Queue, Session Map, Event Bus, and the Node(s).` Well, based on this description, it's not clear. Does he himself have to go there?...

> Yes, because the DNS information is updated, I believe. You know better your environment, can you check that? There is definitely no DNS in it. The externalUri confirms this....