FTS 3.3.X

Posted by FTS Team on June 19, 2015 |

FTS3 3.3.2

Bug

  • [FTS-242] - SLS now requires namespaces
  • [FTS-246] - If hostcert.pem and hostkey.pem are owned by fts3, Globus loads them first
  • [FTS-253] - Checksum errors are *not* recoverable
  • [FTS-256] - Proxy expired should be NON recoverable
  • [FTS-257] - If the connection to the broker go away, should be able to recover
  • [FTS-259] - --proxy is only used for REST
  • [FTS-241] - Transfers executed twice when the node pool changes (Reported by ATLAS, affects all previous releases)
  • [FTS-273] - URL Copy sends two messages for the same file if signals are involved (Reported by ATLAS, affects all previous releases)
  • [FTS-331] - Debug should be disabled by default on the monitoring

Improvement

  • [FTS-224] - Log by default if the destination file has been deleted or not
  • [FTS-225] - Generate coredump in addition to the backtrace
  • [FTS-243] - Missing fields in the server configuration view
  • [FTS-258] - Log if the error is considered recoverable or not recoverable
  • [FTS-260] - Messages: Timestamp should have milliseconds resolution
  • [FTS-333] - Web monitoring in a separate wsgi process
  • [FTS-334] - Web Mon: Use MySQLdb.cursors.SSCursor to reduce memory footprint

New Feature

  • [FTS-244] - Allow to specify the FTS3 endpoint via an environment variable
  • [FTS-245] - Use gfal2 functionality to pass some extra information to the storages

Task

  • [FTS-248] - Prepare packaging to reduce dependency with Bamboo

FTS3 REST 3.3.3

Bug

  • [FTS-208] - Reduce memory consumption
  • [FTS-209] - Avoid updates of t_optimize_active on submission
  • [FTS-212] - In credentials.py, we are binding from a dicitonary without copying, which has side effects
  • [FTS-261] - REST Client: Context seems to be leaking (Reported by LHCb, affect all previous releases)
  • [FTS-265] - When polling multiple jobs with file fields at once, inner fields are duplicated between jobs (Reported by ATLAS, affects only 3.3.0)
  • [FTS-269] - /jobs/<job-id>/files leaks db connections (Found by Andrea Manzi, affects previous versions of 3.3)
  • [FTS-270] - IntegrityError on submission when another job inserted the same storage pair in t_optimizer_active (Reported by ATLAS, affects latest 3.2.x)

Improvement

  • [FTS-205] - Allow specifying the priority on submission time
  • [FTS-207] - Improve performance of job listing
  • [FTS-210] - Improve OAuth2 granularity
  • [FTS-211] - Allow time_window to be in minutes as well
  • [FTS-214] - Select the first best replica at submission time via REST
  • [FTS-215] - Forbid submission of multiple replica combined with other types of jobs
  • [FTS-216] - Re-factorize a bit, paying attention to SonarQube output
  • [FTS-222] - Try to reduce job submission latency
  • [FTS-223] - Validate version as part of the packaging

New Feature

  • [FTS-183] - Web interface to use the REST configuration API
  • [FTS-203] - Requested: Allow to specify only a subset of the job's fields
  • [FTS-204] - Add support for urn:ietf:wg:oauth:2.0:oob
  • [FTS-217] - Allow to cancel a single (or set of) file within a job
  • [FTS-218] - Expose if an error is recoverable or not recoverable via REST API
  • [FTS-219] - max_time_in_queue is missing in REST

Task

  • [FTS-248] - Prepare packaging to reduce dependency with Bamboo