We're pleased to announce the coming availability of Senate Matching Release 1.5.0 (August 2019). This release is focused on performance and operations improvements to the Senate Matching networks in Australia, Singapore and the USA.

Release 1.5.0 includes changes to how the Matcher Nodes organise their data storage. This is being done to improve performance times for uploading and matching data. 

Here's what you need to know:

Performance and security enhancements

  • We've upgraded our centralised logging for improved monitoring and security information and event management.
  • The Matcher Nodes can now load data faster and from multiple simultaneous contributors. You should expect 1M records to load in around 2 minutes, or 10M records to load in just over 20 minutes.
  • Matching speed has also improved. Large customers running matching projects with 10-20M records can expect match job results to be available in 2-3 hours.

Bug fixes and cosmetic changes

  • When the Contributor Node was put in HTTP/1 Compatibility Mode it ignored the proxy settings in the environment. This has been fixed.
  • Deleting tokens in your Contributor Node now updates the token count visible in the UI.
  • The Contributor Node UI is now sporting the new Data Republic brand. Now we match the look and feel of Senate!

Here's what you need to do:

Customers who upgraded to the June 2019 Contributor Node (1.4.0, 1.4.1) may want to upgrade to the latest version of 1.5.0. Users on older releases are strongly encouraged to upgrade to the new release.

To upgrade your Contributor Node, follow these steps:

Shutdown your current Contributor Node

To stop your currently running node, use the command contributor.sh down which will cleanly shutdown the Docker container.

$ sudo bash contributor.sh down

Update your start up script

Attached to these release notes is a new version of contributor.sh. Download and save this file in your environment.Edit your configuration settings

In your contributor.sh file you may want to change some of the settings from their default value. In particular, you should check:

  • API key / password (set HITCH_BASICAUTHPASSWORD)
  • HTTP proxy settings (use HTTPS_PROXY)
  • If your node has had trouble communicating with Matcher nodes due to issues with HTTP/2 support set HITCH_HTTP1COMPATIBILITYMODE to "true"

Restart your Contributor Node

Start your Contributor Node with the contributor.sh up command. The script will download the latest version of the node software (assuming you installed the new version). Your data will be preserved during the update. The "-d" option starts the Docker containers in the background.

$ sudo bash contributor.sh up -d

That's it! Grab some test data and try it out!

FAQ

Do I HAVE to update?

DR recommends all customers update to this latest version of the Contributor Node. The update is not urgent however (there are no known security issues in the previous release).

Where do I get contributor.sh from?

The email containing these release notes should have the required files attached. Contact Customer Success if there are any issues.

Did this answer your question?