[Solved] best practice for LB probes? - MS Azure

Options
mindlube
edited October 2013 in Photon Server
Have been testing the MS Azure VM load balancer, and it supports a few options for it's 'probes'. Neither of which seems to be a good fit for Photon:

1) A TCP probe, which I can point at the photon TCPListener, while this does work, but results in a lot of timeouts in my logfiles (one for every probe request, I assume). I suspect thats wasteful from a resource point of view having Photon idling out a socket every few seconds or so.

2) A HTTP probe, which I can point at the PolicyListener or the websockets listener, but that errors out because the http request doesn't match the expected protocol

3) My workaround just to figure out how it was all working, was to install mongoose http server, and point the http probe at that.

It would be better if the probe was pointing at something the Photon service controlled, so if Photon crashed (or more likely, I stopped the Photon server, the probe would see that right away). And not depending on yet another network service.

Comments

  • Although, it would probably be short work to add some simple TCP listener in my Photon C# server code. But don't want to overlook a simpler solution. :D
  • So with .NET's httplistener class, this task is only like 20 lines of code.