XROOT prepare and Query:

• The attached document provided by Michael was extensively reviewed.
  • (Feedback has been provided to Michael after the meeting.) 
• Additional notes on EOS rate limiter:
  • The EOS rate limiter was designed for keeping away rogue users from the system. In the case of EOSCTA, it was activated during EOSCTA stress testing as a workaround for minimising the impact of EOS request type handling imbalance - EOS does not provide fairsharing of different EOS request types (e.g. prepare vs archive requests).
  • For every file in a prepare request, fsctl is triggererd synchronously. The rate limiter may cause some of these to fail which in turn results in a fraction of the multi-file prepare requests to not work.
  • How is the client interpreting it - needs follow-up with Andreas/Elvin (after the meeting, cf attached mail)