Do you say that it will never be removed before nay less than FIVE minutes? Where shall one put this parameter RefreshIntervalSecs ? In the reg.xml at registration time? Or in the upstream.xml file?
--- On Wed, 10/8/08, Charles Bacon <[EMAIL PROTECTED]> wrote: > From: Charles Bacon > Subject: Re: [gt-user] Erase info when Index departs/ <upstream> hierarchy > chain > http://www.globus.org/toolkit/docs/4.2/4.2.1/info/admin/#mdsAdmin > > It looks like it's controlled by the refresh interval > in the upstream > configuration. The default is to request a lifetime 2x the > refresh > interval. If that times out, then it will be removed > within 5 minutes of the expiration. > > So as long as you can satisfy the equation: > SOON >= (2 * RefreshIntervalSecs / 60 ) + 5, then you should be able to > get what you want. > > > Charles > > On Oct 8, 2008, at 12:09 PM, Maria Jonas wrote: > > > I have set up a hierarchy of index services with the > <upstream> value in the files hierarchy.xml. > > > > But wsrf-queries on indexes belonging to hosts which > have been stopped still return data a long time after that the > host is shutdown. > > > > How can I make this data not to be returned SOON after > an host is stopped? > > > > I want to program this in Java and do not use command > line tools. > >
