Thanks dev, will we run into the same issue again? Will your nodes will be able to handle more than 20 connections each?
I think that now it is not good time to substantially rewrite the full node. It is necessary to make the functionality of the pool in it and write a miner that could be compiled and run on any hardware. In the pool, work with the miners will be arranged another way. There will be one thread that will consistently bypass the miners, their number may be more than 20. If any of the miners are forgotten, then this is not terrible for the network, just this miner will go to another pool.
But if there are more pools than 20, this is another case. It should be noted that each pool has an open ip, so they do not have to connect directly to each other, but may be through intermediaries. Therefore, I think the number of connections to other pools can be limited to 20.
maybe limit pool to have active connections to 16-20 another pool for reasonably small time period. after that period some part of active connection canceled and reconnect to other pools. some kind of slow/delayed syncro with all pools in reasonably big time period. but one pool does not have too many active connection if overall pool count is big ?