Week of 170710

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:
      • stable production dominated by simulation + derivation (many small output files stressed some storages)
      • ATLAS P1 to EOS to CASTOR data throughput test ( details)
    • Issues
      • CERN-PROD_DATADISK ran out of inodes (already week ago on Saturday 1.7.) - available inodes was added in monitoring
      • slow data deletion at IN2P3 -CC were caused by IPv6 broken configuration (ACL) - 2+ minutes spent by rucio to create session for file deletion (IPv6 to IPv4 connection timeout)
      • no data in ATLAS DDM Dashboard for file transfer monitoring from Wednesday evening to Friday noon caused by OpenSSL assertion while sending rucio hermes messages to ActiveMQ
      • Taiwan-LCG2 IPv6 connection issues (file transfer failures) to T1 centers in ES & FR cloud seem to be solved GGUS:129371
    • Other
      • WT2 SLAC is no longer T2 (as of October 2016) - we have to replicate primary data to the other sites

  • CMS reports ( raw view) -
    • Virtual report as I (and most others in CMS Computing) will be traveling to our Face to Face meeting in the USA.
    • Please send mails or (better) open GGUS if you have any question for CMS
    • NTR on operation, quiet week and request for resources from the physics community still on the low side

  • ALICE -
    • Very high activity on average
    • CERN:
      • ~10k jobs lost Sun ~21:30 due to ce508 crash
      • ~7k jobs lost Mon ~04:00 due to ce505 crash

  • LHCb reports ( raw view) -
    • Activity
      • User analysis and Monte Carlo simulation
    • Site Issues
      • T0: Jobs hold at HTCondor CEs CERN-PROD (GGUS:129147)
      • T1:
        • NTR

Sites / Services round table:

  • ASGC:
  • BNL: NTR
  • CNAF:
  • EGI:
  • FNAL:
  • IN2P3:
  • JINR:
    • Configuration of IPv6 on SEs completed. WNs also configured for dual stack.
    • This week we will try to improve the reliability of the main link to Moscow.
    • IPv6 routing from JINR on LHCOPN need some configuration on the other sides, our network staff is working on a problem.
  • KISTI:
  • KIT:
  • NDGF:
  • NL-T1:
    • A downtime starting at 15:00 UTC this afternoon until 15:00 UTC tomorrow afternoon at SURFsara. Hardware replacement at the tape back-end. During this downtime it will not be possible to read files from tape.
  • NRC-KI:
  • OSG:
  • PIC: NTR
  • RAL: NTR
  • TRIUMF:

  • CERN computing services:
    • 5/6 July: DNS problem on our hypervisors caused 950 nodes (across HTCondor/LSF/AtlasT0) to get bad resolv.conf - most running jobs on those nodes were lost. OTG:0038529
  • CERN storage services: All CASTOR updates went ahead OK.
  • CERN databases:
  • GGUS:
  • Monitoring:
    • Draft availability reports for June distributed. One re-computation from ATLAS done.
    • Final report generated this Friday.
  • MW Officer: As discussed during the WLCG ops coord last week, we are creating 2 mailing lists for discussions around ARC-CE and HTCondor in WLCG. We will broadcast them as soon as they are ready.
  • Networks:
  • Security:

AOB:

Edit | Attach | Watch | Print version | History: r15 < r14 < r13 < r12 < r11 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r12 - 2017-07-10 - unknown
 
    • 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