Hi,
It's also possible that the reads are going to the master because
prepared statements are being used. The current version of MaxScale does
not yet support read scaling of prepared statements.
Markus
On 09/03/17 14:12, Chaitanya Cheekate wrote:
Thanks for reply. Right now we are are che
Thanks for reply. Right now we are are checking with commands only.
On Thu, Mar 9, 2017 at 5:34 PM, Guillaume Lefranc
wrote:
> If your application uses transactions, e.g. Java/Hibernate, Python
> connector... it will route to master by default.
>
> -GL
>
> Le jeu. 9 mars 2017 à 18:43, Karthick S
If your application uses transactions, e.g. Java/Hibernate, Python
connector... it will route to master by default.
-GL
Le jeu. 9 mars 2017 à 18:43, Karthick Subramanian <
ksubraman...@paycommerce.com> a écrit :
> Follow these below 3 links (especially 3rd link):
>
>
> https://github.com/mariadb
Follow these below 3 links (especially 3rd link):
https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/Tutorials/MySQL-Replication-Read-Write-Splitting-Tutorial.md
https://github.com/mariadb-corporation/MaxScale/blob/master/Documentation/Routers/ReadWriteSplit.md
https://git
Hi
We have configured maxscale in our environment using the links
http://karlssonondatabases.blogspot.in/2014/02/maxscale-for-rest-of-us-part-1.html,
2, 3 . We have two slaves and one master and the replication between them
is working well. But after configuring read/write split the select queries
5 matches
Mail list logo
