Timeline for MariaDB Maxscale caching not working
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2022 at 9:20 | comment | added | Suraj | thank you very much. I had missed to add the filter. Now it is working as expected. | |
| Feb 1, 2022 at 9:19 | vote | accept | Suraj | ||
| Jan 31, 2022 at 17:22 | comment | added | markusjm |
I think I realized why it wasn't working: you didn't add filters=Cache to the service definition. I've updated the answer with the real reason why it works.
|
|
| Jan 31, 2022 at 17:19 | history | edited | markusjm | CC BY-SA 4.0 |
Realized why it wasn't working.
|
| Jan 31, 2022 at 16:01 | comment | added | Suraj | I enabled the log and have also attached the log image in the question. | |
| Jan 31, 2022 at 13:07 | comment | added | markusjm |
You might want to add log_info=true under the [maxscale] section in maxscale.cnf to see how the query routing is done. You should be able to see when caching is used and when it isn't. Note that only queries that are identical can be cached: if you use something like sysbench which generates unique queries, the caching rate will be slower.
|
|
| Jan 30, 2022 at 12:43 | comment | added | Suraj | I tried with the suggested configuration changes but still there is not much change. When I am using 100 concurrency I can see 50 connections in each of 2 nodes and 1 node is not receiving any. Also I assume that if it takes for example 7 secs for 100 concurrency then subsequent queries should take much less as they are cached but I do not see that. Is there are anything I am missing. | |
| Jan 18, 2022 at 8:28 | history | answered | markusjm | CC BY-SA 4.0 |