Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
MXS-SPRINT-166
Description
There are good reasons to have different settings for various timeouts like:
- max_statement_time
- wait_timeout
- lock_wait_timeout
- innodb_lock_wait_timeout
- etc
for primary/master server vs slave/replica. When failover happens these settings should be changed and assuming Maxscale does and controls failover process, it should get options to do this. I mean separate settings for "primary" and "replica" timeouts or maybe any/all global variables to enforce on a node that switches to that status.
Attachments
Activity
This should already be possible using the promotion and demotion SQL files: https://mariadb.com/kb/en/mariadb-maxscale-25-mariadb-monitor/#promotion_sql_file-and-demotion_sql_file
valerii do you think this would be adequate or would some more refined behavior be required?
Yes, for any global dynamic variables these files seem to provide a way to solve the problem. But I'd appreciate some clear examples on how to use them to set timeouts in the KB and/or Enterprise documentation.
Could you give some example values that one would use with the given variables you had? We can then add these as examples into the documentation for these parameters.
Changing this to a New Feature since that's what it is.