I recently discovered it is possible to have multiple front-ends which bind to the same ip/port combination. I was surprised to find this was even possible - I would have expected an error on start-up in this scenario. I see from some discussion here is that the likely behaviour is that traffic will be (non deterministically?) distributed between the front-ends by the kernel.
Not sure why this behaviour is even allowed, why would ever want to do this. Wondering if this less of a deliberate behaviour and more of a side effect of the way multi threaded/multi process mode works?
In any case, my key question is whether these is any way to disable this and/or force a validation error on start-up in such a situation? The reason I ask is that we generate our config automatically from other sources and the process can sometime introduce such a situation, leading to unpredictable behaviour. It would preferable if this just failed. If no other option we will just update our config generation processes to validate for this!