java.util.concurrent.TimeoutException on MySQL source

Hi!

After a change in internal IP used to connect to MySQL source (runs on AWS) we are seeing this error:

java.util.concurrent.TimeoutException: Waited 80 seconds (plus 86797 nanoseconds delay) for SettableFuture@57294610[status=PENDING]

This only happens on some tables, generally larger ones. For other tables, connection works fine. Simple Google search suggests clearing the cache.

Any help would be appreciated!

For anyone else with this issue - this is specific to MySQL 8. The workaround is to use EXTERNAL_QUERY capabilities in Dremio and to specify at least one WHERE condition in the external query:

SELECT 
*
FROM   
TABLE (source_name.EXTERNAL_QUERY('SELECT  * FROM db.table WHERE id > 0))

@klemens Just to understand the issue clearly, the SQL failed with timeoutexception but adding a dummy WHERE clause it was successful?

Any chance you can share both the profiles? Failed without WHERE and successful with WHERE

Hi @klemens As this is being investigated on Dremio Cloud chat and currently under investigation by our engineering team if this is a release specific issue or mysql version8 specific. To avoid duplication, further we will also share the details on this Thread.

1 Like

I’ve recently added a MySQL 8 source to our dremio account and experienced the same issue outline around feb 2024 - any further insight here would be greatly appreciated. (The external query works but we would prefer avoiding this workaround if possible)

@nate-mm can you please add the job profile to see the error stack?

No profile b/c this is the first time we are trying to configure a table setting on a mysql source table.

same error message shows when clicking on reflections and reflection refresh sections

@nate-mm Does this happen on all tables? or tables with wide columns? or lots of rows? Can you please send the server.log from the coordinator when this issue happened?

We’re experiencing this on Dremio Cloud so no server.log for us to share.

Data itself was a large number of rows and 55columns wide. Issue only happens on some tables but row count doesnt seem to be directly coorelated with the issue.

@nate-mm I see an issue related to this, want to check if the trace is the same. Can you please add the job profile

ALternatively, send a DM to me with your org id and I can pull it down

@balaji.ramaswamy - I’m seeing similar issues with Dremio Cloud connecting to Redshift.