Author Topic: PipelineFX Qube 6.3.1 Core/Supervisor/Worker maintenance release is available  (Read 2335 times)

jburk

  • Administrator
  • *****
  • Posts: 484
A new 6.3.1 maintenance release is now available for the Qube 6.3 Core/Supervisor/Worker. This is a recommended release for all customers running Qube v6.3.

Below is a list of the fixes and enhancements since the last point-release.

================================================
@RELEASE: 6.3.1

@NEW: Add CentOS/RHEL 6 x64 support

==== CL 9150 ====
@INTERNAL: QbDebug::filename(QbString) took if statement out, so resetting _filename is allowed

==== CL 9145 ====
@FIX: disabled logging to /var/spool/qube/{host,user}, as it was creating large log files and causing sluggish performance.

An option to enable these logs may be made available in the future.

==== CL 9142 ====
@FIX: fixed issue where global resources tracking drift sand more subjobs than can be accomodated by the actual global resource count is dispatched.

ZD: 5074

==== CL 9133 ====
@INTERNAL: CentOS support for "buildpyc" in rpm/quberpm.pm

==== CL 9105 ====
@NEW: A new transitional "dying" state for jobs that have been ordered to be "killed", but still being processed by the system

==== CL 9085 ====
@INTEG: main -> rel-6.[0,1,2,3]  CL 9083, 9084
-----
@CHANGE: increase MySQL wait_timeout value from default of 8 hours to 36 hours to decrease frequency of "MySQL server has gone away (2006)" error messages.
@CHANGE: increase MySQL max_allowed_packet value from default of 1MB to 64MB to decrease frequency of "MySQL server has gone away (2006)" error messages.

==== CL 9066 ====
@FIX: fixed "cpus" (subjob) count inaccuracy when a job's "cpus" was modifed down and then up.

For example, if a job with initially 10 "cpus" was reduced to 5, then
subsequently increased to 6, the system had inaccurately recomputed the
subjob count to be 10.

==== CL 9058 ====
@FIX: renaming logs during rotation would fail on Windows

==== CL 8939 ====
@FIX: fixed another small "hole" that could cause race-conditions to dispatch a single subjob more than once

ZD: 4783
BUGZID: 63657

==== CL 8937 ====
@FIX: supe issue where the same subjob can be dispatched more than once to worker(s).

ZD: 4783
BUGZID: 63657