Anchor
2.4 2.4

Changes in 2.4 2069290

Tractor 2.4 is an update focused on overall performance, and handling large scale farm size, job size, and number of concurrently connected user sessions. Changes include:

• A significant code refactoring effort addressed several internal thread contention bottlenecks, including those related

  A fairly invasive refactoring effort, simplification, and mutex contention changes to address several bottlenecks, especially with regards

  to frequent password checks and identity management. The new logic results in improved throughput, especially on very large farms (5000+ blades) where many dashboard sessions and automated scripts (1000+) are accessing job status.

• A more robust job-global system for sorting newly ready commands produced by "expand" tasks. This change addresses the "Cmd not Ready?" error problem - which was due to sorting key collisions (precision) on large recursively expanded jobs.
• Optimization of some "inner loop" Optimized limit checking operations, especially around repeated tokenization, trace message construction, and efficient handling of limits that are currently preventing new dispatches because they are at their max valueat their maximum capacity that temporarily throttle new dispatching.
• Addition of a new "connecting" entry in the queue/backlog diagnostic (the "status&qlen=1" query). This count just gives distinct visibility to the number of connected but incomplete inbound RESTful requests that are incomplete, those still awaiting network i/o for their complete http request body contents, they are "connected but incomplete, not yet dispatched into the engine modules for processing.".

• The number handler threads for running custom menu item backend scripts now scales up along with other thread pools based on tractor.config settings.

• Fix for a string handling bug issue that could sometimes result in intermittent loss of access to task log output.

• Fix for a tractor-engine crash during error message construction in response to unparseable (control) characters in "expand task" job graph extensions.
• Fixed Dashboard custom job filter matching on array types such as job Project names. Previously only exact matches were working for these entries, but not "starts with" or "contains" comparisons.
• Updated command-line options for the tractor-spool job submission utility. Several new formatting options such as zero padding are now supported on "range" values used to construct new jobs directly from command line parameters (as distinct from submitting previously constructed complete job files).
• Fixed a problem with "tractor-spool --ribs *.rib" wildcard expansion handling on Windows.

• Fixed mismatched version strings in some of the system service start up scriptsAdded some additional execution handler threads for running custom menu item backend scripts. The number of threads now scales up along with other thread pools based on configuration settings.

Anchor
2.3 2.3

Changes in 2.3 1923604

• Updated environment handlers and paths to accommodate batch processing of RenderMan 22 scenes from Maya and Katana.
• Addressed a Dashboard selection and copy issue related to a change of Firefox webkit css settings.
• Updated Dashboard links to the newest Tractor documentation.
• Address path separator issue on Windows in the Python Job Authoring module.
• Address a task state transition race condition in some "expand chunk" use cases.
• Fixed full job restart pruning of previously expanded tasks that were created by the "expand chunk" mechanism.
• Addressed potential security issues related to malicious interface use by on-site Tractor users.

Anchor
2.2 2.2

Upgrading to 2.2

• NOTE: Upgrading to Tractor 2.2 is "permanent" in the sense that you cannot revert to an older tractor-engine while also retaining your old jobs once the 2.2 job database upgrade has been performed. If you BACKUP your current job database before installing 2.2, then it is possible to revert to the older engine version along with jobs restored to their state at the time of the backup. Please refer to the guidelines described in Upgrading.
• Upgrading to 2.2
• Upgrading to 2.1
• Upgrading from 1.x