Proceedings of the 2005 ACM Conference on Emerging Network Experiment and Technology - CoNEXT'05 2005
DOI: 10.1145/1095921.1095939
|View full text |Cite
|
Sign up to set email alerts
|

Location based placement of whole distributed systems

Abstract: The high bandwidth and low latency of the modern internet has made possible the deployment of distributed computing platforms.The XenoServer platform provides a distributed computing platform open to all and presents three major new challenges for resource discovery: Firstly, network location is key for effectively provisioning services, to mitigate against high-latency, high-load or component failure. Secondly, many services require a presence on several servers, with inter-related requirements. Finally, as t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2006
2006
2015
2015

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 16 publications
(10 citation statements)
references
References 34 publications
(26 reference statements)
0
9
0
Order By: Relevance
“…When the crashed primary node restarts, it receives the new data accumulated during its down time from the new primary node. When the failed node cannot reboot fast enough, a human operator or a system monitoring service selects a new backup node based on its available NVMM size, its networking topology, and other criteria [6,53]. The new node receives a complete copy of the memory region and begins processing updates from the new mirror node.…”
Section: Recoverymentioning
confidence: 99%
“…When the crashed primary node restarts, it receives the new data accumulated during its down time from the new primary node. When the failed node cannot reboot fast enough, a human operator or a system monitoring service selects a new backup node based on its available NVMM size, its networking topology, and other criteria [6,53]. The new node receives a complete copy of the memory region and begins processing updates from the new mirror node.…”
Section: Recoverymentioning
confidence: 99%
“…When the crashed primary node restarts, it receives the new data accumulated during its down time from the new primary node. When the failed node cannot reboot fast enough, a human operator or a system monitoring service selects a new backup node based on its available NVMM size, its networking topology, and other criteria [6,53]. The new node receives a complete copy of the memory region and begins processing updates from the new mirror node.…”
Section: Recoverymentioning
confidence: 99%
“…However, this approach is based on assumption that system experiences low churn rate [32]. Gossiping and onehop routing approach has been used for maintaining the routing overlay in the work [33].…”
Section: Dhtmentioning
confidence: 99%