Difference between revisions of "Atlas:SC4-May07"
M (→Logbook) |
M (→T0-T1-T2 transfer tests) |
||
Ligne 1: | Ligne 1: | ||
= T0-T1-T2 transfer tests = | = T0-T1-T2 transfer tests = | ||
* A new DDM version (called 0.3) is under test. The first goal is to reach a steady transfer from CERN (T0) to T1s. | * A new DDM version (called 0.3) is under test. The first goal is to reach a steady transfer from CERN (T0) to T1s. | ||
− | * A new Arda monitoring | + | * A new Arda monitoring from DDM 0.3 is accessible at this [http://dashb-atlas-data-test.cern.ch/dashboard/request.py/site address] |
* A [https://twiki.cern.ch/twiki/bin/view/Atlas/DDMMorningMeetings Twiki page] is maintained for the whole transfers | * A [https://twiki.cern.ch/twiki/bin/view/Atlas/DDMMorningMeetings Twiki page] is maintained for the whole transfers | ||
* [http://lxarda08.cern.ch/dashboard/request.py/site DDM 0.2] (MC production transfers) and [http://dashb-atlas-data-test.cern.ch/dashboard/request.py/site DDM 0.3] (T0_T1-T2 transfers) run concurently. Both use the same FTS instance in LYON. | * [http://lxarda08.cern.ch/dashboard/request.py/site DDM 0.2] (MC production transfers) and [http://dashb-atlas-data-test.cern.ch/dashboard/request.py/site DDM 0.3] (T0_T1-T2 transfers) run concurently. Both use the same FTS instance in LYON. |
Version du 16:05, 17 mai 2007
Sommaire
T0-T1-T2 transfer tests
- A new DDM version (called 0.3) is under test. The first goal is to reach a steady transfer from CERN (T0) to T1s.
- A new Arda monitoring from DDM 0.3 is accessible at this address
- A Twiki page is maintained for the whole transfers
- DDM 0.2 (MC production transfers) and DDM 0.3 (T0_T1-T2 transfers) run concurently. Both use the same FTS instance in LYON.
T0-LYON tests
General remarks
- Lyon participated to the T0-T1 test since the beginning (beginning of May).
- The main problems was Castor stability at CERN
- Datasets exists during 24 hours. After 24 hours, the datasets are deleted but not the physical files and the LFC entries.
- As a consequence of previous point, since 16 May, subscriptions T0->T1 of datasets older than 12 hours are removed
- Files are kept 8 hours in dcache disk area (cleaning managed by dcache team)
Logbook
- Transfers started mid-April
- Status plot with one bin per day (15 May)
LYON-T2 tests
General remarks
- Only AOD datasets are transfered to T2s. Each dataset include one file of 3.6 GB.
- A cron script is run from LAPP to request
- transfer of datasets to each T2/T3 site
- delete files and LFC entries when the dataset transfer is complete or the dataset disappeared (operated by CERN)
- Files have to be transfered before the files (in LYON) and the datasets (at CERN) disappear. So from time to time, no datasets fullfill these constraints
Logbook
- 12 May First tests of LYON->T2. These tests should not affect T0->T2 transfers (dcache load)
- 15 May: Status plot for (15 May)
- First comments (15 May):
- CPPM, LAPP, LAL, SACLAY, LPNHE, LPC : OK
- NIPNE_02, NIPNE_07 : Seems to have network limitations
- TOKYO : Many transfers pending with DDM 0.2. Big fight between both DDM versions
- BEIJING : Problem to get TURL
- First comments (15 May):
- Transfers from LYON to T2s are probably affected by the saturation of the line between Computing Center and the NRD (RENATER node)[link]. All T1->T2 transfers go through this line.
- 16 May:
- TURL problem with BEIJING solved. Now problem of access right
- FTS T1->T2 behaves much better when CC->NRD link is not saturated
- 17 May :
- LYON->T2 transfers subscribed but not treated by DDM 0.3. Request help from DDM team.