Stopping the network server prevents new jobs from being submitted. You
can still do a edg-job-status for the already submitted ones.
However you cannot retrieve the output after the job finishes. You'll have
to restart the network server in order to do that.
Jose Gabadinho
On Tuesday 08 June 2004 10:13, you wrote:
> Hi,
> I am not aware of a proper procedure to do this. However, we'll try to
> stop the NS service on the RB.
> This should disable submitting jobs. Jose tries if it still will allow
> to get the status and sandboxes.1
>
> I think on the longer term we should publish the RBs in the information
> system and make the client tools check that the
> service is present.
>
> markus
>
> On Tuesday, Jun 8, 2004, at 09:54 Europe/Zurich, Steve Traylen wrote:
> > Hi,
> >
> > We plan to set up a second RB in the next couple of days on faster
> > hardware with more swap as the current one is having problems.
> >
> > Is there a procedure for draining an RB to stop it accepting new jobs,
> > obviously we will point our UI at the new one and I think sandboxes
> > are deleted after 10 days? During that time we will leave it running.
> >
> > Steve
> >
> > --
> > Steve Traylen
> > [log in to unmask]
> > http://www.gridpp.ac.uk/
>
> ************************************************************************
> *******
> Markus Schulz
> CERN IT
|