Inderpreet Chopra wrote:
Hi all
I am working on the fault-tolerance and the security aspects of Grid. I
want to work on these two aspects in globus .
For this I want to know about the internal structure of Globus and its
components.
Do you mean Globus or the job management component in Globus?
Is Globus is using some Async or sync queues for taking request for
executing the jobs?
I'm not entirely sure what you mean by that. A client does not hold a connection
open until a job finished processing completely, only until a job resource has
been created on the server-side, which is used so that a client can refer
to his job. Once the job resource has been created the processing starts
on the server-side, without client-interaction.
What if some node fails in between means is there some way to recover
the pending task being stuck in the erronous node?
What do you mean by "some node"? A client, the globus-server, or a machine of
a cluster which was picked by the local resource manager (like PBS, Condor) to
execute the job?
Can anyone please guide me in getting answer to my questions and also
some documents describing globus internal architecture.
The following webpage gives an overview over key concepts gram (job management):
http://www.globus.org/toolkit/docs/4.2/4.2.1/execution/key/#executionKey
A starting point for more information about gram is this:
http://www.globus.org/toolkit/docs/4.2/4.2.1/execution/
Martin
Also any suggestions related to my area of intrest i.e fault tolerance
and security in globus. What is still pending that i can take and work upon.
Regards,
Inderpreet
