Hi All,
finally I can now proudly announce the 2.7 release of schedulix to be the latest stable release.
To check it out from github, you do a
git clone https://github.com/schedulix/schedulix.git -b v2.7 schedulix-2.7this will create a new directory called schedulix-2.7 with the current v2.7 sources. Subsequent pulls will keep the sandbox up to date.
To upgrade from 2.6.1 to 2.7, do the following:
- shut down the installation (i.e. the schedulix server and any jobservers running at the same node)
- make a database backup
- execute the generated-upgrade-2.6.1-to-2.7.sql; This file is found in the sql/dbms_gen directory (dbms \in {ing, pg, mysql})
- now copy the 2.7 tree next to the 2.6.1 tree
- let the schedulix symbolic link point to the new schedulix-2.7 (rm && ln)
- start the scheduling server with "server-start -protected" which disables internal threads as well as "normal" user logins
- connect as SYSTEM and inspect the system
- shut down the server and start up normally
As always, it is a good idea to understand the above steps. It is only a rough recipe and might need some adaptations to match your setup.
The database backup allows you to downgrade to the 2.6.1 version again. BUT beware, the backup is not aware of newly submitted jobs or jobs that are reported to be finished..
And of course, we're here to help :-)
The change between 2.6.1 and 2.7 that caused the most work is the implementation of multiple writers.
Because of the ease of producing bugs in concurrent environments, we still regard the feature as experimental. But any of you is heartily invited to test it.
(You'll have to set the property
WriterThreads in the
server.conf file to some reasonable value greater than 1; we tested with up to 10 parallel writer threads).
Other new features include
- JSON renderer
- Rerun triggers restart broken finished jobs
- 'sdmsctl test' reads the server configuration and tries to connect to the database. If this is successful, the server will start without problems.
- Improved filter management
- Jobs can export parameters to their environment
- Broken State is allowed to be a final state
- Local suspend doesn't suspend the children of a batch or job
- SHOW SYSTEM WITH LOCKS; shows the locks in the system (only interesting if working with multiple writer threads)
- Job On Ice (comment out a job) -- this was actually a feature request from one of you
- Enhanced comments
Have fun!
Regards,
Ronald