Data grid

Short description: Set of services used to access, modify and transfer geographical data

This is a simple high level view of a data grid depicting distributed storage.

A data grid is an architecture or set of services that gives individuals or groups of users the ability to access, modify and transfer extremely large amounts of geographically distributed data for research purposes. Data grids make this possible through a host of middleware applications and services that pull together data and resources from multiple administrative domains and then present it to users upon request. The data in a data grid can be located at a single site or multiple sites where each site can be its own administrative domain governed by a set of security restrictions as to who may access the data. Likewise, multiple replicas of the data may be distributed throughout the grid outside their original administrative domain and the security restrictions placed on the original data for who may access it must be equally applied to the replicas. Specifically developed data grid middleware is what handles the integration between users and the data they request by controlling access while making it available as efficiently as possible. The adjacent diagram depicts a high level view of a data grid.

Middleware

Middleware provides all the services and applications necessary for efficient management of datasets and files within the data grid while providing users quick access to the datasets and files. There is a number of concepts and tools that must be available to make a data grid operationally viable. However, at the same time not all data grids require the same capabilities and services because of differences in access requirements, security and location of resources in comparison to users. In any case, most data grids will have similar middleware services that provide for a universal name space, data transport service, data access service, data replication and resource management service. When taken together, they are key to the data grids functional capabilities.

Universal namespace

Since sources of data within the data grid will consist of data from multiple separate systems and networks using different file naming conventions, it would be difficult for a user to locate data within the data grid and know they retrieved what they needed based solely on existing physical file names (PFNs). A universal or unified name space makes it possible to create logical file names (LFNs) that can be referenced within the data grid that map to PFNs. When an LFN is requested or queried, all matching PFNs are returned to include possible replicas of the requested data. The end user can then choose from the returned results the most appropriate replica to use. This service is usually provided as part of a management system known as a Storage Resource Broker (SRB). Information about the locations of files and mappings between the LFNs and PFNs may be stored in a metadata or replica catalogue. The replica catalogue would contain information about LFNs that map to multiple replica PFNs.

Data transport service

Another middleware service is that of providing for data transport or data transfer. Data transport will encompass multiple functions that are not just limited to the transfer of bits, to include such items as fault tolerance and data access. Fault tolerance can be achieved in a data grid by providing mechanisms that ensures data transfer will resume after each interruption until all requested data is received. There are multiple possible methods that might be used to include starting the entire transmission over from the beginning of the data to resuming from where the transfer was interrupted. As an example, GridFTP provides for fault tolerance by sending data from the last acknowledged byte without starting the entire transfer from the beginning.

The data transport service also provides for the low-level access and connections between hosts for file transfer. The data transport service may use any number of modes to implement the transfer to include parallel data transfer where two or more data streams are used over the same channel or striped data transfer where two or more steams access different blocks of the file for simultaneous transfer to also using the underlying built-in capabilities of the network hardware or specifically developed protocols to support faster transfer speeds. The data transport service might optionally include a network overlay function to facilitate the routing and transfer of data as well as file I/O functions that allow users to see remote files as if they were local to their system. The data transport service hides the complexity of access and transfer between the different systems to the user so it appears as one unified data source.

Data access service

Data access services work hand in hand with the data transfer service to provide security, access controls and management of any data transfers within the data grid. Security services provide mechanisms for authentication of users to ensure they are properly identified. Common forms of security for authentication can include the use of passwords or Kerberos (protocol). Authorization services are the mechanisms that control what the user is able to access after being identified through authentication. Common forms of authorization mechanisms can be as simple as file permissions. However, need for more stringent controlled access to data is done using Access Control Lists (ACLs), Role-Based Access Control (RBAC) and Tasked-Based Authorization Controls (TBAC). These types of controls can be used to provide granular access to files to include limits on access times, duration of access to granular controls that determine which files can be read or written to. The final data access service that might be present to protect the confidentiality of the data transport is encryption. The most common form of encryption for this task has been the use of SSL while in transport. While all of these access services operate within the data grid, access services within the various administrative domains that host the datasets will still stay in place to enforce access rules. The data grid access services must be in step with the administrative domains access services for this to work.

Data replication service

To meet the needs for scalability, fast access and user collaboration, most data grids support replication of datasets to points within the distributed storage architecture. The use of replicas allows multiple users faster access to datasets and the preservation of bandwidth since replicas can often be placed strategically close to or within sites where users need them. However, replication of datasets and creation of replicas is bound by the availability of storage within sites and bandwidth between sites. The replication and creation of replica datasets is controlled by a replica management system. The replica management system determines user needs for replicas based on input requests and creates them based on availability of storage and bandwidth. All replicas are then cataloged or added to a directory based on the data grid as to their location for query by users. In order to perform the tasks undertaken by the replica management system, it needs to be able to manage the underlying storage infrastructure. The data management system will also ensure the timely updates of changes to replicas are propagated to all nodes.

Replication update strategy

There are a number of ways the replication management system can handle the updates of replicas. The updates may be designed around a centralized model where a single master replica updates all others, or a decentralized model, where all peers update each other. The topology of node placement may also influence the updates of replicas. If a hierarchy topology is used then updates would flow in a tree like structure through specific paths. In a flat topology it is entirely a matter of the peer relationships between nodes as to how updates take place. In a hybrid topology consisting of both flat and hierarchy topologies updates may take place through specific paths and between peers.

Replication placement strategy

There are a number of ways the replication management system can handle the creation and placement of replicas to best serve the user community. If the storage architecture supports replica placement with sufficient site storage, then it becomes a matter of the needs of the users who access the datasets and a strategy for placement of replicas. There have been numerous strategies proposed and tested on how to best manage replica placement of datasets within the data grid to meet user requirements. There is not one universal strategy that fits every requirement the best. It is a matter of the type of data grid and user community requirements for access that will determine the best strategy to use. Replicas can even be created where the files are encrypted for confidentiality that would be useful in a research project dealing with medical files. The following section contains several strategies for replica placement.

Dynamic replication

Dynamic replication is an approach to placement of replicas based on popularity of the data. The method has been designed around a hierarchical replication model. The data management system keeps track of available storage on all nodes. It also keeps track of requests (hits) for which data clients (users) in a site are requesting. When the number of hits for a specific dataset exceeds the replication threshold it triggers the creation of a replica on the server that directly services the user’s client. If the direct servicing server known as a father does not have sufficient space, then the father’s father in the hierarchy is then the target to receive a replica and so on up the chain until it is exhausted. The data management system algorithm also allows for the dynamic deletion of replicas that have a null access value or a value lower than the frequency of the data to be stored to free up space. This improves system performance in terms of response time, number of replicas and helps load balance across the data grid. This method can also use dynamic algorithms that determine whether the cost of creating the replica is truly worth the expected gains given the location.

Adaptive replication

This method of replication like the one for dynamic replication has been designed around a hierarchical replication model found in most data grids. It works on a similar algorithm to dynamic replication with file access requests being a prime factor in determining which files should be replicated. A key difference, however, is the number and frequency of replica creations is keyed to a dynamic threshold that is computed based on request arrival rates from clients over a period of time. If the number of requests on average exceeds the previous threshold and shows an upward trend, and storage utilization rates indicate capacity to create more replicas, more replicas may be created. As with dynamic replication, the removal of replicas that have a lower threshold that were not created in the current replication interval can be removed to make space for the new replicas.

Fair-share replication

Like the adaptive and dynamic replication methods before, fair-share replication is based on a hierarchical replication model. Also, like the two before, the popularity of files play a key role in determining which files will be replicated. The difference with this method is the placement of the replicas is based on access load and storage load of candidate servers. A candidate server may have sufficient storage space but be servicing many clients for access to stored files. Placing a replicate on this candidate could degrade performance for all clients accessing this candidate server. Therefore, placement of replicas with this method is done by evaluating each candidate node for access load to find a suitable node for the placement of the replica. If all candidate nodes are equivalently rated for access load, none or less accessed than the other, then the candidate node with the lowest storage load will be chosen to host the replicas. Similar methods to the other described replication methods are used to remove unused or lower requested replicates if needed. Replicas that are removed might be moved to a parent node for later reuse should they become popular again.

Other replication

The above three replica strategies are but three of many possible replication strategies that may be used to place replicas within the data grid where they will improve performance and access. Below are some others that have been proposed and tested along with the previously described replication strategies.

• Static – uses a fixed replica set of nodes with no dynamic changes to the files being replicated.
• Best Client – Each node records number of requests per file received during a preset time interval; if the request number exceeds the set threshold for a file a replica is created on the best client, one that requested the file the most; stale replicas are removed based on another algorithm.
• Cascading – Is used in a hierarchical node structure where requests per file received during a preset time interval is compared against a threshold. If the threshold is exceeded a replica is created at the first tier down from the root, if the threshold is exceeded again a replica is added to the next tier down and so on like a waterfall effect until a replica is placed at the client itself.
• Plain Caching – If the client requests a file it is stored as a copy on the client.
• Caching plus Cascading – Combines two strategies of caching and cascading.
• Fast Spread – Also used in a hierarchical node structure this strategy automatically populates all nodes in the path of the client that requests a file.

Tasks scheduling and resource allocation

Such characteristics of the data grid systems as large scale and heterogeneity require specific methods of tasks scheduling and resource allocation. To resolve the problem, majority of systems use extended classic methods of scheduling. Others invite fundamentally different methods based on incentives for autonomous nodes, like virtual money or reputation of a node. Another specificity of data grids, dynamics, consists in the continuous process of connecting and disconnecting of nodes and local load imbalance during an execution of tasks. That can make obsolete or non-optimal results of initial resource allocation for a task. As a result, much of the data grids utilize execution-time adaptation techniques that permit the systems to reflect to the dynamic changes: balance the load, replace disconnecting nodes, use the profit of newly connected nodes, recover a task execution after faults.

Resource management system (RMS)

The resource management system represents the core functionality of the data grid. It is the heart of the system that manages all actions related to storage resources. In some data grids it may be necessary to create a federated RMS architecture because of different administrative policies and a diversity of possibilities found within the data grid in place of using a single RMS. In such a case the RMSs in the federation will employ an architecture that allows for interoperability based on an agreed upon set of protocols for actions related to storage resources.

RMS functional capabilities

• Fulfillment of user and application requests for data resources based on type of request and policies; RMS will be able to support multiple policies and multiple requests concurrently
• Scheduling, timing and creation of replicas
• Policy and security enforcement within the data grid resources to include authentication, authorization and access
• Support systems with different administrative policies to inter-operate while preserving site autonomy
• Support quality of service (QoS) when requested if feature available
• Enforce system fault tolerance and stability requirements
• Manage resources, i.e. disk storage, network bandwidth and any other resources that interact directly or as part of the data grid
• Manage trusts concerning resources in administrative domains, some domains may place additional restrictions on how they participate requiring adaptation of the RMS or federation.
• Supports adaptability, extensibility, and scalability in relation to the data grid.

Topology

Data grids have been designed with multiple topologies in mind to meet the needs of the scientific community. On the right are four diagrams of various topologies that have been used in data grids. Each topology has a specific purpose in mind for where it will be best utilized. Each of these topologies is further explained below.

Federation topology is the choice for institutions that wish to share data from already existing systems. It allows each institution control over their data. When an institution with proper authorization requests data from another institution it is up to the institution receiving the request to determine if the data will go to the requesting institution. The federation can be loosely integrated between institutions, tightly integrated or a combination of both.

Monadic topology has a central repository that all collected data is fed into. The central repository then responds to all queries for data. There are no replicas in this topology as compared to others. Data is only accessed from the central repository which could be by way of a web portal. One project that uses this data grid topology is the Network for Earthquake Engineering Simulation (NEES) in the United States. This works well when all access to the data is local or within a single region with high speed connectivity.

Hierarchical topology lends itself to collaboration where there is a single source for the data and it needs to be distributed to multiple locations around the world. One such project that will benefit from this topology would be CERN that runs the Large Hadron Collider that generates enormous amounts of data. This data is located at one source and needs to be distributed around the world to organizations that are collaborating in the project.

Hybrid Topology is simply a configuration that contains an architecture consisting of any combination of the previous mentioned topologies. It is used mostly in situations where researchers working on projects want to share their results to further research by making it readily available for collaboration.

History

The need for data grids was first recognized by the scientific community concerning climate modeling, where terabyte and petabyte sized data sets were becoming the norm for transport between sites. More recent research requirements for data grids have been driven by the Large Hadron Collider (LHC) at CERN, the Laser Interferometer Gravitational Wave Observatory (LIGO), and the Sloan Digital Sky Survey (SDSS). These examples of scientific instruments produce large amounts of data that need to be accessible by large groups of geographically dispersed researchers. Other uses for data grids involve governments, hospitals, schools and businesses where efforts are taking place to improve services and reduce costs by providing access to dispersed and separate data systems through the use of data grids.

From its earliest beginnings, the concept of a Data Grid to support the scientific community was thought of as a specialized extension of the “grid” which itself was first envisioned as a way to link super computers into meta-computers. However, that was short lived and the grid evolved into meaning the ability to connect computers anywhere on the web to get access to any desired files and resources, similar to the way electricity is delivered over a grid by simply plugging in a device. The device gets electricity through its connection and the connection is not limited to a specific outlet. From this the data grid was proposed as an integrating architecture that would be capable of delivering resources for distributed computations. It would also be able to service numerous to thousands of queries at the same time while delivering gigabytes to terabytes of data for each query. The data grid would include its own management infrastructure capable of managing all aspects of the data grids performance and operation across multiple wide area networks while working within the existing framework known as the web.

The data grid has also been defined more recently in terms of usability; what must a data grid be able to do in order for it to be useful to the scientific community. Proponents of this theory arrived at several criteria. One, users should be able to search and discover applicable resources within the data grid from amongst its many datasets. Two, users should be able to locate datasets within the data grid that are most suitable for their requirement from amongst numerous replicas. Three, users should be able to transfer and move large datasets between points in a short amount of time. Four, the data grid should provide a means to manage multiple copies of datasets within the data grid. And finally, the data grid should provide security with user access controls within the data grid, i.e. which users are allowed to access which data.

The data grid is an evolving technology that continues to change and grow to meet the needs of an expanding community. One of the earliest programs begun to make data grids a reality was funded by the Defense Advanced Research Projects Agency (DARPA) in 1997 at the University of Chicago. This research spawned by DARPA has continued down the path to creating open source tools that make data grids possible. As new requirements for data grids emerge projects like the Globus Toolkit will emerge or expand to meet the gap. Data grids along with the "Grid" will continue to evolve.

References

• Allcock, Bill; Chervenak, Ann; Foster, Ian; Kesselman, Carl; Livny, Miron (2005). "Data Grid tools: enabling science on big distributed data". Journal of Physics: Conference Series 16 (1): 571–575. doi:10.1088/1742-6596/16/1/079. Bibcode: 2005JPhCS..16..571A. 

• Allcock (2001). High-performance remote access to climate simulation data: A challenge problem for data grid technologies. ACM Press. 

• Arcot, Rajasekar; Wan, Michael; Moore, Reagan; Schroeder, Wayne; Kremenek, George. "Storage resource broker – managing distributed data in a grid". http://www.npaci.edu/DICE/Pubs/CSI-paper-sent.doc. 

• Belalem, Ghalem; Meroufel, Bakhta (2011). "Management and placement of replicas in a hierarchical data grid". International Journal of Distributed and Parallel Systems 2 (6): 23–30. doi:10.5121/ijdps.2011.2603. https://www.scribd.com/doc/75105419/Management-and-Placement-of-Replicas-in-a-Hierarchical-Data-Grid. Retrieved April 28, 2012. 

• Chervenak, A.; Foster, I.; Kesselman, C.; Salisbury, C.; Tuecke, S. (2001). "The data grid: towards an architecture for the distributed management and analysis of large scientific datasets". Journal of Network and Computer Applications 23 (3): 187–200. doi:10.1006/jnca.2000.0110. http://www.globus.org/alliance/publications/papers/JNCApaper.pdf. Retrieved April 11, 2012. 

• Chervenak, Ann; Schuler, Robert; Kesselman, Carl; Koranda, Scott; Moe, Brian (November 14, 2005). "Wide area data replication for scientific collaborations". IEEE. http://www.globus.org/alliance/publications/papers/chervenakGrid2005.pdf. 

• Coetzee, Serena (2012). "Reference model for a data grid approach to address data in a dynamic SDI". GeoInformatica 16 (1): 111–129. doi:10.1007/s10707-011-0129-4. 

• Epimakhov, Igor; Hameurlain, Abdelkader; Dillon, Tharam; Morvan, Franck (2011). "Resource Scheduling Methods for Query Optimization in Data Grid Systems". Vienna, Austria: Springer Berlin Heidelberg. pp. 185–199. doi:10.1007/978-3-642-23737-9_14. 

• Globus (2012). "About the globus toolkit". Globus. http://www.globus.org/toolkit/about.html. 

• Heingartner, Douglas (March 8, 2001). "The Grid: The Next-Gen Internet". Wired. https://www.wired.com/science/discoveries/news/2001/03/42230. Retrieved May 13, 2012. 

• Izmailov, Rauf; Ganguly, Samrat; Tu, Nan (2004). "Fast parallel file replication in data grid". http://www.cs.huji.ac.il/labs/danss/p2p/resources/fast-parallel-file-replication-on-data-grid.pdf. 

• Kranthi, G. Aruna; Rekha, D. Shashi (2012). "Protected data objects replication in data grid". International Journal of Network Security & Its Applications 4 (1): 29–41. doi:10.5121/ijnsa.2012.4103. ISSN 0975-2307. 

• Krauter, Klaus; Buyya, Rajkumar; Maheswaran, Muthucumaru (2002). "A taxonomy and survey of grid resource management systems for distributed computing". Software: Practice and Experience 32 (2): 135–164. doi:10.1002/spe.432. 

• Lamehamedi (2002). "Data replication strategies in grid environments". Press. pp. 378–383. 

• Padala, Pradeep. A survey of data middleware for Grid systems. 

• Raman, Vijayshankar; Narang, Inderpal; Crone, Chris; Hass, Laura; Malaika, Susan (February 9, 2003). "Services for data access and data processing on grids". http://www.ogf.org/documents/GFD.14.pdf. 

• Ranganathan, Kavitha; Foster, Ian (2001). "Identifying dynamic replication strategies for a high performance data grid". pp. 75–86. doi:10.1007/3-540-45644-9_8. 

• Shorfuzzaman, Mohammad; Graham, Peter; Eskicioglu, Rasit (2010). "Adaptive replica placement in hierarchical data grids". Journal of Physics: Conference Series 256 (1): 1–18. doi:10.1088/1742-6596/256/1/012020. Bibcode: 2010JPhCS.256a2020S. 

• Sreelatha, Malempati (2011). "Grid based approach for data confidentiality". International Journal of Computer Applications 25 (9): 1–5. doi:10.5120/3063-4186. ISSN 0975-8887. Bibcode: 2011IJCA...25i...1M. 

• Thibodeau, P. (May 30, 2005). "Governments plan data grid projects". Computerworld 39 (42): 14. ISSN 0010-4841. http://www.computerworld.com/s/article/102119/Governments_Plan_Data_Grid_Projects. Retrieved April 28, 2012. 

• Thomas, R. K.; Sandhu, R. S. (1997). "Task-based authorization controls (tbac): a family of models for active and enterprise-oriented authorization management". http://profsandhu.com/confrnc/ifip/i97tbac.pdf. 

• Tierney, Brian L. (2000). "Data grids and data grid performance issues". http://www-didc.lbl.gov/presentations/CSC2000-tierney.pdf. 

• Venugopal, Srikumar; Buyya, Rajkumar; Ramamohanarao, Kotagiri (2006). "A taxonomy of data grids for distributed data sharing, management and processing". ACM Computing Surveys 38 (1): 1–60. doi:10.1145/1132952.1132955. http://www.cloudbus.org/reports/DataGridTaxonomy.pdf. Retrieved April 10, 2012. 

• {{cite web

|last1=Zhu 
|first1=Lichun 
|title=Metadata management in grid database federation 
|url=http://cs.uwindsor.ca/richard/cs510/lichun_zhu_survey.pdf 
|access-date=May 15, 2012 

Further reading

• Allcock, W. (April 2003). "Gridftp: protocol extensions to ftp for the grid". Argonne National Laboratory. http://www.globus.org/alliance/publications/papers/GFD-R.0201.pdf. 

• Allcock, W.; Bresnahan, J.; Kettimuthu, R.; Link, M.; Dumitrescu, C.; Raicu, I.; Foster, I. (November 2005). "The globus striped gridftp framework and server". ACM Press. http://www.globus.org/alliance/publications/papers/gridftp_final.pdf. 

• Foster, Ian; Kesselman, Carl; Tuecke, Steven (2001). "The anatomy of the grid enabling scalable virtual organizations". International Journal of High Performance Computing Applications 15 (3): 200–222. doi:10.1177/109434200101500302. Bibcode: 2001cs........3025F. http://www.globus.org/alliance/publications/papers/anatomy.pdf. Retrieved April 10, 2012. 

• Foster, Ian; Kesselman, Carl; Nick, Jeffrey M.; Tuecke, Steven (June 22, 2002). "The physiology of the grid: an open grid services architecture for distributed systems integration". http://forge.gridforum.org/sf/go/doc13483?nav=1. 

• Hancock, B. (2009). "A simple data grid using the inferno operating system". Library Hi Tech 27 (3): 382–392. doi:10.1108/07378830910988513. 

• Hoschek, W.; McCance, G. (October 10, 2001). "Grid enabled relational database middleware". Global Grid Forum. http://ppewww.ph.gla.ac.uk/preprints/2001/11/GGF3Rome2001.pdf. 

• Kunszt, Peter Z.; Guy, Leanne P. (July 7, 2002). "The open grid services architecture and data grids". http://www.computing.surrey.ac.uk/courses/csm23/Papers/data_grid.pdf. 

• Moore, Reagan W.. "Evolution of data grid concepts". http://www.nesc.ac.uk/events/GGF10-DA/programme/papers/06-Moore-Grid-evolution.pdf. 

• Rajkumar, Kettimuthu; Allcock, William; Liming, Lee; Navarro, John-Paul; Foster, Ian (March 30, 2007). "GridCopy moving data fast on the grid". Long Beach: IEEE International. pp. 1–6. http://www.globus.org/alliance/publications/papers/GridCopy.pdf. Retrieved April 29, 2012. 

• Thenmozhi, N.; Madheswaran, M. (2011). "Content based data transfer mechanism for efficient bulk data transfer in grid computing environment". International Journal of Grid Computing & Applications 2 (4): 49–62. doi:10.5121/ijgca.2011.2405. ISSN 2229-3949. https://www.scribd.com/doc/78611092/Content-Based-Data-Transfer-Mechanism-for-Efficient-Bulk-Data-Transfer-in-Grid-Computing-Environment. Retrieved April 28, 2012. 

• {{cite journal

|last1=Tu 
|first1=Manghui 
|last2=Li 
|first2=Peng 
|last3=I-Ling 
|first3=Yen 
|last4=Thuraisingham 
|first4=Bhavani 
|last5=Khan 
|first5=Latifur 
|year=2010 
|title=Secure data objects replication in data grid 
|journal=IEEE Transactions on Dependable and Secure Computing 
|volume=7 
|issue=1 
|pages=50–64 
|doi=10.1109/tdsc.2008.19 
|s2cid=8934783 
|url=http://www.utdallas.edu/~lkhan/papers/Secure_Data_Objects_Replication_in_Data_Grid.pdf 
|access-date=April 26, 2012