Release Notes for MariaDB MaxScale 2.5.27

The Cache Filter (cache) hangs if a statement is split across multiple packets. (MXS-4659)

• In previous releases, if a statement is split across multiple packets, the cache filter will forward the first packet and wait for a server response before sending the following ones, thus causing the session to hang.

• Starting with this release, if a protocol command is split across multiple packets, the subsequent packets are sent forward without waiting for a response.

Setting session_track_trx_state=true when transaction_replay=true and optimistic_trx=true could result in excessive memory consumption and the process being killed by the OOM (out-of-memory) killer. (MXS-4656)

• Starting with this release, when session_track_trx_state is enabled, transaction_replay and optimistic_trx will be disabled.

When unsuccessfully starting a listener, a bad configuration could be persisted on disk. The error message generated by the unsuccessful start is misleading and incorrectly logged in the MaxScale log instead of being captured and sent to the REST API client. (MXS-4665)

• Starting with this release, the following message is sent to the REST API client:

  Listener 'NAME' was created but failed to start it.
  

REST API 404 errors do not provide enough information about the cause of a problem. (MXS-4657)

• Added a clarification to the MaxCtrl error message whenever an HTTP 404 response is given. Since the endpoints themselves should always be correct, the only thing that can go wrong is the object name or type.

• The new error message is:

  Check that the object exists and that it is of the correct type.