The user sets the lifetime for each file. You can set a maximum lifetime for
the SA MaxPinDuration.
I don't think we want to get into setiing these values without a MUCH wider
discussion. I seriously doubt that any user is using them to decide which SE
to use. They'll get a lot more angry if we say we deleted your files because
we set this parameter that says we can, than they did when files get deleted
by accident or through misunderstanding.
There is a LOT more discussion needed with experiments on how they use
Storage between T2-T1-T0.
John
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Brew, CAJ (Chris)
> Sent: 14 January 2005 15:14
> To: [log in to unmask]
> Subject: Re: Looking for LHCb files at Birmingham LCG site
>
>
> Hi,
>
> And both the "durable" and "volatile" setting have a lifetime
> associated - what do I have to set to publish that?
>
> Thanks,
> Chris.
>
> > -----Original Message-----
> > From: Testbed Support for GridPP member institutes
> > [mailto:[log in to unmask]] On Behalf Of owen maroney
> > Sent: 14 January 2005 15:06
> > To: [log in to unmask]
> > Subject: Re: Looking for LHCb files at Birmingham LCG site
> >
> > Hi,
> >
> > It is interesting to see this parameter, but this still
> doesn't answer
> > Chris's question. If I set:
> >
> > GlueSAPolicyFileLifeTime: volatile
> >
> > then am I free to set up whatever cron jobs I like to clean
> files more
> > than X months old (and by clean, I do mean files must be
> cleaned from
> > the replica-catalog at the same time!)? And how long can X be?
> >
> > I would certainly be recommending that all LT2 sites
> configure their
> > disk storage systems this way. In fact, it seems very
> strange to me
> > that this "volatile" *not* the default setting!
> >
> > regards
> > Owen.
> >
> > NB. According to the definitions, the sys admin is
> perfectly free to
> > delete files from 'permanent' storage anyway...
> >
> > Burke, S (Stephen) wrote:
> >
> > > Testbed Support for GridPP member institutes
> > >
> > >>[mailto:[log in to unmask]] On Behalf Of Brew, CAJ
> > (Chris) said:
> > >>When looking through the information published by my SE I
> > noticed that
> > >>there's a line:
> > >>
> > >>GlueSAPolicyFileLifeTime: permanent
> > >>
> > >>What are the other available settings for this. Can sites change
> > >>this to 3 months and the delete stuff when it's been there three
> > >>months?
> > >
> > >
> > > The schema currently says:
> > >
> > > Definition 2. Permanent file type: a file stored in a
> > Storage Space that can
> > > be removed only by the owner or by the system administrator [1]
> > >
> > > Definition 3. Volatile file type: a file stored in a
> > Storage Space that can
> > > be removed by the Storage Service when space is needed. A
> > volatile file is
> > > pinned in the cache for a certain "lifetime" period. The
> > length of the
> > > "lifetime" is the choice of the Storage Service
> > Administrator or the Storage
> > > Service's policy. Usually, a file is expected to be
> > "released" or "unpinned"
> > > by the client before its lifetime expires. Provisions can
> > be made for
> > > extending the pinning of a file, but we felt that honoring
> > pinning extension
> > > requests should be an implementation choice as well. [1]
> > >
> > > Definition 4. Durable file type: a file stored in a Storage
> > Space that is
> > > intended to be removed as soon as possible, but should not
> > be deleted by the
> > > Storage Service. It has a "lifetime" associated with it
> > (perhaps longer than
> > > that of a volatile file), but when its lifetime expires a system
> > > administrator is alerted. Similar to a permanent file it
> > can be only removed
> > > by the owner or the administrator. Thus, the concept of a
> > "durable" file has
> > > the features of both volatile and permanent files.
> > >
> > > The need for a "durable" file status was inspired by the
> > scenario of files
> > > generated by some compute resource, and there is a need to
> > temporarily store
> > > them in a shared space before they are archived. Normally,
> > the files are
> > > stored in the shared space as "durable", and then scheduled
> > to be archived
> > > on some other archival storage system. After the files are
> > archived, they
> > > are released either automatically by the archiving Storage
> > Service or by the
> > > client. In case that the client neglects to release them,
> > an administrator
> > > is alerted when the lifetime expires. [1]
> > >
> > > Stephen
> >
> > --
> > =======================================================
> > Dr O J E Maroney # London Tier 2 Technical Co-ordinator
> >
> > Tel. (+44)20 759 47802
> >
> > Imperial College London
> > High Energy Physics Department
> > The Blackett Laboratory
> > Prince Consort Road, London, SW7 2BW
> > ====================================
> >
>
|