Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Presenter

Notes

Vector Read updates to Echo

/wiki/spaces/GRIDPP/pages/188153912

Post-mortem to be held today

Next steps for WN deployment

Move to 5.5.4-2 (core) + 5.5.4-3 (xroot-ceph-buffered):

Status:

EBUSY in readV requests

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-64

Discussion on merging bufferedIO into master.
Also to discuss pushing changes to “upstream” (xrootd/xroot-ceph”

https://github.com/stfc/xrootd-ceph/pull/44

Needs testing for ‘correctness’

Also some discussion ongoing on xrootd “issues” on the xrootd-ceph sub-module:
https://github.com/xrootd/xrootd/pull/2008

SEGV investigations with -S multi-stream flags

CMSD status

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-41

Thomas, Jyothish (STFC,RAL,SC) identified that xrdcp via the redirector using root protocol requires two “/” in the LFN to work correctly.

  • Although this is the nominally correct path construction for xroot-based paths; existing transfers work with just a single-/ and may break from some corner-case person/VO.

Possible solution is Assuming we want a solution which maintains backwards compatibility, we may need to explicitly add:

Code Block
all.export cms #and other pool / # already existing line
# add in the lines
all.export cms
all.export store #special cms 'namespace' 
# and for other pools

What’s the impact? Do we need “/” export now. Should we consider the authdb file logic too ?
To understand exactly how the export / authdb / “// | /" finally interact ?

Transfers of 0-byte files

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-62

Observed Dune transfer failures using 0-byte files

...