Week of 171030

WLCG Operations Call details

  • At CERN the meeting room is 513 R-068.

  • For remote participation we use the Vidyo system. Instructions can be found here.

General Information

  • The purpose of the meeting is:
    • to report significant operational issues (i.e. issues which can or did degrade experiment or site operations) which are ongoing or were resolved after the previous meeting;
    • to announce or schedule interventions at Tier-1 sites;
    • to inform about recent or upcoming changes in the experiment activities or systems having a visible impact on sites;
    • to provide important news about the middleware;
    • to communicate any other information considered interesting for WLCG operations.
  • The meeting should run from 15:00 until 15:20, exceptionally to 15:30.
  • The SCOD rota for the next few weeks is at ScodRota
  • General information about the WLCG Service can be accessed from the Operations Web
  • Whenever a particular topic needs to be discussed at the daily meeting requiring information from site or experiments, it is highly recommended to announce it by email to wlcg-operations@cernSPAMNOTNOSPAMPLEASE.ch to make sure that the relevant parties have the time to collect the required information or invite the right people at the meeting.

Tier-1 downtimes

Experiments may experience problems if two or more of their Tier-1 sites are inaccessible at the same time. Therefore Tier-1 sites should do their best to avoid scheduling a downtime classified as "outage" in a time slot overlapping with an "outage" downtime already declared by another Tier-1 site supporting the same VO(s). The following procedure is recommended:

  1. A Tier-1 should check the downtimes calendar to see if another Tier-1 has already an "outage" downtime in the desired time slot.
  2. If there is a conflict, another time slot should be chosen.
  3. In case stronger constraints cannot allow to choose another time slot, the Tier-1 will point out the existence of the conflict to the SCOD mailing list and at the next WLCG operations call, to discuss it with the representatives of the experiments involved and the other Tier-1.

As an additional precaution, the SCOD will check the downtimes calendar for Tier-1 "outage" downtime conflicts at least once during his/her shift, for the current and the following two weeks; in case a conflict is found, it will be discussed at the next operations call, or offline if at least one relevant experiment or site contact is absent.

Links to Tier-1 downtimes




  • local: Alberto (monitoring), Cedric (ATLAS), Enrico (storage), Gavin (computing), Jan (storage), Julia (WLCG), Maarten (SCOD + ALICE + GGUS), Marian (networks), Vincent (security), Vladimir (LHCb)
  • remote: Andrew (NLT1), John (RAL), Kyle (OSG), Marcelo (CNAF), Pepe (PIC), Sang-Un (KISTI), Tommaso (CMS), Vincenzo (EGI), Xin (BNL)

Experiments round table:

  • ATLAS reports ( raw view) -
    • Activities:
      • Normal activity
      • Continuously >250k of running slots of jobs
      • Still huge number of jobs to process at the T0
      • We foresee a derivation campaign on data in 2-3 weeks
    • Problems
      • Backlog moving files from EOS to Castor. Being investigated
        • Jan: the matter is being investigated; it does not seem to be on the CASTOR side;
          the GridFTP doors may be overloaded at times, and therefore we recommend
          that Xrootd be used instead for "internal" transfers between CASTOR and EOS
      • Low transfer efficiency between one T2 and Russian T1 : GGUS:131375

  • CMS reports ( raw view) -
    • all resources under heavy use.
    • Tier-0 suffering from backlog. 40k jobs "late" with respect to first possible start. CMS started to overflow to the CERN T2 resources; currently not much more than a test, can ramp up if needed.
    • Tier-0 backlog mostly to KIT; disk + tape O (1 PB). Changed after XeXe run decreased the slope, but did not invert the sign
    • disk storage equally suffering, 3 Tier-1s over 90%: JINR, CNAF, KIT
    • overall "unmovable" disk is climbing fast towards 80% of the total. A disk cleaning will be needed in short notice

  • ALICE -
    • High activity on average
    • CERN: more EOS crashes Fri evening (OTG:0040600).
      • A storm of activity appears to have triggered a bug in XRootD.
      • A mitigation was applied while the matter is not understood.

  • LHCb reports ( raw view) -
    • Activity
      • Monte Carlo simulation, data processing and user analysis
      • pre-staging progressing well
    • Site Issues
      • T0:
        • NTR
      • T1:
        • CNAF Alarm ticket (GGUS:131366) solved
        • Vladimir: there also appears to have been a temporary overload due to staging from tape to disk at RRC-KI

Sites / Services round table:

  • ASGC:
  • BNL: NTR
  • CNAF:
    • Xrootd problem for CMS still under investigation. (GGUS:131385)
    • the issue from the LHCb alarm ticket was caused by a missing firewall rule
  • EGI: NTR
  • FNAL:
  • IN2P3:
  • JINR: Nothing to report
  • KIT:
  • NDGF: Oslo will upgrade pools Wed Nov. 1 14-15 CET. Short outages expected during reboot. Some Atlas data affected. (Christian,Can't attend. In another meeting.)
  • NL-T1: NTR
  • NRC-KI:
  • OSG: NTR
  • PIC:
    • on Nov 7 we will have a downtime to upgrade dCache, reboot WN for kernel patches
      and do a firmware update in the tape library
  • RAL: NTR
  • TRIUMF: Apology for that I could not join. For the issue reported in GGUS ticket, 131004, it should be caused by that the tape writing pools were getting full, thus there were not enough available slots for data transferred to tape. Our storage expert did some changes to mitigate this problem last Monday, this situation should be improved.

  • CERN computing services:
    • SIR for LHCb VO box incident: ServiceIncidentCloud20171017. TL;DR possible hot-spot, being investigated.
    • Have noted no ill effects from last week's CREAM retirement.
  • CERN storage services: NTA
  • CERN databases:
  • Monitoring:
    • NTR
  • MW Officer:
  • Networks:
    • GGUS:128489 - RO-02-NIPNE to multiple sites - MTU step-down suspected in combination with some load balancing (MPLS, LAG)
  • Security: EGI SVG Alert: up to critical kernel vulnerability:
    • Only on RHEL7 derivatives, if unprivileged user namespaces are allowed (namespace.unpriv_enable=1 in kernel and user.max_user_namespaces sysctl non zero)
    • Singularity "non-SUID" deployment would be affected


Edit | Attach | Watch | Print version | History: r19 < r18 < r17 < r16 < r15 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r19 - 2017-10-30 - GavinMcCance
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 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