We continued to work on optimizing and evaluating the replication architecture.
In order to comprehensively analyze the tradeoffs involved when replicating database systems on wide area networks, we implemented the modular version of the replication algorithm (Maintaining Database Consistency in P2P networks). We are practically evaluating the performance of this approach and comparing it with the performance of our replication architecture.
We are investigating algorithmic and practical solutions for optimizing the cost of reconfigurations in the presence of faults in a wide-area network environment. We are also investigating algorithms that minimize the replication costs based on data partitioning and access patterns.
We focused our work on the client-daemon communication in Spines. We develpoped a socket-like API for unreliable, best-effort UDP communication, and also for the session-based TCP reliable communication. This brings us the level of transparency necessary for making Spines easy to use in the socket programming paradigm, in a first step towoards complete transparency. We also analyzed the possibilities of poviding IP multicast service using Spines while using only simple unicast communication at the network level.
We have adapted Wackamole in order to provide n-way fail-over for routers. An example layout for this application of Wackamole consists of multiple physical routers that act as a single virtual router. An indivisible set of virtual addresses on different interfaces is allocated to the physical router currently acting as the fail over router. If the interface through which the machine is connected to Spread fails, or the machine itself crashes, the set of virtual addresses will be reallocated to a different machine. The set of physical routers running Wackamole, each of which is potentially "the" router, can be conceptualized as a single virtual router. facilities and enhancing the multiplatform support.
An On-Demand Secure Routing Protocol Resilient to Byzantine Failures |
ps,
ps.gz,
pdf.
In ACM Workshop on Wireless Security (WiSe) , Atlanta, Georgia, September
28 2002.
Baruch Awerbuch,
Dave Holmer,
Cristina Nita-Rotaru,
and Herbert Rubens.
An ad hoc wireless network is an autonomous self-organizing system of
mobile nodes connected by wireless links where nodes not in direct
range can communicate via intermediate nodes. A common technique used
in routing protocols for ad hoc wireless networks is to establish the
routing paths on-demand, as opposed to continually maintaining a
complete routing table. A significant concern in routing is the
ability to function in the presence of byzantine failures which
include nodes that drop, modify, or mis-route packets in an attempt to
disrupt the routing service.
|
On the Performance of Synchronous Wide-Area Database Replication |
Technical Report CNDS-2002-4, September 2002.
Yair Amir, Claudiu Danilov, Michal Miskin-Amir, Jonathan Stanton and Ciprian Tutu.
A fundamental challenge in database replication is maintaining
a low cost of updates while assuring global system consistency.
The problem is magnified for wide-area replication due to the high latency
and the increased likelihood of network partitions. As a consequence,
most database replication research moved away from strictly consistent
models to update models with weaker semantics, relying on application
knowledge to resolve conflicts.
|