ProxySQL - SQL queries with large datasets (1m+ rows) stop in different rows while executed, direct DB Access works fine
Budget: $250 – $750 USD
We are running a local talend to start SQL queries via our ProxySQL in AWS to the DB. The DB is outside AWS. All queries are routed through the proxysql.
When we run the queries directly to the DB all goes smoothly.
When we run it through the proxysql the session stays active but no rows are received at some point (700.000 rows or 900.000 rows or 450.000 rows).
Same behavior with stopping datatransfer also happens with the mysql workbench when routing via the proxysql.
We need a ProxySQL Specialist to fix it.
current Setup:
ProxySQL rev. 2.2.1-39-g837a720
MySQL 5.6.48-log
When we run the queries directly to the DB all goes smoothly.
When we run it through the proxysql the session stays active but no rows are received at some point (700.000 rows or 900.000 rows or 450.000 rows).
Same behavior with stopping datatransfer also happens with the mysql workbench when routing via the proxysql.
We need a ProxySQL Specialist to fix it.
current Setup:
ProxySQL rev. 2.2.1-39-g837a720
MySQL 5.6.48-log