2011
DOI: 10.1109/tpds.2010.207
|View full text |Cite
|
Sign up to set email alerts
|

Data Replication in Data Intensive Scientific Applications with Performance Guarantee

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 72 publications
(33 citation statements)
references
References 44 publications
0
33
0
Order By: Relevance
“…The most directly related work to this replication work is complicated process on clouds server. The data replication and request response on cloud server as a static optimization problem on user access [7]. They show that this problem is NP-hard and request delay, which means that present, is no polynomial algorithm that provides an accurate solution.…”
Section: Related Workmentioning
confidence: 99%
“…The most directly related work to this replication work is complicated process on clouds server. The data replication and request response on cloud server as a static optimization problem on user access [7]. They show that this problem is NP-hard and request delay, which means that present, is no polynomial algorithm that provides an accurate solution.…”
Section: Related Workmentioning
confidence: 99%
“…The design of NFS involves simplicity and hence they did not take into consideration any of the complex concurrent read/write issues. Dharma et al [38] propose a data replication algorithm that not only has a provable theoretical performance guarantee, but also can be implemented in a distributed and practical manner. Specifically, authors have designed a polynomial time centralized replication algorithm that reduces the total data file access delay by at least half of that reduced by the optimal replication solution.…”
Section: Related Workmentioning
confidence: 99%
“…It's based on a masterslave architecture, the NameNode as a master and the DataNodes as slaves. The NameNode is responsible for managing the file system namespace, it keeps tracks of files during creation, deletion, replication [3] and manages all the related metadata [4] in the server memory. The NameNode splits files into blocks and sends the writes requests to be performed locally by DataNodes.…”
Section: Hadoop Storagementioning
confidence: 99%