CH or NT must implement keep-alive about distributed-process HOT 6 CLOSED

http://nitoprograms.blogspot.co.uk/2009/05/detection-of-half-open-dropped.html might provide some useful insights.

from distributed-process.

See http://rabbitmq.1065348.n5.nabble.com/Re-The-rabbitmq-server-stop-command-hangs-td23180.html for an example of this happening in another network protocol. I have some thoughts about this. Firstly, it can be solved at the OS level by tuning kernel params and/or switching on TCP keep-alive, but that only works for TCP.

Personally I think this should be handled at the NT level and that it should be configurable.

from distributed-process.

Personally I think this should be handled at the NT level and that it should be configurable.

Agreed.

from distributed-process.

We do this in RabbitMQ so I've some familiarity with the problem space. I'll take a look at submitting a patch, but things are rather busy at the moment so it might not materialise for a week or so.

from distributed-process.

so it might not materialise for a week or so.

Nah, it's going to be quite a bit longer than that before I even start thinking about this one. Still interested in picking it up though => assigning to myself unless someone else wants to come and steal it first. :)

from distributed-process.

This issue was moved to haskell-distributed/network-transport#26

from distributed-process.