Replicated data management in the grid

Abstract

Grid environments more and more target novel domains such as eScience, eHealth or digital libraries that feature a variety of data-intensive applications. Consequently, issues related to data management in Grids are becoming increasingly important. In terms of data management, the Grid allows keeping a large number of replicas of data objects, possibly with different versions or levels of freshness, to allow for a high degree of availability, reliability and performance so as to best meet the needs of users and applications. At the same time, the seamless integration of replication management into the Grid while taking into account its special characteristics, needs to be done without any central component for managing data or metadata. In this paper, we report on the ongoing Re:GRIDiT project which aims at addressing all the above requirements. Re:GRIDiT distinguishes between potentially many updateable and read-only replicas which can be distributed across a Grid environment. First, Re:GRIDiT provides new protocols for the correct synchronization of concurrent updates to different updateable replicas and their subsequent propagation in a completely distributed way. Second, Re:GRIDiT takes into account the semantics of the data which is managed in the Grid: mutable data can be subject to updates; immutable data, in turn, cannot be changed once created, but may be subject to version control. Third, Re:GRIDiT will be dynamic in a way that according to the current load, new replicas (updateable or read-only) can be created or removed on demand. Fourth, Re:GRIDiT will provide read-only transactions the full flexibility to specify the freshness (for mutable data) or version number (for immutable data) -which is particularly useful * This work has been partly supported by the Hasler Foundation within the project COSA (Compiling Service-oriented Architectures).

A Survey on Data Replication and Resource Management in Distributed Systems

“…Other research on dealing with data consistency in Cloud application are found in [39], [40], [41] and [42]. In these studies, another variant of asynchronous update protocol on replicated data is proposed in the Cloud computing environment.…”

Transaction processing in a peer to peer database network

“…[27,28,59], a concept of transaction processing in a P2P environment is presented. The authors propose a decentralized concurrency control for transactions relying on a decentralized serialization graph.…”

How replicated data management in the cloud can benefit from a data grid protocol

“…Re:GRIDiT has been developed to address the needs of novel data-intensive eScience applications in the Grid [16]. In short, Re:GRIDiT can be characterized as follows:…”

“…In terms of replication management, most Data Grids suffer from several shortcomings as they merely deal with files as the replication granularity, do not allow replicated data to be updated, and/or require the manual placement of files [8,13]. Recently, we have developed the Re:GRIDiT system that provides advanced data and replication management in the Grid [16,17]. Re:GRIDiT follows a truly distributed approach to replication management in the Grid by bringing together replication management, originally developed for database clusters [15,4], and distributed transaction management that does not rely on a global coordinator [11].…”