0.147.0

Important

With version 0.147.0, routing-release now requires configuration of a relational database for Routing API.

If you are upgrading from a version between 0.141.0 and 0.146.0, and are using etcd for the datastore, you may migrate to a relational database by configuring routing_api.sqldb in the same deploy as your upgrade.

If you are upgrading from a version before 0.141.0, you must first upgrade to a version between 0.141.0 and 0.146.0, inclusive, while keeping etcd as the datastore. Then, with a subsequent deploy you may migrate to a relational database by configuring routing_api.sqldb in the same deploy an upgrade to this or a newer version.

For additional information, see our deployment instructions:

• Deployment Prerequisites - Warning
• Migrating from etcd

Note: If your strategy for enabling TLS in etcd involves destroying the etcd cluster, TCP Routing will fail. Before configuring etcd to require TLS or destroying etcd, migrate Routing API to use a relational database as described above.

Release Highlights

• Routing API now requires a relational database; migrations from etcd are still supported details
• Default for router.drain_wait is now 20 seconds details
• When router.max_idle_connections is greater than 0 (keepalive connections enabled), gorouter will retry a backend when an idle connection is severed by the server details

Performance Comparison

Performance comparison of 0.146.0 vs 0.147.0 can be found in the attachment below. Raw results for the performance tests can be found in the following files:

• perfResults 0.147.0
• cpuStats 0.147.0

Manifest Property Changes

gorouter

Default for router.drain_wait is now 20.