1 / 1

FAX Deployment Status

FAX Deployment Status. Working with several T1s to deploy FAX service PIC will rejoin FAX, has to stay at dCache 2.2, but want to use dCache xrootd door directly (instead of using a proxy ) Working with IN2P3-CC and TRIUMF, no update yet S tress tests

errol
Download Presentation

FAX Deployment Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FAX Deployment Status • Working with several T1s to deploy FAX service • PIC will rejoin FAX, has to stay at dCache 2.2, but want to use dCachexrootd door directly (instead of using a proxy) • Working with IN2P3-CC and TRIUMF, no update yet • Stress tests • Repeat FTS transfers using FAX, no update yet • Stress FAX using US Cloud analysis jobs • Ask US global redirection to find all input files from all US cloud analysis jobs (no update from Ilija yet) • Preliminary results from 21,22,23 of March: • 50K – 100K input files daily, FAX can easily handle this load • Daily failure rates are between 0.5-1%. • Surprise (?) finding: some US sites still have significant number of files in non-RUCIO path. • Other updates • dCache (2.6) Xrootd door is not SHA2 ready • In V16 of localSetupFAX, renamed all commands from “FAX-*” to “fax-*” FAX status - Wei, 2014-03-24

More Related