Difference between revisions of "Tier1 Operations Report 2016-03-23"

From GridPP Wiki
Jump to: navigation, search
(→‎)
(→‎)
 
(15 intermediate revisions by one user not shown)
Line 9: Line 9:
 
| style="background-color: #b7f1ce; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Review of Issues during the week 16th to 23rd March 2016.
 
| style="background-color: #b7f1ce; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Review of Issues during the week 16th to 23rd March 2016.
 
|}
 
|}
−
* Nothing particular to report. Security updates being rolled out.
+
* Security updates have been rolled out. There an outage of Castor last Thursday during which all the component servers were successfully updated and rebooted within the announced downtime. During this time job starts were blocked on the batch farm. Various batch farm nodes (Condor masters etc) were also rebooted at this time and there was a confusion that led to batch jobs not being re-allowed to start until later that evening.
−
* We have uncovered a problem where draining of Castor disk servers is now going very slowly. We need to drain a few old servers to provide spares - this being part of the deployment plan and server lifecycle. Although this does not yet impact services we are having to investigate this.
+
 
<!-- ***********End Review of Issues during last week*********** ----->
 
<!-- ***********End Review of Issues during last week*********** ----->
 
<!-- *********************************************************** ----->
 
<!-- *********************************************************** ----->
Line 21: Line 20:
 
| style="background-color: #f8d6a9; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Resolved Disk Server Issues
 
| style="background-color: #f8d6a9; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Resolved Disk Server Issues
 
|}
 
|}
−
* GDSS677 (CMSTape - D0T1) crashed in the morning of Tuesday 8th March. It was returned to service on Friday (11th Mar). Two disk drives were replaced.
+
* None
−
* GDSS698 (LHCbDst - D1T0) crashed in the morning of Friday 11th March. It was returned to service that evening although no cause for the crash was identified.
+
−
* GDSS646 (LHCbUser - D1T0) crashed on Saturday 12th March. It was put back in service the following day (Sun) in read-only mode. An update of the RAID card firmware revealed some disk problems - which were fixed before the server was put back in read/write mode yesterday (Tuesday 15th)
+
 
<!-- ***********End Resolved Disk Server Issues*********** ----->
 
<!-- ***********End Resolved Disk Server Issues*********** ----->
 
<!-- ***************************************************** ----->
 
<!-- ***************************************************** ----->
Line 36: Line 33:
 
* There is a problem seen by LHCb of a low but persistent rate of failure when copying the results of batch jobs to Castor. There is also a further problem that sometimes occurs when these (failed) writes are attempted to storage at other sites. A recent modification has improved, but not completed fixed this.
 
* There is a problem seen by LHCb of a low but persistent rate of failure when copying the results of batch jobs to Castor. There is also a further problem that sometimes occurs when these (failed) writes are attempted to storage at other sites. A recent modification has improved, but not completed fixed this.
 
* The intermittent, low-level, load-related packet loss seen over external connections is still being tracked. Likewise we have been working to understand some remaining low level of packet loss seen within a part of our Tier1 network.
 
* The intermittent, low-level, load-related packet loss seen over external connections is still being tracked. Likewise we have been working to understand some remaining low level of packet loss seen within a part of our Tier1 network.
 +
* The draining of Castor disk servers is very slow. We need to drain a few old servers to provide spares - this being part of the deployment plan and server lifecycle. This does not yet impact services but is being followed up.
 
<!-- ***********End Current operational status and issues*********** ----->
 
<!-- ***********End Current operational status and issues*********** ----->
 
<!-- *************************************************************** ----->
 
<!-- *************************************************************** ----->
Line 46: Line 44:
 
| style="background-color: #f8d6a9; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Ongoing Disk Server Issues
 
| style="background-color: #f8d6a9; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Ongoing Disk Server Issues
 
|}
 
|}
−
* GDSS620 (GenTape - D0T1) Reported a read-only file system yesterday (Tuesday) morning and was taken out of production. Two T2K files that were not yet copied to tape were corrupt and have been reported as lost. Investigations ongoing.
+
* GDSS620 (GenTape - D0T1) Reported a read-only file system on the 15th March and was taken out of production. Two T2K files that were not yet copied to tape were corrupt and have been reported as lost. Work still ongoing.
 
<!-- ***************End Ongoing Disk Server Issues**************** ----->
 
<!-- ***************End Ongoing Disk Server Issues**************** ----->
 
<!-- ************************************************************* ----->
 
<!-- ************************************************************* ----->
Line 57: Line 55:
 
| style="background-color: #b7f1ce; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Notable Changes made since the last meeting.
 
| style="background-color: #b7f1ce; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Notable Changes made since the last meeting.
 
|}
 
|}
−
* The planned network intervention on Monday (14th) for a small network reconfiguration and firmware update in a pair of network switches was successful.
+
* Firmware updates were carried out on Monday (21st) on the RAID cards in the "Clustervision '11" batch of worker nodes that are in D1T0 service classes.
−
* Patching for security updates ongoing.
+
* Patching and rebooting for security updates.
 +
* A load balancer has been brought partly into service in front of the Test FTS3 instance.
 
<!-- *************End Notable Changes made this last week************** ----->
 
<!-- *************End Notable Changes made this last week************** ----->
 
<!-- ****************************************************************** ----->
 
<!-- ****************************************************************** ----->
Line 69: Line 68:
 
| style="background-color: #d8e8ff; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Declared in the GOC DB
 
| style="background-color: #d8e8ff; border-bottom: 1px solid silver; text-align: center; font-size: 1em; font-weight: bold; margin-top: 0; margin-bottom: 0; padding-top: 0.1em; padding-bottom: 0.1em;" | Declared in the GOC DB
 
|}
 
|}
−
{| border=1 align=center
+
None
−
|- bgcolor="#7c8aaf"
+
−
! Service
+
−
! Scheduled?
+
−
! Outage/At Risk
+
−
! Start
+
−
! End
+
−
! Duration
+
−
! Reason
+
−
|-
+
−
| All Castor (All SRM endpoints)
+
−
| SCHEDULED
+
−
| OUTAGE
+
−
| 17/03/2016 09:30
+
−
| 17/03/2016 15:00
+
−
| 5 hours and 30 minutes
+
−
| Downtime on RAL Storage for security updates
+
−
|}
+
 
<!-- **********************End GOC DB Entries************************** ----->
 
<!-- **********************End GOC DB Entries************************** ----->
 
<!-- ****************************************************************** ----->
 
<!-- ****************************************************************** ----->
Line 100: Line 82:
 
|}
 
|}
 
<!-- ******* still to be formally scheduled and/or announced ******* ----->
 
<!-- ******* still to be formally scheduled and/or announced ******* ----->
−
* At Risk on the whole Tier1 next Monday, 14th March, 11:00 - 16:00 while a network reconfiguration is made followed by the firmware update in a pair of network switches. ('''Note:''' The date of this work was updated after the meeting.)
 
 
* The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful resolution of that problem and completion of testing before scheduling.
 
* The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful resolution of that problem and completion of testing before scheduling.
 
* Decommissioning of "GEN Scratch" storage in Castor.
 
* Decommissioning of "GEN Scratch" storage in Castor.
Line 136: Line 117:
 
! Reason
 
! Reason
 
|-
 
|-
−
| Whole site
+
| All Castor
 
| SCHEDULED
 
| SCHEDULED
−
| WARNING
+
| OUTAGE
−
| 14/03/2016 11:00
+
| 17/03/2016 09:30
−
| 14/03/2016 16:00
+
| 17/03/2016 13:38
−
| 5 hours
+
| 4 hours and 8 minutes
−
|Warning on Site during a network test and firmware upgrade on a pair of network switches.
+
| Downtime on RAL Storage for security updates
 
|}
 
|}
 
<!-- **********************End GOC DB Entries************************** ----->
 
<!-- **********************End GOC DB Entries************************** ----->
Line 158: Line 139:
 
|-style="background:#b7f1ce"
 
|-style="background:#b7f1ce"
 
! GGUS ID !! Level !! Urgency !! State !! Creation !! Last Update !! VO !! Subject
 
! GGUS ID !! Level !! Urgency !! State !! Creation !! Last Update !! VO !! Subject
 +
|-
 +
| 120350
 +
| Green
 +
| Less Urgent
 +
| In Progress
 +
| 2016-03-22
 +
| 2016-03-22
 +
| LSST
 +
| Enable LSST at RAL
 +
|-
 +
| 120307
 +
| Green
 +
| Less Urgent
 +
| Waiting Reply
 +
| 2016-03-21
 +
| 2016-03-21
 +
| Atlas
 +
| Can't find FTS log.
 
|-
 
|-
 
| 119841
 
| 119841
−
| Amber
+
| Green
 
| Less Urgent
 
| Less Urgent
 
| In Progress
 
| In Progress
 
| 2016-03-01
 
| 2016-03-01
−
| 2016-03-08
+
| 2016-03-22
 
| LHCb
 
| LHCb
 
| HTTP support for lcgcadm04.gridpp.rl.ac.uk
 
| HTTP support for lcgcadm04.gridpp.rl.ac.uk
Line 193: Line 192:
 
! Day !! OPS !! Alice !! Atlas !! CMS !! LHCb !! Atlas HC !! CMS HC !! Comment
 
! Day !! OPS !! Alice !! Atlas !! CMS !! LHCb !! Atlas HC !! CMS HC !! Comment
 
|-
 
|-
−
| 16/03/16 || 100 || 100 || 100 || 100 || 100 || 98 || 100 ||
+
| 16/03/16 || 100 || 100 || 100 || 100 || 100 || 100 || 100 ||
 
|-
 
|-
 
| 17/03/16 || style="background-color: lightgrey;" | 82.3 || 100 || style="background-color: lightgrey;" | 77 || style="background-color: lightgrey;" | 83 || style="background-color: lightgrey;" | 83 || 100 || 92 || Mainly Castor outage for security update/reboot.  
 
| 17/03/16 || style="background-color: lightgrey;" | 82.3 || 100 || style="background-color: lightgrey;" | 77 || style="background-color: lightgrey;" | 83 || style="background-color: lightgrey;" | 83 || 100 || 92 || Mainly Castor outage for security update/reboot.  
Line 199: Line 198:
 
| 18/03/16 || 100 || 100 || 100 || style="background-color: lightgrey;" | 97 || 100 || 100 || 100 || ARC CE jobs held.
 
| 18/03/16 || 100 || 100 || 100 || style="background-color: lightgrey;" | 97 || 100 || 100 || 100 || ARC CE jobs held.
 
|-
 
|-
−
| 19/03/16 || 100 || 100 || 100 || 100 || 100 || 100 || 100 ||
+
| 19/03/16 || 100 || 100 || 100 || 100 || 100 || 98 || 100 ||
 
|-
 
|-
−
| 20/03/16 || 100 || 100 || 100 || style="background-color: lightgrey;" | 58 || 100 || 100 || N/A || Problems running CE tests across CMS sites.
+
| 20/03/16 || 100 || 100 || 100 || style="background-color: lightgrey;" | 58 || 100 || 98 || N/A || Problems running CE tests across CMS sites.
 
|-
 
|-
−
| 21/03/16 || 100 || 100 || 100 || 100 || 100 || 100 || 100 ||
+
| 21/03/16 || 100 || 100 || style="background-color: lightgrey;" | 99 || 100 || 100 || 93 || 100 || Single SRM test failure on GET (User timeout).
 
|-
 
|-
 
| 22/03/16 || 100 || 100 || 100 || 100 || 100 || 100 || 100 ||
 
| 22/03/16 || 100 || 100 || 100 || 100 || 100 || 100 || 100 ||

Latest revision as of 21:43, 22 March 2016

RAL Tier1 Operations Report for 23rd March 2016

Review of Issues during the week 16th to 23rd March 2016.
  • Security updates have been rolled out. There an outage of Castor last Thursday during which all the component servers were successfully updated and rebooted within the announced downtime. During this time job starts were blocked on the batch farm. Various batch farm nodes (Condor masters etc) were also rebooted at this time and there was a confusion that led to batch jobs not being re-allowed to start until later that evening.
Resolved Disk Server Issues
  • None
Current operational status and issues
  • There is a problem seen by LHCb of a low but persistent rate of failure when copying the results of batch jobs to Castor. There is also a further problem that sometimes occurs when these (failed) writes are attempted to storage at other sites. A recent modification has improved, but not completed fixed this.
  • The intermittent, low-level, load-related packet loss seen over external connections is still being tracked. Likewise we have been working to understand some remaining low level of packet loss seen within a part of our Tier1 network.
  • The draining of Castor disk servers is very slow. We need to drain a few old servers to provide spares - this being part of the deployment plan and server lifecycle. This does not yet impact services but is being followed up.
Ongoing Disk Server Issues
  • GDSS620 (GenTape - D0T1) Reported a read-only file system on the 15th March and was taken out of production. Two T2K files that were not yet copied to tape were corrupt and have been reported as lost. Work still ongoing.
Notable Changes made since the last meeting.
  • Firmware updates were carried out on Monday (21st) on the RAID cards in the "Clustervision '11" batch of worker nodes that are in D1T0 service classes.
  • Patching and rebooting for security updates.
  • A load balancer has been brought partly into service in front of the Test FTS3 instance.
Declared in the GOC DB

None

Advanced warning for other interventions
The following items are being discussed and are still to be formally scheduled and announced.
  • The Castor 2.1.15 update is pending. Testing has shown a database related performance issue which is being followed up. We await successful resolution of that problem and completion of testing before scheduling.
  • Decommissioning of "GEN Scratch" storage in Castor.

Listing by category:

  • Databases:
    • Switch LFC/3D to new Database Infrastructure.
  • Castor:
    • Update SRMs to new version (includes updating to SL6).
    • Update to Castor version 2.1.15.
    • Migration of data from T10KC to T10KD tapes (affects Atlas & LHCb data).
  • Networking:
    • Replace the UKLight Router. Then upgrade the 'bypass' link to the RAL border routers to 2*10Gbit.
  • Fabric
    • Firmware updates on remaining EMC disk arrays (Castor, LFC)
  • Grid Services
    • A Load Balancer (HAProxy) will be used in front of the FTS service.
Entries in GOC DB starting since the last report.
Service Scheduled? Outage/At Risk Start End Duration Reason
All Castor SCHEDULED OUTAGE 17/03/2016 09:30 17/03/2016 13:38 4 hours and 8 minutes Downtime on RAL Storage for security updates
Open GGUS Tickets (Snapshot during morning of meeting)
GGUS ID Level Urgency State Creation Last Update VO Subject
120350 Green Less Urgent In Progress 2016-03-22 2016-03-22 LSST Enable LSST at RAL
120307 Green Less Urgent Waiting Reply 2016-03-21 2016-03-21 Atlas Can't find FTS log.
119841 Green Less Urgent In Progress 2016-03-01 2016-03-22 LHCb HTTP support for lcgcadm04.gridpp.rl.ac.uk
117683 Green Less Urgent In Progress 2015-11-18 2016-02-17 CASTOR at RAL not publishing GLUE 2
Availability Report

Key: Atlas HC = Atlas HammerCloud (Queue ANALY_RAL_SL6, Template 508); CMS HC = CMS HammerCloud

Day OPS Alice Atlas CMS LHCb Atlas HC CMS HC Comment
16/03/16 100 100 100 100 100 100 100
17/03/16 82.3 100 77 83 83 100 92 Mainly Castor outage for security update/reboot.
18/03/16 100 100 100 97 100 100 100 ARC CE jobs held.
19/03/16 100 100 100 100 100 98 100
20/03/16 100 100 100 58 100 98 N/A Problems running CE tests across CMS sites.
21/03/16 100 100 99 100 100 93 100 Single SRM test failure on GET (User timeout).
22/03/16 100 100 100 100 100 100 100
Retrieved from "https://www.gridpp.ac.uk/w/index.php?title=Tier1_Operations_Report_2016-03-23&oldid=11094"