Week of 171016

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: Andrea (MW Officer + data management), Carolina (computing), Ignacio (databases), Ivan (ATLAS), Jan (storage), Julia (WLCG), Maarten (SCOD + ALICE), Roberto (storage)
  • remote: Andrew (NLT1), Chi Hsun (ASGC), Christoph (CMS), David B (IN2P3), David M (FNAL), Di (TRIUMF), Dimitri (KIT), Dmytro (NDGF), Elena (CNAF), John (RAL), Kyle (OSG), Sang-Un (KISTI), Stefan (LHCb), Vincent (security), Vincenzo (EGI), Xin (BNL)

Experiments round table:

  • ATLAS reports ( raw view) -
    • Stable Operation ~ 250k cores
    • No major site issues
    • We have managed to fill CERN OS ATLAS quota. Deletion was implemented.

  • CMS reports ( raw view) -
    • High overall CPU utilization: 235k cores in total (~195k for production + 40k for analysis)
    • XeXe run
      • Went o.k. form the computing side
      • PromptRECO almost finished (supposed to start 48h after datataking)
    • Datatransfer backlog from CERN to T1s
      • Mainly to CNAF and KIT
      • Will subscribe less data to these two sites for now ongoing pp run

  • ALICE -
    • Low to high activity on average
      • Low activity due to CERN resources draining for kernel security patch
    • CERN: follow-up of CASTOR instabilities, mainly due to overload.
      • At lower levels than in the past due to lower gateway capacity.
      • The number of concurrent reco jobs has been capped to 10k for now.
      • The CASTOR team will look into more gateways.

  • LHCb reports ( raw view) -
    • Activity
      • Monte Carlo simulation, data processing and user analysis
      • pre-staging of 2015 data for reprocessing progressing well, ~ 1/3 of data on disk buffers
    • Site Issues
      • T1:
        • INFN-T1 tape buffer running full, fixed by site admins
        • RAL disk server down with effects on production workflows
    • Aob
      • Request grid wide deployment of latest HepOSlibs meta-rpm, including deployment of git client.
        • Andrea: we will follow up

Sites / Services round table:

  • ASGC: NTR
  • BNL: FTS stopped updating transfer status due to disk space issue, recovered shortly
  • CNAF:
    • This week is planned the update to IPv6 for ATLAS, IPv6 for CMS is temporarily suspended for the critical situation of these weeks.
    • ATLAS timeline:
      • 17/10: xrootd
      • 18/10: gridftp
      • 24/10: storm
  • EGI: NTR
  • FNAL: NTR
  • IN2P3: NTR
  • JINR:
    • SAM srm errors after accidentally java update on dCache nodes, dcache restarted on affected service nodes.
    • errors on links to T1_RU_JINR_Disk from T1_ES_PIC_Disk. Investigating.
  • KISTI: NTR
  • KIT:
    • the dCache instance for LHCb will be upgraded on Oct 25, 07:00-16:00 UTC
  • NDGF: NTR
  • NL-T1: NTR
  • NRC-KI:
  • OSG: NTR
  • PIC:
  • RAL: NTR
  • TRIUMF: NTR

  • CERN computing services: NTR
  • CERN storage services: NTR
  • CERN databases: NTR
  • GGUS:
    • network maintenance might affect GGUS on Oct 19, 06:00-08:00 UTC (downtime entry)
  • Monitoring:
    • Report distributed and receiving corrections.
  • MW Officer: NTR
  • Networks:
  • Security: NTR

AOB:

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r13 - 2017-10-16 - 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback