Site
| Question | ________________________________Response__________________________________ |
| Site and Endpoints | |
|---|---|
| What is the site name? | T1-JINR |
| Which endpoint URLs do your archival systems expose? | se-hd02-mss.jinr-t1.ru |
| How is tape storage selected for a write (choice of endpoint, specification of a spacetoken, namespace prefix). | The whole storage is dedicated to single client CMS |
| Queue | |
| What limits should clients respect? | Only physical tape limits (all tapes) |
| ---> Max number of outstanding requests | |
| ---> Min/Max requests submitted at one time | |
| ---> Min/Max bulk request size? | |
| Should clients back off under certain circumstances? | |
| ---> How is this signalled to client? | |
| ---> For which operations? | |
| Is it advantageous to group requests by a particular criterion (e.g. tape family, date)? | |
| ---> What criterion? | |
| Prioritisation | |
| Can you handle priority requests? | No. |
| ---> How is this requested? | |
| Protocol support | |
| Are there any unsupported or partially supported operations (e.g. pinning) ? | All supported by dCache. |
| Timeouts | |
| What timeouts do you recommend? | No timeouts. Tasks beyond reasonable time are handled manually. |
| Do you have hardcoded or default timeouts? | No timeouts |
| Operations and metrics | |
| Can you provide total sum of data stored by VO in the archive to 100TB accuracy? | 6300 TB |
| Can you provide space occupied on tapes by VO (includes deleted data, but not yet reclaimed space) to 100TB accuracy? | 7190 TB |
| How do you allocate free tape space to VOs? | The whole space to CMS VO. |
| What is the frequency with which you run repack operations to reclaim space on tapes after data deletion? | After massive deletion. |
| Recommendations for clients | |
| Recommendation 1 | |
| ---> Information required by users to follow advice | |
| Recommendation 2 | |
Topic revision: r2 - 2018-03-05 - NikolayVoytishin
HEPTape Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
- ABATBEA
- ACPP
- ADCgroup
- AEGIS
- AfricaMap
- AgileInfrastructure
- ALICE
- AliceEbyE
- AliceSPD
- AliceSSD
- AliceTOF
- AliFemto
- ALPHA
- ArdaGrid
- ASACUSA
- AthenaFCalTBAna
- Atlas
- AtlasLBNL
- AXIALPET
- CAE
- CALICE
- CDS
- CENF
- CERNSearch
- CLIC
- Cloud
- CloudServices
- CMS
- Controls
- CTA
- CvmFS
- DB
- DefaultWeb
- DESgroup
- DPHEP
- DM-LHC
- DSSGroup
- EGEE
- EgeePtf
- ELFms
- EMI
- ETICS
- FIOgroup
- FlukaTeam
- Frontier
- Gaudi
- GeneratorServices
- GuidesInfo
- HardwareLabs
- HCC
- HEPIX
- ILCBDSColl
- ILCTPC
- IMWG
- Inspire
- IPv6
- IT
- ItCommTeam
- ITCoord
- ITdeptTechForum
- ITDRP
- ITGT
- ITSDC
- LAr
- LCG
- LCGAAWorkbook
- Leade
- LHCAccess
- LHCAtHome
- LHCb
- LHCgas
- LHCONE
- LHCOPN
- LinuxSupport
- Main
- Medipix
- Messaging
- MPGD
- NA49
- NA61
- NA62
- NTOF
- Openlab
- PDBService
- Persistency
- PESgroup
- Plugins
- PSAccess
- PSBUpgrade
- R2Eproject
- RCTF
- RD42
- RFCond12
- RFLowLevel
- ROXIE
- Sandbox
- SocialActivities
- SPI
- SRMDev
- SSM
- Student
- SuperComputing
- Support
- SwfCatalogue
- TMVA
- TOTEM
- TWiki
- UNOSAT
- Virtualization
- VOBox
- WITCH
- XTCA
 |
|
Copyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback