Week of 190701

WLCG Operations Call details

  • 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 Geneva time 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 Portal
  • Whenever a particular topic needs to be discussed at the operations meeting requiring information from sites or experiments, it is highly recommended to announce it by email to wlcg-scod@cernSPAMNOTNOSPAMPLEASE.ch to allow the SCOD to make sure that the relevant parties have the time to collect the required information, or invite the right people at the meeting.

Best practices for scheduled downtimes

Monday

Attendance:

  • local: Maarten (ALICE), Petr (ATLAS), Paul (Storage), Borja (Monitoring), Vincent (Security), Gavin (Compute), Miroslav (Chair, DB)
  • remote: Andrew (NIKHEF), Brian (RAL), Dmytro (NDGF), David (IN2P3), Dave (FNAL), Sang-Un (KISTI), Jose (PIC), Chris (LHCb)

Experiments round table:

  • ATLAS reports ( raw view) -
    • quite week while all experts at one place ( ATLAS Software & Computing Week #62)
    • production transfers using WebDAV protocol
      • caused by an algorithm used within Rucio to select protocol for multisource replica transfer
      • impact especially on dCache sites where even small fraction of WebDAV transfers seems to cause troubles
      • reported high number of errors in log files (FTS / gfal try push / pull / stream) that filled partition and made dCache inoperable
      • plans to improve rucio replica protocol selection, but WebDAV transfers still possible with sites that doesn't support GridFTP
    • AGLT2 - 80Gb transfer rate to the site and close to saturation (queued job outputs)

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • Activity:
      • MC, user jobs and re-stripping of 2018 data.
    • Issues:
      • Staging issues at CERN, Gridka, Sara
      • More generally: It would be nice to have minimal answers to the ticket, even outside the 9:00-17:00 Mon-Friday time period. We can always convert tickets to alarm, it's an overkill most of the time, but if there are no answers for 2 days, that's our only option.

Issues:

Sites / Services round table:

  • ASGC: NC
  • BNL: NC
  • CNAF: NC
  • EGI: NC
  • FNAL: NTR
  • IN2P3: NTR
  • JINR: The WAN problem of data transfer (to mainly US sites) is under investigation.
  • KISTI: NTR
  • KIT: NC
  • NDGF: NTR
  • NL-T1: NTR
  • NRC-KI: NC
  • OSG: NC
  • PIC:
    • Chair note: Heat wave problems required temporary shutdown of some compute systems to maintain cooling. Another heat wave is expected.
  • RAL: NTR
  • TRIUMF: NTR

  • CERN computing services: NTR
  • CERN storage services: LHCb storage instabilities are being followed up.
  • CERN databases: NTR
  • GGUS: NTR
  • Monitoring: NTR
  • MW Officer: NTR
  • Networks: NTR
  • Security: NTR

AOB:

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r13 - 2019-07-01 - MaartenLitmaath
 
    • 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-2024 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