[erlang-questions] Fault-Tolerant TCP/IP Servers

[David Mercer]

No, TCP/IP is used for the message stream I am thinking of.  Basically, the
client opens a TCP/IP connection to the server, and then sends HL7 messages
(a message format used in the healthcare industry) over the connection,
delimited by beginning- and end-of-message control codes.  If the connection
is closed (e.g., server fails), the client will attempt to reconnect.  My
thought is that if the secondary can remap the network so that connections
to that IP address are now routed to it, the reconnect would automatically
go to the secondary.

 

  _____  

From: erlang-questions-bounces@REDACTED
[mailto:erlang-questions-bounces@REDACTED] On Behalf Of Rick R
Sent: Wednesday, July 16, 2008 09:35
To: erlang-questions@REDACTED
Subject: Re: [erlang-questions] Fault-Tolerant TCP/IP Servers

 

You mentioned TCP/IP, but is SCTP an option? If so, your problem is solved
automatically and (almost) instantly via SCTP's multi-homing. 

2008/7/16 David Mercer <dmercer@REDACTED>:

I must admit, I am disappointed that there is no Erlang solution.  This
seems like a basic building block to fault-tolerant systems.  So, I am going
to toy with my idea of having the secondary detect the failure and send the
appropriate commands to the network to redirect traffic for the primary
server's IP address to the secondary.  Am thinking there must be some DHCP
commands to reassign the IP address.  Before I begin, does anyone see any
obvious flaws in my thinking.  I am not a networking expert.  Thanks.

 

David

 

  _____  

From: David Mercer [mailto:dmercer@REDACTED] 
Sent: Friday, July 11, 2008 10:59
To: 'erlang-questions@REDACTED'
Subject: Fault-Tolerant TCP/IP Servers

 

Say I have a TCP/IP server (e.g., a web server, FTP server, etc.) written in
Erlang, and I want it to work through hardware failures; I need at least two
of them.  The problem is, clients are connecting to the primary's IP
address, so when it fails, client connections are refused instead of being
rerouted to the secondary.  What is the Erlang approach to solving this?

 

My thought is that you have the secondary detect the failure and send the
appropriate commands to the network to redirect traffic for the primary
server's IP address to the secondary.  That's my idea, but I don't really
know if this is the appropriate solution, nor how to implement something
like this in Erlang.

 

Please advise.  Thank-you.

 

David Mercer

 

 


_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://www.erlang.org/mailman/listinfo/erlang-questions




-- 
An idea that is not dangerous is unworthy of being called an idea at all. --
Oscar Wilde 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080716/7f2568ff/attachment.htm>