Week of 160711

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

ALICE ATLAS CMS LHCB
  BNL FNAL  

Monday

Attendance:

  • local:
  • remote:

Experiments round table:

  • ATLAS reports (raw view) -
    • Activities:
      • T0 spillover ran at BNL on the biggest run (38 hours)
    • Problems:
      • Problems affecting EOS :
        • Namespace server crashed, then bad space reported after
        • Bad throughput rate from EOS to T1_TAPE for some files due to switches
      • Some T1s getting full. Deletion campaign of derived data is being done + rebalancing of data

  • CMS reports (raw view) -
    • (Daniele at the CMS MB today - will try to connect, depending on where we are with the agenda)
    • Excellent LHC performance continues to keep the T0 busy for CMS
      • quite some debugging and optimization has been done at EOS, FTS, PhEDEx levels. Reference ticket is GGUS:122415
      • T0-outbound traffic more healthy, plus thanks to internal CMS re-prioritizations we are increasing our ability to send out of T0 the most urgent data tiers
      • we need to work on higher transfer rates though, we are confident we can achieve more (e.g. on per-file transfer rates) with an ad-hoc task force in synergy with EOS/FTS friends

  • ALICE -
    • NTR

  • LHCb reports (raw view) -
    • Activity
      • Monte Carlo simulation, data reconstruction/stripping and user jobs on the Grid
    • Site Issues
      • T0:
      • T1: NTR

Sites / Services round table:

  • ASGC:
  • BNL:
  • CNAF: On Wednesday morning (13/07) we have planned an intervention on LHCb storage (scheduled as at risk). ATLAS reported a problem which may be related to network issues (GGUS:122737), under investigation.
  • FNAL:
  • GridPP:
  • IN2P3: NTR
  • JINR:
  • KISTI:
  • KIT:
  • NDGF: NTR
  • NL-T1:
  • NRC-KI:
  • OSG:
  • PIC: NTR
  • RAL:
  • TRIUMF: Main site power transformation was problematic, as a prevention all services and equipment were shut down around 10:00 (UTC time) today, will bring all services back when the problem is solved.

AOB:

Edit | Attach | Watch | Print version | History: r16 | r14 < r13 < r12 < r11 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r12 - 2016-07-11 - JosepFlix
 
    • 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-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback