Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascade ProxySQL and Charset #1019

Open
stangred opened this issue May 12, 2017 · 10 comments
Open

Cascade ProxySQL and Charset #1019

stangred opened this issue May 12, 2017 · 10 comments

Comments

@stangred
Copy link

Im not sure if this is a bug, but i have configuration:

App -> ProxySQL -> ProxySQL -> DB

Right now when application send query "set names to utf-8" only ProxySQL1 will change this, ProxySQL2 is still working on latin1. I know that this query is not sent to a backend, but tracked internally on ProxySQL1. Maybe it will be good to add some variable that will change this and will force ProxySQL to sent query also to a backend ?

@renecannao
Copy link
Contributor

Hi.
When the App sends "SET NAMES utf8", ProxySQL2 doesn't get that.
But when the App sends a query, the charset should be changed all the way down from ProxySQL1 to ProxySQL2 and then DB.
Is that the case?

@stangred
Copy link
Author

Yes, exactly...

@renecannao
Copy link
Contributor

Ok, so if charset is changed all the way down when a query is executed, that is working ok.
Think what happens if you don't have just 2 proxies (and I guess you have more), ProxySQL1 have ProxySQL2 and ProxySQL3 as backends, and ProxySQL1 sends traffic to either ProxySQL2 or ProxySQL3 based on certain query rules.
It is expected that the charset on 2nd layer of proxy (ProxySQL2 or ProxySQL3) is changed when a query is routed to the right backend.
Does it make sense?

@stangred
Copy link
Author

Yes, behind ProxySQL1 i have two ProxySQL, something like this:
---ProxySQL2
ProxySQL1 --<
--- ProxySQL3

With mysql-multiplexing='true', charset is working randomly.

@renecannao
Copy link
Contributor

@stangred : can you please describe your setup and the result you get with further details, so that I will try to reproduce it?

Thanks

@stangred
Copy link
Author

stangred commented May 13, 2017

Yes, this is current configuration:

WK01 - WK03 - servers http with proxysql on localhost.
DB1 - DB2 - Mysql Cluster SQL Nodes
DB5 - Mysql Replication from DB1
DB6 - Mysql Replication from DB2

Problem is when mysql-multiplexing is true, then charset is working randomly.

test

@renecannao
Copy link
Contributor

@stangred : a lot of improvements were implemented since when this issue was created.
Is the issue still relevant?

@stangred
Copy link
Author

stangred commented Oct 1, 2019

@renecannao We will try to test this configuration one more time, thank you

@renecannao
Copy link
Contributor

Please wait for 2.0.7

@dyipon
Copy link

dyipon commented Oct 1, 2019

I have the same issue with "SET NAMES utf8" command, with an easier infrastructure:
one proxysql server, with 5 backends (mysql 5.7). 2 weeks before I migrated to proxysql2. From this time, I have issue with hungarian accents. (Our legacy app using PHP 5.6, and every mysql connect we have to use 'SET NAMES UTF8'). A few times this utf8 command does not apply (in 1:~50.000).
Maybe our isssue is related to that? Maybe 2.0.7 will fix it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants