Fifth IEEE/ACM International Workshop on Grid Computing
DOI: 10.1109/grid.2004.51
|View full text |Cite
|
Sign up to set email alerts
|

Phoenix: Making Data-Intensive Grid Applications Fault-Tolerant

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
17
0
1

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 20 publications
(18 citation statements)
references
References 18 publications
0
17
0
1
Order By: Relevance
“…A fault tolerant middleware has been described in Kola et al (2004) for data intensive distributed applications by examining the environmental conditions and classifying failures such that a suitable strategy can be applied to handle operations in a transient way. The methodology described in Kola et al (2004) uses log information from the job scheduler and the data placement scheduler and takes the next action according to user policies.…”
Section: Related Workmentioning
confidence: 99%
“…A fault tolerant middleware has been described in Kola et al (2004) for data intensive distributed applications by examining the environmental conditions and classifying failures such that a suitable strategy can be applied to handle operations in a transient way. The methodology described in Kola et al (2004) uses log information from the job scheduler and the data placement scheduler and takes the next action according to user policies.…”
Section: Related Workmentioning
confidence: 99%
“…Phoenix [13] detects failures by scanning scheduler log files. It can diagnose execution and data transfer errors.…”
Section: Related Workmentioning
confidence: 99%
“…Hence, users can resubmit their jobs to other resources. As demonstrated in this example, both detection and recovery schemes must be an integral part of the Grid computing infrastructure [13,18]. Therefore, it is important to conduct thorough study and evaluation of new reliability models, error detection and recovery techniques before they can be deployed in production Grid environments.…”
Section: Introductionmentioning
confidence: 99%
“…Here, each layer handles the errors within its own scope, pass others up the hierarchy [23]. This approach simplifies higher-level layers, however, at the expense of performance penalties as higher layers themselves can not adapt any more [18]. Building FT into each component in a grid is also not practical, due to scale and diversity of components.…”
Section: Failures In Grid Environmentsmentioning
confidence: 99%
“…Phoenix is detecting failures by scanning scheduler log files [18]. It can diagnose execution and data transfer errors.…”
Section: Related Workmentioning
confidence: 99%