A Cost Benefit Approach to Fault Tolerant Communication and Information Access

Quarterly Technical Report, October 2001

Progress:

• Cost benefit decision making: We have rewritten our global flow control in the ns2 simulation. The new implementation scales much better with the number of sites. We are now able to simulate our cost-benefit flow control in network scenarios with up to 1600 sites, 800 different senders sending to several groups each, out of 800 different groups in the system. This gives us the ability to simulate very large overlay networks.

• New replication protocol: We have started to experiment with the replication server we developed. We are now benchmarking the replication server with and without the Postgres database on local area network and on the CAIRN wide area network. We are experiencing a lot of problems in terms of the CAIRN nodes' performance (e.g. disk sync performance) and hope to be able to get a better network in place. We could use any external help that can be provided here...

• Wackamole: We have developed and released Wackamole, a software tool that allows N-Way Fail Over for IP Addresses in a cluster.

  Wackamole is a tool that helps with making a cluster highly available. It manages a bunch of virtual IPs that should be available to the outside world at all times. Wackamole ensures that exactly one machine within the cluster is listening on each virtual IP address that Wackamole manages. If it discovers that particular machines within the cluster are not alive, it will almost immediately ensure that other machines acquire the virtual IP addresses the down machines were managing. At no time will more than one connected machine be responsible for any virtual IP.

  Wackamole also works toward achieving a balanced distribution of the public IPs within the cluster it manages.

  How it works:
  Wackamole runs as root on each of the cluster's machines. It uses the membership notifications provided by the Spread Toolkit , also developed in our lab, to generate a consistent state that is agreed upon among all of the connected Wackamole instances. Wackamole uses this knowledge to ensure that all of the public IP addresses served by the cluster will be covered by exactly one Wackamole instance.

• Archipelago: We have developed an initial version of the Archipelago system. The system allows us to investigate efficient ways to form an extended ad-hoc network of laptops, handhelds, and other wireless capable devices, and bridge it to the Internet. Archipelago constructs a multi-hop dynamic network using the wireless devices of participating users. The current system is fully operational, capable of supporting up to about fifty participants using handhelds (Windows CE) and laptops (Windows and Linux), and up to 10 hops in network diameter.

Papers:

Software:

Plans for Next Quarter:

• Data level resiliency: We plan to investigate and optimize the performance of our replication architecture over local and wide area network.

• Overlay network infrastructure: We plan to start investigating a cost-benefit routing for overlay networks. We hope the cost-benefit framework will help us to dynamically utilize various overlay network paths in parallel as we route messages.

  We plan to investigate techniques to make our overlay network architecture seamless to existing applications that use TCP/IP.

• Wackamole: We plan to update our initial implementation as external feedback is received from the Internet community. We also plan to port the initial (Linux) version to support Solaris and FreeBSD.

• Archipelago: We plan to continue with this promising direction.