Difference between revisions of "RAL Tier1 weekly operations castor 24/08/2015"
From GridPP Wiki
(Created page with "== Operations News == * CMS disk read issues much improved. ** Changed I/O scheduler for cmsDisk nodes from 'cfq' to 'noop'. We are now seeing performance roughly in line with...") |
|||
| Line 2: | Line 2: | ||
* CMS disk read issues much improved. | * CMS disk read issues much improved. | ||
** Changed I/O scheduler for cmsDisk nodes from 'cfq' to 'noop'. We are now seeing performance roughly in line with other CMS Tier 1 sites. | ** Changed I/O scheduler for cmsDisk nodes from 'cfq' to 'noop'. We are now seeing performance roughly in line with other CMS Tier 1 sites. | ||
| + | ** CPU efficiency now 85% was 40% | ||
* Disk server draining on hold due to ATLAS being very full | * Disk server draining on hold due to ATLAS being very full | ||
== Operations Problems == | == Operations Problems == | ||
| + | * Atlas moving large amount of data from atlasdisk to tape, slow write to tape experienced. Config changed to allow more tapes to write simultaneously, much improved. | ||
| + | * GGUS ticket from Atlas - File recalled from tape resulted in a file slightly bigger than expected (with incorrect checksum), also staged with incorrect checksum – this needs further investigation | ||
* The large numbers of checksum tickets seen by the production team are not thought to be due to the rebalancer. The source of these needs to be identified. Shaun is investigating | * The large numbers of checksum tickets seen by the production team are not thought to be due to the rebalancer. The source of these needs to be identified. Shaun is investigating | ||
* The gridmap file on the the webdav host lcgcadm04.gridpp.rl.ac.uk is not auto-updating. | * The gridmap file on the the webdav host lcgcadm04.gridpp.rl.ac.uk is not auto-updating. | ||
| Line 9: | Line 12: | ||
== Planned, Scheduled and Cancelled Interventions == | == Planned, Scheduled and Cancelled Interventions == | ||
| + | * Looking to schedule disk server SL6 deployments for next week | ||
| + | ** plan to put at risk all day (wed/thurs) | ||
| + | ** all VOs / all castor disks | ||
| + | ** action by server number taking highest number first (newest / biggest) | ||
| + | * GDSS 720 / 707 draining > CPU / motherboard fixes | ||
* Stress test SRM poss deploy week after (Shaun) | * Stress test SRM poss deploy week after (Shaun) | ||
* Upgrade CASTOR disk servers to SL6 | * Upgrade CASTOR disk servers to SL6 | ||
| Line 24: | Line 32: | ||
* Staff absence/out of the office: | * Staff absence/out of the office: | ||
== New Actions == | == New Actions == | ||
| + | * GS to review tickets in an attempt to identify when checksum/partial file creation issues started | ||
| + | * SdW to submit a change control to make I/O scheduler for cmsDisk nodes from 'cfq' to 'noop' change persistent on CMSdisk / into SL6 | ||
| + | * RA / SdW to contact CERN Dev about checksum issue / partial file creation | ||
| + | |||
== Existing Actions == | == Existing Actions == | ||
Revision as of 11:24, 21 August 2015
Contents
Operations News
- CMS disk read issues much improved.
- Changed I/O scheduler for cmsDisk nodes from 'cfq' to 'noop'. We are now seeing performance roughly in line with other CMS Tier 1 sites.
- CPU efficiency now 85% was 40%
- Disk server draining on hold due to ATLAS being very full
Operations Problems
- Atlas moving large amount of data from atlasdisk to tape, slow write to tape experienced. Config changed to allow more tapes to write simultaneously, much improved.
- GGUS ticket from Atlas - File recalled from tape resulted in a file slightly bigger than expected (with incorrect checksum), also staged with incorrect checksum – this needs further investigation
- The large numbers of checksum tickets seen by the production team are not thought to be due to the rebalancer. The source of these needs to be identified. Shaun is investigating
- The gridmap file on the the webdav host lcgcadm04.gridpp.rl.ac.uk is not auto-updating.
Blocking Issues
Planned, Scheduled and Cancelled Interventions
- Looking to schedule disk server SL6 deployments for next week
- plan to put at risk all day (wed/thurs)
- all VOs / all castor disks
- action by server number taking highest number first (newest / biggest)
- GDSS 720 / 707 draining > CPU / motherboard fixes
- Stress test SRM poss deploy week after (Shaun)
- Upgrade CASTOR disk servers to SL6
- One tape-backed node being upgraded, more tape-backed nodes next week.
- Oracle patching schedule planned. (End 13th October)
Advanced Planning
Tasks
- Proposed CASTOR face to face W/C Oct 5th or 12th
- Discussed CASTOR 2017 planning, see wiki page.
Interventions
Staffing
- Castor on Call person next week
- SdW
- Staff absence/out of the office:
New Actions
- GS to review tickets in an attempt to identify when checksum/partial file creation issues started
- SdW to submit a change control to make I/O scheduler for cmsDisk nodes from 'cfq' to 'noop' change persistent on CMSdisk / into SL6
- RA / SdW to contact CERN Dev about checksum issue / partial file creation
Existing Actions
- SdW to modify cleanlostfiles to log to syslog so we can track its use - under testing
- SdW to look into GC improvements - notify if file in inconsistent state
- SdW to replace canbemigr test - to test for file that have not been migrated to tape (warn 8h / alert 24h)
- SdW testing/working gfalcopy rpms
- RA/JJ to look at information provider re DiRAC (reporting disk only etc)
- RA to look into procedural issues with CMS disk server interventions
- RA to investigate why we are getting partial files
- BC to document processes to control services previously controlled by puppet
- GS to arrange meeting castor/fab/production to discuss the decommissioning procedures
- GS to investigate providing checks for /etc/noquattor on production nodes & checks for fetch-crl - ONGOING
- BD to chase AD about using the space reporting thing we made for him
- Someone - mice, what access protocol do they use?
- GS to investigate how/if we need to declare xrootd endpoints in GOCDB BDII
