[MXS-2730] Connection attributes are not passed on Created: 2019-10-23  Updated: 2020-08-25  Resolved: 2019-12-10

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbbackend
Affects Version/s: 2.3.12, 2.4.2
Fix Version/s: 2.5.0

Type: Bug Priority: Minor
Reporter: Hartmut Holzgraefe Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-96

 Description   

When connecting through maxscale custom connection attributes are not passed through.

When e.g. connecting directly with the command line client, we can see the following connection attributes being set by the client:

SELECT * 
  FROM performance_schema.session_connect_attrs 
 WHERE processlist_id = connection_id();
 
+----------------+-----------------+------------+------------------+
| PROCESSLIST_ID | ATTR_NAME       | ATTR_VALUE | ORDINAL_POSITION |
+----------------+-----------------+------------+------------------+
|             13 | _os             | Linux      |                0 |
|             13 | _client_name    | libmariadb |                1 |
|             13 | _pid            | 1889       |                2 |
|             13 | _client_version | 3.0.10     |                3 |
|             13 | _platform       | x86_64     |                4 |
|             13 | program_name    | mysql      |                5 |
|             13 | _server_host    | node-1     |                6 |
+----------------+-----------------+------------+------------------+

When connecting through maxscale, none of the connections attributes are visible in the PERFORMANCE_SCHEMA.SESSION_CONNECT_ATTRS table ...

See also:

https://mariadb.com/kb/en/library/mysql_optionsv/#connection-attribute-options

https://mariadb.com/kb/en/library/performance-schema-session_connect_attrs-table/



 Comments   
Comment by markus makela [ 2019-12-10 ]

MaxScale now passes the client attributes through to the backends.

Generated at Thu Feb 08 04:16:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.