10th IEEE International Symposium on Object and Component-Oriented Real-Time Distributed Computing (ISORC'07) 2007
DOI: 10.1109/isorc.2007.37
|View full text |Cite
|
Sign up to set email alerts
|

Exploiting Tuple Spaces to Provide Fault-Tolerant Scheduling on Computational Grids

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0
2

Year Published

2008
2008
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(8 citation statements)
references
References 15 publications
0
6
0
2
Order By: Relevance
“…Tuple spaces along with checkpointing and replication mechanisms have been applied to grid scheduling in [12]. The performance of distributed checkpointing protocols has been evaluated by Agbaria and Friedman [4].…”
Section: Related Workmentioning
confidence: 99%
“…Tuple spaces along with checkpointing and replication mechanisms have been applied to grid scheduling in [12]. The performance of distributed checkpointing protocols has been evaluated by Agbaria and Friedman [4].…”
Section: Related Workmentioning
confidence: 99%
“…After executing a task, the resources send the result to the broker and the broker assembles all results and returns them to the user. In [7], all communication between brokers/masters and resources/workers is done exclusively through the tuple space.…”
Section: Related Workmentioning
confidence: 99%
“…For example, Chao et al [2] propose a centralized method using BPEL whereas Eymann et al [3] and Cao et al [1] concentrate on a decentralized agent-based approach. Another notable example is the work of Favarim et al [4] who propose to use the tuple-space model for coordination. The last approach seems most promising since its space and time independence allow for late-binding and disconnected operationqualities that fit well to the decentralized service-2-service nature of the SORCER environment.…”
Section: Related Workmentioning
confidence: 99%
“…Those providers that fulfill functional requirements (offer the requested service type) read the corresponding envelops (3) and start the process of issuing an SLA offer. At first they call the SlaPrioritizer service and request a permission to execute and the assigned priorities (4). If a permission is given (5) the provider matches its current QoS parameter values against QoS requirements retrieved from the envelop (6) and based on the outcome creates an SLA offer (if all QoS requirements are met) or proposes an updated SLA contract (otherwise).…”
Section: Sla Negotiation In Space Computingmentioning
confidence: 99%