Difference between revisions of "Tier1 Operations Report 2017-10-25"

From GridPP Wiki
Jump to: navigation, search
()
()
 
(5 intermediate revisions by 2 users not shown)
Line 10: Line 10:
 
| 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 18th to 25th October 2017.
 
| 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 18th to 25th October 2017.
 
|}
 
|}
* Nothing significant to report.
+
* On Tuesday (24th Oct) CMS were switched over to using xrootd.echo.stfc.ac.uk. This means that CMS jobs used xrootd.echo.stfc.ac.uk as the primary means of accessing local data via xrootd. However, this change was then reverted that evening as some errors were seen and are currently being worked through. See (GGUS#131299 below).
 
<!-- ***********End Review of Issues during last week*********** ----->
 
<!-- ***********End Review of Issues during last week*********** ----->
 
<!-- *********************************************************** ----->
 
<!-- *********************************************************** ----->
Line 64: Line 64:
 
| 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.
 
|}
 
|}
* Switched CMS over to using xrootd.echo.stfc.ac.uk. This means that CMS jobs will use xrootd.echo.stfc.ac.uk as the primary means of accessing local data via xrootd.
 
 
* Re-distribution of data in Echo onto the 2015 capacity hardware is ongoing.
 
* Re-distribution of data in Echo onto the 2015 capacity hardware is ongoing.
 
<!-- *************End Notable Changes made this last week************** ----->
 
<!-- *************End Notable Changes made this last week************** ----->
Line 260: Line 259:
 
| 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;" | Notes from 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;" | Notes from Meeting.
 
|}
 
|}
* None yet
+
* (Note added after): Work is going on both:
 +
** On a new distributed database (a Galera MariaDB cluster) for FTS3
 +
** Investigating dual stack IPv4/IPv6 for one of the existing FTS3 instances

Latest revision as of 07:31, 26 October 2017

RAL Tier1 Operations Report for 25th October 2017

Review of Issues during the week 18th to 25th October 2017.
  • On Tuesday (24th Oct) CMS were switched over to using xrootd.echo.stfc.ac.uk. This means that CMS jobs used xrootd.echo.stfc.ac.uk as the primary means of accessing local data via xrootd. However, this change was then reverted that evening as some errors were seen and are currently being worked through. See (GGUS#131299 below).
Resolved Disk Server Issues
  • None
Current operational status and issues
  • There is a problem on the site firewall which is causing problems for some specific data flows. Discussions have been taking place with the vendor. This is having an effect on our data that flows through the firewall (such as to/from worker nodes).
Ongoing Disk Server Issues
  • None
Limits on concurrent batch system jobs.
  • CMS Multicore 550
Notable Changes made since the last meeting.
  • Re-distribution of data in Echo onto the 2015 capacity hardware is ongoing.
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.

Pending - but not yet formally announced:

  • Re-distribute the data in Echo onto the 2015 capacity hardware. (Ongoing)

Listing by category:

  • Castor:
    • Update systems (initially tape servers) to use SL7 and configured by Quattor/Aquilon.
    • Move to generic Castor headnodes.
  • Echo:
    • Re-distribute the data in Echo onto the remaining 2015 capacity hardware.
  • Networking
    • Extend the number of services on the production network with IPv6 dual stack. (Done for Perfsonar, all squids and the CVMFS Stratum-1 servers).
  • Services
    • The Production and "Test" (Atlas) FTS3 services will be merged and will make use of a resilient distributed database.
Entries in GOC DB starting since the last report.
  • None
Open GGUS Tickets (Snapshot during morning of meeting)
GGUS ID Level Urgency State Creation Last Update VO Subject
131299 Green Urgent In Progress 2017-10-24 2017-10-24 CMS T1_UK_RAL HammerCloud failures
131213 Green Urgent Waiting for Reply 2017-10-19 2017-10-23 CMS Issues with fallback requests
130949 Green Urgent In Progress 2017-10-06 2017-10-23 CMS Transfers failing to T1_UK_RAL_Disk
130207 Amber Urgent On Hold 2017-08-24 2017-10-11 MICE Timeouts when copying MICE reco data to CASTOR
127597 Red Urgent On Hold 2017-04-07 2017-10-05 CMS Check networking and xrootd RAL-CERN performance
124876 Red Less Urgent On Hold 2016-11-07 2017-01-01 OPS [Rod Dashboard] Issue detected : hr.srce.GridFTP-Transfer-ops@gridftp.echo.stfc.ac.uk
117683 Red Less Urgent On Hold 2015-11-18 2017-07-06 CASTOR at RAL not publishing GLUE 2.
Availability Report
Day OPS Alice Atlas CMS LHCb Atlas Echo Comment
18/10/17 100 100 98 98 100 100 Atlas: Single SRM test failure: "error 500 Command failed."; CMS: Two SRM test failures on PUT ([SRM_FAILURE] Unable to issue PrepareToPut request to Castor).
19/10/17 100 100 100 100 100 100
20/10/17 100 100 100 100 100 100
21/10/17 100 100 100 96 100 100 Three SRM test failures on PUT ([SRM_FAILURE] Unable to issue PrepareToPut request to Castor).
22/10/17 100 100 100 100 100 100
23/10/17 100 100 100 100 100 100
24/10/17 100 100 100 99 100 100 Single SRM test failure on PUT ([SRM_FAILURE] Unable to issue PrepareToPut request to Castor).
Hammercloud Test Report

Key: Atlas HC = Atlas HammerCloud (Queue ANALY_RAL_SL6, Template 845); Atlas HC Echo = Atlas Echo (Template 841);CMS HC = CMS HammerCloud

Day Atlas HC Atlas HC Echo CMS HC Comment
18/10/17 98 100 99
19/10/17 94 100 97
20/10/17 100 99 83
21/10/17 100 100 98
22/10/17 98 100 97
23/10/17 99 100 98
24/10/17 100 N/A 47 CMS - Problems arising following switchover to use Echo.
Notes from Meeting.
  • (Note added after): Work is going on both:
    • On a new distributed database (a Galera MariaDB cluster) for FTS3
    • Investigating dual stack IPv4/IPv6 for one of the existing FTS3 instances