Hi Nate, I got your point but which part of the code is doing all these things, I mean how exactly this is done. Is it using any other function apart from recover?
Regards Harendra On Wed, Jun 1, 2011 at 8:56 AM, Nate Coraor <n...@bx.psu.edu> wrote: > Harendra chawla wrote: > > Hi everyone, > > > > I am trying to modify the *recover* function from the drmaa.py > > (/galaxy_central/lib/galaxy/job/runners/drmaa.py) as per my requirements. > > But I am not ale to understand the flow of that function. > > > > The recover function is called when the galaxy server is restarted. It > first > > looks for the running jobs from the database. Then my problem is how it > > regains the same old state of the galaxy (specially the GUI) which was > > before the galaxy got restarted. > > Can anyone explain me the flow of the recover function and how the old > state > > is regained. > > Hi Harendra, > > I'm not sure I understand what you mean by old state and the GUI - all > that's really necessary here is to determine what Galaxy considers to be > the state of the job (new, queued, running), recreate the in-memory job > components (the JobWrapper), and place the job back in Galaxy's > DRM-monitoring queue, which will then proceed with the process of > finishing the job if it's finished in the DRM or waiting for it to > finish if it's still queued or running in the DRM. > > --nate > > > > > Regards > > Harendra > > > ___________________________________________________________ > > Please keep all replies on the list by using "reply all" > > in your mail client. To manage your subscriptions to this > > and other Galaxy lists, please use the interface at: > > > > http://lists.bx.psu.edu/ > >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
