|
From: Peter S. <pe...@bs...> - 2017-12-05 01:01:24
|
Hello All, Metpx-sarracenia release 2.17.12a1 is now available. The package is available from all our usual distribution locations: https://sourceforge.net/projects/metpx/files/sarracenia https://launchpad.net/~ssc-hpc-chp-spc/+archive/ubuntu/metpx https://pypi.python.org/pypi/MetPX-sarracenia Changelog: http://metpx.sourceforge.net/CHANGES.html Upgrade Notes: https://sourceforge.net/p/metpx/sarracenia/ci/master/tree/doc/UPGRADING.rst The major focus of the last few weeks has been improving reliability. Enhanced reliability should come from three main features: -- timeouts: all remote operations now have associated timeouts, and then attempt to re-connect. -- pulse: brokers now have a separate queue to keep idle connections alive transparently using a pulse message sent periodically. -- retry_queue: instead of attempting to send X times (where X is set by "attempts"), the transfer is set aside to a .retry file. This automates use of the save/restore logic, so no analyst intervention is needed. When there are no messages to send, the subscriber or sender will pick a message from the retry queue and try to send it. So the senders should be able to transparently recover from even prolonged outages. The old behaviour can be restored via *retry off* setting in the configuration file. There is one change in interpretation of configuration files compared to previous versions: When an sr_subscribe or an sr_sender has no accept/reject clauses, then previous versions would send everything. The new version sends nothing. To have it send everything, as before, append to the config file: accept_unmatch Aside from the above, there are also several bugfixes made since 11a3 (SENDER=, and "Sends:" in particular.) |