Known storage outstanding issues

  1. dCache: Random failures (observed at Lyon) in accessing files via gsidcap. The error is as follows:
    06/09 14:39:46 Cell(DCap-gsi-ccdcacsn007@gsidcap-ccdcacsn007Domain) : acceptThread (Thread[ClinetThread-/134.158.240.23:56002,5,DCap-gsi-ccdcacsn007-threads]): creating protocol engine
    Failure unspecified at GSS-API level. Caused by COM.claymoresystems.ptls.SSLThrewAlertException: Handshake failure
            at COM.claymoresystems.ptls.SSLConn.alert(SSLConn.java:235)
    
  2. dCache: slowness with bulk deletion. TRIUMF overcame this with a special setup:
    At TRIUMF we run the PNFS service and SRM service on two separate higf-end machines. Each machine has its own local Postgres DB.
    Their tuning uses 512MB of shared buffers and other tweaked parameters.
    Another important factor is that we use dedicated 15K rpm SAS disks for the DB access exclusively. All system logs and dCache services logs are written to a separate disk.
    
  3. dCache or LHCb env: Invalid XML character:
    2008-06-09 13:56:07 UTC Wrapper_83309/InputDataByProtocol DEBUG: {'OK': True, 'Value': {'Successful': {}, 'Failed': {'srm://ccsrm.in2p3.fr/pnfs/in2p3.fr/data/lhcb/data/CCRC08/RAW/LHCb/CCRC/23406/023406_0000041562.raw': ' SRM2Storage.__gfal_turlsfromsurls: Failed to perform gfal_turlsfromsurls:httpg://ccsrm.in2p3.fr:8443/srm/managerv2: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x10) was found in the element content of the document.'}}}
    2008-06-09 13:56:07 UTC Wrapper_83309/InputDataByProtocol  WARN: Found 1 problematic TURL(s) for job 83309
    2008-06-09 13:56:07 UTC Wrapper_83309/InputDataByProtocol  INFO: Failed to obtain TURL for srm://ccsrm.in2p3.fr/pnfs/in2p3.fr/data/lhcb/data/CCRC08/RAW/LHCb/CCRC/23406/023406_0000041562.raw
    2008-06-09 13:56:07 UTC Wrapper_83309/InputDataByProtocol  INFO:  Problem:  SRM2Storage.__gfal_turlsfromsurls: Failed to perform gfal_turlsfromsurls:httpg://ccsrm.in2p3.fr:8443/srm/managerv2: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x10) was found in the element content of the document.
    

-- FlaviaDonno - 16 Jun 2008

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2008-06-16 - FlaviaDonno
 
    • 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